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.
How should we proceed here? What solutions are available and which one do we want to aim
for?
Am 01.07.2022 um 17:35 schrieb Chris Murphy
<lists(a)colorremedies.com>:
On Fri, Jul 1, 2022 at 2:12 AM Peter Boy <pboy(a)uni-bremen.de> wrote:
>
> As discussed on our meeting I created an issue
(
https://pagure.io/fedora-server/issue/89) for this matter. According to my tests,
software raid is working with uefi booting.
I added a comment to the article,
https://pagure.io/fedora-server/issue/89#comment-804315 that employing
Linux RAID 1 on the EFI System partition is not an acceptable way of
syncing EFI system partitions. The only way it could be reliable is if
you can guarantee no writes to the file system outside of the kernel's
md driver, which is not certain. The firmware has write access, as do
EFI programs and those exist outside the Linux RAID driver leading to
out of sync EFI System partitions.
--
Chris Murphy
_______________________________________________
server mailing list -- server(a)lists.fedoraproject.org
To unsubscribe send an email to server-leave(a)lists.fedoraproject.org
Fedora Code of Conduct:
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines:
https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives:
https://lists.fedoraproject.org/archives/list/server@lists.fedoraproject.org
Do not reply to spam on the list, report it:
https://pagure.io/fedora-infrastructure