To identify the EFI System Partition (ESP) used for booting, open a terminal and run
sudo fdisk -l or
lsblk -f. Look for a partition with the type code
FAT32 and the filesystem label
EFI or
SYSTEM. This partition is typically mounted at
/boot/efi on Linux systems.
The EFI System Partition is a critical component of modern computers that use UEFI firmware instead of legacy BIOS. It stores the bootloader files, kernel images, and other essential data required to start your operating system. Without correctly identifying this partition, you cannot troubleshoot boot issues, reinstall GRUB, or manage dual-boot configurations effectively. Many users struggle to find it because it is often small, hidden from standard file managers, or located on a different disk than the main OS drive. Understanding how to locate and verify this partition ensures you can maintain system stability and perform advanced maintenance tasks safely.
Identifying the ESP via Command Line Tools
The most reliable method to find the EFI System Partition is using command-line tools available in Linux environments. These tools provide detailed information about disk partitions, their types, and their mount points.
Using fdisk
Run the command
sudo fdisk -l to list all disk partitions. Look for a partition that has a type ID of
EF00, which indicates an EFI System Partition. The output will show the device name, such as
/dev/sda1 or
/dev/nvme0n1p1. Verify that the partition size is usually between 100MB and 500MB, as ESPs are rarely larger than this.
Using lsblk
The
lsblk command provides a tree view of block devices. Run
lsblk -f to see filesystem details. Identify the partition where the
FSTYPE column shows
vfat and the
MOUNTPOINT is
/boot/efi. If the partition is not mounted, check the
FSTYPE and look for a FAT32 filesystem on a small partition. This method is particularly useful because it directly shows where the system expects the ESP to be.
Using blkid
For UUID-based identification, use
sudo blkid. The ESP will have a
TYPE="vfat" attribute. You can also look for specific labels like
EFI or
SYSTEM. Note the UUID, as it is often used in configuration files like
/etc/fstab to ensure the correct partition is mounted even if device names change.
Verifying the Mount Point
Once you have identified the potential ESP, verify its contents to ensure it is the correct one. The ESP must contain the bootloader files for your operating system. On Linux, navigate to the mounted directory, typically
/boot/efi/EFI/. You should see folders named after your distribution, such as
ubuntu,
fedora, or
debian, each containing the respective bootloader binaries. If you are running Windows, you might see a
Microsoft folder with
Boot subdirectories.
If the partition is empty or contains unrelated files, it is likely not the active ESP. In some cases, especially with dual-boot setups, there may be multiple FAT32 partitions. Ensure you are looking at the one mounted at
/boot/efi or referenced by your bootloader configuration.
Common Issues and Troubleshooting
Sometimes, the ESP is not automatically mounted, making it difficult to access. If
lsblk shows no mount point, you can manually mount it using
sudo mount /dev/sdXN /mnt, replacing
sdxN with your partition identifier. After checking, unmount it with
sudo umount /mnt.
Another common issue is confusion between the ESP and a regular data partition formatted as FAT32. Always cross-reference the partition size, type code, and mount point. A data partition will not contain bootloader files and will not be listed in your system's boot configuration.
For more complex scenarios involving cloning drives or fixing boot issues, refer to our guide on
Cloning Linux Drive: Boot UUID and UEFI Files Connection via SATA/USB Freezes. Additionally, if your BIOS fails to recognize the bootloader after partition changes, consult
BIOS won't recognize bootloader: Troubleshooting Guide.
Why Correct Identification Matters
Incorrectly identifying the ESP can lead to broken boots, failed updates, or accidental deletion of critical files. When performing system migrations or reinstallations, having the correct ESP ensures that your bootloader remains functional. It also allows you to update firmware or add new operating systems without disrupting existing installations. Always double-check before making any changes to this partition.
Frequently Asked Questions
Can I delete the EFI System Partition?
No, deleting the ESP will render your computer unbootable until you recreate it and restore the bootloader files. It contains essential data required for the UEFI firmware to start the operating system. Always back up the contents before making significant changes to disk partitions.
How do I know if my computer uses UEFI or Legacy BIOS?
Check your system's firmware settings during startup; UEFI systems explicitly list "UEFI" options, while Legacy BIOS does not. Alternatively, in Linux, if the
/sys/firmware/efi directory exists, your system is using UEFI. Legacy BIOS systems do not have an EFI System Partition.
What should I do if the ESP is missing from lsblk?
If the ESP is not listed, it may be unmounted or corrupted. Use
sudo fdisk -l to find the partition by its type code
EF00. Once identified, you can manually mount it to verify its contents and fix any mounting issues in
/etc/fstab.
Is the ESP always on the first disk?
Not necessarily. While it is common for the ESP to be on the primary boot drive, it can reside on any disk accessible by the UEFI firmware. Check your motherboard's boot order settings to see which disk the firmware prioritizes for loading bootloaders.
How can I recover a corrupted ESP?
Recovery involves recreating the partition structure and reinstalling the bootloader. You can use tools like
gdisk to create a new ESP with the correct type code and then reinstall GRUB or your preferred bootloader. Refer to
How is the grub boot menu presented if the gpt looks for efi system partition for insights into bootloader presentation and recovery steps.