🟠 High   ⏱ 5–30 min  Last verified: 20 May 2026
Affected versions: FreeBSD 14

📖 ~1 min read

Table of contents
  1. Symptom & Impact
  2. Environment & Reproduction
  3. Root Cause Analysis
  4. Quick Triage
  5. Step-by-Step Diagnosis
  6. Solution – Primary Fix
  7. Solution – Alternative Approaches
  8. Verification & Acceptance Criteria
  9. Rollback Plan
  10. Prevention & Hardening
  11. Related Errors & Cross-Refs
  12. References & Further Reading

Symptom & Impact

Host drops to firmware shell after reboot following disk migration or clone operation.

Environment & Reproduction

Appears when EFI System Partition is copied without required loader files or NVRAM entry.

gpart show
ls /boot/efi/EFI/BOOT
efibootmgr -v || true

Root Cause Analysis

UEFI cannot locate a valid FreeBSD loader path on ESP or boot entry references old disk GUID.

Quick Triage

Identify active boot mode and verify ESP mount and file presence.

sysctl machdep.bootmethod
mount | grep efi
ls -la /boot/efi/EFI

Step-by-Step Diagnosis

Confirm partition scheme and inspect fallback boot path population.

gpart list | egrep 'Name:|rawuuid|type: efi' -A3
file /boot/loader.efi
fsck_msdosfs -n /dev/
Illustrative mockup for freebsd-14 — terminal_or_console
Diagnosis commands for post 175 — Illustrative mockup — Progressive Robot

Solution – Primary Fix

Mount ESP, copy loader to standard fallback path, and recreate firmware boot entry.

Still having issues? Our Server Management team can diagnose and resolve this for you. Get in touch for a free consultation.

mkdir -p /boot/efi
mount -t msdosfs /dev/ /boot/efi
mkdir -p /boot/efi/EFI/BOOT
cp /boot/loader.efi /boot/efi/EFI/BOOT/BOOTX64.EFI
efibootmgr -c -l 'EFIBOOTBOOTX64.EFI' -L 'FreeBSD-15'
Illustrative mockup for freebsd-14 — log_or_dashboard
Fix validation evidence for post 175 — Illustrative mockup — Progressive Robot

Solution – Alternative Approaches

Use fallback-only boot path without NVRAM entry in constrained firmware environments.

cp /boot/loader.efi /boot/efi/EFI/BOOT/BOOTX64.EFI

Verification & Acceptance Criteria

System boots directly into FreeBSD from cloned disk across multiple restart cycles.

efibootmgr -v
shutdown -r now

Rollback Plan

Reattach original boot disk or restore previous firmware entry if boot remains unstable.

efibootmgr -v
# select prior boot target in firmware menu

Prevention & Hardening

Include ESP content and boot entry validation in clone runbooks.

tar -C /boot/efi -cf /root/esp-backup.tar EFI
efibootmgr -v > /root/efibootmgr.prechange.txt

Often paired with GPT attribute mismatches and incorrect root pool hints in loader.conf.

Related tutorial: View the step-by-step tutorial for FreeBSD 14.

View all FreeBSD 14 tutorials on the Tutorials Hub →

Browse all common problems & solutions on the Tutorials Hub.

References & Further Reading

FreeBSD UEFI boot handbook section, gpart manual, and efibootmgr usage notes.

Need Expert Help?

If you cannot resolve this yourself, our team offers hands-on Server Management, Managed IT Services, and flexible Support Plans. Contact us today — we respond within one business day.