On Wednesday 09 September 2009 04:37:49 Maxim Wexler wrote: > Hi group, > > On an Asus netbook during boot after the line > > *checking all filesystems > > there'll be a message something like 'filesystem mounted 36 times > without being checked. Check forced' then something like '17.1% > non-contiguous' then a long delay. Then one of two things, either a > message saying 'errors fixed' or a forced reboot. > > What does it mean 'without being checked' Does the boot process expect > a filesystem check, in this case e2fsck? Why should their be errors. I > shut the machine like this '#shutdown -h(or -r) now' Everything is > unmounted and the machine turns off without a glitch that I''m aware > of. > > How can I run e2fsck on the drives *before* they are mounted, if that > is what is required here?
It's a feature of ext2. It doesn't have much in the way of internal checks when being used to make sure that it's structure is consistent, so the default setting is to force a full fsck after every X mounts or after every Y days, which ever comes first. You do not want to disable it. It is your safety net and the expected behaviour. It is working correctly as the fs is being checked before it is mounted. Read the various man pages related to ext2 for more info. -- alan dot mckinnon at gmail dot com
