Re: [gentoo-user] Boot disk "renames" /dev/md6 to /dev/md127.

[Todd Goodman]

* Rich Freeman <rich0@g.o> [150203 08:36]:
> On Tue, Feb 3, 2015 at 8:14 AM, Alan Mackenzie <acm@×××.de> wrote:
> > So, what was it that chewed up my RAID configuration so badly that
> > /dev/md6 got renamed to /dev/md127?  Can I change it back to /dev/md6,
> > somehow?  Do I need to bother?
>
> I ran into similar issues a while back.  In my case some of my arrays
> were using older metadata (which was required at the time to boot
> without an initramfs).  I suspect that either this metadata lacked the
> info needed for a boot CD to assign the same ID, or perhaps the ID I
> was using was already allocated somehow and the boot CD chose another
> one and wrote that ID to the metadata so that it stuck.
>
> My solution was to move to using UUIDs or labels for everything and
> not relying on array numbering.  This of course requires an initramfs
> - personally I've found Dracut to be the best one out there.  It is
> just far less prone to breakage when some update causes stuff to move
> around like this.

I also had the same problem a while ago and like Rich I started using
UUIDs (actually I had started on another system where it mounted my
/home partition as /tmp and rm -rf'd it during startup because of the
/dev/md devices being scrambled around, but at that point I switched all
my systems to UUIDs.)

I also use dracut and aside from some problems with it starting up my
raid arrays, it works well and I don't think much about it.

Todd