I built a new RAID1 using 13.1 YaST2 partitioner. This is the slightly condensed output from mdadm --detail --scan, with appended the 2 sda/sdb partitions making up each device: ARRAY /dev/md/md-tmp metadata=1.0 name=srv10:md-tmp UUID=... # P08 ARRAY /dev/md/mdroot1 metadata=1.0 name=srv10:mdroot1 UUID=... # P09 ARRAY /dev/md/mdroot2 metadata=1.0 name=srv10:mdroot2 UUID=... # P10 ARRAY /dev/md/mdroot3 metadata=1.0 name=srv10:mdroot3 UUID=... # P11 ARRAY /dev/md/mdroot4 metadata=1.0 name=srv10:mdroot4 UUID=... # P12 ARRAY /dev/md/md-srv metadata=1.0 name=srv10:md-srv UUID=... # P13 ARRAY /dev/md/md-usrl metadata=1.0 name=srv10:md-usrl UUID=... # P14 ARRAY /dev/md/md-home metadata=1.0 name=srv10:md-home UUID=... # P15 ARRAY /dev/md/md-pub metadata=1.0 name=srv10:md-pub UUID=... # P16 ARRAY /dev/md/md-isos metadata=1.0 name=srv10:md-isos UUID=... # P17 In using yast to build each md device, I took partitions in order from front to back of disks, so P08 comes from sda8 & sdb8, P09 from sda9 & sdb9, etc. In creating each md device, yast inexplicably skipped over md0 through md9, and used a range from md118 through md127, and assigned most without regard to the order given it. It gave 118 to the first, then 119 to the second, but scrambled the rest in what looks like semi-randomized inverse order: md118 = sda8 + sdb8 label: 1md08tmp md119 = sda9 + sdb9 label: 1md09root1 md120 = sda17 + sdb17 label: 1md17isos md121 = sda16 + sdb16 label: 1md16pub md122 = sda15 + sdb15 label: 1md15home md123 = sda14 + sdb14 label: 1md14usrl md124 = sda13 + sdb13 label: 1md13srv md125 = sda12 + sdb12 label: 1md12root4 md126 = sda10 + sdb10 label: 1md10root2 md127 = sda11 + sdb11 label: 1md11root3 After completing the YaST2 build process, I installed 13.1 on 1md09root1. This is the (condensed) mdadm.conf installation created, with appended the 2 sda/sdb partitions making up each device: DEVICE containers partitions ARRAY /dev/md/srv10:md-home UUID=99e6... ARRAY /dev/md/srv10:md-isos UUID=637f... # P17 ARRAY /dev/md/srv10:md-pub UUID=f825... # P16 ARRAY /dev/md/srv10:md-srv UUID=99d9... # P13 ARRAY /dev/md/srv10:md-tmp UUID=4c61... # P08 ARRAY /dev/md/srv10:md-usrl UUID=919d... # P14 ARRAY /dev/md/srv10:mdroot1 UUID=d0ef... # P09 ARRAY /dev/md/srv10:mdroot2 UUID=c37e... # P10 ARRAY /dev/md/srv10:mdroot3 UUID=b094... # P11 ARRAY /dev/md/srv10:mdroot4 UUID=5577... # P12 I'd like to get back the orderly simplicity of md0-md9 11.2's YaST2 RAID1 installation created. I don't like that yast incorporated the temporary hostname used to install either, so would like to see those gone. In order to try and get where I hope to go, I looked at the mdadm.conf man page. It makes my brain swim in confusion. Anyone know if it tells me I can, or how? Is mdadm.conf even the right place to look? Can I simply edit away the hostname portion, sort the balance into partition order, and have the boot process assign device names in predictable sequence each time? I tried rewriting mdadm.conf, using the following form: ARRAY /dev/md1 UUID=d0ef38d5:1a18ccdd:3fc41f94:5b274f89 # P09 13.1 ARRAY /dev/md2 UUID=c37e5de4:f454e44b:afe26e50:d920a464 # P10 13.2 and also rebuilding initrds via chroot. I can get the md devs recognized as md0-9 by booting something else chrooting from to use that mdadm.conf, but can't seem to get any boot process (initrd) to find any md device either by volume label or by filesystem UUID, even by having the raid modules explicit in /etc/sysconfig/kernel, or in a 13.2 installation rsync'd over from normal partition to the #3 md made from sd[ab]10. WRT 13.2, http://bugzilla.opensuse.org/show_bug.cgi?id=905863 is complicating things further. And, from 13.2 emergency shell, reboot fails, so I have to use the power/reset button to escape, while the no-installed-plymouth 13.1 emergency shell never provides a prompt, scrolling systemd received flush journal messages over and over and over. :~( -- "The wise are known for their understanding, and pleasant words are persuasive." Proverbs 16:21 (New Living Translation) Team OS/2 ** Reg. Linux User #211409 ** a11y rocks! Felix Miata *** http://fm.no-ip.com/ -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org