Linux Boot Failed — System Won't Start Fix

What Does This Error Mean?

When Linux fails to boot, you might see a black screen, a flashing cursor, error messages scrolling by, or your system gets stuck at the logo screen. The most common causes are a failed kernel update, a corrupted fstab file, a missing initramfs, or a full disk. Most Linux boot failures can be fixed without reinstalling the entire system.

Affected Models

Ubuntu
Debian
Fedora
CentOS
Arch Linux
Linux Mint
openSUSE

Common Causes

A kernel update failed, leaving the system with a broken or incomplete kernel
The /etc/fstab file references a drive or partition that no longer exists
The root filesystem is full and Linux cannot write the files needed to complete boot
A system service required for boot is failing and preventing the rest of the startup sequence
The initramfs (the initial boot environment) is corrupted or missing

How to Fix It

Try booting a previous kernel. At the GRUB menu (hold Shift at startup), choose Advanced Options and select a kernel from before the update. If the system boots, the new kernel is the problem.

If you do not see the GRUB menu automatically, hold down the Shift key (for BIOS systems) or press Escape (for UEFI systems) during boot.
Boot into recovery mode. From the GRUB Advanced Options menu, select your distribution with 'recovery mode' in the name. Choose 'root — Drop to root shell prompt' when the recovery menu appears.

Recovery mode starts a minimal Linux with just enough to let you fix problems. You get a root terminal without needing to log in.
Check disk space in recovery. Run: df -h to check if the root filesystem is full. If it is at 100%, run: apt clean or rm -rf /tmp/* to free space.

A full disk can prevent boot by blocking log writing and temporary file creation that boot processes need.
Regenerate the initramfs. If boot fails with 'initramfs unpacking failed,' run: sudo update-initramfs -u -k all (Debian/Ubuntu) or sudo dracut --regenerate-all --force (Fedora/CentOS).

The initramfs is a tiny file system that Linux uses in the very early stages of boot. Regenerating it fixes corruption.
Boot from a live USB and repair. If recovery mode does not work, boot from a live USB. Mount your root partition: sudo mount /dev/sda2 /mnt. Then chroot into it: sudo chroot /mnt and run repair commands.

Chroot gives you a shell that thinks it is running your broken system, letting you run repair tools like update-grub, update-initramfs, and apt.

When to Call a Professional

Most Linux boot failures can be fixed with a live USB and some terminal work. If you are not comfortable with the command line and your data is critical, a Linux technician can recover it. Do not attempt to force-reinstall Linux without trying recovery options first — you may delete your data unnecessarily.

Frequently Asked Questions

Will fixing a boot failure delete my files?

The fixes described here do not touch your personal files. Your home folder, documents, photos, and other data are separate from the system files that cause boot failures. Always back up important files when possible, but fixing GRUB, fstab, or initramfs does not remove personal data.

My screen goes blank after the GRUB menu. What does that mean?

A blank screen after GRUB usually means the kernel or initramfs is loading but the graphics driver is failing before the login screen appears. Try adding 'nomodeset' to the kernel boot parameters in GRUB. Highlight the kernel entry in GRUB, press E, find the linux line, add 'nomodeset' before 'quiet splash,' then press F10 to boot.

How do I know if a kernel update caused my boot failure?

If the boot failure happened immediately after running apt upgrade or dnf upgrade, a kernel update is the likely cause. Booting the previous kernel from GRUB Advanced Options confirms this. If the previous kernel works, hold off on the new kernel until the distribution releases a fix.