From: Samuel Tardieu <sam@rfc1149.net>
To: linux-raid@vger.kernel.org
Subject: Debian/raid1/mdadm/devices not created at boot time
Date: 15 Dec 2004 10:38:04 +0100 [thread overview]
Message-ID: <87r7lrnbpf.fsf@beeblebrox.rfc1149.net> (raw)
Hi.
I have migrated my Debian -unstable system to raid1 handled by madm as
directed in http://xtronics.com/reference/SATA-RAID-debian-for%202.6.html.
I use Linux 2.6.9, / is on md2, /boot on md0 and swap on md1. I use
mdadm 1.7.0 (the one shipped with Debian).
At boot time, the kernel correctly boots from md2 but init fails to
mount md0 as /boot and setup the swap space on md1 as those devices do
not exist.
If I create them by hand with "cd /dev && ./MAKEDEV md" when I get a
root shell for maintenance and start them using "mdadm -A -s", I can
continue the boot process manually.
The partition types are set to 0xfd, /proc/mdstat reports:
Personalities : [raid1]
md0 : active raid1 sda1[0] sdb1[1]
192640 blocks [2/2] [UU]
md1 : active raid1 sda5[0] sdb5[1]
1951744 blocks [2/2] [UU]
md2 : active raid1 sda6[0] sdb6[1]
37110016 blocks [2/2] [UU]
unused devices: <none>
As far as I can tell, the "mdadm-raid" script which does "mdadm -A -s"
is present as /etc/rcS.d/S25mdadm-raid which is a right place as it
will be run before mounting other file systems. However, the absence
of /dev/md0 and /dev/md1 prevent the raid arrays from being started.
What can I do to ensure that /dev/md0 and /dev/md1 exist when the
script is run?
Sam
--
Samuel Tardieu -- sam@rfc1149.net -- http://www.rfc1149.net/sam
next reply other threads:[~2004-12-15 9:38 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-12-15 9:38 Samuel Tardieu [this message]
[not found] ` <41C031FD.1020809@chemie.uni-erlangen.de>
2004-12-15 12:54 ` Debian/raid1/mdadm/devices not created at boot time Samuel Tardieu
2004-12-15 12:57 ` Norman Schmidt
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=87r7lrnbpf.fsf@beeblebrox.rfc1149.net \
--to=sam@rfc1149.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 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).