I have a Toshiba AC100 computer. It used to have Android installed, but then I installed Ubuntu onto one of the flash drive partitions. Some other partitions from Android remained untouched.
They can be mounted as ext3 without problems in Android, but
fsck.ext3 fails to check them -- https://bugs.launchpad.net/ac100/+bug/1046455:
root@potka:~# umount /dev/mmcblk0p7 root@potka:~# fsck.ext3 /dev/mmcblk0p7 e2fsck 1.42 (29-Nov-2011) fsck.ext3: Superblock invalid, trying backup blocks... fsck.ext3: The ext2 superblock is corrupt при попытке открыть /dev/mmcblk0p7 The superблок could not be read or does not describe a correct ext2 ФС. If the устройство is valid and it really contains an ext2 ФС (and not swap or ufs or something else), then the superблок is corrupt, and you might try running e2fsck with an alternate superблок: e2fsck -b 8193 <устройство> root@potka:~# mount /dev/mmcblk0p7 root@potka:~# dmesg | tail [12523.855878] tegra_dvfs: rate 216000000 too high for dvfs on disp1 [14798.460340] tegra_dvfs: rate 216000000 too high for dvfs on disp1 [25522.814250] ec system event c5 04 01 00 02 00 ...... [27051.782313] ec system event c5 04 01 00 00 00 ...... [27052.067613] tegra_dvfs: rate 216000000 too high for dvfs on disp1 [28435.236168] EXT3-fs: barriers not enabled [28435.238916] kjournald starting. Commit interval 5 seconds [28435.239018] EXT3-fs (mmcblk0p7): warning: maximal mount count reached, running e2fsck is recommended [28435.244047] EXT3-fs (mmcblk0p7): using internal journal [28435.244144] EXT3-fs (mmcblk0p7): mounted filesystem with writeback data mode root@potka:~#
Is this some kind of a well-known problem of e2fsck from Linux?