📖 ~1 min read
Table of contents
Symptom & Impact
Reboots take excessively long or stop at filesystem check prompts.
Environment & Reproduction
Usually follows unclean shutdown, storage errors, or abrupt power loss.
Root Cause Analysis
Dirty UFS metadata or repeated fsck retries due to unresolved disk issues.
Quick Triage
Capture boot messages and identify affected filesystem.
dmesg -a | tail -n 120
cat /etc/fstab
geom disk list
Step-by-Step Diagnosis
Run manual checks from single-user mode on impacted devices.
fsck -fy /dev/ada0p2
smartctl -a /dev/ada0
glabel status

Solution – Primary Fix
Repair filesystem and correct mount options before returning multi-user mode.
Still having issues? Our IT Solutions & Services team can diagnose and resolve this for you. Get in touch for a free consultation.
fsck -fy
mount -uw /
reboot

Solution – Alternative Approaches
Migrate critical data to ZFS to reduce fsck dependency for large volumes.
Verification & Acceptance Criteria
System boots without fsck prompt and no new filesystem errors appear in logs.
Rollback Plan
Restore from snapshot/backup if filesystem remains inconsistent after repair.
Prevention & Hardening
Use clean shutdown policies, UPS protection, and regular SMART health checks.
Related Errors & Cross-Refs
`UNEXPECTED SOFT UPDATE INCONSISTENCY`, repeated fsck passes, boot timeout.
Related tutorial: View the step-by-step tutorial for freebsd-12.
View all freebsd-12 tutorials on the Tutorials Hub →
Browse all common problems & solutions on the Tutorials Hub.
References & Further Reading
`fsck(8)`, `fstab(5)`, FreeBSD storage troubleshooting docs.
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.