From: Daniel Pittman <daniel@rimspace.net>
To: linux-raid@vger.kernel.org
Subject: Re: hard drives with "variable" device names - mdadm raid assembly options setup
Date: Sat, 31 Dec 2005 11:44:32 +1100 [thread overview]
Message-ID: <87d5jep027.fsf@rimspace.net> (raw)
In-Reply-To: 200512300908.19390.mlaks@verizon.net
Mitchell Laks <mlaks@verizon.net> writes:
G'day Mitchell.
> I notice on my system that the hard drives "device names" can change.
>
> The hard drives are connected to the motherboard SATA connectors or to
> PCI SATA cards. They get different "names" /dev/sda or /dev/sdc
> depending how many of the cards are "active".
>
> For instance the hard drives on the motherboard itself are called
> /dev/sde and /dev/sdf if there are hard drives on the 2 PCI cards and
> are called /dev/sda and /dev/sdb if there are none.
Well, one solution is udev, but since you prefer to avoid that...
[...]
> Now I am confused: unfortunately this does not seem to help me:
> if it relys on the configuration file /etc/mdadm/mdadm.conf
> this config file - i create with the aid of mdadm --detail --scan
> seems to still have the (problematic) "variable" device names in it.
...you can simply remove the 'device names' variable, and list the
theoretically possible devices for MD stuff in the configuration:
DEVICE /dev/hd*
DEVICE /dev/sd*
That will include all the IDE and SCSI disks (including SATA), so they
will be scanned at an appropriate time.
Then, list your arrays:
ARRAY /dev/md2 level=raid1 num-devices=2 UUID=529d70fa:e5fe992b:ceb05593:bfcc6c25
That will cause mdadm to scan all those device entries (all the disks
and partitions) looking for an array with the right UUID, and assemble
it from all the components it finds.
Regards,
Daniel
next prev parent reply other threads:[~2005-12-31 0:44 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-12-30 14:08 hard drives with "variable" device names - mdadm raid assembly options setup Mitchell Laks
2005-12-31 0:44 ` Daniel Pittman [this message]
2005-12-31 4:40 ` Max Waterman
2006-01-01 11:12 ` Daniel Pittman
2006-01-27 11:39 ` Matthias Urlichs
2005-12-31 12:01 ` Luca Berra
2005-12-31 13:09 ` Gregory Seidman
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=87d5jep027.fsf@rimspace.net \
--to=daniel@rimspace.net \
--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).