Linux-kernel mailing list archive 1999-23,: OT: corrupted e2fs super-block

# OT: corrupted e2fs super-block

Tom Tom Tom (dumbkid@wt.net)
Fri, 11 Jun 1999 03:01:31 -0500 (CDT)

- Messages sorted by: [ date ][ thread ][ subject ][ author ]
- Next message: B. James Phillippe: "Re: Strange kernel symbols with genksyms"
- Previous message: Keith Owens: "Strange kernel symbols with genksyms"

Hi all,

I have a mail spool drive w/ corrupted super-block
and don't know how to recovery the data.

During e2fsck on the /dev/sdc1 , it said "bad magic
number in super-block"

I made a mirror drive "dd if=/dev/sdc of=/dev/sdb"
and after I "mke2fs -S /dev/sdb1; e2fsck -y /dev/sdb1"
I can mount the drive and see the content.

However after reboot, the drive (/dev/sdb1) goes back
to "bad magic number in super-block" and after that,
I do "dd if=/dev/sdc of=/dev/sdb" again, and then
do mke2fs -S and e2fsck the partition again. But this
time, I got lots of

"Group xxx's inode bitmap (xxxx) is bad. Relocate? yes"
and after seeing "Bad block 0 used as bad block indirect
block?!?", it loops back to beginning ... and I can never
make it work again.

Tried "e2fsck -b <8192*[1-20]+1> /dev/sdb1" and same "bad
magic number " error.

Any idea on how to recovery the drive? Is there any tools
available to do this?

Thanks in advance.

Regards,
Tom

P.S. System: SMP PII450 - kernel 2.0.36 - adaptec 2940uw

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.rutgers.edu
Please read the FAQ at http://www.tux.org/lkml/

- Next message: B. James Phillippe: "Re: Strange kernel symbols with genksyms"
- Previous message: Keith Owens: "Strange kernel symbols with genksyms"