EFI system partition
{{Short description|Partition used by Unified Extensible Firmware Interface}}
File:EFI system partition on Linux screenshot.png]]
The EFI (Extensible Firmware Interface) system partition or ESP is a partition on a data storage device (usually a hard disk drive or solid-state drive) that is used by computers that have the Unified Extensible Firmware Interface (UEFI). When a computer is booted, UEFI firmware loads files stored on the ESP to start operating systems and various utilities.
An ESP contains the boot loaders, boot managers, or kernel images of installed operating systems (which are typically contained in other partitions), device driver files for hardware devices present in a computer and used by the firmware at boot time, system utility programs that are intended to be run before an operating system is booted, and data files such as error logs.{{cite web
| url = https://www.uefi.org/specifications
| title = Unified Extensible Firmware Interface (UEFI) Specification (versions 2.10 and older)
| date = August 2022 | access-date = 2022-12-12
| website = UEFI.org | format = PDF
}}
Overview
{{See also|Unified Extensible Firmware Interface#UEFIBOOT|Unified Extensible Firmware Interface#CSMBOOT|l1=UEFI § UEFI booting|l2=UEFI § CSM booting}}
The EFI system partition is formatted with a file system whose specification is based on the FAT file system and maintained as part of the UEFI specification; therefore, the file system specification is independent from the original FAT specification. The actual extent of divergence is unknown:{{cite web
| url = http://www.uefi.org/sites/default/files/resources/UEFI%202_5.pdf#page=585
| title = UEFI Specification Version 2.5, Section 12.3 File System Format
| date = April 2015 | access-date = 2015-05-29
| website = UEFI.org
| format = PDF | pages = 536, 537
| quote = The file system supported by the Extensible Firmware Interface is based on the FAT file system. EFI defines a specific version of FAT that is explicitly documented and testable. Conformance to the EFI specification and its associate reference documents is the only definition of FAT that needs to be implemented to support EFI. To differentiate the EFI file system from pure FAT, a new partition file system type has been defined.
| url = https://www.intel.com/content/dam/doc/reference-guide/efi-firmware-file-system-specification.pdf
| title = Intel Platform Innovation Framework for EFI Firmware File System Specification
| date = September 2003
| website = intel.com
| format = PDF}} Apple maintains a separate tool that should be used on Intel/x86-64 Macs,{{cite web
| url = https://developer.apple.com/library/mac/technotes/tn2166/_index.html#//apple_ref/doc/uid/DTS10003927-CH1-SUBSECTION6
| title = Technical Note TN2166: Secrets of the GPT
| date = 2006-11-06 | access-date = 2015-05-06
| website = Developer.Apple.com
}} while other systems use FAT utilities just fine.{{cite web |title=EFI system partition |url=https://wiki.archlinux.org/index.php/EFI_system_partition |website=ArchWiki |access-date=14 March 2020}} The globally unique identifier (GUID) for the EFI system partition in the GUID Partition Table (GPT) scheme is {{Mono|C12A7328-F81F-11D2-BA4B-00A0C93EC93B}}, while its ID in the master boot record (MBR) partition-table scheme is {{Mono|0xEF}}. Both GPT- and MBR-partitioned disks can contain an EFI system partition, as UEFI firmware is required to support both partitioning schemes. Also, El Torito bootable format for CD-ROMs and DVDs is supported.
UEFI provides backward compatibility with legacy systems by reserving the first block (sector) of the partition for compatibility code, effectively creating a legacy boot sector. On legacy BIOS-based systems, the first sector of a partition is loaded into memory, and execution is transferred to this code. UEFI firmware does not execute the code in the MBR, except when booting in legacy BIOS mode through the Compatibility Support Module (CSM).
The UEFI specification requires MBR partition tables to be fully supported. However, some UEFI implementations immediately switch to the BIOS-based CSM booting upon detecting certain types of partition table on the boot disk, effectively preventing UEFI booting from being performed from EFI system partitions contained on MBR-partitioned disks.{{cite web
| url = https://bbs.archlinux.org/viewtopic.php?id=142637
| title = UEFI system booting from MBR partition table and GRUB legacy
| date = June 2012 | access-date = 2013-10-06
| website = ArchLinux.org
}}
UEFI firmware supports booting from removable storage devices such as USB flash drives. For that purpose, a removable device is formatted with a FAT12, FAT16 or FAT32 file system, while a boot loader needs to be stored according to the standard ESP file hierarchy, or by providing a complete path of a boot loader to the system's boot manager. On the other hand, FAT32 is always expected on fixed drives.
Usage
=Linux=
{{See also|Unified Extensible Firmware Interface#Linux|l1=UEFI and Linux disk device compatibility}}
GRUB 2, elilo and systemd-boot serve as conventional, full-fledged standalone UEFI boot managers (a.k.a. bootloader managers) for Linux. Once loaded by a UEFI firmware, they can access and boot kernel images from all devices, partitions and file systems they support, without being limited to the EFI system partition.
The mount point for the EFI system partition varies depending on the bootloader used. Older bootloaders such as GRUB 2 and lilo/elilo default to /boot/efi. Alternatively, systemd-boot prefers either /efi or /boot over /boot/efi due to potential complications with nested autofs mounts. Regardless of the mount point path, its contents are accessible after Linux is booted.{{cite web |date=2013-12-21 |title=UEFI - Community Ubuntu Documentation |url=https://help.ubuntu.com/community/UEFI |access-date=2013-12-27 |website=Ubuntu.com}}{{Cite web |title=Boot Loader Specification |url=https://uapi-group.org/specifications/specs/boot_loader_specification/ |access-date=2024-02-15 |website=uapi-group.org |language=en}}
== Linux Kernel EFI Boot Stub ==
EFI Boot Stub makes it possible to boot a Linux kernel image without the use of a conventional UEFI boot loader. By masquerading as a PE/COFF executable image and appearing to the firmware as a UEFI application, a Linux kernel image with EFI Boot Stub enabled can be directly loaded and executed by a UEFI firmware. Such kernel images can still be loaded and run by BIOS-based boot loaders; thus, EFI Boot Stub allows a single kernel image to work in any boot environment.{{cite web |date=2014-06-16 |title=The EFI Boot Stub - The Linux Kernel Documentation |url=https://docs.kernel.org/admin-guide/efi-stub.html |url-status=live |archive-url=https://web.archive.org/web/20231004135314/https://docs.kernel.org/admin-guide/efi-stub.html |archive-date=2023-10-04 |access-date=2024-02-14 |website=The Linux Kernel documentation}}
Linux kernel's support for the EFI Boot Stub is enabled by turning on option CONFIG_EFI_STUB (EFI stub support) during the kernel configuration.{{cite web
| url = https://git.kernel.org/cgit/linux/kernel/git/stable/linux-stable.git/tree/arch/x86/Kconfig?id=refs/tags/v3.11.1#n1575
| title = Linux kernel 3.11.1 arch/x86/Kconfig: CONFIG_EFI_STUB (line #1575)
| access-date = 2013-10-06
| website = Kernel.org
}} It was merged into version 3.3 of the Linux kernel mainline, released on March 18, 2012.{{cite web
| url = http://kernelnewbies.org/Linux_3.3#head-b8360946e9fb561ee77f807ced5396e64aabeca4
| title = Linux kernel 3.3: 1.10. EFI boot support
| date = 2012-03-18 | access-date = 2013-10-06
| website = KernelNewbies.org
}}
Systemd-boot is a simple UEFI boot manager that loads and runs configured EFI images, accessing only the EFI system partition. Configuration file fragments, kernel images and initrd images are required to reside on the EFI system partition, as systemd-boot does not provide support for accessing files on other partitions or file systems. Linux kernels need to be built with CONFIG_EFI_STUB=y so they can be directly executed as UEFI images.{{cite web |date=2021-05-07 |title=systemd-boot UEFI Boot Manager |url=https://www.freedesktop.org/wiki/Software/systemd/systemd-boot/ |url-status=live |archive-url=https://web.archive.org/web/20240214190517/https://www.freedesktop.org/wiki/Software/systemd/systemd-boot/ |archive-date=2024-02-14 |access-date=2024-02-14 |website=Freedesktop.org}}
=Apple=
== macOS on [[Intel]] ([[x86]] and [[x86-64]]) ==
On Apple Mac computers using Intel x86-64 processor architecture, the EFI system partition is initially left blank and unused for booting into macOS.{{cite web|url=http://refit.sourceforge.net/myths/|title=rEFIt: Myths and Facts About Intel Macs – Myth: Mac OS X Requires a Hidden EFI System Partition|website=rEFIt.SourceForge.net}}{{Cite web |title=Boot process for an Intel-based Mac |url=https://support.apple.com/guide/security/boot-process-sec5d0fab7c6/web |access-date=2024-02-14 |website=Apple Support |language=en}}
However, the EFI system partition is used as a staging area for firmware updates{{cite web|url=http://support.apple.com/kb/HT2434|work=Apple Knowledgebase|title=Firmware updates for Intel-based Macs require a GUID partition scheme}} and for the Microsoft Windows bootloader for Mac computers configured to boot into a Windows partition using Boot Camp.{{Cite web |title=Boot modes of an Intel-based Mac with an Apple T2 Security Chip |url=https://support.apple.com/guide/security/boot-modes-sec7703b1423/web |access-date=2024-02-14 |website=Apple Support |language=en}}
Custom Apple UEFI firmware named iBoot controls the logic for finding and loading bootloaders. iBoot will select the desired bootloader (potentially configured via Startup Keyboard Combinations or NVRAM), optionally falling back to either the internal macOS Installation, or a recovery system called recoveryOS.{{Cite web |title=Startup Security Utility on a Mac with an Apple T2 Security Chip |url=https://support.apple.com/guide/security/startup-security-utility-secc7b34e5b5/1/web/1 |access-date=2024-02-14 |website=Apple Support |language=en}}
Older pre-UEFI Apple–Intel architecture machines required the EFI system partition to be formatted in HFS+. Third-party bootloaders needed to be "blessed" by a special ioctl command before becoming bootable by the firmware, a relic of the System Folder blessing from Classic Mac OS. There are otherwise no limitations to what kinds of EFI operating system or bootloader an Intel-based Apple computer can run.{{cite web |date=7 September 2014 |title=Ubuntu + Mac: Pure EFI Boot |url=http://heeris.id.au/2014/ubuntu-plus-mac-pure-efi-boot#fixing-efi |url-status=dead |archive-url=https://web.archive.org/web/20210308000444/https://heeris.id.au/2014/ubuntu-plus-mac-pure-efi-boot/#fixing-efi |archive-date=8 March 2021 |access-date=17 November 2019 |website=The Slightly Disgruntled Scientist}}{{Cite web |title=BLESS(8) |url=https://keith.github.io/xcode-man-pages/bless.8.html |access-date=2024-02-14 |website=keith.github.io}}
== iOS, iPadOS, macOS on [[Apple silicon]] ([[AArch64]]) ==
Devices using Apple silicon (AArch64) such as iPhones, iPads and all Mac computers from 2023 onward do not contain EFI/UEFI functionality and subsequently do not use EFI system partitions.{{Cite web |date=2023-11-02 |title=Introduction to Apple Silicon: Storage |url=https://github.com/AsahiLinux/docs/wiki/Introduction-to-Apple-Silicon |url-status=live |archive-url=https://web.archive.org/web/20240214214100/https://github.com/AsahiLinux/docs/wiki/Introduction-to-Apple-Silicon#storage |archive-date=2024-02-14 |access-date=2024-02-14 |website=GitHub - Asahi Linux Wiki |language=en}}{{Cite web |title=Boot process for a Mac with Apple silicon |url=https://support.apple.com/guide/security/boot-process-secac71d5623/web |access-date=2024-02-14 |website=Apple Support |language=en}}
= Windows =
UEFI support in Windows began in 2008 with Windows Vista SP1.{{cite web |title=UEFI and Windows |url=http://www.microsoft.com/whdc/system/platform/firmware/UEFI_Windows.mspx |website=Windows Hardware Developer Central (WHDC) |publisher=Microsoft Corporation. |access-date=May 5, 2024 |archive-url=https://web.archive.org/web/20090104140919/http://www.microsoft.com/whdc/system/platform/firmware/UEFI_Windows.mspx |archive-date=January 4, 2009 |date=July 24, 2008}}
The Windows boot manager is located at the {{code|\EFI\Microsoft\Boot\}} subfolder of the EFI system partition.{{cite web |title=Subdirectory Registry {{!}} Unified Extensible Firmware Interface Forum |url=https://uefi.org/registry |website=uefi.org |publisher=UEFI Forum |access-date=5 May 2024}}
On Windows XP 64-Bit Edition and later, access to the EFI system partition is obtained by running the {{mono|mountvol}} command. Mounts the EFI system partition on the specified drive. Available on Itanium-based computers only.{{cite web |title=Mountvol |url=http://technet.microsoft.com/en-us/library/cc772586.aspx |website=Windows Server 2012 R2 and Windows Server 2012 |publisher=learn.microsoft.com |access-date=5 May 2024 |language=en-us |date=31 August 2016}}
See also
References
{{Reflist|30em}}
External links
- [https://uefi.org/registry EFI System Partition Subdirectory Registry] – A registry of the subdirectories that lie below the
/EFIdirectory on an EFI system partition