From: Robin Bowes <robin-lists@robinbowes.com>
To: linux-raid@vger.kernel.org
Subject: Re: new array not starting
Date: Wed, 08 Nov 2006 12:55:33 +0000 [thread overview]
Message-ID: <eisk45$1ef$1@sea.gmane.org> (raw)
In-Reply-To: <eirgp8$rd7$1@sea.gmane.org>
Robin Bowes wrote:
>
> Well, at the risk of having a complete conversation with myself, I've
> created partitions of type "fd" on each disk and re-created the array
> out of the partitions instead of the whole disk.
>
> mdadm --create /dev/md2 --auto=yes --raid-devices=8 --level=6 /dev/sdc1
> /dev/sdd1 /dev/sde1 /dev/sdf1 /dev/sdg1 /dev/sdh1 /dev/sdi1 /dev/sdj1
>
> I'm hoping this will enable the array to be auto-detected and started at
> boot.
That seemed to do the trick.
I left the array to build overnight and rebooted this morning, and
/dev/md2 started normally.
R.
next prev parent reply other threads:[~2006-11-08 12:55 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-11-08 1:59 new array not starting Robin Bowes
2006-11-08 2:12 ` Robin Bowes
2006-11-08 2:37 ` Robin Bowes
2006-11-08 2:52 ` Robin Bowes
2006-11-08 12:55 ` Robin Bowes [this message]
2006-11-08 16:58 ` Bill Davidsen
2006-11-08 2:53 ` Richard Scobie
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='eisk45$1ef$1@sea.gmane.org' \
--to=robin-lists@robinbowes.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).