Linux Kernel & Boot Errors: GRUB, kernel panic, initramfs, emergency mode

Kernel and Boot Errors

When a Linux box won’t boot, the diagnostic surface is much smaller than a running system: GRUB, the kernel command line, initramfs, and the root filesystem mount. Most boot failures fall into one of those four categories. The ten errors below are what you’ll see on the console of a non-booting server.

#071 Kernel panic – not syncing

Description: Kernel encountered an unrecoverable error.

Common causes: Wrong root= UUID, missing initramfs module for the storage controller, hardware fault.

Solution: Boot a previous kernel from GRUB; mount root from rescue media and check /etc/fstab UUIDs against blkid; rebuild initramfs with update-initramfs -u -k all or dracut -f --regenerate-all.

#072 GRUB: error: file `/boot/vmlinuz-X` not found

Solution: Boot from rescue, mount root, chroot, then update-grub or grub2-mkconfig -o /boot/grub2/grub.cfg.

#073 Cannot find boot device / VFS: Unable to mount root fs

Description: Kernel loaded but couldn’t find the root filesystem.

Solution: Common after disk replacement — UUID changed. Rescue boot, fix /etc/fstab with new UUIDs, regenerate initramfs.

#074 emergency mode / dependency failed

Description: systemd dropped to emergency shell because a critical mount failed.

Solution: Login at the prompt; journalctl -xb for what failed; usually a stale fstab entry. systemctl daemon-reload + mount -a.

#075 No init found

Solution: Wrong root= on kernel cmdline OR /sbin/init missing/corrupt. Boot rescue, chroot, reinstall systemd or upstart.

#076 module not found / missing module in initramfs

Solution: Add module name to /etc/initramfs-tools/modules (Debian) or /etc/dracut.conf.d/ (RHEL); regenerate initramfs.

#077 fsck failed during boot

Solution: At the rescue prompt: fsck -y /dev/sdaN; for repeated failures, the disk is dying.

#078 Out of memory at boot (initramfs)

Solution: Tiny VMs with too-fat initramfs; rebuild with --no-hostonly reduced; add RAM if VM.

#079 Kernel command line typo (cannot parse)

Solution: At GRUB menu, press e to edit, fix the line, Ctrl-X to boot. Then permanent edit in /etc/default/grub + update-grub.

#080 Boot loops without explicit error

Solution: Kernel command line missing quiet — or has it — check the actual messages by removing quiet splash at GRUB to see what’s happening. Often hardware: failing disk, bad RAM (run memtest86+).

Conclusion

1. Always keep a previous kernel installed; GRUB’s submenu lets you boot it if a new one breaks.
2. Test update-initramfs before rebooting (regenerate then verify content with lsinitramfs).
3. Use UUIDs in fstab, not /dev/sdaN — survives disk reordering.
4. Memorize the rescue boot procedure for your distro before you need it.
5. Snapshot/backup before kernel upgrades on critical hosts.

Related Linux Admin articles

• Linux Disk & Filesystem — for fstab and UUID handling
• Linux Storage & RAID Errors — for boot failures stemming from RAID/LVM
• Linux Filesystem & Disk Errors — for fsck-during-boot scenarios