From: "David M. Strang" <dstrang@shellpower.net>
To: Neil Brown <neilb@suse.de>
Cc: linux-raid@vger.kernel.org
Subject: Re: MD or MDADM bug?
Date: Fri, 2 Sep 2005 04:48:50 -0400 [thread overview]
Message-ID: <019601c5af9b$23d8ce50$c100a8c0@NCNF5131FTH> (raw)
In-Reply-To: 17176.4401.418417.56385@cse.unsw.edu.au
Neil Brown wrote:
> On Friday September 2, dstrang@shellpower.net wrote:
> >
> > > mdadm 2.0 had a fix for assembling version-1 arrays that would
> > > particularly affect raid5. Try using that instead of -devel-3.
> >
> > No luck --
> >
> > -(root@abyss)-(~)- # mdadm -A /dev/md0 /dev/sda /dev/sdb /dev/sdc
> > /dev/sdd
> > /dev/sde /dev/sdf /dev/sdg /dev/sdh /dev/sdi /dev/sdj /dev/sdk /dev/sdl
> > /dev/sdm /dev/sdn /dev/sdo /dev/sdp /dev/sdq /dev/sdr /dev/sds /dev/sdt
> > /dev/sdu /dev/sdv /dev/sdw /dev/sdx /dev/sdy /dev/sdz /dev/sdaa
> > /dev/sdab -f
> > mdadm: /dev/md0 assembled from 26 drives - not enough to start the
> > array.
> >
> > Any other suggestions?
> >
>
> Can you run that with '-v' for me?
mdadm: looking for devices for /dev/md0
mdadm: /dev/sda is identified as a member of /dev/md0, slot 0.
mdadm: /dev/sdb is identified as a member of /dev/md0, slot 1.
mdadm: /dev/sdc is identified as a member of /dev/md0, slot 2.
mdadm: /dev/sdd is identified as a member of /dev/md0, slot 3.
mdadm: /dev/sde is identified as a member of /dev/md0, slot 4.
mdadm: /dev/sdf is identified as a member of /dev/md0, slot 5.
mdadm: /dev/sdg is identified as a member of /dev/md0, slot 6.
mdadm: /dev/sdh is identified as a member of /dev/md0, slot 7.
mdadm: /dev/sdi is identified as a member of /dev/md0, slot 8.
mdadm: /dev/sdj is identified as a member of /dev/md0, slot 9.
mdadm: /dev/sdk is identified as a member of /dev/md0, slot 10.
mdadm: /dev/sdl is identified as a member of /dev/md0, slot 11.
mdadm: /dev/sdm is identified as a member of /dev/md0, slot -1.
mdadm: /dev/sdn is identified as a member of /dev/md0, slot 13.
mdadm: /dev/sdo is identified as a member of /dev/md0, slot 14.
mdadm: /dev/sdp is identified as a member of /dev/md0, slot 15.
mdadm: /dev/sdq is identified as a member of /dev/md0, slot 16.
mdadm: /dev/sdr is identified as a member of /dev/md0, slot 17.
mdadm: /dev/sds is identified as a member of /dev/md0, slot 18.
mdadm: /dev/sdt is identified as a member of /dev/md0, slot 19.
mdadm: /dev/sdu is identified as a member of /dev/md0, slot 20.
mdadm: /dev/sdv is identified as a member of /dev/md0, slot 21.
mdadm: /dev/sdw is identified as a member of /dev/md0, slot 22.
mdadm: /dev/sdx is identified as a member of /dev/md0, slot 23.
mdadm: /dev/sdy is identified as a member of /dev/md0, slot 24.
mdadm: /dev/sdz is identified as a member of /dev/md0, slot 25.
mdadm: /dev/sdaa is identified as a member of /dev/md0, slot -1.
mdadm: /dev/sdab is identified as a member of /dev/md0, slot 27.
mdadm: added /dev/sdb to /dev/md0 as 1
mdadm: added /dev/sdc to /dev/md0 as 2
mdadm: added /dev/sdd to /dev/md0 as 3
mdadm: added /dev/sde to /dev/md0 as 4
mdadm: added /dev/sdf to /dev/md0 as 5
mdadm: added /dev/sdg to /dev/md0 as 6
mdadm: added /dev/sdh to /dev/md0 as 7
mdadm: added /dev/sdi to /dev/md0 as 8
mdadm: added /dev/sdj to /dev/md0 as 9
mdadm: added /dev/sdk to /dev/md0 as 10
mdadm: added /dev/sdl to /dev/md0 as 11
mdadm: no uptodate device for slot 12 of /dev/md0
mdadm: added /dev/sdn to /dev/md0 as 13
mdadm: added /dev/sdo to /dev/md0 as 14
mdadm: added /dev/sdp to /dev/md0 as 15
mdadm: added /dev/sdq to /dev/md0 as 16
mdadm: added /dev/sdr to /dev/md0 as 17
mdadm: added /dev/sds to /dev/md0 as 18
mdadm: added /dev/sdt to /dev/md0 as 19
mdadm: added /dev/sdu to /dev/md0 as 20
mdadm: added /dev/sdv to /dev/md0 as 21
mdadm: added /dev/sdw to /dev/md0 as 22
mdadm: added /dev/sdx to /dev/md0 as 23
mdadm: added /dev/sdy to /dev/md0 as 24
mdadm: added /dev/sdz to /dev/md0 as 25
mdadm: no uptodate device for slot 26 of /dev/md0
mdadm: added /dev/sdab to /dev/md0 as 27
mdadm: added /dev/sda to /dev/md0 as 0
mdadm: /dev/md0 assembled from 26 drives - not enough to start the array.
next prev parent reply other threads:[~2005-09-02 8:48 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-09-01 21:26 MD or MDADM bug? David M. Strang
2005-09-02 6:36 ` Claas Hilbrecht
2005-09-02 6:42 ` Claas Hilbrecht
2005-09-02 8:15 ` Neil Brown
2005-09-02 8:33 ` David M. Strang
2005-09-02 8:45 ` Neil Brown
2005-09-02 8:48 ` David M. Strang [this message]
2005-09-02 9:34 ` Neil Brown
2005-09-02 9:41 ` David M. Strang
2005-09-02 10:03 ` Neil Brown
2005-09-02 10:08 ` David M. Strang
2005-09-02 11:18 ` Neil Brown
2005-09-02 21:22 ` David M. Strang
2005-09-02 21:49 ` Neil Brown
2005-09-02 23:34 ` David M. Strang
2005-09-03 3:52 ` Neil Brown
2005-09-03 8:21 ` Tyler
2005-09-04 6:18 ` Neil Brown
2005-09-05 9:20 ` danci
2005-09-05 9:35 ` Mario 'BitKoenig' Holbe
2005-09-05 16:45 ` Molle Bestefich
2005-09-05 21:13 ` Luca Berra
2005-09-06 1:38 ` Neil Brown
2005-09-06 6:38 ` bart
2005-09-06 10:17 ` Molle Bestefich
2005-09-07 2:04 ` berk walker
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='019601c5af9b$23d8ce50$c100a8c0@NCNF5131FTH' \
--to=dstrang@shellpower.net \
--cc=linux-raid@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox