FreeBSD 15 Boot Environment Activation Not Persisting

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

System reboots into an unexpected environment, reintroducing old packages and configs.

Environment & Reproduction

Occurs after update/rollback workflows where loader variables were not updated.

sudo bectl list

Root Cause Analysis

Boot loader points to previous dataset despite activation command.

Quick Triage

Confirm currently booted environment and next boot target.

sysctl -n vfs.root.mountfrom

Step-by-Step Diagnosis

Validate ZFS bootfs property and active flags across environments.

zpool get bootfs zroot

Solution – Primary Fix

Reactivate the desired environment and set pool bootfs explicitly.

sudo bectl activate  && sudo zpool set bootfs=zroot/ROOT/ zroot

Solution – Alternative Approaches

Manually choose environment in boot menu for one-time recovery.

Verification & Acceptance Criteria

After reboot, mount source indicates the intended boot environment.

Rollback Plan

Re-activate previous stable environment from boot menu or rescue shell.

Prevention & Hardening

Standardize BE naming and activation steps in maintenance runbooks.

Related Errors & Cross-Refs

Can overlap with loader.conf drift and failed post-upgrade scripts.

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 environment administration documentation.