unexpected inconsistency; run fsck manually SOLVED
Forum rules
Before you post read how to get help. Topics in this forum are automatically closed 6 months after creation.
Before you post read how to get help. Topics in this forum are automatically closed 6 months after creation.
unexpected inconsistency; run fsck manually SOLVED
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.
Reason: Topic automatically closed 6 months after creation. New replies are no longer allowed.
- Pjotr
- Level 24
- Posts: 20124
- Joined: Mon Mar 07, 2011 10:18 am
- Location: The Netherlands (Holland) 🇳🇱
- Contact:
Re: boot up fail BUSYBOX
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:
(if you type: the letter F is a capital letter)
Press Enter.
Copy/paste the output in your next message.
- 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
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.
Keep your Linux Mint healthy: Avoid these 10 fatal mistakes
Twitter: twitter.com/easylinuxtips
All in all, horse sense simply makes sense.
Re: boot up fail BUSYBOX
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
Re: boot up fail BUSYBOX
Try a check out system partition from a live CD/USB and when You are logged in the live system try
sdxn must be your system partition
Code: Select all
sudo fsck -yv /dev/sdnx
sdxn must be your system partition
Re: boot up fail BUSYBOX
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.
Re: boot up fail BUSYBOX
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
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
Re: boot up fail BUSYBOX
that's what I was saying, a manual check, but you seem to have the encrypted partition and I do not mean it
Re: boot up fail BUSYBOX
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.
Re: boot up fail BUSYBOX
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 commandsshez375 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.
Code: Select all
sudo fdisk -l
sudo lsblk --sort name --output name,size,uuid,fstype,mountpoint
Re: boot up fail BUSYBOX
You will have to boot to the live media and runshez375 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.
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
Re: unexpected inconsistency; run fsck manually
turns out that the motherboard is terminal