In that case, please boot into the rescue mode and try to repair the filesystem. One of the user has commented that he/she can't type anything in the initramfs prompt. What If I can't Fix It From Busybox Shell? Try Rescue Mode In order to fix initramfs error in Debian-based systems, simply follow the aforementioned steps. The initramfs error can occur on Debian, and other Ubuntu derivatives such as Pop OS, Linux mint etc. In that case, it is recommended to backup the data and replace the hard disk as soon as possible. Heads Up: If you keep getting this error often, probably your hard disk is getting weaker. If you are stuck in initramfs prompt, this guide will definitely help to fix initramfs error in Ubuntu. These steps helped me and many others (see the comment section below) to solve Busybox Initramfs error on Ubuntu Linux operating system. If the reboot command doesn't work, type exit and hit ENTER.Ĭross your fingers and wait for the system to reboot! If all went well, your system will boot normally without any problem. Next, type reboot and hit ENTER to restart your system! (initramfs) rebootįix Busybox Initramfs Error On Ubuntu Linux Now the fsck command will start to fix all bad blocks automatically in the filesystem.Īfter a couple minutes, you will see an output like below: /dev/sda1: ***** FILE SYSTEM WAS MODIFIED ***** Otherwise, you should manually type -y and hit ENTER each time to fix an error.Ģ. Refer this guide to list disk partitions in Linux. You can use cat /proc/partitions or blkid or lsblk commands to get your Linux partition details in Busybox. In your system, it could be /dev/sdb1, /dev/sdc1 etc. Replace /dev/sda1 with your partition name. To solve initramfs error on Ubuntu Linux, you need to repair the filesystem in the corrupted partition using fsck command like below: (initramfs) fsck /dev/sda1 -y Fix Busybox Initramfs Error On Ubuntu Linuxġ. It contains the tools and scripts required to mount the file systems before the init binary on the real root file system is called. Initramfs is an initial ram file system based on tmpfs. It provides replacements for most of the utilities you usually find in GNU fileutils, shellutils, etc.
STARTX WONT WIRK ROOT UBUNTU MANUAL
The root filesystem on /dev/sda1 requires a manual fsck.įor those wondering, BusyBox is software suite that provides many common UNIX utilities into a single small executable.
dev/sda1: UNEXPECTED INCONSISTENCY RUN fsck MANUALLY. dev/sda1: Inodes that were part of a corrupted orphan linked list found. dev/sda1: Inode 4329004 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 4326843 extent tree (at level 1) could be narrower, IGNORED. Inode 4326476 extent tree (at level 1) could be narrower, IGNORED. dev/sda1 contains a file system with errors, check forced. So I simply passed the exit command to see what happens.Īnd then I saw the actual error: (initramfs) exit I wasn't sure about what to do at this point. Also it doesn't show what exactly the problem is. BusyBox v1.30.1 (Ubuntu 1:1.30.1-4ubuntu6.1) built-in shell (ash)Įnter 'help' for a list of built-in commands.
0 kommentar(er)
