Look bad again! Try to get a backup of the superblock for the file system check. Here you get the list of superblocks Code: sudo gainroot dumpe2fs /dev/mmcblk0p2 | grep -i superblock You get an output like this:Then check the file system with one of the backups again like this Code: fsck -b 294912 -af /dev/mmcblk0p2 Hope it helps!
sudo gainroot dumpe2fs /dev/mmcblk0p2 | grep -i superblock
fsck -b 294912 -af /dev/mmcblk0p2
BusyBox v1.10.2 (Debian 3:1.10.2.legal-1osso30+0m5) built-in shell (ash) Enter 'help' for a list of built-in commands. ~ $ ~ $ sudo gainroot Root shell enabled BusyBox v1.10.2 (Debian 3:1.10.2.legal-1osso30+0m5) built-in shell (ash) Enter 'help' for a list of built-in commands. /home/user # 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 Backup superblock at 1605632, Group descriptors at 1605633-1605633 /home/user # /home/user # /home/user # fsck -b 294912 -af /dev/mmcblk0p2 fsck 1.41.3.maemo0 (12-Oct-2008) /dev/mmcblk0p2: ext3 recovery flag is clear, but journal has data. /dev/mmcblk0p2: Recovery flag not set in backup superblock, so running journal anyway. /dev/mmcblk0p2: recovering journal /dev/mmcblk0p2: ext3 recovery flag is clear, but journal has data. /dev/mmcblk0p2: Recovery flag not set in backup superblock, so running journal anyway. fsck.ext3: unable to set superblock flags on /dev/mmcblk0p2 /home/user #