From: Theodore Ts'o <tytso@mit.edu>
To: Lars Noschinski <lars@public.noschinski.de>
Cc: linux-ext4@vger.kernel.org
Subject: Re: Recover files from a broken ext3 partition
Date: Mon, 16 Dec 2013 09:59:20 -0500 [thread overview]
Message-ID: <20131216145920.GA6991@thunk.org> (raw)
In-Reply-To: <52AF1253.1000608@public.noschinski.de>
On Mon, Dec 16, 2013 at 03:46:43PM +0100, Lars Noschinski wrote:
> I have got a hard disk which was damaged by a fall and would like to
> recover a few files from that. (There is a backup for most of the
> data, but a handful of recent files are missing. These are important
> enough to spend some time on them, but not for paying a professional
> data recovery service).
>
> Using GNU ddrescue I was able to read 99.8% of an ext3(or 4?)
> partition, so there's hope the data is still there. Unfortunately,
> some key parts of the file system seem to be damaged, so e2fsck fails:
>
> - ------------------------------
> % ddrescuelog -l- -b4096 sdd5.ddrescue.log > badblocks.sdd5.4096
> % e2fsck -b 20480000 -v -f -L badblocks.sdd5.4096 sdd5
> [...]
> Pass 1: Checking inodes, blocks, and sizes
> Block 1 in the primary group descriptors is on the bad block list
>
> If the block is really bad, the filesystem can not be fixed.
> You can remove this block from the bad block list and hope
> that the block is really OK. But there are no guarantees.
> - ------------------------------
> [at 20480000 there seems to be an intact superblock; got the number
> (and the block size) from 'mke2fs -n']
What I'd suggest doing is making a complete copy of the disk using
ddrescue to a known good disk, and then run e2fsck on that. It's
going to be simplest, most foolproof way to recover the data. Yes it
will take a while, but you can let it run overnight...
- Ted
prev parent reply other threads:[~2013-12-16 14:59 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-12-16 14:46 Recover files from a broken ext3 partition Lars Noschinski
2013-12-16 14:59 ` Theodore Ts'o [this message]
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=20131216145920.GA6991@thunk.org \
--to=tytso@mit.edu \
--cc=lars@public.noschinski.de \
--cc=linux-ext4@vger.kernel.org \
/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;
as well as URLs for NNTP newsgroup(s).