Corrupted superblocks?

We had a power outage, so everything crashed. Most up fine (fsck done auto etc) except one boxen

If boots up okay (hw stuff fine) until it is time to check the partition of hda.
Says no ext3
then says no ext2
cramfs: wrong magic
/sbin/init can not open /dev/console....
Kernel panic.

Basically, how do I fix it?

I have tried manually running fsck/e2fsck but it always complains about bad superblock and yes I've tried alternate superblocks (well a few 8193, 16385,32769.

Are these the correct numbers?
Tried googling for a list of superblock numbers, but no luck
I am assuming that they are n*(4096) +1.

Would really like to be able to recover this users hard disk.

TIA

No votes yet

Comment viewing options

Select your preferred way to display the comments and click "Save settings" to activate your changes.

don't boot from that disk

Use a "Live CD" or better still, temporarily attach that disk to another Linux system to inspect it. If this second system still has trouble making sense of the partitions, you will need to use a file recovery tool.

Syndicate content