Affected versions: Ubuntu 24.04 LTS

πŸ“– ~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 cannot boot normally and stops in initramfs prompt.

Environment & Reproduction

Often occurs after abrupt shutdown, filesystem corruption, or UUID mismatch.

blkid
cat /etc/fstab

Root Cause Analysis

Root filesystem cannot be mounted due to fs errors, missing modules, or wrong fstab entries.

Quick Triage

Identify failing block device and run non-destructive checks.

ls /dev/disk/by-uuid
cat /proc/cmdline

Step-by-Step Diagnosis

Compare kernel root UUID, fstab UUID, and filesystem health.

sudo blkid
sudo fsck -N /dev/sdXN
grep -v '^#' /etc/fstab
Illustrative mockup for ubuntu-24-04-lts β€” terminal_or_shell
Diagnostic output for boot/initramfs-recovery β€” Illustrative mockup β€” Progressive Robot

Solution – Primary Fix

Repair filesystem and regenerate initramfs with correct root references.

Still having issues? Our Server Management team can diagnose and resolve this for you. Get in touch for a free consultation.

sudo fsck -fy /dev/sdXN
sudo update-initramfs -u -k all
sudo update-grub
sudo reboot
Illustrative mockup for ubuntu-24-04-lts β€” log_or_console
Resolution output for boot/initramfs-recovery β€” Illustrative mockup β€” Progressive Robot

Solution – Alternative Approaches

Boot from live media and chroot for deep repair if root cannot mount.

sudo mount /dev/sdXN /mnt
for i in /dev /proc /sys; do sudo mount --bind $i /mnt$i; done
sudo chroot /mnt

Verification & Acceptance Criteria

System boots to multi-user or graphical target without initramfs interruption.

systemctl is-system-running
lsblk -f

Rollback Plan

Restore disk snapshot or backup image if filesystem corruption recurs.

sudo lsblk
sudo mount | head

Prevention & Hardening

Use clean shutdown policies and monitor SMART plus filesystem errors.

sudo smartctl -H /dev/sda 2>/dev/null || true
sudo journalctl -p err -b --no-pager

Related messages include gave up waiting for root file system device.

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

View all Ubuntu 24.04 LTS tutorials on the Tutorials Hub β†’

Browse all common problems & solutions on the Tutorials Hub.

References & Further Reading

Ubuntu recovery mode, initramfs, and filesystem repair documentation.

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.