Yeah, that's what I was intending to do, but the question is, should I? I mean, won't those corrupted files disrupt the computing?
Depends on which files are involved and what type of error. I once had a machine with some sort of FS error (on ext3, that was caused by mounting it via a utility on Windows, bleh) that I couldn't figure out and didn't have the time to. I let it run for almost a couple months with no problems.
]]>EDIT: realized that wasn't very clear. For example,
UUID=c022f3bf-a633-470e-807a-6db5e9131118 / ext3 defaults 0 1
should become
UUID=c022f3bf-a633-470e-807a-6db5e9131118 / ext3 defaults 0 0
Notice the far right 1 has been changed to a 0.
]]>Well, first of all, are you sure that fsck just stalled? It can take some time to finish a full fsck, perhaps you were just impatient. When did that initial fsck occur?
You should get to the bottom of this and make sure that fscks don't stall, instead of disabling them.
Well it went like this... I rebooted the pc after forcing it shutdown, then during that bootup it said some files contained errors, and it died out spitting errors while checking files.
Filesystem checks should not be disabled, because:
* Filesystem drivers can contain bugs. Hopefully the checker-and-repairer doesn't
* Hard drive platters wear out, causing errors all by themselves - mostly automatically fixable, which is why we don't see them.
I don't think (or wholeheartedly hope) that the ext3 drivers are buggy.
And I don't think it has to do with the hard drive because other Linux distros and Windows run fine.
]]>* Filesystem drivers can contain bugs. Hopefully the checker-and-repairer doesn't
* Hard drive platters wear out, causing errors all by themselves - mostly automatically fixable, which is why we don't see them.
]]>You should get to the bottom of this and make sure that fscks don't stall, instead of disabling them.
]]>So, if you say it is not good to disable it permanently, then what can I do instead? Please elaborate.
Thanks
]]>Yes, disabling file system checks should be done via fstab. But remember, file system checking is there for a reason, so don't disable it permanently.
]]>Tomorrow I will be trying to install Arch 2008.06 again, but this time I don't want it to become unbootable.
So I was wondering, is it safe to just disable that filesystem check or is there any other way? If I have to disable the fsck is it enough to edit /etc/fstab?
Please reply. Thanks
]]>