From: Samuel Tardieu <tardieu@gmail.com>
To: schmidt@naa.net
Cc: linux-raid@vger.kernel.org
Subject: Re: Debian/raid1/mdadm/devices not created at boot time
Date: Wed, 15 Dec 2004 13:54:01 +0100 [thread overview]
Message-ID: <e626068b04121504545fbb93cf@mail.gmail.com> (raw)
In-Reply-To: <41C031FD.1020809@chemie.uni-erlangen.de>
> I just overflew the link you gave. There the partition type "fd"
> approach is used, which needs either compiled-in raid functionality or
> raid as a module in the initial ramdisk (which is both at least fo Woody
> not the standard case; I built a bootable cd with a kernel with
> compiled-in raid support so that I could install directly onto a raid).
I have raid as a module in the initrd.
> If you want the disks to be started by the mdadm call in that script,
> then the devices shouldn´t be assembled (or even tried to) by
> autodetection before. Try changing the type back to 83/82 or whatever fs
> you use.
It won't change anything (I had 83 before I noticed I forgot this
part), but I understand what you're saying.
> What exactly does lead you to the thought that /dev/md0 and /dev/md1 do
> not exist? Are the actual entries in /dev issing? If so, why are they
> missing again after you made them wit MAKEDEV?
When I get the maintenance root prompt, I see that /dev/md0 and
/dev/md1 are missing from /dev. When I reboot, they have disappeared
again.
Although nothing appears in mnttab, I suspect my system may be using devfs:
willow# df -k /dev
Filesystem 1K-blocks Used Available Use% Mounted on
none 5120 2944 2176 58% /dev
At boot time, no entries are created in this devfs for /dev/md0 and
/dev/md1. How can I create them? I thought loading the md module from
initrd would be enough but it looks like it isn't.
Sam
-
To unsubscribe from this list: send the line "unsubscribe linux-raid" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2004-12-15 12:54 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-12-15 9:38 Debian/raid1/mdadm/devices not created at boot time Samuel Tardieu
[not found] ` <41C031FD.1020809@chemie.uni-erlangen.de>
2004-12-15 12:54 ` Samuel Tardieu [this message]
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=e626068b04121504545fbb93cf@mail.gmail.com \
--to=tardieu@gmail.com \
--cc=linux-raid@vger.kernel.org \
--cc=sam@rfc1149.net \
--cc=schmidt@naa.net \
/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).