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

touch /forcefsck [SOLVED]

Help for Current Versions of MX
Message
Author
User avatar
fehlix
Forum Guide
Forum Guide
Posts: 2395
Joined: Wed Apr 11, 2018 5:09 pm

Re: touch /forcefsck

#21 Post by fehlix » Thu Jul 05, 2018 5:40 pm

turtlebay777 wrote:
Thu Jul 05, 2018 8:45 am
...
sudo touch /forcefsck is redundant on debian.
...
You found the answer to your question yourself. Well done.
Let me sum up what we've learned.

To manually start a complete filesystem-check on MX Linux at boot time,
you can use one of the following kernel boot parameters.

Code: Select all

forcefsck 
or

Code: Select all

fsck.mode=force
All partitons from /etc/fstab, where last field fs_passno is greater than 0, will be
undergo a complete filesystem check at next boot.

To have a regular full check carried out you could use this command
as :
sudo tune2fs -c60 -C61 -i30 device
where device = the device to be checked. e.g. /dev/sda1 ,
and with some example settings:
-c60 = max-mount-counts 60
-C61 = set the number of times the filesystem has been mounted.
61 > 60 : will check the filesystem at the next reboot
-i30 = interval-between-checks : 30 days
To disable automatic regualar full fs-check:
sudo tune2fs -c0 -i0 device
Gigabyte Z77M-D3H, Intel Xeon E3-1240 V2 (Quad core), 32GB RAM,
GeForce GTX 770, Samsung SSD 850 EVO 500GB, Seagate Barracuda 4TB

turtlebay777
Forum Regular
Forum Regular
Posts: 245
Joined: Sat Apr 14, 2018 2:40 pm

Re: touch /forcefsck [SOLVED]

#22 Post by turtlebay777 » Fri Jul 06, 2018 6:10 am

This is what Linux is all about, discovering ways of using our chosen OS and solving problems through team work. MX is a great system and I thank the experts and users for their help in solving such issues. Certain other distros have specialists who seem to be a law unto themselves and if one disagrees with their pronouncements and set solutions you are ridiculed. Not so MX and Antix.
Thanks Fehlix and all.

Be OK
Forum Novice
Forum  Novice
Posts: 37
Joined: Thu Aug 17, 2017 7:00 am

Re: touch /forcefsck [SOLVED]

#23 Post by Be OK » Sun Jul 08, 2018 8:52 am

Wonder if that works for the EFI drive to ? lsblk give

Code: Select all

 sda      8:0    0 931.5G  0 disk 
├─sda1   8:1    0   256M  0 part /boot/efi
├─sda2   8:2    0 929.2G  0 part /
└─sda3   8:3    0     2G  0 part [SWAP]
sdb      8:16   0   1.8T  0 disk 
└─sdb1   8:17   0   1.8T  0 part /media/jan/mobile-1
sr0     11:0    1  1024M  0 rom  
sda1 this case as its fat :)

User avatar
fehlix
Forum Guide
Forum Guide
Posts: 2395
Joined: Wed Apr 11, 2018 5:09 pm

Re: touch /forcefsck [SOLVED]

#24 Post by fehlix » Sun Jul 08, 2018 9:23 am

Be OK wrote:
Sun Jul 08, 2018 8:52 am
Wonder if that works for the EFI drive to ?
IMHO, neither vfat nor ntfs, will be checked.

EDIT: Correction: Just verified: forcefsck will also force vfat to be checked.
The log is available at /var/log/fsck/checkfs.
Gigabyte Z77M-D3H, Intel Xeon E3-1240 V2 (Quad core), 32GB RAM,
GeForce GTX 770, Samsung SSD 850 EVO 500GB, Seagate Barracuda 4TB

Post Reply

Return to “MX Help”