http://ext4.wiki.kernel.org/index.php/E ... ing_Debian
Of course, this was from lenny (hence the -dev). The partition was fine, and I mounted it numerous times. I also performed a dist-upgrade to squeeze. I shutdown that computer with the usual 'shutdown -h now' and disconnected the AC power cord from it, because I wasn't planning on using that machine for awhile. As far as I could determine, everything was fine before I unplugged it.
Every time that computer is powered off, the clock resets to 1999 because the battery is bad. So I am used to getting the "last mount time is in the future" error.
Three weeks after halting, I powered the computer back on. It was unplugged until this point. I got an error message when it attempted to mount /dev/sda3
- Code: Select all
e2fsck 1.41.9 (22-Aug-2009)
e2fsck: Superblock invalid, trying backup blocks...
e2fsck: Bad magic number in super-block while trying to open /dev/sda3
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>
I then removed its line from /etc/fstab, rebooted. and tried to check it, but I just keep getting the same error-- even with the '-b 8193' option.
I am confused as to how this happened, since the machine was unplugged the whole time. I also don't exactly know what to do about it. It seems like the error message is generic. I have found a lot of forum posts containing it, but none seem to deal with my situation.
The machine is still using the 2.6.26 kernel from lenny. I am building a new one right now (2.6.30), hoping that the problem is caused by the ext4dev/ext4 module. Otherwise I don't know what to do.