On 09/03/18 19:57, Charles E. Blair wrote:
I have been getting messagessuperblock mount time in future, probably due to hardware clock incorrectly set.I tried using hwclock to fix this, but don't know what I'm doing. I created the batch file: date > datetest hwclock >> datetest and ran it to get the output: Fri Mar 9 00:49:11 CST 2018 2018-03-09 00:49:58.592967-0600 Any advice on a simple fix is welcome.
Compare with another time source. Which is correct? Are you running ntpd? Startup/shutdown scripts should load/store time from the hardware clock.Do you have /etc/adjtime? This file will persist drift information and hardware clock time zone. Try deleting it.
I do not think this is a time zone issue; hwclock displays time in your local time zone even when stored in UTC.
Kind regards, -- Ben Caradoc-Davies <ben@transient.nz> Director Transient Software Limited <https://transient.nz/> New Zealand