> On 20030111.1152, Linux Rocks! said ... > > The unable to read superbblock deal is a sucky one, but you can also use an > alternate superblock, fdisk should tell you how to do this... I think its -b > 8192 or something... googleing..... I found this: > fsck -y /dev/hdb1 (if your / is /dev/hdb1) someone claims it cleans your > superblock > I also found this: > if you using 1k block size, your backup superblock should be at 8193, boot to > single user mode and do a >fsck -b 8193 /dev/hdc > fsck -b 8193 /dev/hda (is more likely what you would use...
I'll see what I can do. > Id suggest doing the fsck from your distro's boot disk, toms root-boot might > work just aswell (or heck, got a linux care cd handy?) > then see what fsck tells you. If its your superblock, you should get a > message that tells you (very specific too!) how to setup an altenate > superblock. I did try to boot with the install disk, and go into rescue mode. But rescue mode still wants to mount the root partition, and I get the same error as mentioned in the first e-mail. -Rob _______________________________________________ Eug-LUG mailing list [EMAIL PROTECTED] http://mailman.efn.org/cgi-bin/listinfo/eug-lug
