From: NeilBrown <neilb@suse.com>
To: Wols Lists <antlists@youngman.org.uk>,
"r23@anchordrop.net" <r23@anchordrop.net>,
linux-raid@vger.kernel.org
Subject: Re: raid-1 starting with 1 drive after brief hiatus with cruddy controller.
Date: Mon, 19 Jun 2017 07:00:28 +1000 [thread overview]
Message-ID: <87y3sp3tar.fsf@notabene.neil.brown.name> (raw)
In-Reply-To: <5946867B.5010200@youngman.org.uk>
[-- Attachment #1: Type: text/plain, Size: 281 bytes --]
On Sun, Jun 18 2017, Wols Lists wrote:
> Hmmm. I don't want to suggest too much, but the array is expecting two
> devices, so saying just "/dev/sdb2" is probably its invalid argument.
> Try changing that to "/dev/sdb2 missing".
"missing" is only relevant for --create
NeilBrown
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 832 bytes --]
next prev parent reply other threads:[~2017-06-18 21:00 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-06-18 4:14 raid-1 starting with 1 drive after brief hiatus with cruddy controller r23
2017-06-18 13:56 ` Wols Lists
2017-06-18 16:08 ` r23
2017-06-18 21:00 ` NeilBrown [this message]
2017-06-18 20:59 ` NeilBrown
2017-06-21 18:29 ` r23
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=87y3sp3tar.fsf@notabene.neil.brown.name \
--to=neilb@suse.com \
--cc=antlists@youngman.org.uk \
--cc=linux-raid@vger.kernel.org \
--cc=r23@anchordrop.net \
/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).