I have set up a pair of disks as RAID10 (“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?
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?
Root Device:
/dev/fd0
/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/sda2
/dev/sda3
/dev/sda4
/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)
/dev/sdd2
/dev/sdd3
/dev/sdd4
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:
resume=/dev/disk/by-id/ata-Hitachi_HDS721616PLAT80_PV1301Z2SXER5A-part1 showopts
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?
How do I put the boot loader to both disks? There is a “Boot Loader Installation” section but it has no provision for which disk to install the loader.
How do I set up GRUB to load from one of the disks?
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?
Root Device:
/dev/fd0
/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/sda2
/dev/sda3
/dev/sda4
/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)
/dev/sdd2
/dev/sdd3
/dev/sdd4
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:
resume=/dev/disk/by-id/ata-Hitachi_HDS721616PLAT80_PV1301Z2SXER5A-part1 showopts
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).
It would be interesting to look at YaST log in your case (/var/log/YaST2/y2log).
The log file (for Aug 18 - Aug 21) is 8MB and some of the entries are 1200 characters long. Not the “interesting” you were thinking, though. I do not know which parts you would find interesting.
Where exactly do you see this?
It is the contents of the dropdown list for the “Root partition” option in YaST:: Boot Loader. The boot loader location is set to “Boot from Root Partition,” not “Boot from Master Boot Record.”
The log file (for Aug 18 - Aug 21) is 8MB and some of the entries are 1200 characters long. Not the “interesting” you were thinking, though. I do not know which parts you would find interesting.
The part which logs your invocation of yast - bootloader. “bzip2 -9” should compress it pretty well.
It is the contents of the dropdown list for the “Root partition” option in YaST:: Boot Loader. The boot loader location is set to “Boot from Root Partition,” not “Boot from Master Boot Record.”
Funny, I do not even see this drop down list (in bootloader configuration). Which bootloader did you select? Could you describe step by step how you get to this screen?
RAID1+0 is working for me but with intel software / fake raid and 4 hard drives so I believe it should work with two hard drives too (the system was upgraded from 12.2 though.)
The booting was broken few times due to some bugs in 12.2 and required manual interventions but I believe they closed those bugs in 12.3