Search guides

Fix Linux that will not boot

We'll check where it stops, try recovery mode, run fsck, rebuild initramfs, and reinstall GRUB—or tell you when to escalate.

Troubleshooting · Servers & Linux
30–60 min
What you'll need
  • Live USB (e.g. Ubuntu, Fedora) for fsck and chroot
  • Root or sudo access (when booted)
Step 1 of 8

Quick triage — pick your path

Quick triage — pick your path

Choose the option that matches what you see. You can jump straight to that section.

Show full guide

Steps

Goal: Confirm where the boot stops, try recovery mode, run fsck, rebuild initramfs, and reinstall GRUB if needed.

  • Power on and watch the output. Note whether you see the GRUB menu, a kernel panic, “Loading initial ramdisk” then hang, or filesystem errors.
  • Good: You know where it stops. Proceed to Recovery mode or the matching path.
  • Bad: Screen is blank—check display, try a different monitor or cable.

Recovery mode

Goal: Boot into a root shell or try an older kernel.

  • At the GRUB menu, select “Advanced options for Ubuntu” (or equivalent). Choose “Recovery mode” or an older kernel.
  • Recovery mode often drops to a root shell. If an older kernel boots, the current kernel or initramfs may be corrupted.
  • Good: System boots. Run update-initramfs -u -k all (Debian/Ubuntu) or dracut --force (RHEL/Fedora) to rebuild initramfs, then reboot. Bad: Still hangs—proceed to Run fsck.

Run fsck

Goal: Repair filesystem errors that prevent boot.

  • Boot from a live USB. Mount the root partition (e.g. /dev/sda1). Run fsck -y /dev/sda1 (use your partition). The -y flag auto-answers yes to repairs.
  • Unmount and reboot. Good: System boots. Bad: No filesystem errors—check disk space with df -h and df -i (see fix-linux-server-has-disk-full), or rebuild initramfs.

Rebuild initramfs

Goal: Fix a corrupted initramfs that hangs boot after “Loading initial ramdisk.”

  • Boot from live USB. Mount root and necessary mounts (e.g. /dev, /proc, /sys). Chroot into the system.
  • Run update-initramfs -u -k all (Debian/Ubuntu) or dracut --force (RHEL/Fedora). Exit chroot, unmount, reboot.
  • Good: System boots. Bad: Still hangs—reinstall GRUB or escalate.

Reinstall GRUB

Goal: Fix a missing or corrupted GRUB boot loader.

  • Boot from live USB. Mount root and, for UEFI, the EFI partition. Chroot into the system.
  • Run grub-install /dev/sda (use your disk, not partition). For UEFI: grub-install --target=x86_64-efi --efi-directory=/boot/efi. Run update-grub. Exit chroot, unmount, reboot.
  • Good: GRUB menu appears and system boots. Bad: Disk may have failed—check SMART, escalate.

When to get help

Escalate if:

  • You cannot reach a shell (no GRUB, no recovery).
  • The disk may have failed (SMART errors, repeated fsck failures).
  • Recovery mode, fsck, initramfs rebuild, and GRUB reinstall did not help.

Provide: last visible message, whether GRUB appears, distro and version, and steps tried.

Verification

  • The system boots to the GRUB menu and reaches a login prompt.
  • No kernel panic or filesystem errors during boot.
  • Services start normally after login.

Escalation ladder

Work from the device outward. Stop when the problem is fixed.

  1. Recovery mode or older kernel At GRUB, select Advanced options > Recovery mode or older kernel.
  2. Run fsck Boot from live USB; fsck the root partition.
  3. Rebuild initramfs Chroot from live USB; update-initramfs or dracut --force.
  4. Reinstall GRUB Chroot from live USB; grub-install and update-grub.
  5. Escalate Provide last message, GRUB status, distro, steps tried.

What to capture if you need help

Before calling support or posting for help, have these ready. It speeds everything up.

  • Last visible message before hang or reboot
  • Whether GRUB menu appears
  • Distro and version
  • Steps already tried

Where does the boot stop?

No GRUB, kernel panic, initramfs hang, or filesystem errors—each points to a different fix.

Power on and watch the output. No GRUB: GRUB missing or corrupted—reinstall. GRUB appears: try recovery mode or older kernel. Kernel panic: bad kernel or hardware. Initramfs hang: rebuild initramfs. Filesystem errors: run fsck.

GRUB appears No GRUB or different

You can change your answer later.

Does recovery mode or an older kernel boot?

Recovery mode drops to root shell. Older kernel rules out current kernel/initramfs.

At GRUB: Advanced options > Recovery mode or select an older kernel. Good: system boots—current kernel or initramfs may be bad; rebuild initramfs or keep older kernel. Bad: still hangs—check fsck, disk space, or initramfs.

Yes No

You can change your answer later.

Rebuild initramfs or keep older kernel

If recovery boots, run `update-initramfs -u -k all` (Debian/Ubuntu) or `dracut --force` (RHEL/Fedora). Reboot. If an older kernel works, you can keep using it or rebuild initramfs for the current kernel.

Done

Do you see filesystem errors?

EXT4-fs error or "filesystem has errors" means fsck is needed.

Boot from live USB. Mount root read-only. Run `fsck -y /dev/sda1` (use your root partition). Reboot. Good: system boots. Bad: no filesystem errors—check disk space, rebuild initramfs, or reinstall GRUB.

Yes No

You can change your answer later.

Run fsck from live USB

Boot from live USB. Mount root. Run `fsck -y` on the root partition. Reboot. See Run fsck for full steps.

Done

Boot hangs after "Loading initial ramdisk"?

Initramfs corruption can hang boot at that stage.

Boot from live USB, chroot, run `update-initramfs -u -k all` or `dracut --force`. Reboot. Good: system boots. Bad: still hangs—reinstall GRUB or escalate.

Yes No

You can change your answer later.

Rebuild initramfs

Chroot from live USB. Run update-initramfs or dracut. Reboot. See Rebuild initramfs for full steps.

Done

Reinstall GRUB

No GRUB menu or "file not found" means GRUB is corrupted or missing.

Boot from live USB. Chroot into the system. Run `grub-install /dev/sda` and `update-grub`. For UEFI: `grub-install --target=x86_64-efi --efi-directory=/boot/efi`. Reboot. Good: GRUB appears. Bad: disk may have failed—check SMART, escalate.

Done

Reviewed by Blackbox Atlas

Frequently asked questions

Why would Linux fail to boot?
Common causes: corrupted GRUB, bad kernel or initramfs, filesystem errors (needs fsck), full disk, or hardware failure. Check where it stops—before GRUB, at GRUB, or after kernel load.
Can I fix a Linux boot without a live USB?
If GRUB appears, you can try recovery mode or an older kernel. For fsck or initramfs rebuild, you often need a live USB or rescue environment.
When should I escalate a boot failure?
If you cannot reach a shell, the disk may have failed, or you have tried recovery mode and fsck with no change. Have a backup before major changes.

Rate this guide

Was this helpful?

Continue to