Fedora Linux 43 is set to bring a significant change to how it handles system installations. Specifically, for systems using UEFI firmware on x86 architecture, the Anaconda installer will soon require the use of GPT partition tables.
Table of Contents
Fedora 43 Change Proposal: Anaconda Drop Support UEFI on MBR
The core of the proposal is simple: Anaconda, Fedora's installer, will no longer support installing Fedora in UEFI mode on older MBR-partitioned disks for x86 systems.
Moving forward, if you are installing Fedora 43 on an x86 machine booted in UEFI mode, your disk must use a GPT (GUID Partition Table).
This is a proposed change for Fedora Linux. It needs approval from the Fedora Engineering Steering Committee (FESCo) before it becomes official. If approved, it's targeted for Fedora Linux 43.
As of writing this, the current poll status regarding the proposal to disallow UEFI on MBR for x86 in Anaconda shows a strong positive sentiment towards the change.
Benefits for Fedora Users
This isn't just a technical tweak; it's about making Fedora better. There are several key reasons behind this decision:
- Improved Reliability: While the UEFI specification does technically permit booting from MBR disks, this setup is often unreliable in practice. It's also inconsistently supported by firmware. Enforcing GPT aims to prevent frustrating bootloader failures, such as issues with
efibootmgrbeing unable to register UEFI boot entries on MBR disks. This makes for a much more robust installation experience. - Reduced Support Burden: Fedora does not currently test UEFI on MBR configurations. Dropping this untested and rarely used setup makes Fedora easier to test and maintain. This helps avoid confusion for users, too, by not implying that MBR+UEFI is a good long-term solution.
- Alignment with Modern Standards: Fedora’s GRUB2 bootloader documentation already assumes the use of a GPT partition table for UEFI installations. Furthermore, reasons for originally adding UEFI on MBR support (like accommodating older cloud environments that didn't support UEFI on GPT) no longer apply to modern cloud platforms.
Who is Affected (and Who Isn't)?
Before jumping into any conclusion, you need to understand the scope of this change.
You ARE Affected if you plan to install new Fedora Linux 43 (or later) on an x86 system that uses UEFI mode and currently has an MBR-partitioned disk.
You are NOT Affected if:
- You have an existing Fedora system: This change does not affect upgrades of current Fedora systems. If your current setup uses UEFI on MBR, it should continue to function and upgrade normally. The change only impacts the installation process for new systems.
- You use other architectures: This change only applies to x86 systems. Other architectures, such as ARM and RISC-V, are not affected. Their UEFI implementations might still rely on MBR partitioning.
- You use Legacy (BIOS) installations: This proposal is specifically about UEFI mode and does not impact traditional BIOS boot methods.
How Can You Test This Change?
For those eager to try it out, once Anaconda PR #6484 is merged, you can test this change.
Simply download a current Fedora Rawhide ISO and try to install Fedora in UEFI mode on an MBR-partitioned x86 system.
The installer should fail gracefully with a clear error message, indicating that GPT is required for UEFI installations.
Looking Ahead
This proposed change is a significant step towards a more stable and predictable Fedora experience for x86 UEFI users.
By standardising on GPT, Fedora aims to avoid common boot issues and streamline its development and support efforts.
As I already mentioned, it is just a proposal. Let us hope for the official approval from FESCo!
Similar Read:
