From: Roman Mamedov <rm@romanrm.ru>
To: Bryan Wintermute <bryanwintermute@gmail.com>
Cc: linux-raid@vger.kernel.org
Subject: Re: RAID 5 - One drive dropped while replacing another
Date: Wed, 2 Feb 2011 04:36:05 +0500 [thread overview]
Message-ID: <20110202043605.593f0c5c@natsu> (raw)
In-Reply-To: <AANLkTikSjLhoUM5f2ibqCUmo8XF-tsrhxZ7oieg08dtD@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 768 bytes --]
On Tue, 1 Feb 2011 15:27:50 -0800
Bryan Wintermute <bryanwintermute@gmail.com> wrote:
> I have a RAID5 setup with 15 drives.
Looks like you got the problem you were so desperately asking for, with this
crazy setup. :(
> Is there anything I can do to get around these bad sectors or force mdadm
> to ignore them to at least complete the recovery?
I suppose the second failed drive is still mostly alive, just has some
unreadable areas? If so, I suggest that you get another new clean drive, and
while your mdadm array is stopped, copy whatever you can with e.g. dd_rescue
from the semi-dead drive to this new one. Then remove the bad drive from the
system, and start the array with the new drive instead of the bad one.
--
With respect,
Roman
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 198 bytes --]
next prev parent reply other threads:[~2011-02-01 23:36 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <AANLkTinXTYds442gPrs9a9vKtWTo4OcDHDEzvO0njvyv@mail.gmail.com>
2011-02-01 23:27 ` RAID 5 - One drive dropped while replacing another Bryan Wintermute
2011-02-01 23:36 ` Roman Mamedov [this message]
2011-02-02 6:20 ` Leslie Rhorer
2011-02-02 14:21 ` hansbkk
2011-02-02 14:28 ` Roman Mamedov
2011-02-02 15:28 ` hansbkk
[not found] ` <AANLkTikm5unULgkUBM__d8N9XPReu9BtjijAHt9zzvaP@mail.gmail.com>
2011-02-02 16:29 ` hansbkk
2011-02-02 21:15 ` David Brown
2011-02-02 17:25 ` Leslie Rhorer
2011-02-02 17:51 ` hansbkk
2011-02-02 20:56 ` Leslie Rhorer
2011-02-02 14:29 ` Mathias Burén
2011-02-02 14:47 ` Robin Hill
2011-02-02 16:24 ` David Brown
2011-02-02 16:48 ` hansbkk
2011-02-02 21:22 ` David Brown
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=20110202043605.593f0c5c@natsu \
--to=rm@romanrm.ru \
--cc=bryanwintermute@gmail.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;
as well as URLs for NNTP newsgroup(s).