I have a serious problem with what seems to be a superblock corruption on /dev/hda3. When running fsck, it bails out with the following error:
e2fsck 1.18, 11-Nov-1999 for EXT2 FS 0.5b, 95/08/09 Couldn't find ext2 superblock, trying backup blocks... fsck.ext2: Attempt to read block from filesystem resulted in short read while trying to open /dev/hda3 Could this be a zero-length partition? Any attempt to mount the partition fails. Now the delicate aspect of this is that /boot sits on hda3 and that lilo resides on hda3 as well... Nevertheless, I can boot the system just fine with no lilo problems at all, but unfortunately this is all I can do. The cause that comes to mind is the following: I accidentally sent hda into sleep mode with hdparm -Y while hda3 was mounted as /boot (it's the only ext2 partition on hda and it is usually not mounted at all, unless I install a new kernel). While rebooting, I was confronted (in the shutdown sequence) with a bunch of IRQ timeout messages from the kernel, but it eventually managed to reset the drive, so that I could hear it spin up again, /boot was unmounted, and the system rebooted. But whenever I boot now, fsck wants to send me into single user mode. I have no idea what is going on here. How do you fix a corrupt superblock? What excately IS a superblock, anyway? This is scary, because I can't afford to loose or even reinstall this box at the moment. Any help will be very much appreciated... -- Philipp Lehman <[EMAIL PROTECTED]>
