From: "Vojtěch Kletečka" <vojta.kletecka@gmail.com>
To: Phil Turmel <philip@turmel.org>
Cc: Wols Lists <antlists@youngman.org.uk>, linux-raid@vger.kernel.org
Subject: Re: Data recovery
Date: Thu, 21 Sep 2017 15:22:46 +0200 [thread overview]
Message-ID: <CAEmSg08aYMppy6Ardarjz_0P6-HDU8_GCkcOV88g32-T053k_g@mail.gmail.com> (raw)
In-Reply-To: <54c6f639-0912-1f82-41b9-0a778fb5bb89@turmel.org>
I tried both reasonable versions without success:
sudo mdadm --assemble --verbose --force /dev/md127 /dev/sd[ce]1
[sudo] password for vojtech:
mdadm: looking for devices for /dev/md127
mdadm: /dev/sdc1 is identified as a member of /dev/md127, slot 2.
mdadm: /dev/sde1 is identified as a member of /dev/md127, slot 1.
mdadm: no uptodate device for slot 0 of /dev/md127
mdadm: added /dev/sdc1 to /dev/md127 as 2 (possibly out of date)
mdadm: added /dev/sde1 to /dev/md127 as 1
mdadm: /dev/md127 assembled from 1 drive - not enough to start the array.
sudo mdadm --assemble --verbose --force /dev/md127 /dev/sd[de]1
mdadm: looking for devices for /dev/md127
mdadm: /dev/sdd1 is identified as a member of /dev/md127, slot 0.
mdadm: /dev/sde1 is identified as a member of /dev/md127, slot 1.
mdadm: added /dev/sde1 to /dev/md127 as 1
mdadm: no uptodate device for slot 4 of /dev/md127
mdadm: added /dev/sdd1 to /dev/md127 as 0
mdadm: failed to RUN_ARRAY /dev/md127: Input/output error
next prev parent reply other threads:[~2017-09-21 13:22 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-09-21 0:08 Data recovery Vojtěch Kletečka
2017-09-21 0:37 ` Wols Lists
2017-09-21 12:10 ` Phil Turmel
2017-09-21 12:55 ` Vojtěch Kletečka
2017-09-21 13:13 ` Phil Turmel
2017-09-21 13:22 ` Vojtěch Kletečka [this message]
2017-09-21 14:37 ` Phil Turmel
[not found] ` <CAEmSg0-AD09KM=S21a-EVGQEEE0=em-PCpb9LAAbd8cP2+ysBA@mail.gmail.com>
2017-09-21 15:15 ` Wols Lists
2017-09-21 15:32 ` Wols Lists
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=CAEmSg08aYMppy6Ardarjz_0P6-HDU8_GCkcOV88g32-T053k_g@mail.gmail.com \
--to=vojta.kletecka@gmail.com \
--cc=antlists@youngman.org.uk \
--cc=linux-raid@vger.kernel.org \
--cc=philip@turmel.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).