Try to check the file system with a badblocks test first then repair with more force Code: fsck.ext3 -c -y /dev/mmcblk0p2 fsck.ext3 -r -f -y /dev/mmcblk0p2
fsck.ext3 -c -y /dev/mmcblk0p2 fsck.ext3 -r -f -y /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 # fsck.ext3 -c -y /dev/mmcblk0p2 e2fsck 1.41.3.maemo0 (12-Oct-2008) /dev/mmcblk0p2: recovering journal fsck.ext3: unable to set superblock flags on /dev/mmcblk0p2 /home/user # fsck.ext3 -r -f /dev/mmcblk0p e2fsck 1.41.3.maemo0 (12-Oct-2008) fsck.ext3: No such file or directory while trying to open /dev/mmcblk0p The superblock could not be read or does not describe a correct ext2 filesystem. If the device is valid and it really contains an ext2 filesystem (and not swap or ufs or something else), then the superblock is corrupt, and you might try running e2fsck with an alternate superblock: e2fsck -b 8193 <device> /home/user #