Thread: Trying to resurrect dead Nokia N9
View Single Post
jdb2 is offline jdb2
2019-03-03 , 16:49
Posts: 51 | Thanked: 63 times | Joined on Jun 2010 @ Klein/Spring, Texas, USA
#8
Originally Posted by juiceme View Post
You are correct about ubiboot not charging the device. That's a problem I could not overcame at that time; there was a lot we did not know about the device and charging logic was one of the things I was unfamiliar with.

By the time I knew how to do that things had moved forward and N9 was fading into obsolency...
Thanks for your reply It seems that the N9 rescue initrd and kernel doesn't run or enable the charging code either. I say this because I had used it yesterday to export my N9's partitions in the hopes that I might get a successful dd copy of my 64GiB eMMC and that the rescue kernel would enable the charging code. Well, yesterday, I had to charge the N9 just past 10% and then I let it trickle charge for about an hour. When I plugged it into the wall charger, that same boot-loop with the warning screen was displayed. This, however, didn't stop me from loading the N9 rescue kernel and initrd. I would have backed up all my data, but, I forgot to tell pv not to abort on read or I/O errors and by the time I checked back on the N9, it had discharged its battery again.

Right now, there seems to be some slight, but fixable, corruption in the rootfs partition. dumpe2fs shows that the filesystem on the partition is mostly healthy, save for a few errors. When I try to mount it I either get errors such as "stale file handle" or "missing/corrupt root inode". If the superblock is corrupt, then I have several backups in the filesystem, which I hope bodes well for recovering the rootfs.

Running dumpe2fs on the rootfs partition shows :

Code:
$ sudo dumpe2fs /dev/sdg2 | grep -i backup
dumpe2fs 1.44.1 (24-Mar-2018)
Journal backup:           inode blocks
  Backup superblock at 32768, Group descriptors at 32769-32769
  Backup superblock at 98304, Group descriptors at 98305-98305
  Backup superblock at 163840, Group descriptors at 163841-163841
  Backup superblock at 229376, Group descriptors at 229377-229377
  Backup superblock at 294912, Group descriptors at 294913-294913
  Backup superblock at 819200, Group descriptors at 819201-819201
  Backup superblock at 884736, Group descriptors at 884737-884737
Code:
$ sudo dumpe2fs -h /dev/sdg2 | grep -i super
dumpe2fs 1.44.1 (24-Mar-2018)
Filesystem features:      has_journal ext_attr resize_inode dir_index filetype extent flex_bg sparse_super large_file huge_file uninit_bg dir_nlink extra_isize
Code:
$ sudo dumpe2fs -h /dev/sdg2
dumpe2fs 1.44.1 (24-Mar-2018)
Filesystem volume name:   rootfs
Last mounted on:          /
Filesystem UUID:          4127add5-d4f3-48d1-abdf-f4cf6a99b0f6
Filesystem magic number:  0xEF53
Filesystem revision #:    1 (dynamic)
Filesystem features:      has_journal ext_attr resize_inode dir_index filetype extent flex_bg sparse_super large_file huge_file uninit_bg dir_nlink extra_isize
Filesystem flags:         signed_directory_hash test_filesystem 
Default mount options:    (none)
Filesystem state:         clean with errors
Errors behavior:          Continue
Filesystem OS type:       Linux
Inode count:              262144
Block count:              1048576
Reserved block count:     52428
Free blocks:              407449
Free inodes:              194775
First block:              0
Block size:               4096
Fragment size:            4096
Reserved GDT blocks:      255
Blocks per group:         32768
Fragments per group:      32768
Inodes per group:         8192
Inode blocks per group:   512
RAID stripe width:        8
Flex block group size:    16
Filesystem created:       Wed Feb 29 04:21:42 2012
Last mount time:          Wed Dec 31 18:00:01 1969
Last write time:          Wed Dec 31 18:00:07 1969
Mount count:              320
Maximum mount count:      32
Last checked:             Wed Feb 29 04:21:42 2012
Check interval:           15552000 (6 months)
Next check after:         Mon Aug 27 05:21:42 2012
Lifetime writes:          96 GB
Reserved blocks uid:      0 (user root)
Reserved blocks gid:      0 (group root)
First inode:              11
Inode size:	          256
Required extra isize:     28
Desired extra isize:      28
Journal inode:            8
Default directory hash:   half_md4
Directory Hash Seed:      79f02ced-f80d-4173-85c1-f7601c5bc4f7
Journal backup:           inode blocks
Journal features:         journal_incompat_revoke
Journal size:             8M
Journal length:           2048
Journal sequence:         0x001a9f8f
Journal start:            0
Notice the "Lifetime writes: 96 GB" field. I think that the flash is corrupt due to normal flash wear caused by too much writing, but, once I recover the partitions, I should be able to mark the bad blocks without having to swap out the mainboard or eMMC chip.

Here is a link to the full dumpe2fs output :

http://www.mediafire.com/file/36gj9v...log-4.zip/file

I'm hoping that if I can recover most of the sectors from the eMMC with ddrescue then I'll be able to fix the fs corruption errors and/or restore the superblock. I can then wipe the eMMC using the flasher tool and then mark bad blocks and then, hopefully, copy all the partitions back.

Any opinions or advice as to the rootfs fs corruption issue would be appreciated

All I need to do now is charge the N9 with the flasher tool again, then let it trickle charge for about an hour and then run ddrescue after having booted into Ubiboot

Thanks,

jdb2
 

The Following 5 Users Say Thank You to jdb2 For This Useful Post: