![](https://seccdn.libravatar.org/avatar/3035b38ff33cf86f480bb169b8500b80.jpg?s=120&d=mm&r=g)
https://bugzilla.novell.com/show_bug.cgi?id=811830
https://bugzilla.novell.com/show_bug.cgi?id=811830#c21
--- Comment #21 from Michael Chang
Created an attachment (id=538562) --> (http://bugzilla.novell.com/attachment.cgi?id=538562) [details] YaST2 BootGRUB2.ycp patch to enable Linux MD recognition
The patch looks good to me. Without it you'll have to go the the yast bootloader setting page, see redundancy array enabled AND you must click the OK to save it to true to get the redundancy really work. Otherwise it will be regular, non redundancy installation although the UI default says it's enabled, it's underlying is a uninitialized nil value. I was fooled by the buggy behavior during my testing.
BootGRUB2.pm did not initialize Linux MD state (see first attached patch). I do not know whether it was intentional. This patch does enable processing of both array members, but due to the way it is implemented it is *extremely* dangerous. pbl just calls grub2-install two times. If grub2 could be embedded in both cases, that's OK. If grub2 could *not* be embedded, openSUSE forces it to use blocklists. Second invocation of grub2-install will recreate core.img, rendering grub2 on first drive unbootable.
We should distinguish the options in perl bootloader. Believe or not it's not as easy as it should be ... $ MBR : <NO OPTIONS> $ BOOT AND ROOT Partition : --force $ EXTENDED : --force --skip-fs-probe $ CUSTOM : <DETECT and pick the best>
I'm still having this on my TODO list, but I still do not have clean way to support multiple install devices. Or, better said - it requires much more efforts than I want to spend on it.
What is worse, even if we remove "--force" parameter, second grub2-install invocation still recreates core.img potentially rendering grub2 on the first disk unbootable.
Why? Isn't core.img was embedded already to first disk ? The recreated file should not destroy it.
I'll get a look once more what can be done here.
Thanks. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.