Linux Mint initramfs Prompt at Boot

Linux Mint initramfs prompt appears after booting computer. A BusyBox Ubuntu built-in shell (ash) screen with initramfs prompt displays after switching on Linux Mint PC as shown in the image below. The computer does not boot up properly and instead of going straight to the login screen, drops through to a initramfs command line prompt.

Linux Mint initramfs Prompt
Linux Mint initramfs Prompt

The BusyBox initramfs prompt suggests entering ‘help’ for a list of built-in commands. When help is entered, the commands are listed as shown in the above image.

Linux Mint initramfs Prompt at Boot Problem

The problem described above has happened to me twice, both on Linux Mint 18.3 computers. Both times it happened after upgrading the Linux kernel using the Linux Mint Update Manager. Firstly it occurred on a dedicated Linux Mint laptop and then again on Linux Mint 18.3 MATE (Sylvia) running in a virtual machine using VMware Workstation 14 Player (the free for home user version of VMware Player). I decided to blog the solution so that I would have quick access to it if it happens again. I hope that it helps you too.

Linux Mint initramfs Prompt Solution

The solution below works when Linux Mint 18.3 drops through to the (initramfs) prompt after updating the Linux kernel. There may be other instances where it does not work. Three commands must be run at the BusyBox command prompt.

1. Run the exit Command

First enter exit at the initramfs prompt.

(initramfs) exit

After typing exit and pressing the Enter key, the following appears at the prompt. The information displayed will be different for different computers.

BusyBox initramfs Prompt after exit Command
BusyBox initramfs Prompt after exit Command

Take note of the path of the file system from the above image and shown below. Your root file system name will probably be different, so use the information displayed on your system, which is used in the next command.

The root filesystem on /dev/mapper/mint--vg-root requires a manual fsck

2. Run the fsck Command

Use the fsck command with the file system path determined above. This is in the following format.

fsck <your file system path> -y

For the above example this is entered at the initramfs prompt as shown below. Be sure to use your file system path as determined above instead and end with the -y switch.

fsck /dev/mapper/mint--vg-root -y

When the fsck command runs after entering it as above, it fixes the system. Text scrolls on the screen while it is busy.

3. Run the reboot Command

Finally enter the reboot command at the (initramfs) command prompt.

reboot

This reboots the computer to the Linux Mint login prompt. Everything should now be working properly again.

64 thoughts on “Linux Mint initramfs Prompt at Boot”

      1. Bom dia eu.
        Coloca aqui exatamente o que aconteceu ao executar o comando.
        Se possível vc copia e cola para q possamos te ajudar.

  1. Linux mint 18.3; same problem:
    After pressing exit, I get a sort of “track” and no URL containing and /dev items; I also get a lot of IRQ’s in this list
    Also this command “fsck” does not work AT ALL.. and it is not in my list of initramfs commands.. and I cannot see it in your displayed list of initramfs commands; how do you make it work then?

    1. Thanks.This makes sense and we’ll explained.I wish all post were like this.I was about to go to sleep about 3AM and decided to give it a go.I messed mine up trying to change it to android
      Thanks again.

    2. fsck isn’t one of the listed commands, that’s normal and you can still use it. If you can use the “fdisk -l” command you will be able to locate all your partitions and use fsck on them. If you can’t use this command then you can try it blindly by typing “fsck -y /dev/sda1”. fsck will know if your partition is the one used by your system and repair it himself (don’t worry it can’t damage a partition unused by the system)

  2. Bam! This is just what I needed! I haven’t seen this problem before. Looks like there were some corrupted files and directories.

  3. You are a life-saver. Been battling with this for weeks, even did a few installs from scratch, but got the same result each time. Five stars to you.

  4. Could someone please help with Linux Mint 17.3. this wont work. when I type exit it freezes the machine at command saying not synching , attempted to kill init.

  5. Many thanks, this worked on Linux Mint Tara (64bit). One question, though… what caused this in the first place? I hadn’t done any system or s/w updates, so it seems a bit random to me.

  6. Thanks a lot, this work for me in Linux Mint 19 on a notebook HP Pavillon with dual boot with Windows 10. But this problem appears ever that I run Windows and then I try to run Linux. Someone knows how to solve the problem forever?

  7. Hey, Hey. You are a saviour! What a wonderful solution – very lucidly explained. It solved my problem. I am using mint 18.3

  8. This is very odd thing, happened like 5 times to me since i updated to latest Mint.
    I left my pc online for night, and on the morning every update mentioned system is in “read-only” mode. Seems the system screws itself up.

  9. Worked for me like a charm. Thank you very much for this post. I’m a newbie when it comes to Linux and thanks to you I don’t have to reinstall or whatever. Many thanks.

  10. Hats off to the stranger
    for tellin’ me what he knows
    Lighthouse

    Thanks man, I thought I was SOL

  11. Worked fine for me at Tara… 🙂
    It occurred just after resize the disk and try to intall nvida propietary driver.

  12. In Mint 18.3 Xfce – for the last command in step 2 – I had to use the line format “fsck /dev/mapper” instead – then it worked. Otherwise I would get a “directory not found” error.

  13. Thank you, it worked for Linux mint 19.1

    The issue came up while the battery drained, shut down and i tried to boot after plugging to the power source.

  14. I had the same problem after a failed (?) update.
    This solution worked perfectly.
    Thank you so much.

  15. Worked on 19.1 Tessa 32-bit, but now I’ve had to use it twice (about a week in between) any idea of what could be causing it in the first place? Always suspending it at night not shutting down.

  16. You are a life saver bro. Thanks for the solution. Works perfectly.
    The other times this happened, i had to format and reinstall my OS

  17. In my case, I had installed a custom kernel build, which had nvme support turned off. It seems that `make localmodconfig` wasn’t enabling it for some reason. When grub would tell the kernel what device to use as the root, it didn’t know how to communicate to nvme devices, so none were visible.

Leave a Reply

Your email address will not be published. Required fields are marked *