How To Fix Busybox Initramfs Error On Linux based OS

Author - Webner
6.09.2021
|
0 Comments
||

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 dev@webners.com for your Insurance, eLearning and Salesforce applications.

Leave a Reply

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