Boot problem

[goersorg]

Hi, I have MX16-64 on my DT puter. During the boot process readout it eventually hangs with a message that the "fsck from util-linux 2.25.2 No such file or directory fsck.fat 3.0.27 (2014-11-12). I have set the the uitil-linux to do a fsck every 30 days, but it is being disobedient. It does the fsck for both root and user. It tells me to do a manuak fsck which I did, but no difference. It gives me the option to give root password for maintenance or ctrl-D to continue, which I have been doing. Any advice for this issue? Many thanks.

[tascoast]

I experienced this maintenance/Ctrl-D message recently. I realised that I'd almost filled the /root partition. I did need to delete a couple of large files, booting via a live USB or my AntiX 16 partition, but once space was available, normal booting resumed.

[goersorg]

My root partition is 15.9Gb, only 49% is used.

[skidoo]

No such file or directory fsck.fat

Maybe the message is reporting, literally, a missing file?

sudo updatedb & sudo locate fsck.fat
found /sbin/fsck.fat on my system, so I checked dpkg-query -S /sbin/fsck.fat and the output shows it was installed by "dosfstools" package.

AFAICT, dosfstools is only a "recommends" for the util-linux package. If so, it might have been uninstalled by an "apt get autoremove whee yay now im clean" operation?

I would: reinstall the dosfstools package, reboot, retest.

[goersorg]

I get this now:
fsck exited with error code 6
dosfstools is installed ok
I must press ctrl-D to continue to start mx16
Any suggestions anyone?

[asinoro]

From live usb or other linux os:
viewtopic.php?f=104&t=42094&p=412492&hilit=fsck#p412492

[goersorg]

I followed through with that article, but it made no difference.
May have to reinstall MX sometime?

[Adrian]

Why fsck.fat did you install on a FAT partition? If not, can you check from Live environment what the partitions look like? You can also run fsck from Live.

You shouldn't need to reinstall, at this point you have two choices, have patience and try to find the root cause of the problem or at least a solution (that might take more time and effort than re-installing but you might learn something, plus you might be able to avoid the problem in the future) or reinstall it can be done pretty quickly, like I said probably faster than figuring out what the problem is. Your choice...