On Di, 14.10.25 22:43, Chris Murphy ([email protected]) wrote: > Last time this came up (5ish years ago) they said no because it's > too simple, doesn't support enough of RHEL's use cases. And that > they had insufficient bandwidth for more work. > > And it's the same in Fedora. Fedora Server can't use systemd-boot or > plain FAT only $BOOT, because they require support for /boot on > mdadm raid1. Same with CentOS and RHEL.
Sorry, but using mdadm raid1 in the boot loader is a really bad idea, you have to replicate the whole raid stack, because as mentioned many times, *write* support actually matters for boot count/RNG support. If you have a software raid setup and want to boot from it, that's OK, but then simply install the boot loader individually on each HDD, with its own ESP/XBOOTLDR, and apply raid only to the rootfs itself, but not ESP/XBOOTLDR. It's the only thing that is reasonably safe, as firmware generally has no understanding of linux raid, and you never want to risk things go out of sync, because firmware doesn't respect raid, but other stuff does. With "bootctl install" you can use --esp-path= and --xbootldr-path= to install systemd-boot into as many ESPs/XBOOTLDRs as you want. kernel-install has the same. Lennart -- Lennart Poettering, Berlin -- _______________________________________________ devel mailing list -- [email protected] To unsubscribe send an email to [email protected] 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/[email protected] Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
