From: Neil Brown <neilb@suse.de>
To: Jan Ceuleers <jan.ceuleers@computer.org>
Cc: linux-raid <linux-raid@vger.kernel.org>
Subject: Re: Need help with recovery
Date: Thu, 15 Jul 2010 07:37:29 +0200 [thread overview]
Message-ID: <20100715073729.06c4f11a@notabene> (raw)
In-Reply-To: <4C3DCB95.9010104@computer.org>
On Wed, 14 Jul 2010 16:37:09 +0200
Jan Ceuleers <jan.ceuleers@computer.org> wrote:
> Hi guys.
>
> I've been having trouble with a four-disk raid5 array, which I now believe were caused by a flaky eSATA cable. The cable has been replaced, and the controller now seems to reliably see all four disks.
>
> In fact I have five disks, and so a partition on the fifth disk acts as a spare. Over the past several days I've been connecting and disconnecting drives in ways that I didn't realise were unreliable (due to the faulty cable).
>
> This has resulted in the md metadata being out of sync on the different partitions. Please could someone provide advice as to how to recover this array (which contains an ext3 filesystem)?
>
>
> Many thanks!
>
> Jan
mdadm -A /dev/md2 --force /dev/sd[ade]2
sdc2 this it is a spare, so you don't want it just now.
sdb2 and sde2 both think that are 'device 0', but sde2 is clearly newer.
So run the above mdadm comment (assuming none of the devices have been
renamed again since you created the --examine output), then
fsck -n /dev/md2
and make sure it is happy.
If it is you can added sdb2 and sde2 as spares.
NeilBrown
next prev parent reply other threads:[~2010-07-15 5:37 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-07-14 14:37 Need help with recovery Jan Ceuleers
2010-07-15 5:37 ` Neil Brown [this message]
2010-07-15 9:50 ` Ceuleers, Jan (Jan)
2010-07-15 13:40 ` Neil Brown
2010-07-15 19:27 ` Jan Ceuleers
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=20100715073729.06c4f11a@notabene \
--to=neilb@suse.de \
--cc=jan.ceuleers@computer.org \
--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).