Linux Mint GRUB Rescue & Initramfs Boot Error: Complete Fix Guide (2026)

You press the power button, wait for Linux Mint to load — and instead you're staring at a blinking cursor next to grub rescue> or a cryptic (initramfs) prompt. Neither is a blue screen of death, but both are just as alarming when you need your machine running right now.

The good news: these errors are almost always fixable without reinstalling Linux Mint. This guide covers every major scenario — GRUB rescue errors, BusyBox initramfs shells, and filesystem corruption — with exact commands for Linux Mint 21.x and 22.x (2026).

What Do These Boot Errors Actually Mean?

Before touching a single command, it helps to know what broke so you fix the right thing.

• GRUB rescue> prompt — GRUB loaded its core image but cannot find its configuration file or modules. Common after a Windows update overwrites the EFI boot entry, a failed GRUB install, or a repartitioned drive.
• (initramfs) BusyBox prompt — The Linux kernel loaded successfully, but the early init system cannot mount your root filesystem. Common after a kernel update that failed to regenerate the initramfs image, or filesystem corruption (power cut, forced shutdown).
• error: no such partition. Entering rescue mode… — GRUB cannot locate the partition it expects. Usually caused by UUID changes after disk operations or a new drive replacing the old one.

Knowing which screen you see tells you exactly which section of this guide to follow.

Fix 1: Recover from the GRUB Rescue Prompt (No Live USB Needed)

If you see grub rescue>, GRUB is alive but lost. You can often boot your system from within the rescue shell itself, then repair GRUB permanently once you're in.

Step 1 — List available partitions:

grub rescue> ls

You'll see output like (hd0) (hd0,gpt1) (hd0,gpt2) (hd0,gpt3). Each entry is a partition.

Step 2 — Find which partition holds your Linux Mint root filesystem:

grub rescue> ls (hd0,gpt3)/
grub rescue> ls (hd0,gpt2)/

Try each until one lists familiar Linux directories like boot etc home usr var. That is your root partition.

Step 3 — Set the root and prefix, then load GRUB normally:

grub rescue> set root=(hd0,gpt3)
grub rescue> set prefix=(hd0,gpt3)/boot/grub
grub rescue> insmod normal
grub rescue> normal

This loads the full GRUB menu. Select your Linux Mint entry and boot into your desktop.

Step 4 — Fix GRUB permanently from the running system:

sudo update-grub
sudo grub-install /dev/sda

Replace /dev/sda with your actual disk (use lsblk to confirm). For UEFI systems, use:

sudo grub-install --target=x86_64-efi --efi-directory=/boot/efi --bootloader-id=linuxmint

Fix 2: Fix the Initramfs BusyBox Shell

The (initramfs) BusyBox prompt usually means the root filesystem has errors and the automated check failed. The fix is to run fsck manually.

Step 1 — Identify your root partition:

(initramfs) blkid

Look for the partition with TYPE="ext4" (or btrfs) and no LABEL="EFI". Note the device path, e.g., /dev/sda2 or /dev/nvme0n1p3.

Step 2 — Run filesystem check:

(initramfs) fsck -y /dev/sda2

The -y flag automatically answers yes to all repair prompts. You'll see a list of inodes and blocks being repaired. This can take several minutes on a large drive.

Step 3 — Exit and reboot:

(initramfs) exit

Typing exit causes the initramfs to retry mounting the root filesystem. If fsck did its job, the system boots normally. If it still fails, reboot:

(initramfs) reboot -f

If the system boots but the problem returns after the next kernel update, your initramfs image may be corrupted. See Fix 4 below.

Fix 3: Use Boot-Repair from a Live USB (Easiest All-In-One Fix)

When the rescue shell commands feel intimidating, or when GRUB is so broken it cannot even enter rescue mode, the Boot-Repair tool handles everything automatically. You'll need a Linux Mint Live USB (or Ubuntu USB).

Step 1 — Boot from the Live USB and connect to the internet.

Step 2 — Open a terminal and install Boot-Repair:

sudo add-apt-repository ppa:yannubuntu/boot-repair
sudo apt update
sudo apt install -y boot-repair
boot-repair

Step 3 — Click "Recommended Repair" in the Boot-Repair GUI. The tool will:

• Detect all installed operating systems
• Reinstall GRUB to the correct disk and partition
• Regenerate grub.cfg with all OS entries
• Fix EFI boot entries on UEFI systems

Step 4 — Follow the on-screen instructions, reboot, and remove the USB when prompted. In most cases, GRUB returns to its normal menu within five minutes.

Boot-Repair also generates a paste URL with a detailed diagnostic report — useful if you want to share the problem with the Linux Mint forums.

Fix 4: Regenerate a Corrupted Initramfs Image (Chroot from Live USB)

If Linux Mint boots after an fsck repair but drops back to the initramfs shell after the next reboot or kernel update, the initramfs image itself is broken. You need to regenerate it from a chroot environment.

Step 1 — Boot from a Linux Mint Live USB and open a terminal.

Step 2 — Mount your root partition:

sudo mount /dev/sda2 /mnt
sudo mount /dev/sda1 /mnt/boot/efi    # UEFI systems only
sudo mount --bind /dev /mnt/dev
sudo mount --bind /proc /mnt/proc
sudo mount --bind /sys /mnt/sys

Replace /dev/sda2 with your actual root partition (use lsblk to identify it).

Step 3 — Enter the chroot environment:

sudo chroot /mnt

Step 4 — Regenerate all initramfs images:

update-initramfs -u -k all

You'll see output for each installed kernel. This process rewrites the initramfs images from scratch.

Step 5 — Update GRUB and exit:

update-grub
exit
sudo reboot

Remove the Live USB when the system restarts. Linux Mint should now boot normally with a freshly generated initramfs.

Fix 5: Repair GRUB After Windows Overwrites the EFI Boot Entry

One of the most common causes of GRUB failure in 2026 is a Windows update that re-registers the Windows Boot Manager as the primary EFI boot entry, silently bypassing GRUB. Your Linux Mint installation is completely intact — Windows just cut in line.

Step 1 — Boot from a Linux Mint Live USB.

Step 2 — Check current EFI boot entries:

sudo efibootmgr -v

You'll see entries like Boot0000* Windows Boot Manager and possibly a missing or deprioritised Linux entry.

Step 3 — Reinstall GRUB to the EFI partition:

sudo mount /dev/sda2 /mnt               # your Linux root partition
sudo mount /dev/sda1 /mnt/boot/efi      # your EFI partition
sudo grub-install --target=x86_64-efi --efi-directory=/mnt/boot/efi --boot-directory=/mnt/boot --bootloader-id=linuxmint

Step 4 — Confirm the new boot entry:

sudo efibootmgr -v

You should now see a linuxmint entry. If Windows is still set as first, reorder with:

sudo efibootmgr --bootorder XXXX,YYYY

Replace XXXX with the Linux Mint boot number and YYYY with Windows, so Linux boots first and shows the GRUB dual-boot menu.

To prevent Windows from overwriting GRUB again, consider enabling the "Linux Boot Manager" entry protection in your UEFI firmware settings, or use a scheduled task in Windows to restore the boot order after updates.

When Nothing Works: Contact a Linux Expert

If you've worked through every fix above and Linux Mint still refuses to boot, there may be a deeper issue — a failing drive, severe filesystem corruption, or a misconfigured UEFI — that requires hands-on diagnostics. Rather than risk losing data with trial-and-error commands, get a professional to look at it remotely.

CloudHouse remote support connects you with Linux experts who diagnose and fix GRUB, initramfs, and boot failures via secure remote session — no shipping your machine anywhere, no waiting days for a quote. Most Linux boot issues are resolved in a single session.

Frequently Asked Questions

Will fixing GRUB delete my files?

No. GRUB is a bootloader — it lives in the /boot directory and the EFI partition. Running update-grub, grub-install, or Boot-Repair does not touch your home directory, documents, or application data. Your files remain completely intact throughout the repair process.

How do I know if my issue is GRUB or initramfs?

Look at the exact text on screen. A grub rescue> or error: no such partition message is a GRUB problem. A (initramfs) prompt followed by "ALERT! /dev/disk/by-uuid/… does not exist" is an initramfs or filesystem problem. The two share similar symptoms but have different fixes.

Can a bad hard drive cause these errors?

Yes. Filesystem corruption from a failing drive is one of the most common causes of initramfs errors. After you recover, run sudo smartctl -a /dev/sda (install smartmontools first) to check the drive's SMART health data. If reallocated sectors are climbing, back up your data immediately and plan for a drive replacement.

My Linux Mint boots after fsck, but the initramfs error comes back. Why?

This points to two likely culprits: the drive is still failing (and corrupting the filesystem again between boots), or the initramfs image itself is malformed and needs regenerating with update-initramfs -u -k all inside a chroot. If the drive SMART data is clean, follow Fix 4 in this guide to regenerate all initramfs images.

Does this guide work for Linux Mint 22 (Wilma) and Linux Mint 21 (Vera)?

Yes. All commands in this guide apply to Linux Mint 21.x (Vera, Vanessa, Victoria) and Linux Mint 22.x (Wilma) running GRUB 2. The underlying bootloader and filesystem tooling is identical across these releases. If you're on the older Linux Mint 20 series, the commands are the same but Boot-Repair's PPA may require a different Ubuntu base codename when installing.