Error fix

Fixing Busybox Initramfs Error

Fixing Busybox Initramfs Error

Hello Hackers,

Lets read some Cybersecurity Blog’s

Today we will learn about some error that happens with our system and the error is Busybox Initramfs (The initramfs is a complete set of directories that you would find on a normal root filesystem).

It was a normal day, when I came across this error to my Dell Inspiron. I think this normally happens in only laptop which is Dual Bootable with Linux.

BusyBox v1.30.1 (Ubuntu 1:1.30.1-4ubuntu6.1) built-in shell (ash) 
Enter 'help' for a list of built-in commands.

(initramfs)

The upper thing I got as an error…

I was totally confused because it was the first time I have noticed this issue. So I have normally use exit command to get back from it…

(initramfs) exit
/dev/sda1 contains a file system with errors, check forced.
Inode 4326476 extent tree (at level 1) could be narrower, IGNORED.
/dev/sda1: Inode 4326843 extent tree (at level 1) could be narrower, IGNORED.
/dev/sda1: Inode 4327012 extent tree (at level 1) could be narrower, IGNORED.
/dev/sda1: Inode 4329004 extent tree (at level 1) could be narrower, IGNORED.
/dev/sda1: Inodes that were part of a corrupted orphan linked list found.

/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.30.1 (Ubuntu 1:1.30.1-4ubuntu6.1) built-in shell (ash)
Enter 'help' for a list of built-in commands.

This is what the actual error was!! because the /dev/sda1 partition is corrupted.

If you got this error anytime you can fix this error by fixing the Linux filesystem by using a command fsck(file system consistency check).

For fixing this initramfs error you can run the commands of fsck, to repair the Linux filesystem which has been corrupted…

(initramfs) fsck /dev/sda1 -y

This command will start repairing your corrupted filesystem in mine case it is /dev/sda1 in your it can be different or may be same filesystem…

After some time fsck will end up with its work and show a response like this,

/dev/sda1: ***** FILE SYSTEM WAS MODIFIED *****
/dev/sda1: 497733/30531584 files (1.5% non-contiguous), .......

Finally your corrupted filesystem will be perfectly allright,..

The final command is remaining is reboot

(initramfs) reboot

It will successfully reboot the system and now you will be able to open your OS.

Its done for today, GOOD BYE for now…

Happy Hacking!!

Share this post

About the author

Leave a Reply

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