I have had my Fedora 5 computer off for a few days and I just went to turn it on and it said something to the lines of /dev/hdb1 bad superblock run fsck with alternative boot block etc etc...

Well, I use LVM2 for my system drive. That is the default way that I stupidly let the fedora installer set up. So there was no question that my superblock was bad, but they way it told me to fix it was bs.

So here's what I did so far,

e2fsck -f -y -b 32678 /dev/LogGroup00/LogVol00

It repaired all the files on the drive, i'm able to mount it as a lvm2 drive in knoppix now, But the damn thing is giving the exact same error and still not allowing the system to boot. It just dumps me to a low-level read-only operating system,Repair Filesystem 1# etc.... Any help would be appreciated.

I have had this experience in the past when I ran e2fsck against a different partition than the one which had the problem. Are you sure that /dev/hdb1 and /dev/LogGroup00/LogVol00 are the same thing? You could try booting a live CD and use e2fsck to repair /dev/hdb1.

--------------------
Steve Stites

/dev/hdb1 doesn't exist. When it was mounted, /dev/hda1 was boot and /dev/hda2 was the system partition. That's why i'm so lost. I don't know where /dev/hdb2 came from or why it isn't allowing my system to boot because of a non existent bad superblock on a non existent partition. Grub is still configured to boot the system from /dev/LogGroup00/LogVol00. No hdb in there anywhere. I need to know how to remove any thought of my os looking for the non existent hdb.