FreeBSD 15 Loader Prompt Appears Instead of Normal Boot

📖 ~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 does not auto-boot, requiring console intervention and causing downtime.

Environment & Reproduction

Seen after boot disk changes, loader.conf edits, or failed updates.

boot

Root Cause Analysis

Boot loader cannot locate kernel or valid root filesystem without manual input.

Quick Triage

Identify boot device and attempt single-user boot for recovery.

lsdev

Step-by-Step Diagnosis

Inspect /boot/loader.conf and verify ZFS bootfs/root hints.

cat /boot/loader.conf

Solution – Primary Fix

Correct loader settings and reinstall bootcode if disk mapping changed.

sudo gpart bootcode -b /boot/pmbr -p /boot/gptzfsboot -i 1 

Solution – Alternative Approaches

Boot from installation media and chroot to repair boot configuration.

Verification & Acceptance Criteria

System boots unattended to multi-user target on next restart.

Rollback Plan

Restore prior loader.conf and bootcode backup where available.

Prevention & Hardening

Snapshot boot config before maintenance and test reboot in change windows.

Related Errors & Cross-Refs

May overlap with damaged GPT metadata and missing kernel files.

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

View all freebsd-15 tutorials on the Tutorials Hub →

Browse all common problems & solutions on the Tutorials Hub.

References & Further Reading

FreeBSD boot loader and recovery handbook sections.