Ubuntu 26.04 LTS – boot enters emergency mode and requests manual fsck

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

Administrators observe: Ubuntu 26.04 LTS – boot enters emergency mode and requests manual fsck. Systems fail to reach multi-user target automatically.

Environment & Reproduction

Issue appears after abrupt power loss, storage faults, or mismatched fstab entries.

# Baseline context
lsb_release -a
systemctl --failed
cat /etc/fstab
lsblk -f
journalctl -xb --no-pager | tail -n 200

Root Cause Analysis

Boot dependencies fail when critical filesystem checks fail or required mount UUIDs cannot be resolved.

Quick Triage

Identify failing device and compare with fstab entries.

# Quick triage
blkid
cat /etc/fstab
systemctl status systemd-fsck* --no-pager

Step-by-Step Diagnosis

Collect emergency mode logs and verify filesystem integrity from rescue shell.

# Detailed diagnosis
journalctl -xb --no-pager | grep -Ei 'fsck|mount|dependency failed'
# In rescue/live media, run:
# fsck -f /dev/

Solution – Primary Fix

Repair filesystem, correct fstab UUIDs, and continue boot.

# Primary fix
# Run from rescue when target fs unmounted:
# fsck -fy /dev/
sudo blkid
sudoedit /etc/fstab
sudo systemctl daemon-reload

Solution – Alternative Approaches

Mark non-critical mounts as nofail to avoid blocking boot.

# Alternative
sudoedit /etc/fstab
# Add nofail,x-systemd.device-timeout=10 to non-critical entries

Verification & Acceptance Criteria

System boots to default target without emergency prompts and all required mounts are active.

# Verify
systemctl get-default
systemctl is-system-running
findmnt -a

Rollback Plan

Restore prior fstab from backup and boot with last known-good kernel/recovery path.

# Rollback
sudo cp -a /etc/fstab /etc/fstab.rollback.$(date +%F)
# Restore backup file if new changes fail

Prevention & Hardening

Use clean shutdown, monitor disk health, and validate fstab changes with findmnt –verify.

# Hardening
findmnt --verify
sudo systemctl enable --now smartd

Related Errors & Cross-Refs

Related patterns include dependency failed for local file systems and fsck exited with status code 4.

Related tutorial: View the step-by-step tutorial for Ubuntu 26.04 LTS.

View all Ubuntu 26.04 LTS tutorials on the Tutorials Hub →

Browse all common problems & solutions on the Tutorials Hub.

References & Further Reading

systemd emergency mode docs, fstab reference, and Ubuntu recovery procedures.