I'm having a small issue in antix 12 installed as a guest in VirtualBox. I had installed the MATE DE and I'm using lightDM instead of slim. After I had used it for a week or two I had a message on boot that there were file system errors and I needed to run fsck manually which I did. It seemingly found errors and corrected them. My problem is, now everytime I boot it says I have errors and it runs check fsck forced but it doesn't find any errors. So basically I have to wait till it runs the tests for no apparent reason. I'm not all that familiar with Linux other than how to theme it.

any thoughts?

no idea why that happens but you should be able to turn them off by opening / etc/ fstab, find your boot drive and home drive . then the last number at the end of those lines you need to change to a 0 i belive

Dave wrote:no idea why that happens but you should be able to turn them off by opening / etc/ fstab, find your boot drive and home drive . then the last number at the end of those lines you need to change to a 0 i belive

I'm not sure what you mean by boot and home drive. I just have the one drive which currently says...

UUID=47531206-6b30-4289-a35b-18c73f975cb6 / ext3 defaults,noatime 1 1

so you're saying I should change the 1s to 0s?

i think only the last one needs to be 0 but you can change both and it will be more than fine

Hi loukingjr ! Howdy ?

About fstab and the numbers at the end of the line, I know a nice web page which explains the basis of the fstab file.


========= SCRAPER REMOVED AN EMBEDDED LINK HERE ===========
url was:"http://www.tuxfiles.org/linuxhelp/fstab.html"
linktext was:"http://www.tuxfiles.org/linuxhelp/fstab.html"
====================================

melodie wrote:Hi loukingjr ! Howdy ?

About fstab and the numbers at the end of the line, I know a nice web page which explains the basis of the fstab file.


========= SCRAPER REMOVED AN EMBEDDED LINK HERE ===========
url was:"http://www.tuxfiles.org/linuxhelp/fstab.html"
linktext was:"http://www.tuxfiles.org/linuxhelp/fstab.html"
====================================

well hello Melodie! LTNS __{{emoticon}}__ danke for the link. __{{emoticon}}__

loukingjr wrote: My problem is, now everytime I boot it says I have errors and it runs check fsck forced but it doesn't find any errors.

Lou,

Check the root directory to see if there is a file named forcefsck. In other words, /forcefsck. If the file exists, remove it as root user.

djohnston wrote:

loukingjr wrote: My problem is, now everytime I boot it says I have errors and it runs check fsck forced but it doesn't find any errors.

Lou,

Check the root directory to see if there is a file named forcefsck. In other words, /forcefsck. If the file exists, remove it as root user.

well hi DJ __{{emoticon}}__ it's like old home week around here lol
I will look when I'm back in antix but changing the 1s to 0s also worked.

okay, no forcefsck in root but I'm marking this as solved because changing the fstab numbers to 0 0 seems to have worked.

The forcefsck file was a trick from the dev of the distro because the default partition tool was systematically removing the automatic forcefsck feature from the filesystem while creating it. At that time I went to the mdv chan to ask why they had tweaked drakdisk that way. I had a

The forcefsck file was a trick from Texstar, founder of the pclos distro because the default partition tool was systematically removing the automatic forcefsck feature from the filesystem while creating it. At that time I went to the mdv chan to ask why they had tweaked drakdisk that way. This was a story. The file forcefsck was to trigger the fsck at boot in case the system was closed brutally. Anyhow in Debian and derived this has never been a problem, the ext3 and above systems are checked automatically each 20 to 28 boots approximately. (And the related flag are the numbers at the end of the fstab lines).