View Single Post
Posts: 2,102 | Thanked: 1,937 times | Joined on Sep 2008 @ Berlin, Germany
#3
Try fsck with a backup superblock, that might give you a fair chance.
To list the backups of the superblock created during initial make of the file system do:
Code:
sudo gainroot
dumpe2fs /dev/mmcblk0p2 | grep -i superblock
You will receive a table containing your superblocks. They are different than my example:
[1|root@Nokia-N900|~]dumpe2fs /dev/mmcblk0p2 | grep -i superblock
dumpe2fs 1.41.3.maemo0 (12-Oct-2008)
Primary superblock at 0, Group descriptors at 1-1
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
Then pick up one of the superblocks and hand it with the -b option to fsck. From my example it would be
Code:
fsck -b 294912 -af /dev/mmcblk0p2
Hope it get you further on that problematic partition.