linux-raid.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Neil Brown <neilb@suse.de>
To: "Mr. James W. Laferriere" <babydr@baby-dragons.com>
Cc: linux-raid maillist <linux-raid@vger.kernel.org>
Subject: Re: raid6 array ,  part id 'fd' not assembling at boot .
Date: Sat, 17 Mar 2007 16:36:23 +1100	[thread overview]
Message-ID: <17915.32343.270875.583164@notabene.brown> (raw)
In-Reply-To: message from Mr. James W. Laferriere on Friday March 16

On Friday March 16, babydr@baby-dragons.com wrote:
>  	Hello All ,  I am having a dickens of a time with preparing this system 
> to replace my present one .
>  	I created a raid6 array over 6 147GB scsi drives .
>  	steps I followed were .
> 
>  	fdisk /dev/sd[c-h] ( one at a time of course )
>  	  created a partition starting at cyl 2 & -10 Cyls from the end of the drive .
>  	  typed the partion FD
>  	  w
>  	repeat until all six drives partitioned .
> 
>  	mdadm --create /dev/md3 --chunk=64 --metadata=1.2 --verbose --bitmap=internal --level=6 --raid-devices=6 --spare-devices=0 /dev/sd[cdefgh]1
>  	Built just fine .

In-kernel auto-assembly using partition type 0xFD only works for
metadata=0.90.  This is deliberate.

Don't use 0xFD partitions.  Use mdadm to assemble your array, either
via an initrd or (if it don't hold the root filesystem) via an init.d
script.

NeilBrown

  reply	other threads:[~2007-03-17  5:36 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-03-17  1:48 raid6 array , part id 'fd' not assembling at boot Mr. James W. Laferriere
2007-03-17  5:36 ` Neil Brown [this message]
     [not found]   ` <45FC3158.3020104@tmr.com>
2007-03-18 21:40     ` Neil Brown
     [not found]       ` <45FDC355.5000106@tmr.com>
2007-03-19  3:33         ` Mr. James W. Laferriere
2007-03-31 11:58           ` Nix

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=17915.32343.270875.583164@notabene.brown \
    --to=neilb@suse.de \
    --cc=babydr@baby-dragons.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).