How to Fix Ubuntu Boot Stopping at a BusyBox Initramfs Prompt

You switch on your Ubuntu computer and instead of the login screen, you get a black screen with a short message and a strange prompt that says BusyBox and initramfs. There is no desktop, no mouse, and typing normal commands does not seem to help.

This boot failure is scary the first time you see it, but it rarely means your files are gone. It usually means the early boot system could not find or could not read the main Ubuntu partition. A disk check, a small partition error, or a changed disk identifier is often all that is wrong.

This guide explains what the initramfs prompt is, how to run the built-in disk check that fixes most cases in minutes, and what to do when the problem is a deeper boot or disk issue.

Quick Answer

At the (initramfs) prompt, type exit to see the real error and the name of the faulty partition, then run fsck /dev/sdaX -y, replacing X with that partition number, and reboot with reboot. This file system check repairs the root partition in most BusyBox cases and lets Ubuntu boot normally again. If no partition is listed, boot from a live USB and check the disk from there.

What Is BusyBox and the Initramfs Prompt?

When Ubuntu starts, the very first stage loads a tiny temporary system into memory. This mini system is called initramfs. Its job is simple: find the real Ubuntu installation on your disk, check it is ready, and hand over control to it.

BusyBox is a small set of basic commands included in that mini system for emergency work. If the mini system cannot find the root partition, cannot read its file system, or waits too long for the disk to appear, it gives up and drops you to the BusyBox prompt so you can investigate by hand.

In other words, Ubuntu itself has not crashed. It never got the chance to start. The problem sits between the boot loader and the main disk partition.

Most Common Causes

• A file system error on the root partition after an unclean shutdown or power loss.
• A corrupted or outdated initramfs image after a kernel update.
• The disk identifier in the boot configuration no longer matches the disk, often after cloning or partition changes.
• A failing or slowly responding hard drive or SSD, or a loose cable on a desktop.
• An external drive or changed BIOS storage mode, such as a switch between AHCI and RAID, confusing the early boot stage.

Method 1: Run Fsck From the Initramfs Prompt

This fixes the majority of cases. Take your time and copy the device name exactly as the system shows it.

Step-by-Step Disk Check

1. At the (initramfs) prompt, type exit and press Enter. The system will try to continue and then print the real error, which usually names a device such as /dev/sda2 or /dev/nvme0n1p2.
2. Write down that exact device name. Root partitions are often the largest Linux partition, but trust the error message, not a guess.
3. Run the check with fsck /dev/sda2 -y, using your device name instead of the example. The -y option answers yes to repair questions automatically.
4. Let the check run fully. It may report fixing inodes, clearing orphaned files, or correcting free space counts. These are normal repairs after a power cut.
5. If the tool asks about a different file system type, you can be more specific with fsck.ext4 /dev/sda2 -y for a standard Ubuntu ext4 partition.
6. When it finishes, type reboot and press Enter. Remove any USB drives if the system tries to boot from them first.

If Ubuntu now boots, back up important files the same day. This error can be an early warning of a weak drive.

How to List Partitions From BusyBox

If typing exit does not reveal the device name clearly, list what the mini system can see.

• Run blkid to list detected partitions and their types.
• Run ls /dev/sd* or ls /dev/nvme* to see available disk devices.
• Run cat /proc/cmdline to see which root device the boot loader told the kernel to use. If that device is missing from the lists, the kernel cannot see the disk at all, which points to a hardware, cable, or storage mode problem.

Method 2: Check the Disk From a Ubuntu Live USB

Use this method if fsck from the prompt fails, if no partition appears, or if you prefer a graphical tool. You will need a Ubuntu live USB, the same kind used for installation.

1. Boot the computer from the live USB and choose Try Ubuntu.
2. Open the Disks application to see the drive layout, health status, and partition names.
3. Make sure the Ubuntu partition is not mounted. If it is, unmount it from the Disks tool first. Never run a check on a mounted partition.
4. Open a terminal and run sudo fsck -f /dev/sda2, again using your real device name. The -f option forces a full check even if the file system claims to be clean.
5. Alternatively, in the Disks application, select the partition, click the gear icon, and choose Check Filesystem.
6. When the check passes, shut down, remove the USB, and boot normally.

The live environment is also the right place to copy files to an external drive before deeper repairs. The Ubuntu community guide to boot repair tools describes the live session options.

Method 3: Rebuild Initramfs and Check the Boot Configuration

If the file system is clean but the prompt keeps returning, the early boot image itself may be broken, often after an interrupted kernel update.

1. Boot from a live USB and open a terminal.
2. Identify and mount your root partition with sudo mount /dev/sda2 /mnt, using your device name.
3. Mount the boot and system folders with sudo mount --bind /dev /mnt/dev, sudo mount --bind /proc /mnt/proc, and sudo mount --bind /sys /mnt/sys. If you have a separate EFI partition, mount it at /mnt/boot/efi.
4. Enter the installed system with sudo chroot /mnt.
5. Rebuild the early boot image with update-initramfs -u -k all.
6. Refresh the boot loader with update-grub, check that the root identifier it prints matches blkid, then type exit, unmount with sudo umount -R /mnt, and reboot.

Our guide on how to repair the GRUB boot loader in Ubuntu covers the boot loader side if your menu is also damaged.

When the Problem Points to a Failing Drive

Not every initramfs prompt is a simple file system fix. Watch for these warning signs.

• FSCK reports new errors on every boot, even after successful repairs.
• The drive makes clicking or grinding sounds, or disappears from blkid intermittently.
• SMART data in the Disks application shows reallocated sectors or a failing overall assessment.
• The boot works sometimes and fails other times with no pattern.

In these cases, stop stressing the drive with repeated checks. Boot the live USB once, copy your personal files to external storage first, and plan a drive replacement. The Arch Wiki page on fsck is a useful technical reference for check options and file system tools across distributions, including Ubuntu.

Common Mistakes and Useful Tips

• Running fsck on the wrong device: Checking a whole disk name when you need a partition, or checking the EFI partition as if it were root, wastes time and confuses results. Always use the device named in the error.
• Running fsck on a mounted partition: This can damage the file system. From the live USB, always unmount first.
• Typing exit repeatedly without reading: The message printed after the first exit contains the key clue. Read it slowly and note the device name.
• Assuming data loss too early: Most BusyBox cases leave your files fully intact behind one partition error. Do not reinstall until a disk check and a live session have been tried.
• Tip: After recovery, run sudo apt update && sudo apt upgrade and reboot once more to make sure a half-finished kernel update is not waiting to trigger the same problem.
• Tip: Keep a live USB in a drawer even if your system is healthy. It turns most boot emergencies into calm, step-by-step repairs.

Conclusion

The BusyBox initramfs prompt means Ubuntu’s early boot stage could not hand over to your main system, most often because the root partition needs a file system check. It looks alarming, but the repair is built right into the prompt itself.

Type exit to learn the faulty device, run fsck with the correct partition name, and reboot. If that is not enough, use a live USB to check the disk, copy your files to safety, and rebuild the initramfs image. If errors keep returning, treat it as a drive health warning and back up before anything else. Handled in that order, most machines are back at the login screen within fifteen minutes.

Frequently Asked Questions

Will fsck delete my personal files?

Normally no. FSCK repairs the file system structure. In rare cases of serious corruption, a damaged file may be moved to the lost and found folder, but a routine check after a power cut does not erase documents.

What if my partition is not sda but nvme?

That is common on modern laptops. Use the exact name the system shows, such as /dev/nvme0n1p2, in the fsck command. The steps are identical.

Why does the initramfs prompt appear after every shutdown?

Repeated appearances suggest the shutdown is not clean, the disk is developing faults, or a storage setting keeps changing. Check drive health with the Disks tool and make sure you shut down from the menu rather than holding the power button.

Can I type normal Ubuntu commands at the BusyBox prompt?

Only a small set. BusyBox includes basic tools like ls, cat, blkid, and fsck. Full programs like APT are not available until the real system boots.

What if fsck says the device does not exist?

Then the early boot system cannot see the disk at all. Check BIOS storage settings, reseat cables on a desktop if you are comfortable doing so, and try the live USB. If the live session also cannot see the drive, it is likely a hardware fault.