Is it RAID1 (as in subject) or RAID10? These are two quite different things.
(“software” RAID using mdadm) and transferred all of the data from the existing single system disk to the RAID pair.
I know to change the BIOS to look at (one or both of) the disks to find a loader.
I am rather confused by YaST::Boot Loader. It indicates that /dev/md0 is a valid boot target. Is this true?
I tested installation of 12.3 on single MD RAID1 (only root partition, nothing else) and it does not offer /dev/md0; it offers MBR and additional check box for “Enable MD RAID redundancy”. It did install grub2 on MBR of both disks. It would be interesting to look at YaST log in your case (/var/log/YaST2/y2log).
The RAID pair is /dev/sda and /dev/sdd. I notice no UUID is given for those devices. Are they a poor choice for booting?
/dev/md0 (mount by ID: md-uuid-cc36f1ac:0474ddb2:9d9a7933:ecf628f0)
/dev/md1 (mount by ID: md-uuid-ff236a4d:0a2bc0f2:1c73f475:9d30a821)
/dev/md2 (mount by ID: md-uuid-769ea2bc:693217d2:300ab260:03f93644)
/dev/sdb1 (mount by ID: ata-ST3250318AS_9VY5AJKT-part1)
/dev/sdc2 (mount by ID: ata-Hitachi_HDS721616PLAT80_PV1301Z2SXER5A-part2)
/dev/sdc3 (mount by ID: ata-Hitachi_HDS721616PLAT80_PV1301Z2SXER5A-part3)
Where exactly do you see this?
Another bothersome entry is the “resume=” value. It remains the original system disk. Should not that have changed as well? A failing in YaST?
Optional Kernel Command Line Parameter:
When I look at “Boot Loader Installation Details,” it shows only the original system disk. Shouldn’t either the RAID disks or the RAID itself be listed?
That I do not know (i.e. I do not know whether this is actually possible).