How To Fix Busybox Initramfs Error On Linux based OS

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

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.
2. BusyBox v1.27.2 (Ubuntu 1:1.27.2–2ubuntu3.2) built-in shell (ash)
   Enter ‘help’ for a list of built-in commands.
3. (initramfs)
   — — — — — — — — — —
4. To resolve the initramfs error you need to run the following commands
5. (initramfs) fsck /dev/sda1 -y
6. Logs after run above command:
7. /dev/sda1: ***** FILE SYSTEM WAS MODIFIED *****
   /dev/sda1: 799258/32614517 files (2.4% non-contiguous), ……..
8. The above command will repair the corrupted partition, after this run the reboot command that I have mentioned below:
9. (initramfs) reboot
   Now your system willboot 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.

Originally published at https://blog.webnersolutions.com on September 6, 2021.