From: Brendan Conoboy <blc@redhat.com>
To: Joe Landman <joe.landman@gmail.com>,
linux-raid list <linux-raid@vger.kernel.org>
Subject: Re: question on how to (correctly) build an initrd for a root disk on a RAID1
Date: Mon, 27 Oct 2008 10:36:21 -0600 [thread overview]
Message-ID: <4905EE05.9070108@redhat.com> (raw)
In-Reply-To: <9f5edc120810270534j3d969d2s18c1017755990c30@mail.gmail.com>
Joe Landman wrote:
> Ok. This is where it gets interesting. If the /etc/mdadm.conf is on
> the RAID, you have a bit of a "chicken and egg" problem to deal with
> here. How does the system find /etc/mdadm.conf to make the RAID when
> /etc/mdadm.conf is on the RAID?
>
> This implies that /etc/mdadm.conf is in the initrd. Peeking inside
> the default centos one, I can see that this is not true. Which
> implies that it doesn't see /etc/mdadm.conf before it assembles the
> array, as the /etc/mdadm.conf is on the array, and not in the initrd
> image.
>
> Is there a way to include the /etc/mdadm.conf into the initrd?
This is almost certainly your problem. If / is a RAID volume, the
initrd itself needs to have an /etc/mdadm.conf that reflects how it is
constructed. This is something that mkinitrd should be doing for you.
I'll second the suggestion of running mkinitrd with sh's -x option to
see why it's not doing this for you. Good luck.
--
Brendan Conoboy / Red Hat, Inc. / blc@redhat.com
next prev parent reply other threads:[~2008-10-27 16:36 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-10-27 2:37 question on how to (correctly) build an initrd for a root disk on a RAID1 Joe Landman
2008-10-27 3:22 ` Steve Cousins
2008-10-27 3:26 ` Joe Landman
2008-10-27 7:16 ` Luca Berra
2008-10-27 12:34 ` Joe Landman
2008-10-27 16:36 ` Brendan Conoboy [this message]
2008-10-27 17:56 ` Doug Ledford
2008-10-27 18:08 ` Joe Landman
2008-10-27 18:02 ` Joe Landman
2008-10-28 6:43 ` Luca Berra
2008-10-28 12:20 ` Joe Landman
2008-10-29 1:42 ` Joe Landman
2008-10-29 2:03 ` Joe Landman
2008-10-29 2:49 ` Joe Landman
2008-10-29 12:13 ` Tru Huynh
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=4905EE05.9070108@redhat.com \
--to=blc@redhat.com \
--cc=joe.landman@gmail.com \
--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 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.