From: "J. Ryan Earl" <ryan@dynaconnections.com>
To: Steve Witt <sawitt@electra.rsc.raytheon.com>, linux-raid@vger.kernel.org
Subject: RE: /dev/md* Device Files
Date: Wed, 26 Jan 2005 16:10:54 -0600 [thread overview]
Message-ID: <OMEKLMBKKEOEENCKLEIDKECLCBAA.ryan@dynaconnections.com> (raw)
In-Reply-To: <Pine.LNX.4.61.0501251445420.6553@electra.rsc.raytheon.com>
Did you have the md module inserted into the kernel at this point? It
should automatically the md device entries for you, at least it does with
udev-045.
-ryan
-----Original Message-----
From: linux-raid-owner@vger.kernel.org
[mailto:linux-raid-owner@vger.kernel.org]On Behalf Of Steve Witt
Sent: Tuesday, January 25, 2005 4:54 PM
To: linux-raid@vger.kernel.org
Subject: /dev/md* Device Files
I'm installing a software raid system on a new server that I've just
installed Debian 3.1 (sarge) on. It will be a raid5 on 5 IDE disks using
mdadm. I'm trying to create the array with 'mdadm --create /dev/md0 ...'
and am getting an error: 'mdadm: error opening /dev/md0: No such file or
directory'. There are no /dev/md* devices in /dev at the present time. I
do have the md and raid5 kernel modules loaded. My question is: how do the
/dev/md* files get created? Are they normal device file that are created
with MAKEDEV?
Thanks...
-
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
prev parent reply other threads:[~2005-01-26 22:10 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-01-25 22:54 /dev/md* Device Files Steve Witt
2005-01-26 7:28 ` Gordon Henderson
2005-01-26 8:41 ` Andrew Walrond
2005-01-26 19:02 ` Steve Witt
2005-01-26 23:21 ` Neil Brown
2005-01-26 23:51 ` Mike Hardy
2005-01-26 22:10 ` J. Ryan Earl [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=OMEKLMBKKEOEENCKLEIDKECLCBAA.ryan@dynaconnections.com \
--to=ryan@dynaconnections.com \
--cc=linux-raid@vger.kernel.org \
--cc=sawitt@electra.rsc.raytheon.com \
/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).