linux-raid.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Bryan Christ <bryan.christ@hp.com>
To: Justin Piszcz <jpiszcz@lucidpixels.com>
Cc: Bill Davidsen <davidsen@tmr.com>, linux-raid@vger.kernel.org
Subject: Re: Raid array is not automatically detected.
Date: Mon, 16 Jul 2007 09:19:33 -0500	[thread overview]
Message-ID: <469B7E75.3030907@hp.com> (raw)
In-Reply-To: <Pine.LNX.4.64.0707140952440.31528@p34.internal.lan>

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.

Justin Piszcz wrote:
> 
> 
> On Sat, 14 Jul 2007, Bill Davidsen wrote:
> 
>> Bryan Christ wrote:
>>> My apologies if this is not the right place to ask this question. 
>>> Hopefully it is.
>>>
>>> I created a RAID5 array with:
>>>
>>> mdadm --create /dev/md0 --level=5 --raid-devices=5 /dev/sda1 
>>> /dev/sdb1 /dev/sdc1 /dev/sdd1 /dev/sde1
>>>
>>> mdadm -D /dev/md0 verifies the devices has a persistent super-block, 
>>> but upon reboot, /dev/md0 does not get automatically assembled (an 
>>> hence is not a installable/bootable device).
>>>
>>> I have created several raid1 arrays and one raid5 array this way and 
>>> have never had this problem.  In all fairness, this is the first time 
>>> I have used mdadm for the job.  Usually, I boot to something like 
>>> SysRescueCD, used raidtools to create my array and then reboot with 
>>> my Slackware install CD.
>>>
>>> Anyone know why this might be happening? 
>>
>> Old type arrays are assembled due to having the proper partition type, 
>> 0xfd "Linux auto RAID" and are assembled by the kernel. All others are 
>> assembled by mdadm running out of initrd or similar, and failures 
>> there result from not having a proper config file in the initrd image.
>>
>> IIRC raidtools does set the array partitions to the auto-assemble 
>> partition type. Hope that points you in the right direction. Running
>>   "fdisk -l"
>> as root will let you see all the partitions, types, etc, for 
>> everything on your system.
>>
>> I may be wrong, I thought auto-assemble only worked with type 0 or 1.
>>
>> -- 
>> bill davidsen <davidsen@tmr.com>
>> CTO TMR Associates, Inc
>> Doing interesting things with small computers since 1979
>>
>> -
>> To unsubscribe from this list: send the line "unsubscribe linux-raid" in
>> the body of a message to majordomo@vger.kernel.org
>> More majordomo info at  http://vger.kernel.org/majordomo-info.html
>>
> 
> I use auto-assemble (in conjunction with Debian's own startup scripts) 
> and for my root RAID1 device,swap and /boot, it is automatically taken 
> care of by the kernel.  For RAID5, it seems to work the same:
> 
> [   58.919378] RAID5 conf printout:
> [   58.919418]  --- rd:10 wd:10
> [   58.919457]  disk 0, o:1, dev:sdc1
> [   58.919498]  disk 1, o:1, dev:sdd1
> [   58.919539]  disk 2, o:1, dev:sde1
> [   58.919579]  disk 3, o:1, dev:sdf1
> [   58.919619]  disk 4, o:1, dev:sdg1
> [   58.919659]  disk 5, o:1, dev:sdh1
> [   58.919719]  disk 6, o:1, dev:sdi1
> [   58.919759]  disk 7, o:1, dev:sdj1
> [   58.919799]  disk 8, o:1, dev:sdk1
> [   58.919839]  disk 9, o:1, dev:sdl1
> 
> Justin.

  parent reply	other threads:[~2007-07-16 14:19 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 [this message]
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
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=469B7E75.3030907@hp.com \
    --to=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).