Re: hard drives with "variable" device names - mdadm raid assembly options setup

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Max Waterman <davidmaxwaterman+gmane@xxxxxxxxxxxxxx> writes:
> Daniel Pittman wrote:
>> Mitchell Laks <mlaks@xxxxxxxxxxx> 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

-
To unsubscribe from this list: send the line "unsubscribe linux-raid" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html

[Index of Archives]     [Linux RAID Wiki]     [ATA RAID]     [Linux SCSI Target Infrastructure]     [Linux Block]     [Linux IDE]     [Linux SCSI]     [Linux Hams]     [Device Mapper]     [Device Mapper Cryptographics]     [Kernel]     [Linux Admin]     [Linux Net]     [GFS]     [RPM]     [git]     [Yosemite Forum]


  Powered by Linux