Linux RAID subsystem development
 help / color / mirror / Atom feed
From: David Greaves <david@dgreaves.com>
To: Brian Ristuccia <bristuccia@starentnetworks.com>
Cc: linux-raid@vger.kernel.org
Subject: Re: best effort rebuild with 1 failed, 1 marginal disks in raid5?
Date: Sun, 28 Nov 2004 16:43:24 +0000	[thread overview]
Message-ID: <41AA002C.8030203@dgreaves.com> (raw)
In-Reply-To: <20041128160649.GB30940@sw.starentnetworks.com>

Brian Ristuccia wrote:

>I have a 3 disk raid5 array which recently suffered catastrophic failure of
>one disk. While the array was degraded, one more disk failed out of the
>array due to a bad block. Investigation with badblocks reveals the marginal
>disk has only a handful of bad blocks.
>
>What I'd like to do is start the array with the good disk and the marginal
>disk, add a 3rd known good disk, and rebuild the array as best as possible.
>Then I'd fail the marginal disk and install another good disk.
>
Well, first of all - don't do anything without verifying it first.

There's a good chance you can recover quite some data if you don't screw 
it up by 'having a go' (I speak from experience :) )

Instead of your plan, can I suggest you try to duplicate the 
disk/partition showing a few bad blocks onto a known good disk.
Then forcefully reassemble the array, then add another good disk for 
reconstruction.

Useful tools include dd_rhelp and dd_rescue

Take a look in the archives as this kinda hit me recently.
http://marc.theaimsgroup.com/?l=linux-raid&m=110025421113782&w=2

David

  reply	other threads:[~2004-11-28 16:43 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-11-28 16:06 best effort rebuild with 1 failed, 1 marginal disks in raid5? Brian Ristuccia
2004-11-28 16:43 ` David Greaves [this message]
2004-11-28 18:09   ` Guy

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=41AA002C.8030203@dgreaves.com \
    --to=david@dgreaves.com \
    --cc=bristuccia@starentnetworks.com \
    --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