linux-raid.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
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: Sun, 01 Jan 2006 22:12:29 +1100	[thread overview]
Message-ID: <87psncnqw2.fsf@rimspace.net> (raw)
In-Reply-To: dp52bc$nh8$1@sea.gmane.org

Max Waterman <davidmaxwaterman+gmane@fastmail.co.uk> writes:
> Daniel Pittman wrote:
>> Mitchell Laks <mlaks@verizon.net> writes:

[...]

>> 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.
>
> I am trying to do this with my 8 (currently only 7 since /dev/hdk is off
> line being replaced) disk raid5 array. mdadm --detail /dev/md0 gives :

[...]

>            UUID : 15bfec75:595ac793:0914f8ee:862effd8

[...]

> I am confused why there are only 4 UUIDs, when there are 7 devices
> listed...what should I put in my mdadm.conf file, which is currently 

You surely are confused, but there is only *one* UUID there, not four.

The UUID is presented as four blocks, with a ':' between them, by mdadm
for some reason beyond my understanding, but it is really just one
string.

Also, the UUID is per *MD* device, not per compontent (hda, sda) device.

So, you list the UUID for the array that mdadm told you as-is.

    Daniel


  reply	other threads:[~2006-01-01 11:12 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
2005-12-31  4:40   ` Max Waterman
2006-01-01 11:12     ` Daniel Pittman [this message]
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=87psncnqw2.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).