Mint Linux BusyBox

[Ashlek]

Hey,
I have a dual boot set up on my old laptop (Windows 10 alongside Mint Cinnamon) and the Windows partition works flawlessly. However everytime I shut down Mint, I will get a BusyBox boot error the next time I boot into Mint.
Although it's an easy fix, with just a few simple commands:
(initramfs) fsck /dev/sda6 - y
(initramfs) reboot
it is quite annoying to go through that process everytime I want to boot into Mint.
What's causing the error and is there a permanent fix?
Thanks in advance.

[Cybertao]

The initram process is having issues mounting /dev/sda6. What is the partition, and what does journalctl have to say about it?

[Ashlek]

引用自 Cybertao：

The initram process is having issues mounting /dev/sda6. What is the partition, and what does journalctl have to say about it?

The /dev/sda6 partition is the partition where Mint is installed. I don't know what journalctl is, sorry, I'm a linux noob.

[Ashlek]

Maybe it's worth mentioning that I had Ubuntu installed prior to Mint and I had the same issue.

[Cybertao]

When you boot and it bombs out into the busybox environment, type 'journalctl -b'. It shows the logs and you'll find something more specific about the problem.

[Ashlek]

引用自 Cybertao：

When you boot and it bombs out into the busybox environment, type 'journalctl -b'. It shows the logs and you'll find something more specific about the problem.

Alright, I'll do that as soon as possible. I can't use the laptop at the moment but I'll report back when possible.

[Marlock]

If a different distro had the same issue on the same partition it is likely that the drive partitioning is causing this.

Also:

Check if you have "fastboot" or something like that enabled on the BIOS/UEFI.

There was a whole generation of laptops with Windows fastboot support implemented in their BIOS/UEFI that were poorly implemented, causing some cache data needed for fastboot to be written over linux partitions (sometimes on the same HDD or on special small SSD drives).


Also:

Grub should have been updated by the linux mint installer, but maybe it has some sort of wrong parameter in it... did you try running "boot-repair" to see if it helps fix you issue?


PS: I never had this kind of issue so my ideas are conjectural. If you didn't do this yet, googling for exactly the error messages you are seeing might give you better insight.