27.11.2015 17:26, garrett.timmins@speedymail.org пишет:
Andrei
command the right command?
No. You always should change bootloader using YaST bootloader module. This ensures that configuration is correctly updated and the right bootloader will be reconfigured when you add/remove kernels.
I'll use the UI but I'd like to also understand what the UI's doing.
Is there a guide to the equivalent manual steps that using the UI represents?
Not that I'm aware of. Sources are open if you are really interested.
Since I have '/boot' partition on a 4-disk RAID-1 array, what's the right way to install grub2 as the bootloader default on that array?
You should install GRUB2 in MBR of each disk if you want full redundancy.
Just to be clear, that means which of the two boxes in the UI
[ ] Boot from Master Record [ ] Write Generic Boot Code to MBR
?
None of them. MBR here means "MBR of the first disk", in whatever disk order YaST finds them.
Do I execute grub2-install 4 times, once for each drive?
grub2-install /dev/sda grub2-install /dev/sdb grub2-install /dev/sdc grub2-install /dev/sdd
Yes, at this time this means running grub-install 4 times.
Unfortunately I am not sure whether YaST actually supports this configuration. It does support 2-way mirror (i.e. RAID1 consisting of two drives). In this case you should see checkbox "Enable MD redundancy" or similar' checking it (it is not default) will cause YaST to automatically configure bootloader location in MBR of each drive.
In that same Yast2 module? In the BootLoader module I don't find any redundancy-related checkbox.
What exactly you did? Which bootloader is currently selected?
But at the Yast2 BootLoader module's
Boot Loader Settings > Boot Code Options > Boot Loader Installation Details
I do get a dialog that lists four drives by-id
Disk Order
That is irrelevant (it only affects which disk is considered first for MBR install). ...
How can I verify that all four drives get the data?
One possibility is https://github.com/arvidjaar/bootinfoscript -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org