FreeBSD 13 – Boot Drops to Loader Prompt After Upgrade – Loader Recovery Workflow

📖 ~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

Server fails to boot and stops at loader prompt, causing service outage.

Environment & Reproduction

Typically follows interrupted upgrades or wrong boot pool selection.

zpool status
gpart show

Root Cause Analysis

Boot loader configuration no longer points to a valid kernel or boot environment.

Quick Triage

Boot from known-good environment and inspect loader settings.

ls /boot
cat /boot/loader.conf

Step-by-Step Diagnosis

Check bootfs property and kernel paths from rescue mode.

zpool get bootfs -H zroot
ls -lah /boot/kernel

Solution – Primary Fix

Set correct bootfs, reinstall bootcode if needed, and reboot.

zpool set bootfs=zroot/ROOT/default zroot
gpart bootcode -b /boot/pmbr -p /boot/gptzfsboot -i 1 da0
reboot

Solution – Alternative Approaches

Select previous boot environment from bectl if newest environment is broken.

bectl list
bectl activate 

Verification & Acceptance Criteria

System reaches multi-user mode and required services start.

service -e | wc -l
last reboot | head

Rollback Plan

Re-activate previous boot environment if kernel panic or boot regressions persist.

Prevention & Hardening

Take ZFS boot environment snapshots before every major upgrade.

Related Errors & Cross-Refs

loader prompt only, cannot find /boot/kernel, no such file or directory.

Related tutorial: View the step-by-step tutorial for freebsd-13.

View all freebsd-13 tutorials on the Tutorials Hub →

Browse all common problems & solutions on the Tutorials Hub.

References & Further Reading

FreeBSD boot process, loader.conf, and ZFS boot environment references.