Quickly inspect and understand UEFI boot entries using efibootmgr and complementary tools. 06.02.2026 | reading time: 3 min When a machine refuses to boot, the EFI entries are the first place to check; this training shows how to list and read UEFI boot entries with `efibootmgr` and companion utilities so you can spot wrong boot orders, missing loaders, or stray entries. A concrete inspection Run a verbose listing and inspect the key fields; for example run `sudo efibootmgr -v` and you might see: \n```\nsudo efibootmgr -v\nBootCurrent: 0001\nTimeout: 2 seconds\nBootOrder: 0001,0002,0003\nBoot0001* ubuntu HD(1,GPT,...)\File(\EFI\ubuntu\shimx64.efi)\nBoot0002* Windows Boot Manager HD(2,GPT,...)\File(\EFI\Microsoft\Boot\bootmgfw.efi)\nBoot0003* USB Key\n```\nRead it like this: BootCurrent is the entry actually running; BootOrder is the priority list used every cold boot; and the loader paths after \File(...) show the exact EFI binaries that the firmware will launch. What to watch for Look for entries that reference missing files, duplicate labels, unexpected boot numbers, or an order that prefers removable media; use `efibootmgr -v` to reveal paths, `-o` to set a persistent BootOrder, `-n` to set the next boot only, and the `-b` with `-B` or `-c` flags to delete or create entries when you know what you are doing. Complementary inspection methods If efibootmgr is unavailable or you need raw data, list NVRAM variables under `/sys/firmware/efi/efivars` or run `efivar -l` to show variable names; on systems with systemd-boot use `bootctl status` to see the loader status and entries; note that these methods show different slices of the same firmware state and are useful when troubleshooting secure-boot or vendor quirks. Limitations and cautions efibootmgr talks to the firmware via efivars so it requires an EFI boot environment; it will not help on legacy BIOS systems and incorrect use of create or delete flags can remove working entries, so always inspect before you change and keep a rescue medium ready. Next steps Practice listing entries on a test machine, compare `efibootmgr -v` with `efivar -l`, and try setting a one-time next boot to validate changes without committing them; mastering these checks will speed up boot troubleshooting and reduce downtime. Join Bits & Bytes Academy First class LINUX exam preparation. boot-process utilities troubleshooting security infrastructure
