On Wed, Jan 01, 2020 at 03:58:25PM +0500, Mikhail Gavrilov wrote: > Hi folks. > > Strange things happen with my ext4 lately: > - At each boot, the file system is checked. > - When I launch fsck manually it didn't found any issue. > - But tune2fs report that last checked and mount time is Sun Dec 15, > but this is incorrect. The problem is casued by the fact that the mount time is incorrect, which indicates that the system time was incorrect at the time when the file system was mounted and when it fsck was run. Since the last write time was in the future, this triggered "time is insane" check. This is inconsistent with your report that started happening when you switched to a new motherboard. That's because the real time clock is not reporting the correct time when the system is booted. Later on, in the boot cycle, after the root file system is checked and remounted read-write, the system time is getting set from an internet time server. This then causes the last write time to be ahead of the last mount time, and "in the future" with respect to the real time clock. Normally, the hardware clock's time gets set to match system time when it is set from network time, or when the system is getting shut down cleanly, but your init scripts aren't doing this properly --- or you normally shut down your system by just flipping the power switch, and not letting the shutdown sequence run correctly. The other possibilty is the real time clock on your system is just completly busted (although normally when that happens, the last mount time would be in the 1970's.) Running "/sbin/hwclock -w" as root may fix things; as is figuring out why this isn't run automatically by your boot scripts. Another workaround is to add to /etc/e2fsck.conf the following: [options] broken_system_lock = true This will disable e2fsck's time checks. Cheers, - Ted
