📖 ~1 min read
Table of contents
Symptom & Impact
zpool status reports DEGRADED and alerts increase data risk until redundancy is restored.
Environment & Reproduction
Triggered by HBA firmware changes, cabling updates, or persistent device naming differences after reboot.
Root Cause Analysis
ZFS cannot map an expected member path, marking the vdev unavailable despite healthy underlying media.
Quick Triage
Confirm affected pool, check device visibility, and review recent hardware or topology modifications.
Step-by-Step Diagnosis
Correlate ZFS GUIDs, disk identifiers, and controller logs to map missing devices precisely.
Solution – Primary Fix
Reattach or replace the missing vdev by GUID and allow resilver to complete fully.
Still having issues? Our Server Management team can diagnose and resolve this for you. Get in touch for a free consultation.
Solution – Alternative Approaches
Temporarily clear path instability, then schedule controlled replacement or enclosure-level maintenance.
Verification & Acceptance Criteria
Pool returns to ONLINE, resilver ends cleanly, and no new checksum or read/write error counts appear.
Rollback Plan
Restore previous HBA pathing or enclosure mapping if reattachment introduces additional instability.
Prevention & Hardening
Use persistent disk identifiers, document topology, and alert early on path flapping events.
Related Errors & Cross-Refs
Commonly linked with CAM timeout errors, enclosure resets, and intermittent multipath visibility.
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
zpool and zfs man pages, FreeBSD storage handbook, and vendor HBA 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.
