Re: Further question(s)

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

 



Shouldn't make any difference.

/dev/md0 is the old-style numbered array.

/dev/md/0 is the new-style named array.

(And the link between numbering and default names is obvious :-)

I just find it slightly odd that it isn't /dev/md127 - the default numbering now counts down from 0xff.

Bear in mind I don't have an mdadm.conf, a couple of ideas to play with are (1) what happens if you boot without an mdadm.conf? (2) what do you get if you regenerate your mdadm.conf (especially if you boot without one)?

I'm guessing your current mdadm.conf is affecting things, and seeing as I've never needed one, I can't really advise ...

Cheers,
Wol

On 01/05/2018 12:59, o1bigtenor wrote:
Greetings

Looking further into things trying to determine what is hindering my
raid array access I'm finding this int # mdadm.conf

ARRAY /dev/md/0 metadata=1.2 UUID . . .

is this supposed to be /dev/md/0   or is it supposed to read /dev/md0  ?

If so where do I change it?

TIA

Dee
--
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

--
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