Boot Delays Due to Missing Mount in fstab

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

Invalid fstab entries can cause long boot waits or emergency shell drops.

Environment & Reproduction

System pauses at mount stage, prompts for manual fsck, or continues with degraded services.

Root Cause Analysis

UFS and ZFS hosts with additional data mounts configured in /etc/fstab.

Quick Triage

Console access and verified mapping between labels, GPT IDs, and mountpoints.

Step-by-Step Diagnosis

[image_ref: 0] Run mount -a -t ufs; gpart show; glabel status; dmesg | grep -i mount; cat /etc/fstab.

Solution – Primary Fix

[image_ref: 1] Use stable identifiers like /dev/gpt/label and valid fs_passno values. Add noauto where optional mounts should not block boot.

Solution – Alternative Approaches

Correct fstab device names and options, test with mount -a, then reboot in maintenance window. For ZFS datasets prefer zfs set mountpoint and avoid duplicate fstab entries.

Verification & Acceptance Criteria

Boot completes without timeout and all required filesystems mount with expected options.

Rollback Plan

Restore previous fstab from /etc/fstab.bak and comment risky entries if immediate recovery is needed.

Prevention & Hardening

Validate fstab edits with a syntax checklist and post-change reboot tests in staging first.

Related Errors & Cross-Refs

Escalate when storage devices intermittently disappear, indicating hardware or controller faults.

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

View all freebsd-14 tutorials on the Tutorials Hub →

Browse all common problems & solutions on the Tutorials Hub.

References & Further Reading

fstab(5), mount(8), gpart(8), zfs(8).