BusyBox prob

[MXTux]

Good evening, I had the same problem with busybox. It says that "needs manual fsck to exit", so I ran MX23 liveusb>GParted>control on root partition with no errors, and had the same problem after rebooting to SSD. I mean: same busybox screen and message after fscking the partition where control is needed. Sorry, I don' t know how to post QSI.

[Eadwine Rose]

@MXTux I have created a topic for you. DOn't tack onto other people's posts, thanks.

QSI is quick system info, in the menu. Run it, copy for forum button, click paste in the post. Don't edit.

[MXTux]

Sorry, I'm new here and in other forums I was used to doing it this way. I suspected that QSI was the Quick System Info program, but I thought there was a feature in the editor to put it in the footer. Regarding the problem, can you help me? Now I am on another pc, so I can' t post system infos.

[Eadwine Rose]

You can paste the qsi in a post. Run it from the menu, copy for forum button, click paste in the post. Don't edit. You can do this on the target computer from the liveusb.

And no sorry, I cannot help with the issue.

[fehlix]

Good evening, I had the same problem with busybox. It says that "needs manual fsck to exit", so I ran MX23 liveusb>GParted>control on root partition with no errors, and had the same problem after rebooting to SSD. I mean: same busybox screen and message after fscking the partition where control is needed. Sorry, I don' t know how to post QSI.

Perhaps you can give us a clue as to what the “same problem” might be. Any error messages on the screen?
Also, have you made any attempt to install remove/repair change something before the incident has shown up.
Note: Busbox is loaded by the kernel at very first action from it's initramdisk (initrd), so in case you have another kernel maybe try to boot with another kernel, which may load a good working initrd.
Further sometimes is also good to have a look at the grub menu entry in case the parameter e.g like root=... are invalid, which can happen if user prefers to use /dev/sdXY device names instead of UUID= or LABEL=. B/c device names are assigned by the kernel at boot and can be different to the ones assigned when the grub-menu was generated.

[MXTux]

"The same thing" is that after a forced shutdown (by power button, because I couldn't 't shutdown it via software), rebooting PC I noticed that after splash screen, without any error screens, it boots to busybox and if I run the "exit" command it tries to run fsck but fails and says it needs manual fsck. So I have reboot to liveusb, ran gparted and control on the root partition with no errors and when I rebooted to SSD I got the same busybox screen. I didn't do anything strange before shutting down the PC for the first time.

[MXTux]

And I think I tried to boot with another kernel, and got same results. I don't know how GRUB parameters might be invalid, since I haven't changed anything since installation.

P.S:I tried to boot to another kernel now and got the same results. Busybox says that fsck returned status code 4.

[fehlix]

And I think I tried to boot with another kernel, and got same results. I don't know how GRUB parameters might be invalid, since I haven't changed anything since installation.

P.S:I tried to boot to another kernel now and got the same results. Busybox says that fsck returned status code 4.

Maybe good to see the QSI report, as mentioned already above.
What messages you see when you are on the (initramfs) busybox prompt?
The status code 4 means filesystem inconsistency,but you missed to mentioned what partition fsck reported this.
To poweroff at busybox prompt:
poweroff -fd0

[MXTux]

Fsck reported inconsistency on rootmx23 partition, and I didn' t mean I couldn't shutdown it from busybox, T couldn't' t shutdown it from MX desktop menu button immediately before noticing the problem, because it was unresponsive. I can' t access to the target computer now, so I can' t post QSI nor see busybox screen.

[indielinuxpower]

I had same thing happen after a recent Windows update. In my case, the update turned RAID on for the SATA Controller 'mode' in BIOS. Go to your BIOS settings find where it mentions SATA. Change to AHCI and you should be able to load MX completely. Of course you did not post your QSI, so only guessing that your issues that sounds just like mine was the same. It was an Intel driver update that Windows 10 forced update when I updated windows. Changing to AHCI fixed things. If Bios does not let you change things, you might have to Windows device manager and change first. In my case, on a Dell Micro 7060 it fixed things just going into BIOS to change things.