From: Moshe Yudkowsky <msha5_17@bl.com>
To: linux-hotplug@vger.kernel.org
Subject: 2.6.15 does not boot -- who creates RAID devices?
Date: Sun, 29 Jan 2006 01:04:58 +0000 [thread overview]
Message-ID: <43DC14BA.1000301@bl.com> (raw)
I can't boot 2.6.15; the problem is rather straightforward, but I'd like
a quick reality check from this list.
In 2.6.14, the device /dev/md/1 is started directly from the /init
script inside initrd.img using mdadm and UUIDs, using info that it
garners during LILO.
In 2.6.15, a script in /scripts/local-top/md calls /sbin/mdrun. mdrun
script explicitly uses mknod to create md devices 0 through 24, and then
calls mdadm to start these devices if they exist. Unfortunately, through
an error that I haven't yet uncovered, it starts the components that I
use for /dev/md/1 as /dev/md/0, my /dev/md/2 as /dev/md/1, etc. In turn,
this conflicts with /etc/fstab, my file system is never mounted, and the
boot stalls. (If anyone is interested, the script is part of the
initramfs tools and can be found, in the Debian distribution, in
/usr/share/initramfs-tools/scripts/local-top/md.)
Now, as far as I can tell from reading /etc/udev/compat-full.rules, the
role of udev is strictly post-device creation; it has no role, even in
theory, of starting these devices; udev just creates a symlink when it
finds out that some other script creates the md device.
Or am I missing something that udev does? I'm particularly perplexed
because the "mdrun" script has been around since 2003, and now it's
suddenly assembling devices in funny way; udev is more in flux. On the
other hand, 2.6.15 boots in a new way, and I suspect that's the culprit.
--
Moshe Yudkowsky
work: http://www.Disaggregate.com
book: http://www.PebbleAndAvalanche.com
-------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc. Do you grep through log files
for problems? Stop! Download the new AJAX search engine that makes
searching your log files as easy as surfing the web. DOWNLOAD SPLUNK!
http://sel.as-us.falkag.net/sel?cmd=lnk&kid\x103432&bid#0486&dat\x121642
_______________________________________________
Linux-hotplug-devel mailing list http://linux-hotplug.sourceforge.net
Linux-hotplug-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/linux-hotplug-devel
reply other threads:[~2006-01-29 1:04 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=43DC14BA.1000301@bl.com \
--to=msha5_17@bl.com \
--cc=linux-hotplug@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).