How do I check UEFI boot entries before changing a dedicated server’s boot order?
UEFI boot entries identify boot loaders and their device paths. A one-time selection and a persistent boot-order change have different effects, and changing between UEFI and legacy boot modes can make an existing installation unbootable. Inspect the current mode and entries before planning any modification.
Before you start
- Authorised access to the dedicated server and the named inspection tools.
Instructions
1. Read the current EFI entries
On a Linux system booted with accessible EFI variables, use the reporting form only. Do not add deletion or order-changing options as part of inspection.
sudo efibootmgr -vReview BootCurrent, BootOrder and any BootNext entry. Device paths should be reconciled with the installed system and provider configuration.
2. Choose the supported recovery route
Use the server’s documented firmware or BMC boot controls. For temporary media, prefer a reviewed one-time target when available, and record how to return to the normal loader. Keep console access during the verification reboot.
Check the result
- The intended loader remains present, the server boots the approved target and normal boot order is verified after the maintenance task.
Troubleshooting
- EFI variables are unavailable
- The machine may be booted in legacy mode, running in a restricted environment or lacking kernel access. Use the platform’s firmware interface instead of forcing changes.
- The disk is visible but no OS boots
- Check loader path, boot mode, Secure Boot compatibility and storage health before reinstalling.
Official references
Use the documentation for your installed version when a flag, service name or platform feature differs.