From mboxrd@z Thu Jan  1 00:00:00 1970
From: Andrew Walrond <andrew@walrond.org>
Subject: Re: /dev/md* Device Files
Date: Wed, 26 Jan 2005 08:41:59 +0000
Message-ID: <200501260841.59090.andrew@walrond.org>
References: <Pine.LNX.4.61.0501251445420.6553@electra.rsc.raytheon.com> <Pine.LNX.4.56.0501260726100.12589@lion.drogon.net>
Mime-Version: 1.0
Content-Type: text/plain;
  charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
Return-path: <linux-raid-owner@vger.kernel.org>
In-Reply-To: <Pine.LNX.4.56.0501260726100.12589@lion.drogon.net>
Content-Disposition: inline
Sender: linux-raid-owner@vger.kernel.org
To: linux-raid@vger.kernel.org
List-Id: linux-raid.ids

On Wednesday 26 January 2005 07:28, Gordon Henderson wrote:
> On Tue, 25 Jan 2005, Steve Witt wrote:
> > 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?
>
> It's odd that they aren't there - they are with Debian 3.0, and have
> remained there when I've upgraded a few test servers to testing/Sarge.
>
>  # cd /dev
>  # ./MAKEDEV md
>
> should do the business.
>

A useful trick I discovered yesterday: Add --auto to your mdadm commandline 
and it will create the device for you if it is missing :)

Andrew Walrond