Comment 159 for bug 204996

Hey hardyn,
I just tried checking all my disks with fsck (that is what you meant, right?)
and for all my ext3 partitions it said clean. But I decided to try checking the drive itself instead of the partition and for my IDE drive (/dev/sdb) it said

fsck 1.40.8 (13-Mar-2008)
e2fsck 1.40.8 (13-Mar-2008)
fsck.ext2: Superblock invalid, trying backup blocks...
fsck.ext2: Bad magic number in super-block while trying to open /dev/sdb

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>

And why does it say ext2 for all my ext3 partitions?
Also, if my problem is caused by bad sectors on the drive, then shouldn't ubuntu have some way of telling me this? And why would it make it lock up? I thought ubuntu and linux was designed to let you know what the problem is if one does happen. I guess I could report it as a suggestion.

-Invader Amoto