Thinking about time

[outlaw]

I also have this problem -> Superblock last mount time in the future. (less than a day)
viewtopic.php?f=108&t=43589

I think this problem is specific to the Debian stretch release.
I've a MX-16 install on the same laptop / hard drive and this error message
does not appear when rebooting.

Interesting observation: The error message is not generated by the boot process
if I shutdown the system overnight. (or several hours)

Stevo, thanks for the input ... but no joy.
After applying your fix I updated the system time (time server) using the MX time tool.
Then synchronized the system time and hardware clock using the MX time tool.
Rebooting results in the same old error message.

A final word ... I don't think the time difference is significant.

Tom

[arjaybe]

Dreamer and/or Outlaw: Do you allow your system to set the time automatically? I do, and there's no conflict among my 5 installs.

[dreamer]

Dreamer and/or Outlaw: Do you allow your system to set the time automatically? I do, and there's no conflict among my 5 installs.

I wouldn't say there is a conflict because my OSes are set to local time. I didn't like the fact that Ubuntu made ntp hard to remove and that the settings didn't provide a way to stop it from modifying BIOS clock at boot. Then I forgot about it. I don't really use Windows 10, but Windows 7 I used a lot and I'm pretty certain that after disabling timeserver in Windows 7 (a checkbox) it never modified BIOS clock.