From: Phil Turmel <philip@turmel.org>
To: Pavel Hofman <pavel.hofman@ivitera.com>
Cc: linux-raid@vger.kernel.org
Subject: Re: Raid auto-assembly upon boot - device order
Date: Mon, 27 Jun 2011 10:47:39 -0400 [thread overview]
Message-ID: <4E08980B.5080002@turmel.org> (raw)
In-Reply-To: <4E089067.8010904@ivitera.com>
Hi Pavel,
On 06/27/2011 10:15 AM, Pavel Hofman wrote:
> Hi,
>
> We are running a raid1 on top of two raid0's. In this specific case we
> cannot use raid10 (different device sizes etc). Upon booting, the raid1
> is always started degraded, with one of the raid0's missing. The log
> says the missing raid could not be found. However, upon booting
> /proc/mdstat lists both the two raid0s OK.
>
> I guess either the raids are assembled in wrong order (no mutual
> dependencies considered), or without letting the previously assembled
> device to "settle down". I am wondering what would be the proper way to
> fix this issue. The raids are huge (over 1TB each) and recovery takes
> many hours.
>
> Our mdadm.conf lists the raids in proper order, corresponding to their
> dependency.
I would first check the copy of mdadm.conf in your initramfs. If it specifies just the raid1, you can end up in this situation.
Most distributions have an 'update-initramfs' script or something similar which must be run after any updates to files that are needed in early boot.
If this is your problem, it also explains why the raid0 appears OK after booting. The init-scripts that are available on the real root filesystem, containing the correct mdadm.conf, will assemble it.
HTH,
Phil
next prev parent reply other threads:[~2011-06-27 14:47 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-06-27 14:15 Raid auto-assembly upon boot - device order Pavel Hofman
2011-06-27 14:47 ` Phil Turmel [this message]
2011-06-28 10:18 ` Pavel Hofman
2011-06-28 11:03 ` Phil Turmel
2011-06-28 12:01 ` Pavel Hofman
2011-06-28 15:39 ` Phil Turmel
2011-06-28 19:18 ` Pavel Hofman
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=4E08980B.5080002@turmel.org \
--to=philip@turmel.org \
--cc=linux-raid@vger.kernel.org \
--cc=pavel.hofman@ivitera.com \
/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.