On Wed, Oct 15, 2025 at 10:15 AM Stephen Smoogen <[email protected]> wrote:
> A big reason that raid1 /boot is because it is one of the least worst > decisions when dealing with server hardware. Actual server class hardware uses hardware raid (1, 5, 6, whatever) controllers, or firmware supported raid such as Intel® Matrix Storage Manager (imsm) if raid is desirable[0]. In those cases the hardware sees a single disk for booting (so, problem "solved"). While I understand that there still are those who want bios boot to work, uefi (and secure boot capability) should be what the project focuses on. And that means, in practice, a large(ish) fat formatted /efi partition. FD: I use imsm raid1 for my /efi partition on two nvme devices with power failure protection (commonly mis-referred to as supercapacitor). I used a 1GB partition for /efi, but at some point I will re-partition and use 4GB to be more future proof for a secure boot world using uki (or equivalent) approaches). [0] For the hyperscalers, you often just reinstall from scratch if a system falls over. And if it falls over consistently, you throw it off the island for future use (where, depending on your maintenance strategy, it may stay powered off until some future hardware swap, or enough systems fail to justify intervention). -- _______________________________________________ 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
