Dracut emergency shell after storage changes

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

Host drops to dracut emergency shell and fails to mount root filesystem on boot.

Environment & Reproduction

RHEL 7 after LVM, multipath, or disk UUID changes without initramfs refresh.

Root Cause Analysis

Stale initramfs or incorrect root= kernel parameter no longer matches actual storage mapping.

Quick Triage

From dracut shell run lsblk, blkid, and lvm pvscan/vgscan to confirm visible root device.

Step-by-Step Diagnosis

Compare grub cmdline root UUID to blkid output and inspect /etc/fstab consistency.

Solution – Primary Fix

Chroot from rescue media, fix fstab/grub root values, run dracut -f and rebuild grub config.

Solution – Alternative Approaches

Boot previous kernel/initramfs combo if available while preparing permanent storage mapping fix.

Verification & Acceptance Criteria

System boots to multi-user.target and root mounts without entering emergency shell.

Rollback Plan

Revert fstab and grub changes to prior snapshot and restore known-good initramfs image.

Prevention & Hardening

Include dracut regeneration in storage change runbooks and test reboot before maintenance close.

Related Errors & Cross-Refs

Warning: /dev/mapper/… does not exist, Cannot find UUID, dracut-initqueue timeout.

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

View all rhel-7 tutorials on the Tutorials Hub →

Browse all common problems & solutions on the Tutorials Hub.

References & Further Reading

dracut man page, RHEL 7 boot process docs, LVM and GRUB troubleshooting references.