From: NeilBrown <neilb@suse.de>
To: Eli Morris <ermorris@ucsc.edu>
Cc: linux-raid@vger.kernel.org
Subject: Re: 4 out of 16 drives show up as 'removed'
Date: Fri, 9 Dec 2011 07:59:31 +1100 [thread overview]
Message-ID: <20111209075931.29b26b5e@notabene.brown> (raw)
In-Reply-To: <46200D05-2D7F-44F8-9323-DCFF720776D2@ucsc.edu>
[-- Attachment #1: Type: text/plain, Size: 2739 bytes --]
On Thu, 8 Dec 2011 12:39:10 -0800 Eli Morris <ermorris@ucsc.edu> wrote:
>
>
> and here is the verbose assemble output:
>
> [root@stratus log]# mdadm --verbose --assemble /dev/md5 --force /dev/sda1 /dev/sdb1 /dev/sdc1 /dev/sdd1 /dev/sde1 /dev/sdf1 /dev/sdg1 /dev/sdh1 /dev/sdi1 /dev/sdj1 /dev/sdk1 /dev/sdl1 /dev/sdm1 /dev/sdn1 /dev/sdo1
> mdadm: looking for devices for /dev/md5
> mdadm: /dev/sda1 is identified as a member of /dev/md5, slot 0.
> mdadm: /dev/sdb1 is identified as a member of /dev/md5, slot -1.
> mdadm: /dev/sdc1 is identified as a member of /dev/md5, slot 2.
> mdadm: /dev/sdd1 is identified as a member of /dev/md5, slot 3.
> mdadm: /dev/sde1 is identified as a member of /dev/md5, slot 4.
> mdadm: /dev/sdf1 is identified as a member of /dev/md5, slot 5.
> mdadm: /dev/sdg1 is identified as a member of /dev/md5, slot 6.
> mdadm: /dev/sdh1 is identified as a member of /dev/md5, slot 7.
> mdadm: /dev/sdi1 is identified as a member of /dev/md5, slot -1.
> mdadm: /dev/sdj1 is identified as a member of /dev/md5, slot 9.
> mdadm: /dev/sdk1 is identified as a member of /dev/md5, slot 10.
> mdadm: /dev/sdl1 is identified as a member of /dev/md5, slot 11.
> mdadm: /dev/sdm1 is identified as a member of /dev/md5, slot 12.
> mdadm: /dev/sdn1 is identified as a member of /dev/md5, slot 13.
> mdadm: /dev/sdo1 is identified as a member of /dev/md5, slot -1.
> mdadm: no uptodate device for slot 1 of /dev/md5
> mdadm: added /dev/sdc1 to /dev/md5 as 2
> mdadm: added /dev/sdd1 to /dev/md5 as 3
> mdadm: added /dev/sde1 to /dev/md5 as 4
> mdadm: added /dev/sdf1 to /dev/md5 as 5
> mdadm: added /dev/sdg1 to /dev/md5 as 6
> mdadm: added /dev/sdh1 to /dev/md5 as 7
> mdadm: no uptodate device for slot 8 of /dev/md5
> mdadm: added /dev/sdj1 to /dev/md5 as 9
> mdadm: added /dev/sdk1 to /dev/md5 as 10
> mdadm: added /dev/sdl1 to /dev/md5 as 11
> mdadm: added /dev/sdm1 to /dev/md5 as 12
> mdadm: added /dev/sdn1 to /dev/md5 as 13
> mdadm: no uptodate device for slot 14 of /dev/md5
> mdadm: no uptodate device for slot 15 of /dev/md5
> mdadm: added /dev/sdb1 to /dev/md5 as -1
> mdadm: added /dev/sdi1 to /dev/md5 as -1
> mdadm: failed to add /dev/sdo1 to /dev/md5: Device or resource busy
> mdadm: added /dev/sda1 to /dev/md5 as 0
> mdadm: /dev/md5 assembled from 12 drives and 2 spares - not enough to start the array.
>
>
Thank.
I know what the 'busy' thing is now.
sdo1 appears the be the 'same' as some other device in some way.
Also it looks like you might have turned some drives into spares
unintentionally, though I'm not sure
Could you pleas send "mdadm --examine" output for all of these drives and
I'll have a look.
Thanks,
NeilBrown
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 828 bytes --]
next prev parent reply other threads:[~2011-12-08 20:59 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-12-07 20:42 4 out of 16 drives show up as 'removed' Eli Morris
2011-12-07 20:51 ` Mathias Burén
2011-12-07 20:57 ` NeilBrown
2011-12-07 22:00 ` Eli Morris
2011-12-07 22:16 ` NeilBrown
2011-12-07 23:42 ` Eli Morris
2011-12-08 19:17 ` Eli Morris
2011-12-08 19:51 ` NeilBrown
2011-12-08 20:39 ` Eli Morris
2011-12-08 20:59 ` NeilBrown [this message]
2011-12-08 21:42 ` Eli Morris
2011-12-08 22:50 ` NeilBrown
2011-12-08 23:03 ` Eli Morris
2011-12-09 3:20 ` NeilBrown
2011-12-09 6:58 ` Eli Morris
2011-12-09 15:31 ` John Stoffel
2011-12-09 16:40 ` Asdo
2011-12-09 19:38 ` Stan Hoeppner
2011-12-09 22:07 ` Eli Morris
2011-12-10 2:29 ` Stan Hoeppner
2011-12-10 4:57 ` Eli Morris
2011-12-11 1:15 ` Stan Hoeppner
2011-12-10 17:28 ` wilsonjonathan
2011-12-10 17:43 ` wilsonjonathan
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=20111209075931.29b26b5e@notabene.brown \
--to=neilb@suse.de \
--cc=ermorris@ucsc.edu \
--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 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.