All of lore.kernel.org
 help / color / mirror / Atom feed
From: Henrik Holst <henrik.holst@idgmail.se>
To: John Reeves <john.reeves@mailc.net>
Cc: linux-raid@vger.kernel.org
Subject: Re: Ubuntu - RAID Array not "assembling" on boot.
Date: Tue, 21 Nov 2006 21:13:00 +0100	[thread overview]
Message-ID: <45635DCC.3010500@idgmail.se> (raw)
In-Reply-To: <1164139592.12278.276853539@webmail.messagingengine.com>

John Reeves wrote:
> Hey,
> 
> Having a great deal of difficulty getting my 3 disk RAID 5 array to
> reappear on restart, Ubuntu 6.10.  Here's the contents of my
> /etc/mdadm/mdadm.conf file:
> 
> ARRAY /dev/md0 level=raid5 num-devices=3
> UUID=6a9a102a:101addd2:f95758f6:11ac6d3c 
> 
> Obviously /dev/md0 does not "appear" on restart, the only way I can get
> the RAID Array to assemble is to issue the following:
> 
> mknod -m 0660 /dev/md0 b 9 0
> mdadm --assemble /dev/md0 /dev/sda1 /dev/sdb1 /dev/sdc1
> 
> I can add these lines to my /etc/init.d/bootmisc.sh which does work, but
> seeing as I'm not 100% sure what the mknod command is doing, and the
> fact that I'm pretty sure that this is not the way it's mean to be... 
> (the mknod is required, or mdadm complains that /dev/md0 does not
> exist).  
> 
> I'm nearly tearing my hair out over this one, so if someone could be of
> assistance I would be greatly appreciative.

Try "dpkg-reconfigure mdadm" as root. Under Debian this will give you
the chance to configure the startup configuration for all software raids
in the system. Under any cirtumstances you should not have to use mknod.
Instead try adding the --auto=yes switch to mdadm. Then mdadm will
create the node itself.

/Henrik Holst


  reply	other threads:[~2006-11-21 20:13 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-11-21 20:06 Ubuntu - RAID Array not "assembling" on boot John Reeves
2006-11-21 20:13 ` Henrik Holst [this message]
2006-11-21 22:26   ` John Reeves
2006-11-22  7:43     ` dean gaudet
2006-11-22 15:41     ` Gabor Gombas
2006-11-21 20:25 ` dean gaudet

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=45635DCC.3010500@idgmail.se \
    --to=henrik.holst@idgmail.se \
    --cc=john.reeves@mailc.net \
    --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.