Initramfs ubuntu error

initramfs ubuntu error

It seems that your bug report is not filed about a specific source package though, rather it is just filed against Ubuntu in general. It is. how to solve initramfs error in ubuntu · Solution move to infinitbility platform click below link to access · Table of content · 1: Type exit command · 2: Modify. Boot repair for Ubuntu initramfs error. · sudo add-apt-repository ppa:yannubuntu/boot-repair · sudo apt-get update · sudo apt-get install boot-repair.

You can watch a thematic video

How to Fix initramfs issue in Ubuntu 16.4 and 18.4

Initramfs ubuntu error - opinion you

Hello everyone, this time I want to share how to solve the boot problem called Initramfs, I imagine that some have happened and even this time I got the error.

Searching the web on various pages I was finally able to gather information and after that I tried the simple solution and it was a success.

To start we follow these steps:

We insert our Live CD (Let's not forget to configure the BIOS to boot from the CD.) We open a terminal and write:

We give and it will give us the name of the device with which your PC starts. example:

Disk / dev / sda: 250.1 GB, 250059350016 bytes 255 heads, 63 sectors / track, 30401 cylinders Units = cylinders of 16065 * 512 = 8225280 bytes Disk identifier: ********** Device Boot Start End Blocks Id System / dev / sda1 * 1 30238 242886703+ 83 Linux / dev / sda2 30239 30401 1309297+ 5 Extended / dev / sda5 30239 30401 1309266 82 Linux swap / Solaris

We write the following again in our terminal and give :

We wait for you to repair the partition. At the end we restart and ready it should start normal.


How To Fix Busybox Initramfs Error On Linux based OS

Some time our OS boot process gets stuck to the BusyBox shell and ends up at the initramfs prompt.

ERROR:
—————————————-
BusyBox v1.27.2 (Ubuntu 1:1.27.2-4ubuntu3.2) built-in shell (ash)
Enter ‘help’ for a list of built-in commands.

(initramfs)
—————————————-
linux busybox

SOLUTION:

Type exit command from initramfs prompt, Now you get to know which partition is corrupted that you need to repair, In my case, it was /dev/sda1. Check my error logs below:

  1. (initramfs) exit

    ———————————————————
    /dev/sda1: UNEXPECTED INCONSISTENCY; RUN fsck MANUALLY.
    (i.e., without -a or -p options)
    fsck exited with status code 4.
    The root filesystem on /dev/sda1 requires a manual fsck.

    BusyBox v1.27.2 (Ubuntu 1:1.27.2-2ubuntu3.2) built-in shell (ash)
    Enter ‘help’ for a list of built-in commands.

    (initramfs)
    ———————————————————-

    To resolve the initramfs error you need to run the following commands

  2. (initramfs) fsck /dev/sda1 -y

    Logs after run above command:

    /dev/sda1: ***** FILE SYSTEM WAS MODIFIED *****
    /dev/sda1: 799258/32614517 files (2.4% non-contiguous), ……..

    The above command will repair the corrupted partition, after this run the reboot command that I have mentioned below:

  3. (initramfs) reboot
    Now your system will boot normally without any problem. I hope you have resolved the BusyBox initramfs issue now.

Note: If the problem still persists then you might have to replace the disk as the disk health is not good.

Webner Solutions is a Software Development company focused on developing Insurance Agency Management Systems, Learning Management Systems and Salesforce apps. Contact us at [email protected] for your Insurance, eLearning and Salesforce applications.
While using your computer, you may encounter various issues not properly booting the operating system is one of them. There are various solutions to solve booting problems, some can get easily be repaired, and for some, you need to reinstall the entire operating system.

Ubuntu may also greet you will similar problems, and “initramfs” is one of them. It is a booting problem of Ubuntu and occurs because of bad blocks or bad sectors in the memory which do not allow operating system boot.

Your system contains many important files, so an error like this can definitely be a bit panicky. No need to worry; this write-up focuses on how to solve the “initramfs” issue and boot Ubuntu normally. So let’s begin:

How to fix the “initramfs” error in Ubuntu

If your screen displays an “initramfs” error, you are already in recovery mode, which means that you can type commands and perform different operations. The error would be like this:

You can type “exit” to get the detail of the error. Note that you may not get the error detail every time you type “exit.” As discussed above, that “initramfs” error occurs when your startup disk gets corrupted. You may have multiple disks attached to check them, use:

(initramfs) df -h

Or

(initramfs) blkid

The partitions can be viewed by the name of /dev/sda, /dev/sdb, or any other. Now to fix the “initramfs” error, we use the “fsck”  utility, also known as “file system consistency check,” which checks the filesystem issues and fixes them. Follow the below-mentioned syntax:

(initramfs) fsck [partitian name (/dev/sdXX)]

For instance, if my partition is by the name of “/dev/sdb,” then the command would be:

(initramfs) fsck /dev/sdb

Press “Enter,” the command will automatically eliminate the bad sectors from memory. Press “y” upon getting prompt. To prevent prompts, simply use the “-y” option with the command:

(initramfs) fsck /dev/sdb -y

If you have multiple partitions, you can check them using the above command; the command will not print anything if the partition is bad-sector-free. Now the system will take some time to analyze and repair the corrupted portion of the memory. Once it is done, type:

(initramfs) reboot

If a reboot does not work, type “exit.” Here we go; the error has been eliminated, and Ubuntu will be booted normally.

Conclusion

The “initramfs” error can affright you, but luckily this error has a very easy and straightforward solution. This error occurs when your memory got corrupted, especially the drive containing the operating system, and does not let it boot. To fix it, simply use the “file system consistency check” or “fsck” utility. This write-up thoroughly explains the process to eliminate the “initramfs” error to boot Ubuntu normally.

Linux Mint initramfs Prompt at Boot

Created on: 29 August 2021

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

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).

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

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.

Books that may interest you:

C Programming with Arduino BookUltimate Arduino MEGA 2560 Hardware ManualUltimage Arduino Uno Hardware Manual

Last night after a series of power cuts, my PC wount boot, after each boot attempt my system out put this error messages:

mount: mounting /dev/disk/by-uuid/***************************** on /root
failed: Invalid argument
mount: mounting /sys on /root/sys failed: No such file or directory
mount: mounting /dev on /root/dev failed: No such file or directory
mount: mounting /sys on /root/sys failed: No such file or directory
mount: mounting /proc on /root/proc failed: No such file or directory
Target file system doesn’t have /sbin/init
No init found. Try passing init= bootarg

Busybox v1.13.3 (Ubuntu 1:1.13.3-1ubuntu7) built-in shell (ash)
Enter ‘help’ for a list of built-in commands
(initramfs) _

Booting into “Recovery Mode” as well as choosing the other kernels listed in grub didn’t help at all.

Solution:

1. Boot from the Ubuntu Live CD;

2. Open/Run Terminal;

3. Type: sudo fdisk -l (to get the device name) then press ENTER;

Disk /dev/sda: 250.1 GB, 250059350016 bytes
255 heads, 63 sectors/track, 30401 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Disk identifier: **********

Device Boot Start End Blocks Id System
/dev/sda1 * 1 30238 242886703+ 83 Linux
/dev/sda2 30239 30401 1309297+ 5 Extended
/dev/sda5 30239 30401 1309266 82 Linux swap / Solaris

The device name for my friend’s system based on the above: /dev/sda1

4. Type: sudo fsck /dev/sda1 then press ENTER;

5. Restart the system and boot normally.

* The laptop booted normally after the fix.

Like this:

LikeLoading...

The “initramfs boot problem” on Ubuntu or Linux Mint is a situation when a computer does not boot up properly and instead of going straight to the login screen, drops you to the BusyBox shell with the initramfs command-line prompt.

This error usually occurs when the partition containing the operating system got corrupted.

Luckily this problem has a very easy and straightforward solution and in this note i will show how to fix it.

Initramfs Boot Problem Fix

The BusyBox shell with the initramfs prompt usually appears after booting the computer if the partition containing the operating system got corrupted:

BusyBox v1.27.2 (Ubuntu 1:1.27.2-2ubuntu3.3) built-in shell (ash) Enter 'help' for a list of built-in commands. (initramfs)

Type to find out the exact name of the corrupted partition:

(initramfs) exit /dev/mapper/ubuntu--vg-root contains a file system with errors, check forced. Inodes that were part of a corrupted orphan linked list found. /dev/mapper/ubuntu--vg-root: UNEXPECTED INCONSISTENCY; RUN fsck MANUALLY. (i.e., without -a or -p options) fsck exited with status code 4. The root filesystem on /dev/mapper/ubuntu--vg-root requires a manual fsck. BusyBox v1.27.2 (Ubuntu 1:1.27.2-2ubuntu3.3) built-in shell (ash) Enter 'help' for a list of built-in commands. (initramfs)

To solve the “initramfs boot problem” on Ubuntu or Linux Mint, you need to fix the filesystem errors on the corrupted partition using the command:

(initramfs) fsck/dev/mapper/ubuntu--vg-root-y

Once the filesystem is repaired, reboot the computer:

... /dev/mapper/ubuntu--vg-root: ***** FILE SYSTEM WAS MODIFIED ***** /dev/mapper/ubuntu--vg-root: 725778/7512064 files (0.8% non-contiguous), 1160813/3002163 blocks (initramfs) reboot
initramfs ubuntu error

0 Comments

Leave a Comment