linux-raid.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Kevin P. Fleming" <kpfleming@starnetworks.us>
Cc: linux-raid@vger.kernel.org
Subject: Re: error opening /dev/md2: No such file or directory
Date: Thu, 02 Dec 2004 11:30:50 -0700	[thread overview]
Message-ID: <41AF5F5A.4090709@starnetworks.us> (raw)
In-Reply-To: <conlcb$14p$1@sea.gmane.org>

Robin Bowes wrote:

> # mdadm --create /dev/md2 --level=1 --raid-devices=2 /dev/sdc1 missing
> mdadm: error opening /dev/md2: No such file or directory

This is a side-effect of the way that the MD driver operates in a 
dynamic /dev environment. mdadm needs the /dev/mdX node to be available 
to be able to manipulate the array, but it doesn't exist until the array 
has been created. Catch-22.

At some point mdadm and the MD driver need a new communication method 
that uses a common device node for all arrays, but that won't happen soon.

In the meantime, you can manually create /dev/mdX nodes with mknod, just 
as you would have done before. Once the array is created, if you have it 
set to auto-start (using 0xfd partition types), it the device node will 
automatically appear when you boot your system. If you don't have it set 
to auto-start, you'll have to add the "mknod" command to your system 
startup scripts before trying to start the array directly.

  reply	other threads:[~2004-12-02 18:30 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-12-02 18:03 error opening /dev/md2: No such file or directory Robin Bowes
2004-12-02 18:30 ` Kevin P. Fleming [this message]
2004-12-02 18:37   ` Robin Bowes
2004-12-02 20:43 ` Luca Berra

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=41AF5F5A.4090709@starnetworks.us \
    --to=kpfleming@starnetworks.us \
    --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).