On Sun, Jul 3, 2022 at 5:25 PM Peter Boy <pboy(a)uni-bremen.de> wrote:
I have added all available variants to the test cases.
Judging from the warning messages Anaconda issues, Anaconda explicitly expects that both
boot loaders (stage 1 and stage 2) should be on a raid each (or none).
The Anaconda developers will have read the technical specs as well, I think.
My understanding is it was done for a RHEL customer, but it's still
not at all supported by upstream mdadm developers and not recommended.
How should we proceed here? What solutions are available and which
one do we want to aim for?
Unfortunately there is no recommended work around. About the best we
have is bootupd.
https://github.com/coreos/bootupd
About the best that can be done is documentation that recommends the
sysadmin manually create an ESP on each RAID member. Then copy the
"canonical" ESP's contents, the one mounted at /boot/efi, to each of
the ESPs. While those additional ESPs will not ever have their shim
and GRUB bootloaders updated when the canonical one is updated, it
should still work as a fallback booth method should the drive
containing the canonical ESP fail.
--
Chris Murphy