On Tuesday 03 February 2015 08:53:13 Todd Goodman wrote: > 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.
I think /dev/md127 is created and started by the installation disk regardless of your wishes. What I did (I think - it's some time ago now) is to issue an mdadm stop command on the automatically named devices, then assemble the device I wanted and proceed as before. Eventually the message sank home, though I can't remember the details. Like Alan, I too lost a good deal of sleep before that simple measure occurred to me. I now have /dev/md5, 6 and 7 working happily. Perhaps the installer was just trying to be helpful, but as so often happens, it achieved the reverse. Rather than booting the Gentoo installation disk, Alan might prefer to chroot from his existing system; that's what I do nowadays, and I find the hardware all set up ready. I don't use UUIDs (nor kernel-assigned network device names), preferring to use names I can read. To each his own, of course. -- Rgds Peter.
