From: Kervin Pierre <kpierre@fit.edu>
To: Richard Gooch <rgooch@ras.ucalgary.ca>
Cc: Andreas Dilger <adilger@turbolabs.com>, linux-kernel@vger.kernel.org
Subject: Re: fs corruption recovery?
Date: Tue, 08 Jan 2002 23:14:04 -0500 [thread overview]
Message-ID: <3C3BC38C.7010808@fit.edu> (raw)
In-Reply-To: <3C3BB082.8020204@fit.edu> <20020108200705.S769@lynx.adilger.int> <200201090326.g093QBF27608@vindaloo.ras.ucalgary.ca>
Hi,
Thanks for the input.
Do you still have any of those scripts around? Or can you give me a
general idea of how you used debugfs to retrieve your files?
I was actually expecting to spend a few hundred instead of a few thousand.
Thanks,
-Kervin
Richard Gooch wrote:
>Andreas Dilger writes:
>
>>On Jan 08, 2002 21:52 -0500, Kervin Pierre wrote:
>>
>>>I install and used 2.4.17 for about a week before my filesystem
>>>corrupted. I've tried 'fsck -a' but it complains that there was no
>>>valid superblock found.
>>>
>>Try "e2fsck -B 4096 -b 32768 <device>" instead.
>>
>>>Are there any tools or techniques that will recover data from the
>>>corrupted filesystem even if there isn't a valid superblock? Or is
>>>there a way to write a temporary superblock so I can access the
>>>information on the disk?
>>>
>>The ext2 format (includes ext3) has backup superblocks for just this reason.
>>
>>>Lastly, if all else fails I'm going to try sending the drive one of
>>>those 'file recovery companies'. Does anyone have a recommendation for
>>>a particular company? I'm guessing that there'll be a few that wouldn't
>>>know what to do with a ext3 partition.
>>>
>>Is the data really that valuable, and you don't have a backup? It may
>>cost you several thousand dollars to do a recovery from such a company.
>>Yet, it isn't worth doing backups, it appears.
>>
>
>And these companies don't really do much that you can't do yourself. I
>had a failing drive some years ago, where some sectors couldn't be
>read. So I tried to dd the raw device to a file elsewhere. Of course,
>dd will quit when it has an I/O error. So I wrote a recovery utility
>that writes a zero sector if reading the input sector gives an I/O
>error. Unfortunately, I couldn't mount the file (too much corruption),
>but I was able to use debugfs on it. I got the most important data
>back.
>
>While I was waiting for 48 hours for the data to be pulled off (each
>time a bad sector was encountered, the drive would retry several
>times, with lots of clicking and rattling), I contacted one of these
>recovery companies. I wanted to know if they could recover the bad
>sectors. I was told no. After some probing, it turns out that all they
>do is basically what I was doing. They just charge $2000 for it.
>
>No doubt if you took your drive to your local CIA/KGB/MI6 offices,
>they could recover some of those bad sectors. But I hear they charge
>their customers quite a lot...
>
> Regards,
>
> Richard....
>Permanent: rgooch@atnf.csiro.au
>Current: rgooch@ras.ucalgary.ca
>-
>To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
>the body of a message to majordomo@vger.kernel.org
>More majordomo info at http://vger.kernel.org/majordomo-info.html
>Please read the FAQ at http://www.tux.org/lkml/
>
next prev parent reply other threads:[~2002-01-09 4:08 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-01-09 2:52 fs corruption recovery? Kervin Pierre
2002-01-09 3:07 ` Andreas Dilger
2002-01-09 3:26 ` Richard Gooch
2002-01-09 4:14 ` Kervin Pierre [this message]
2002-01-09 5:29 ` Richard Gooch
2002-01-09 11:10 ` Walter Hofmann
2002-01-10 15:50 ` Ralf Baechle
2002-01-09 10:24 ` Helge Hafting
2002-01-09 15:12 ` Richard Gooch
2002-01-09 15:22 ` Roy Sigurd Karlsbakk
2002-01-09 12:26 ` Bjorn Wesen
2002-01-09 20:29 ` Alex Bligh - linux-kernel
2002-01-09 4:03 ` Kervin Pierre
2002-01-09 5:20 ` H. Peter Anvin
2002-01-09 9:28 ` Thomas Capricelli
2002-01-09 10:43 ` Andreas Dilger
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=3C3BC38C.7010808@fit.edu \
--to=kpierre@fit.edu \
--cc=adilger@turbolabs.com \
--cc=linux-kernel@vger.kernel.org \
--cc=rgooch@ras.ucalgary.ca \
/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