You can also use 'findsuper' that comes with the e2fs utils pkg. if it
doesn't find a superblock on 0 and 8193, etc, you likely have a screwed up
partition. you'll need to carefully resize/move it until the superblock is
in the right place and a _READONLY_ e2fsck passes. however, an e2fsck won't
be successful if the data has been corrupted but try your e2fsck until it
doesn't complain about the geometry of the partition and the 'findsuper'
grabs a superblock on 0.
-d
On Thu, 20 Jan 2000 tytso@MIT.EDU wrote:
> Date: Thu, 20 Jan 2000 00:30:11 -0500
> From: tytso@MIT.EDU
> To: john@data-source.com
> Cc: linux-kernel@vger.rutgers.edu
> Subject: Re: Recovering from ext2 corruption on an ide drive
>
> Date: Wed, 19 Jan 2000 01:43:55 -0600 (CST)
> From: John <john@data-source.com>
>
> I have some more information regarding this ide filesystem corruption.
> I did not make one point very clear in my first email:
>
> I ran "e2fsck -vyf" only on hda1 and only one time. The other two
> partitions, hda2 and hda5 have not been written to at all.
>
> I have tried all kinds of things to access my data today. I was able to
> set up the old system board that I thought had died and was able to get it
> to boot. I ran an 'e2fsck -vnf' on the partitions, and all three were
> corrupted, with hda1 being the most messed up.
>
> Are you sure that you didn't get your partition table smashed? If
> e2fsck isn't given the proper filesystem boundaries, it's not going to
> do anything useful. That would explain why your hda5 partition is
> smashed:
>
> e2fsck 1.18, 11-Nov-1999 for EXT2 FS 0.5b, 95/08/09
> e2fsck: Bad magic number in super-block while trying to open /dev/hda5
>
> The superblock could not be read or does not describe a correct ext2
> filesystem. If the device is valid and it really contains an ext2
> filesystem (and not swap or ufs or something else), then the superblock
> is corrupt, and you might try running e2fsck with an alternate superblock:
> e2fsck -b 8193 <device>
>
>
> - Ted
>
> -
> 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/
>
-
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/
This archive was generated by hypermail 2b29 : Sun Jan 23 2000 - 21:00:22 EST