From: James <LinuxKernel@jamesplace.net>
To: Neil Brown <neilb@suse.de>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Problem recovering a failed RIAD5 array with 4-drives.
Date: Thu, 12 Jul 2007 18:10:57 -0500 [thread overview]
Message-ID: <200707121810.57648.LinuxKernel@jamesplace.net> (raw)
In-Reply-To: <18070.44975.347933.29688@notabene.brown>
On Thu July 12 2007 5:48 pm, you wrote:
> On Thursday July 12, LinuxKernel@jamesplace.net wrote:
> >
> > []#
> >
mdadm --create --verbose /dev/md0 --assume-clean --level=raid5 --raid-devices=4 --spare-devices=0 /dev/sda1 /dev/sdb1 /dev/sdc1 /dev/sdd1
> >
> snip
> >
> > Number Major Minor RaidDevice State
> > 0 8 17 0 active sync /dev/sdb1
> > 1 8 33 1 active sync /dev/sdc1
> > 2 8 1 2 active sync /dev/sda1
> > 3 8 49 3 active sync /dev/sdd1
>
> Something looks very wrong here. You listed the devices to --create
> in one order:
> a b c d
> but that appear in the array in a different order
> b c a d
>
> Did you cut/paste the command line into the mail, or did you retype
> it? If you retyped it, could you have got it wrong?
>
> You need the order that --detail shows to match the order of the
> original array....
>
> NeilBrown
>
>
I don't know the original order of the array before all the problems started.
Is there a way to determine the original order?
The order that --detail is showing now is the order that appeared after
issuing the command is it is in the email. (ie: a b c d)
Thank again.
next prev parent reply other threads:[~2007-07-12 23:11 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-07-12 13:49 Problem recovering a failed RIAD5 array with 4-drives James
2007-07-12 16:44 ` Lennart Sorensen
2007-07-12 20:21 ` James
2007-07-12 21:41 ` Phil Turmel
2007-07-12 22:48 ` Neil Brown
2007-07-12 23:10 ` James [this message]
2007-07-12 23:21 ` Neil Brown
2007-07-13 0:49 ` Problem recovering a failed RIAD5 array with 4-drives. --RESOLVED James
2007-07-16 15:04 ` David Greaves
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=200707121810.57648.LinuxKernel@jamesplace.net \
--to=linuxkernel@jamesplace.net \
--cc=linux-kernel@vger.kernel.org \
--cc=neilb@suse.de \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.