From: NeilBrown <neilb@suse.de>
To: sanktnelson 1 <sanktnelson@googlemail.com>
Cc: linux-raid@vger.kernel.org
Subject: Re: help please - recovering from failed RAID5 rebuild
Date: Sat, 9 Apr 2011 21:29:30 +1000 [thread overview]
Message-ID: <20110409212930.6f4ffb28@notabene.brown> (raw)
In-Reply-To: <BANLkTimSh8f8cVihRxbKgKZq4zFv6VUmVQ@mail.gmail.com>
On Sat, 9 Apr 2011 11:27:20 +0200 sanktnelson 1 <sanktnelson@googlemail.com>
wrote:
> 2011/4/8 NeilBrown <neilb@suse.de>:
>
> >
> > Maybe the best thing to do at this point is post the output of
> > mdadm -E /dev/sd[bcdef]1
> > and I'll see if I can make sense of it.
>
> Thanks for your advice! here is the output:
It looks like it is in reasonably good shape (relatively speaking...).
I would
mdadm -S /dev/md0
mdadm -Af /dev/md0 /dev/sd[bdef]1
fsck -nf /dev/md0
and if it looks good
mount /dev/md0
copy off any data that you can that you cannot live without.
Then stop the array
mdadm -S /dev/md0
and copy sdd to sdc with dd-rescue
When that completes, assemble the array with
mdadm -A /dev/md0 /dev/sd[bcef]1
fsck -nf /dev/md0
and then if it looks good
mdadm --zero /dev/sdd1
mdadm /dev/md0 --add /dev/sdd1
and with luck it will successfully rebuild sdd1 and you will have redundancy
again.
NeilBrown
--
To unsubscribe from this list: send the line "unsubscribe linux-raid" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2011-04-09 11:29 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-04-07 20:00 help please - recovering from failed RAID5 rebuild sanktnelson 1
2011-04-08 12:01 ` NeilBrown
2011-04-09 9:27 ` sanktnelson 1
2011-04-09 11:29 ` NeilBrown [this message]
2011-04-13 16:45 ` sanktnelson 1
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=20110409212930.6f4ffb28@notabene.brown \
--to=neilb@suse.de \
--cc=linux-raid@vger.kernel.org \
--cc=sanktnelson@googlemail.com \
/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).