From: NeilBrown <neilb@suse.de>
To: Andrew Ryder <tireman@shaw.ca>
Cc: linux-raid@vger.kernel.org
Subject: Re: cannot re-assmble mdadm array
Date: Sat, 12 Apr 2014 19:54:02 +1000 [thread overview]
Message-ID: <20140412195402.3f2a720e@notabene.brown> (raw)
In-Reply-To: <400635298.23842674.1397287112819.JavaMail.root@cds036>
[-- Attachment #1: Type: text/plain, Size: 2594 bytes --]
On Sat, 12 Apr 2014 01:18:32 -0600 (MDT) Andrew Ryder <tireman@shaw.ca> wrote:
>
> # mdadm --assemble --run --force -vvv /dev/md2
>
> mdadm: looking for devices for /dev/md2
> mdadm: /dev/disk/by-id/ata-ST2000DL003-9VT166_5YD4PLD3-part1 is not one of
> /dev/disk/by-id/ata-SAMSUNG_HD204UI_S2HGJ9CZB04511-part1,/dev/disk/by-id/ata-SAMSUNG_HD204UI_S2HGJ9BZB13889-part1,/dev/disk/by-id/ata-ST2000DL001-9VT156_5YD1516L-part1,/dev/disk/by-id/ata-ST3000DM001-1CH166_Z1F31KGY-part1
> mdadm: /dev/disk/by-id/ata-ST2000DL003-9VT166_5YD4PSMK-part1 is not one of
> /dev/disk/by-id/ata-SAMSUNG_HD204UI_S2HGJ9CZB04511-part1,/dev/disk/by-id/ata-SAMSUNG_HD204UI_S2HGJ9BZB13889-part1,/dev/disk/by-id/ata-ST2000DL001-9VT156_5YD1516L-part1,/dev/disk/by-id/ata-ST3000DM001-1CH166_Z1F31KGY-part1
> mdadm: /dev/disk/by-id/ata-ST2000DL003-9VT166_5YD4QHNL-part1 is not one of
> /dev/disk/by-id/ata-SAMSUNG_HD204UI_S2HGJ9CZB04511-part1,/dev/disk/by-id/ata-SAMSUNG_HD204UI_S2HGJ9BZB13889-part1,/dev/disk/by-id/ata-ST2000DL001-9VT156_5YD1516L-part1,/dev/disk/by-id/ata-ST3000DM001-1CH166_Z1F31KGY-part1
> mdadm: Not a listed device for /dev/md1.
> mdadm: Not a listed device for /dev/md3.
> mdadm: Not a listed device for /dev/md1.
> mdadm: Not a listed device for /dev/md3.
> mdadm: Not a listed device for /dev/md1.
> mdadm: Not a listed device for /dev/md3.
> mdadm: Not a listed device for /dev/md1.
> mdadm: Not a listed device for /dev/md3.
> mdadm: /dev/disk/by-id/ata-SAMSUNG_HD204UI_S2HGJ9CZB04511-part1 is identified as a member of /dev/md2, slot 0.
> mdadm: /dev/disk/by-id/ata-SAMSUNG_HD204UI_S2HGJ9BZB13889-part1 is identified as a member of /dev/md2, slot 1.
> mdadm: /dev/disk/by-id/ata-ST2000DL001-9VT156_5YD1516L-part1 is identified as a member of /dev/md2, slot 2.
> mdadm: /dev/disk/by-id/ata-ST3000DM001-1CH166_Z1F31KGY-part1 is identified as a member of /dev/md2, slot 3.
> mdadm: added /dev/disk/by-id/ata-SAMSUNG_HD204UI_S2HGJ9BZB13889-part1 to /dev/md2 as 1
> mdadm: added /dev/disk/by-id/ata-ST2000DL001-9VT156_5YD1516L-part1 to /dev/md2 as 2 (possibly out of date)
> mdadm: added /dev/disk/by-id/ata-ST3000DM001-1CH166_Z1F31KGY-part1 to /dev/md2 as 3 (possibly out of date)
> mdadm: added /dev/disk/by-id/ata-SAMSUNG_HD204UI_S2HGJ9CZB04511-part1 to /dev/md2 as 0
> mdadm: failed to RUN_ARRAY /dev/md2: Input/output error
I haven't looked closely, but what version of mdadm is this?
And what happens if you try the latest
git clone git://neil.brown.name/mdadm;cd mdadm;make;./mdadm....
NeilBrown
> mdadm: Not enough devices to start the array.
>
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 828 bytes --]
prev parent reply other threads:[~2014-04-12 9:54 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1250925833.23839319.1397286490552.JavaMail.root@cds036>
2014-04-12 7:18 ` cannot re-assmble mdadm array Andrew Ryder
2014-04-12 9:54 ` NeilBrown [this message]
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=20140412195402.3f2a720e@notabene.brown \
--to=neilb@suse.de \
--cc=linux-raid@vger.kernel.org \
--cc=tireman@shaw.ca \
/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.