linux-raid.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Bryan Christ <bryan.christ@hp.com>
To: linux-raid@vger.kernel.org
Subject: Raid array is not automatically detected.
Date: Fri, 13 Jul 2007 15:36:01 -0500	[thread overview]
Message-ID: <4697E231.3070906@hp.com> (raw)

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?

Bryan

             reply	other threads:[~2007-07-13 20:36 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-07-13 20:36 Bryan Christ [this message]
2007-07-14  0:03 ` Raid array is not automatically detected 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
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=4697E231.3070906@hp.com \
    --to=bryan.christ@hp.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).