Boot target stuck in emergency mode due to fstab errors

📖 ~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 boots into emergency mode and production services fail to come online.

Environment & Reproduction

RHEL 8 reboot after storage changes where `/etc/fstab` was manually edited.

Root Cause Analysis

Invalid UUID, missing mount path, wrong filesystem type, or strict mount option for noncritical volume.

Quick Triage

Identify failing unit from emergency prompt and avoid repeated reboot loops before correction.

Step-by-Step Diagnosis

Check `systemctl –failed`, inspect `/etc/fstab`, validate with `blkid`, and test mounts manually.

Solution – Primary Fix

Correct problematic `fstab` entry, add `nofail` where appropriate for optional volumes, then `systemctl daemon-reload` and reboot.

Solution – Alternative Approaches

Use systemd mount units with explicit dependencies for complex storage startup ordering.

Verification & Acceptance Criteria

System reaches default target and all required mounts are present without emergency fallback.

Rollback Plan

Restore previous `fstab` from rescue backup and boot with known-good configuration.

Prevention & Hardening

Validate `fstab` edits using `mount -a` in maintenance mode before rebooting production systems.

Related Errors & Cross-Refs

`Dependency failed for /mountpoint`, timeout waiting for device, and emergency shell prompts.

Related tutorial: View the step-by-step tutorial for rhel-8.

View all rhel-8 tutorials on the Tutorials Hub →

Browse all common problems & solutions on the Tutorials Hub.

References & Further Reading

`fstab(5)`, systemd mount unit docs, and RHEL boot troubleshooting references.