From: NeilBrown <neilb@suse.de>
To: Christopher Hoover <ch@murgatroid.com>
Cc: Adam Goryachev <adam@websitemanagers.com.au>, linux-raid@vger.kernel.org
Subject: Re: unable to assemble (mostly?) clean array
Date: Mon, 9 Dec 2013 12:33:05 +1100 [thread overview]
Message-ID: <20131209123305.04e7257f@notabene.brown> (raw)
In-Reply-To: <CACw0PsaCzZAKWeh9MxXK39Fpwh5wg-bjHHMY0-0djW+59Qf-jQ@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 2225 bytes --]
On Sun, 8 Dec 2013 17:08:19 -0800 Christopher Hoover <ch@murgatroid.com>
wrote:
> ch@snaggle:~$ sudo mdadm --assemble --verbose --force /dev/md0 /dev/sd[defg]1
> mdadm: looking for devices for /dev/md0
> mdadm: /dev/sdd1 is identified as a member of /dev/md0, slot 4.
> mdadm: /dev/sde1 is identified as a member of /dev/md0, slot 1.
> mdadm: /dev/sdf1 is identified as a member of /dev/md0, slot 2.
> mdadm: /dev/sdg1 is identified as a member of /dev/md0, slot 5.
> mdadm: ignoring /dev/sde1 as it reports /dev/sdd1 as failed
> mdadm: ignoring /dev/sdf1 as it reports /dev/sdd1 as failed
> mdadm: no uptodate device for slot 0 of /dev/md0
> mdadm: no uptodate device for slot 1 of /dev/md0
> mdadm: no uptodate device for slot 2 of /dev/md0
> mdadm: no uptodate device for slot 3 of /dev/md0
> mdadm: added /dev/sdg1 to /dev/md0 as 5
> mdadm: added /dev/sdd1 to /dev/md0 as 4
> mdadm: /dev/md0 assembled from 0 drives and 2 spares - not enough to
> start the array.
> ch@snaggle:~$
Thanks.
I recognise this bug now. You are running mdadm-3.2.something - correct?
You need 3.3.
Just grab the latest:
cd /tmp;git clone git://neil.brown.name/mdadm ; cd mdadm ; make ; ./mdadm -Avf /dev/md0 /dev/sd[defg]1
NeilBrown
>
> On Sun, Dec 8, 2013 at 5:02 PM, NeilBrown <neilb@suse.de> wrote:
> > On Sun, 8 Dec 2013 16:32:22 -0800 Christopher Hoover <ch@murgatroid.com>
> > wrote:
> >
> >> yes, thanks, typo there. that was done hastily for the e-mail.
> >>
> >> i had tried the right thing previously and here it is again. still no luck:
> >>
> >>
> >> ch@snaggle:~$ sudo mdadm -E /dev/sd[defg]1 | egrep 'Events|^/dev/sd'
> >> /dev/sdd1:
> >> Events : 286024
> >> /dev/sde1:
> >> Events : 286011
> >> /dev/sdf1:
> >> Events : 286024
> >> /dev/sdg1:
> >> Events : 286024
> >> ch@snaggle:~$ sudo mdadm --assemble --force /dev/md0 /dev/sd[dfg]1
> >> mdadm: ignoring /dev/sdf1 as it reports /dev/sdd1 as failed
> >> mdadm: /dev/md0 assembled from 0 drives and 2 spares - not enough to
> >> start the array.
> >> ch@snaggle:~$
> >
> > Please try listing *all* of the devices, and add "-v" for extra output.
> >
> > NeilBrown
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 828 bytes --]
next prev parent reply other threads:[~2013-12-09 1:33 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-12-08 23:32 unable to assemble (mostly?) clean array Christopher Hoover
2013-12-08 23:55 ` NeilBrown
2013-12-09 0:02 ` Adam Goryachev
2013-12-09 0:32 ` Christopher Hoover
2013-12-09 1:02 ` NeilBrown
2013-12-09 1:08 ` Christopher Hoover
2013-12-09 1:33 ` NeilBrown [this message]
2013-12-09 3:00 ` Christopher Hoover
2013-12-09 3:41 ` NeilBrown
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=20131209123305.04e7257f@notabene.brown \
--to=neilb@suse.de \
--cc=adam@websitemanagers.com.au \
--cc=ch@murgatroid.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).