From: Ken Drummond <linuxraid@kendrummond.com>
To: Mike Viau <viaum@sheridanc.on.ca>
Cc: linux-raid@vger.kernel.org
Subject: RE: Impact of missing parameter during mdadm create
Date: Sat, 05 Mar 2011 16:37:35 +1000 [thread overview]
Message-ID: <1299307055.4999.8.camel@tankquad> (raw)
In-Reply-To: <BAY148-w59357147C486E15E514067EFC50@phx.gbl>
On Fri, 2011-03-04 at 23:22 -0500, Mike Viau wrote:
> Attached HOST_SYSLOG.txt is the _complete_ syslog after a system reboot showing only 2 drives are assembled automatically on boot, and the array is degraded.
>
>
OK, I guess I should have thought of this before, your syslog shows that
sdd is attached as a USB device and is not discovered until after md0
has been assembled (using all the devices available at the time). I'm
not sure how you would make md auto assembly wait until after your USB
device has been discovered. Hopefully someone else here can provide
some advice, although it's not strictly a linux-raid issue there are
quite a few helpful people here.
I'm pretty sure if you replaced the USB device with another SATA device
things would work as you expected. Another alternative may be to not
have that array auto assembled but wait and assemble after the boot is
finished, this could probably be scripted.
Ken.
next parent reply other threads:[~2011-03-05 6:37 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <BAY148-w59357147C486E15E514067EFC50@phx.gbl>
2011-03-05 6:37 ` Ken Drummond [this message]
2011-03-05 14:47 ` Impact of missing parameter during mdadm create Mike Viau
2011-03-05 15:02 ` John Robinson
2011-03-01 18:38 Mike Viau
2011-03-03 11:06 ` Ken Drummond
2011-03-04 4:55 ` Mike Viau
2011-03-04 5:01 ` Mike Viau
2011-03-04 7:36 ` Ken Drummond
-- strict thread matches above, loose matches on Subject: below --
2011-03-01 3:19 Mike Viau
2011-03-01 3:59 ` Mike Viau
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=1299307055.4999.8.camel@tankquad \
--to=linuxraid@kendrummond.com \
--cc=linux-raid@vger.kernel.org \
--cc=viaum@sheridanc.on.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 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).