From: Christian Ohm <chr.ohm@gmx.net>
To: Theodore Tso <tytso@mit.edu>
Cc: Andreas Dilger <adilger@sun.com>, Christian Ohm <chr.ohm@gmx.net>,
linux-ext4@vger.kernel.org
Subject: Re: How to recover a damaged ext4 file system?
Date: Sat, 7 Feb 2009 17:27:25 +0100 [thread overview]
Message-ID: <20090207162725.GA27086@moongate.localnet> (raw)
In-Reply-To: <20090106193404.GA18957@mit.edu>
On Tuesday, 6 January 2009 at 14:34, Theodore Tso wrote:
> It looks like both the primary and the backup block group descriptors
> are bad. I'm not sure how this happened; normally nothing touches the
> backup block superblocks at all. Stupid question --- are you sure the
> partition table is sane; that's always the first thing to check.
I created a new partition on the second drive, and I hope I used exactly the
same options. The result of fdisk -l is the following:
corrupted drive:
Disk /dev/sde: 1000.2 GB, 1000204886016 bytes
255 heads, 63 sectors/track, 121601 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Disk identifier: 0xaaaaaaaa
Device Boot Start End Blocks Id System
/dev/sde1 1 121601 976760032 83 Linux
new partition on similar drive:
Disk /dev/sdb: 1000.2 GB, 1000204886016 bytes
255 heads, 63 sectors/track, 121601 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Disk identifier: 0xaaaaaaaa
Device Boot Start End Blocks Id System
/dev/sdb1 1 121601 976760001 83 Linux
The only difference is the number of blocks of the partition, I guess since the
start and end are the same this should be equal as well.
> Can you upload someplace the output of
>
> dumpe2fs /dev/XXX
> dumpe2fs -o superblock=32768 /dev/XXX
> dumpe2fs -o superblock=98304 /dev/XXX
>
> That would be helpful to see what had happened.
Uploaded at http://www.filefactory.com/file/afg88b1/n/dumps_tar_bz2. dump-0 is
the output of the first command, dump-32768 the second, and the third was equal
to the second. The following two lines weren't redirected into the files (even
with 2>&1), and were the same for all three commands (well, at least for the
first line that's not really surprising).
dumpe2fs 1.41.3 (12-Oct-2008)
ext2fs_read_bb_inode: Invalid argument-
I couldn't yet compile the findsuper program (some missing headers), but since
dumpe2fs found some more or less valid data, it shouldn't be necessary, right?
I also tried the R-Linux recovery program mentioned from
http://www.data-recovery-software.net/Linux_Recovery.shtml, but that didn't
really work (not surprising, since it's for ext3 only).
Best regards,
Christian Ohm
PS: Sorry for the late answer, I'll reply more quickly now.
next prev parent reply other threads:[~2009-02-07 16:29 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-01-05 13:53 How to recover a damaged ext4 file system? Christian Ohm
2009-01-06 12:05 ` Andreas Dilger
2009-01-06 19:34 ` Theodore Tso
2009-01-07 21:42 ` Christian Ohm
2009-01-08 10:11 ` Andreas Dilger
2009-02-07 16:27 ` Christian Ohm [this message]
2009-02-07 19:04 ` Eric Sandeen
2009-02-12 21:36 ` Christian Ohm
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20090207162725.GA27086@moongate.localnet \
--to=chr.ohm@gmx.net \
--cc=adilger@sun.com \
--cc=linux-ext4@vger.kernel.org \
--cc=tytso@mit.edu \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox