Linux RAID subsystem development
 help / color / mirror / Atom feed
From: "David Rees" <drees76@gmail.com>
To: Lane Brooks <lbrooks@mit.edu>
Cc: linux-raid@vger.kernel.org
Subject: Re: Multiple Disk Failure Recovery
Date: Sat, 14 Oct 2006 23:35:31 -0700	[thread overview]
Message-ID: <72dbd3150610142335l3920e72ev8756ce1e36b70b5a@mail.gmail.com> (raw)
In-Reply-To: <45319CFC.4050708@mit.edu>

On 10/14/06, Lane Brooks <lbrooks@mit.edu> wrote:
> I am wondering if there is a way to cut my losses with these bad sectors
> and have it recover what it can so that I can get my raid array back to
> functioning.  Right now I cannot get a spare disk recovery to finish
> because these bad sectors.  Is there a way to force as much recovery as
> possible so that I can replace this newly faulty drive?

One technique is to use ddrescue to create an image of the failing
drive(s) (I would image all drives if possible) and use those images
to try to retrieve your data.

-Dave

  reply	other threads:[~2006-10-15  6:35 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-10-15  2:29 Multiple Disk Failure Recovery Lane Brooks
2006-10-15  6:35 ` David Rees [this message]
2006-10-15 12:16   ` Roger Gammans

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=72dbd3150610142335l3920e72ev8756ce1e36b70b5a@mail.gmail.com \
    --to=drees76@gmail.com \
    --cc=lbrooks@mit.edu \
    --cc=linux-raid@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