unexpected inconsistency; run fsck manually SOLVED

Questions about Grub, UEFI,the liveCD and the installer
Forum rules
Before you post read how to get help. Topics in this forum are automatically closed 6 months after creation.
Locked
shez375

unexpected inconsistency; run fsck manually SOLVED

Post by shez375 »

Been having problems with 18.2, it keeps crashing and more often than not will not boot up.It now shows BUSYBOX and it waiting for a command.
Last edited by LockBot on Wed Dec 28, 2022 7:16 am, edited 3 times in total.
Reason: Topic automatically closed 6 months after creation. New replies are no longer allowed.
User avatar
Pjotr
Level 24
Level 24
Posts: 20124
Joined: Mon Mar 07, 2011 10:18 am
Location: The Netherlands (Holland) 🇳🇱
Contact:

Re: boot up fail BUSYBOX

Post by Pjotr »

Please generate an overview of your system like this:
- Launch a terminal window (this is how to launch a terminal window);
- make the terminal window full screen, to avoid chopped lines;
- Copy/paste this command into the terminal:

Code: Select all

inxi -Fxz
(if you type: the letter F is a capital letter)

Press Enter.

Copy/paste the output in your next message.
Tip: 10 things to do after installing Linux Mint 21.3 Virginia
Keep your Linux Mint healthy: Avoid these 10 fatal mistakes
Twitter: twitter.com/easylinuxtips
All in all, horse sense simply makes sense.
shez375

Re: boot up fail BUSYBOX

Post by shez375 »

hi thank you for your quick response, I cannot boot the system up to get a terminal.The boot up stops at BUSYBOX and is waiting for a command
minitux

Re: boot up fail BUSYBOX

Post by minitux »

Try a check out system partition from a live CD/USB and when You are logged in the live system try

Code: Select all

sudo fsck -yv /dev/sdnx


sdxn must be your system partition
shez375

Re: boot up fail BUSYBOX

Post by shez375 »

I can not boot into a live version. I have changed the boot order to cd rom but the GNI GRUB starts and will only try to boot from the hard disk at the point.
shez375

Re: boot up fail BUSYBOX

Post by shez375 »

here is a little more info.The GRUB is telling me this

unexpected inconsistency; run fsck manually
(ie,,without -a or -p option)
fsck exited with status code 4
the root filesystem on /dev/mapper/mint--vg-root requires a manual fsck
minitux

Re: boot up fail BUSYBOX

Post by minitux »

that's what I was saying, a manual check, but you seem to have the encrypted partition and I do not mean it
shez375

Re: boot up fail BUSYBOX

Post by shez375 »

yes, the partition is encrypted, I am entering the password and it excepts it and starts to load but always enters the busybox and I do not know what to do from there.
Laurent85
Level 17
Level 17
Posts: 7081
Joined: Tue May 26, 2015 10:11 am

Re: boot up fail BUSYBOX

Post by Laurent85 »

shez375 wrote:I can not boot into a live version. I have changed the boot order to cd rom but the GNI GRUB starts and will only try to boot from the hard disk at the point.
That's not related to the filesystem inconsistency. Retry booting a live session, check your bios settings or use the boot function key if available (usually F7 or F12). Then from a terminal run the following commands

Code: Select all

sudo fdisk -l
sudo lsblk --sort name --output name,size,uuid,fstype,mountpoint
Image
WharfRat

Re: boot up fail BUSYBOX

Post by WharfRat »

shez375 wrote:yes, the partition is encrypted, I am entering the password and it excepts it and starts to load but always enters the busybox and I do not know what to do from there.
You will have to boot to the live media and run sudo /sbin/cryptsetup luksOpen /dev/sda5 crypt assuming the partition is /dev/sda5 then sudo fsck -fyv /dev/mapper/mint--vg-root

In order to open the LUKS container you'll need to know the password which it appears you do :wink:
shez375

Re: unexpected inconsistency; run fsck manually

Post by shez375 »

turns out that the motherboard is terminal
Locked

Return to “Installation & Boot”