From: Simon Matthews <simon.d.matthews@gmail.com>
To: Asdo <asdo@shiftmail.org>
Cc: linux-raid@vger.kernel.org
Subject: Re: Why do arrays start without some components?
Date: Mon, 15 Mar 2010 14:26:52 -0700 [thread overview]
Message-ID: <40b437201003151426h7bc721e2m69242c044a074e24@mail.gmail.com> (raw)
In-Reply-To: <4B9EA0E8.3020301@shiftmail.org>
On Mon, Mar 15, 2010 at 2:04 PM, Asdo <asdo@shiftmail.org> wrote:
> Simon Matthews wrote:
>>
>> I have a couple of machines on which this is happening now --
>>
>> When the machine boots, the RAID arrays (RAID 1) start, but each array
>> only has one component device. I can add the other component again
>> (using mdadm --add ... ) and the array will sync up, but next time it
>> boots, I have to do the same once more.
>>
>> Why is this and how do I fix it?
>>
>
> Might that be a /etc/mdadm/mdadm.conf in the initramfs listing fewer devices
> than it should?
> I am not sure (because in this case maybe it shouldn't autoassemble the
> array at all), but have a look by unpacking your initramfs. If yes, update
> it.
I don't have an initramfs. This is a Gentoo system and I built the
kernel with all the drivers required to boot built in. This includes
RAID support.
> Or could that be a controller that shows the disks to the kernel too late...
> do you have multiple controllers?
I don't think so, on one machine they are SATA drives, but only one controller.
But, perhaps on the other machine, this may be happening, since the
drive that includes the component that is left out of the array is on
an add-in controller. On this machine, the problematic array uses IDE
drives for its components.
Simon
>
next prev parent reply other threads:[~2010-03-15 21:26 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-03-15 20:26 Why do arrays start without some components? Simon Matthews
2010-03-15 21:04 ` Asdo
2010-03-15 21:26 ` Simon Matthews [this message]
2010-03-16 5:34 ` Simon Matthews
2010-03-16 8:08 ` Majed B.
2010-03-16 15:48 ` Simon Matthews
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=40b437201003151426h7bc721e2m69242c044a074e24@mail.gmail.com \
--to=simon.d.matthews@gmail.com \
--cc=asdo@shiftmail.org \
--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).