From: Dave W <dave+gmane@wuertele.com>
To: linux-raid@vger.kernel.org
Subject: Re: How do I determine which drive should be in which slot?
Date: Tue, 29 Jun 2010 06:26:17 +0000 (UTC) [thread overview]
Message-ID: <loom.20100629T082214-677@post.gmane.org> (raw)
In-Reply-To: loom.20100626T070913-497@post.gmane.org
Previously, I wrote:
> After making some changes in the bios to my boot order, my 5-drive RAID6
> stopped assembling. Three of the five known-good drives suddenly stopped
> getting added to the right slots. There are no disk errors in the logs and
> I can read from the drives with no problems.
Any help with this one? My disks are fine but mdadm seems confused about which
slots they're supposed to be in. How can I tell mdadm to put them in the right
slots?
Thanks,
Dave
# mdadm --stop /dev/md0
mdadm: stopped /dev/md0
# mdadm -v -Af /dev/md0 /dev/sd[bcdef]1
mdadm: looking for devices for /dev/md0
mdadm: /dev/sdb1 is identified as a member of /dev/md0, slot 7.
mdadm: /dev/sdc1 is identified as a member of /dev/md0, slot 6.
mdadm: /dev/sdd1 is identified as a member of /dev/md0, slot 2.
mdadm: /dev/sde1 is identified as a member of /dev/md0, slot 3.
mdadm: /dev/sdf1 is identified as a member of /dev/md0, slot 5.
mdadm: no uptodate device for slot 0 of /dev/md0
mdadm: no uptodate device for slot 1 of /dev/md0
mdadm: added /dev/sde1 to /dev/md0 as 3
mdadm: no uptodate device for slot 4 of /dev/md0
mdadm: added /dev/sdf1 to /dev/md0 as 5
mdadm: added /dev/sdc1 to /dev/md0 as 6
mdadm: added /dev/sdb1 to /dev/md0 as 7
mdadm: added /dev/sdd1 to /dev/md0 as 2
mdadm: /dev/md0 assembled from 2 drives and 3 spares - not enough to start the
array.
#
next prev parent reply other threads:[~2010-06-29 6:26 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-06-26 5:32 How do I determine which drive should be in which slot? Dave W
2010-06-29 6:26 ` Dave W [this message]
2010-06-29 7:02 ` Neil Brown
2010-06-29 16:00 ` Dave W
2010-06-30 1:02 ` Neil 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=loom.20100629T082214-677@post.gmane.org \
--to=dave+gmane@wuertele.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).