All of lore.kernel.org
 help / color / mirror / Atom feed
From: Richard Scobie <richard@sauce.co.nz>
To: Linux RAID Mailing List <linux-raid@vger.kernel.org>
Subject: Re: new array not starting
Date: Wed, 08 Nov 2006 15:53:30 +1300	[thread overview]
Message-ID: <455146AA.6060208@sauce.co.nz> (raw)
In-Reply-To: <eirfst$pd7$1@sea.gmane.org>

Robin Bowes wrote:
> Robin Bowes wrote:
> 
>>This worked:
>>
>># mdadm --assemble --auto=yes  /dev/md2 /dev/sdc /dev/sdd /dev/sde
>>/dev/sdf /dev/sdg /dev/sdh /dev/sdi /dev/sdj
>>mdadm: /dev/md2 has been started with 8 drives.
>>
>>However, I'm not sure why it didn't start automatically at boot. Do I
>>need to put it in /etc/mdadm.conf for it to star automatically? I
>>thought md start all arrays it found at a start up?
> 
> 
> OK, I put /dev/md2 in /etc/mdadm.conf and it didn't make any difference.
> 
> This is mdadm.conf (uuids are on same line as ARRAY):
> 
> DEVICE partitions
> ARRAY /dev/md1 level=raid1 num-devices=2
> uuid=300c1309:53d26470:64ac883f:2e3de671
> ARRAY /dev/md0 level=raid1 num-devices=2
> uuid=89649359:d89365a6:0192407d:e0e399a3
> ARRAY /dev/md2 level=raid6 num-devices=8
> UUID=68c2ea69:a30c3cb0:9af9f0b8:1300276b
> 
> I saw an error fly by as the server was booting saying "/dev/md2 not found".
> 
> Do I need to create this device manually?

Try adding

auto=part

at the end of the /dev/md2 entry.

Regards,

Richard

      parent reply	other threads:[~2006-11-08  2:53 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
2006-11-08 16:58       ` Bill Davidsen
2006-11-08  2:53     ` Richard Scobie [this message]

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=455146AA.6060208@sauce.co.nz \
    --to=richard@sauce.co.nz \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.