Welcome!
Important information
-- Spectre and Meltdown vulnerabilities
-- Change in MX sources

News
-- MX Linux on social media: here
-- Mepis support still here

Current releases
-- MX-17.1 Final release info here
-- antiX-17 release info here

New users
-- Please read this first, and don't forget to add system and hardware information to posts!
-- Here are the Forum Rules

Boot problem

Help for Current Versions of MX
Post Reply
Message
Author
User avatar
goersorg
Forum Novice
Forum  Novice
Posts: 15
Joined: Sat Feb 11, 2017 9:58 pm

Boot problem

#1 Post by goersorg » Wed Apr 19, 2017 7:07 pm

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.
System: Host: mx17 Kernel: 4.13.0-1-amd64 x86_64 bits: 64 Desktop: Xfce 4.12.3
Distro: MX-17_x64 Horizon December 15, 2017

User avatar
tascoast
Forum Guide
Forum Guide
Posts: 1087
Joined: Sat Aug 06, 2011 4:58 am

Re: Boot problem

#2 Post by tascoast » Wed Apr 19, 2017 9:02 pm

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.
Lenovo ThinkCentre A58 4GBRAM (64-bit), MX17/MX-16/antiX17/Mint 19

User avatar
goersorg
Forum Novice
Forum  Novice
Posts: 15
Joined: Sat Feb 11, 2017 9:58 pm

Re: Boot problem

#3 Post by goersorg » Fri Apr 21, 2017 12:59 am

My root partition is 15.9Gb, only 49% is used.
System: Host: mx17 Kernel: 4.13.0-1-amd64 x86_64 bits: 64 Desktop: Xfce 4.12.3
Distro: MX-17_x64 Horizon December 15, 2017

skidoo
Forum Regular
Forum Regular
Posts: 891
Joined: Tue Sep 22, 2015 6:56 pm

Re: Boot problem

#4 Post by skidoo » Fri Apr 21, 2017 3:19 am

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.

User avatar
goersorg
Forum Novice
Forum  Novice
Posts: 15
Joined: Sat Feb 11, 2017 9:58 pm

Re: Boot problem

#5 Post by goersorg » Wed May 10, 2017 3:25 am

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?
System: Host: mx17 Kernel: 4.13.0-1-amd64 x86_64 bits: 64 Desktop: Xfce 4.12.3
Distro: MX-17_x64 Horizon December 15, 2017

User avatar
asinoro
Forum Regular
Forum Regular
Posts: 494
Joined: Mon Feb 22, 2016 12:26 pm

Re: Boot problem

#6 Post by asinoro » Wed May 10, 2017 6:22 am

If your case is solved edit [Solved] to your initial post title to help other users.
Don’t forget to Backup your system
Fix your Grub

User avatar
goersorg
Forum Novice
Forum  Novice
Posts: 15
Joined: Sat Feb 11, 2017 9:58 pm

Re: Boot problem

#7 Post by goersorg » Wed May 10, 2017 10:47 pm

I followed through with that article, but it made no difference.
May have to reinstall MX sometime?
System: Host: mx17 Kernel: 4.13.0-1-amd64 x86_64 bits: 64 Desktop: Xfce 4.12.3
Distro: MX-17_x64 Horizon December 15, 2017

User avatar
Adrian
Forum Veteran
Forum Veteran
Posts: 9018
Joined: Wed Jul 12, 2006 1:42 am

Re: Boot problem

#8 Post by Adrian » Wed May 10, 2017 10:54 pm

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...

Post Reply

Return to “MX Help”