From: David Greaves <david@dgreaves.com>
To: Bryan Christ <bryan.christ@hp.com>
Cc: Justin Piszcz <jpiszcz@lucidpixels.com>,
Bill Davidsen <davidsen@tmr.com>,
linux-raid@vger.kernel.org
Subject: Re: Raid array is not automatically detected.
Date: Mon, 16 Jul 2007 16:21:41 +0100 [thread overview]
Message-ID: <469B8D05.1080003@dgreaves.com> (raw)
In-Reply-To: <469B7E75.3030907@hp.com>
Bryan Christ wrote:
> I do have the type set to 0xfd. Others have said that auto-assemble
> only works on RAID 0 and 1, but just as Justin mentioned, I too have
> another box with RAID5 that gets auto assembled by the kernel (also no
> initrd). I expected the same behavior when I built this array--again
> using mdadm instead of raidtools.
Any md arrays with partition type 0xfd using a 0.9 superblock should be
auto-assembled by a standard kernel.
If you want to boot from them you must ensure the kernel image is on a partition
that the bootloader can read - ie RAID 0. This is nothing to do with auto-assembly.
So some questions:
* are the partitions 0xfd ? yes.
* is the kernel standard?
* are the superblocks version 0.9? (mdadm --examine /dev/component)
David
next prev parent reply other threads:[~2007-07-16 15:21 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-07-13 20:36 Raid array is not automatically detected Bryan Christ
2007-07-14 0:03 ` Zivago Lee
2007-07-14 2:09 ` Bryan Christ
2007-07-14 13:51 ` Bill Davidsen
2007-07-14 13:53 ` Justin Piszcz
2007-07-14 17:10 ` Bill Davidsen
2007-07-14 17:08 ` Justin Piszcz
2007-07-16 14:19 ` Bryan Christ
2007-07-16 15:21 ` David Greaves [this message]
2007-07-18 5:28 ` dean gaudet
2007-07-18 8:06 ` Justin Piszcz
2007-07-18 8:52 ` David Greaves
2007-07-18 14:39 ` Bryan Christ
2007-07-18 15:46 ` David Greaves
2007-07-18 15:49 ` Bryan Christ
2007-07-18 18:56 ` Bill Davidsen
2007-07-18 23:09 ` Neil Brown
-- strict thread matches above, loose matches on Subject: below --
2008-10-17 15:07 Daniel Reichelt
2008-10-17 18:40 ` Bryan Christ
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=469B8D05.1080003@dgreaves.com \
--to=david@dgreaves.com \
--cc=bryan.christ@hp.com \
--cc=davidsen@tmr.com \
--cc=jpiszcz@lucidpixels.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 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).