Try "e2fsck -b 32768 /dev/hda1" (or whatever is the bad partition). I don't believe you use fsck on the whole device (such as /dev/hda) but on partitions on that device (such as /dev/hda1 /dev/hda2 etc... which ever is your bad partition). Oh and here is a good quick over:
http://www.linuxcertified.com/recovery.html Hope that helps. -David On Sat, 2002-10-12 at 13:03, Robert Heinich wrote: > I could use some help in recovering my system. > > Upon boot-up, I receive > Error reading block 65710 (attempt to read block from filesystem > resulted in short read) while doing inode scan > > Tried > fsck -y /dev/hda and it reports that > Couldn't find ext2 superblock, trying backup blocks... > fsck.ext2: Bad magic number in super-block while trying to > open /dev/hda > > Tried > fsck -b 8193 /dev/hda > and > fsck -b 16385 /dev/hda > > both report Bad magic number in super-block while trying to > open /dev/hda > > The Win98SE boots ok. > > If some kind soul would call me, I would appreciate it. > > advTHANKSance, > Robert Heinich > (m) 919-247-4489 > (h) 919-382-9668 > e-mail: [EMAIL PROTECTED] > > :--- > IBM ThinkPad T21, PIII 800Mhz, 384MB > Red Hat v7.2 with all patches; kjournald on > with Win4Lin > Win98SE > > > > _______________________________________________ > TriLUG mailing list > http://www.trilug.org/mailman/listinfo/trilug > TriLUG Organizational FAQ: > http://www.trilug.org/~lovelace/faq/TriLUG-faq.html > _______________________________________________ TriLUG mailing list http://www.trilug.org/mailman/listinfo/trilug TriLUG Organizational FAQ: http://www.trilug.org/~lovelace/faq/TriLUG-faq.html
