From: Bryan Christ <bryan.christ@hp.com>
To: David Greaves <david@dgreaves.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: Wed, 18 Jul 2007 09:39:34 -0500 [thread overview]
Message-ID: <469E2626.30204@hp.com> (raw)
In-Reply-To: <469B8D05.1080003@dgreaves.com>
I'm now very confused...
When I run mdadm --examine /dev/md0 I get the error message: No
superblock detected on /dev/md0
However, when I run mdadm -D /dev/md0 the report clearly states
"Superblock is persistent"
/dev/md0:
Version : 00.90.03
Creation Time : Tue Jul 17 10:17:37 2007
Raid Level : raid5
Array Size : 1953535744 (1863.04 GiB 2000.42 GB)
Used Dev Size : 488383936 (465.76 GiB 500.11 GB)
Raid Devices : 5
Total Devices : 5
Preferred Minor : 0
Persistence : Superblock is persistent
Update Time : Wed Jul 18 10:17:34 2007
State : clean
Active Devices : 5
Working Devices : 5
Failed Devices : 0
Spare Devices : 0
Layout : left-symmetric
Chunk Size : 64K
UUID : ea6c5a9f:021b4ff8:fc5a08c4:23fc5c4b
Events : 0.4
Number Major Minor RaidDevice State
0 8 1 0 active sync /dev/sda1
1 8 17 1 active sync /dev/sdb1
2 8 33 2 active sync /dev/sdc1
3 8 49 3 active sync /dev/sdd1
4 8 65 4 active sync /dev/sde1
David Greaves wrote:
> 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-18 14:39 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
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 [this message]
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=469E2626.30204@hp.com \
--to=bryan.christ@hp.com \
--cc=david@dgreaves.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).