📖 ~1 min read
Table of contents
Symptom & Impact
System drops into dracut shell and production services do not start after reboot.
Environment & Reproduction
RHEL 8 VM or bare metal after storage layout change or kernel update.
Root Cause Analysis
Missing initramfs drivers, incorrect UUID in boot config, or delayed storage device discovery.
Quick Triage
Check whether root device is visible in emergency shell and verify kernel command line root parameters.
Step-by-Step Diagnosis
From rescue mode run `lsblk -f`, compare UUIDs in `/etc/fstab` and GRUB args, then review `/run/initramfs/rdsosreport.txt`.
Solution – Primary Fix
Correct UUID mappings, regenerate initramfs with `dracut -f`, rebuild GRUB config, and reboot for normal startup.
Still having issues? Our IT Solutions & Services team can diagnose and resolve this for you. Get in touch for a free consultation.
Solution – Alternative Approaches
Temporarily boot older known-good kernel or add required storage drivers explicitly in dracut config.
Verification & Acceptance Criteria
System boots to multi-user target and `systemctl is-system-running` returns running or degraded with known exceptions.
Rollback Plan
Select previous kernel from GRUB and restore prior initramfs and boot config backups.
Prevention & Hardening
Validate boot artifacts after kernel upgrades and test reboot in staging before production rollout.
Related Errors & Cross-Refs
`dracut-initqueue timeout`, `Warning: /dev/mapper/… does not exist`, and root mount failures.
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
RHEL boot troubleshooting guides, `dracut.cmdline(7)`, and GRUB2 administration 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.
