📖 ~1 min read
Table of contents
Symptom & Impact
FreeBSD 13 systems using ZFS can drop to degraded startup when pools do not import automatically.
Environment & Reproduction
Datasets are missing after boot, and dependent services fail because mountpoints are unavailable.
Root Cause Analysis
Stale zpool.cache, device path changes, or delayed disk discovery can prevent import during rc sequence.
Quick Triage
Run zpool import, zpool status -v, and check dmesg for attachment timing or I/O errors.
Step-by-Step Diagnosis
Document pool GUIDs and available devices before attempting forced imports. image_ref=0

Solution – Primary Fix
Import with zpool import -f , regenerate cachefile, set zfs_enable=”YES” via sysrc, and reboot validate. image_ref=1
Still having issues? Our IT Solutions & Services team can diagnose and resolve this for you. Get in touch for a free consultation.

Solution – Alternative Approaches
Manage startup ordering with service zfs start and ensure dependent services require mounted datasets.
Verification & Acceptance Criteria
Persist zfs_enable in /etc/rc.conf and verify loader or boot environment settings for root-on-ZFS hosts.
Rollback Plan
For network-backed storage paths, verify interface readiness before remote dataset dependencies start.
Prevention & Hardening
After reboot, confirm zpool status is ONLINE and zfs mount lists expected datasets.
Related Errors & Cross-Refs
Schedule zpool scrub, monitor SMART and zpool events, and test imports after hardware changes.
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
Review man zpool, man zfs, and FreeBSD OpenZFS operational guidance.
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.