I have a 2 fold issue that I thought was issue 1 causing issue 2... 

 

My clock in Unraid will not stay sync'd with the current time, I have tried setting it manually and using available NTP servers, nothing works.

I did have to replace the mainboard battery and the clock in the BIOS is current as of my last reboot.

 

My 2nd issue is that I cannot update successfully from 6.6.7 to 6.7.2

When I did the first time the system ran for 12 hours and then locked up.

I had to do a hard shutdown and when it cam back up it lasted 30 mins and locked up again.

Nothing works not even from the console on the server.

I restated a 3rd time, in SAFE mode, and still same issue, locks up after 30 mins.

 

I rolled back to 6.6.7 and the server runs fine, other than the time issue.

 

I am attaching Diagnostics from 667, have not tried to pull them on 672.

 

I see the time error listed in the logs but not much else, hoping a 2nd pair of eyes may catch something.

 

Thanks...

 

 

unraid1-diagnostics-20191212-0318.zip

   https://tf.nist.gov/tf-cgi/servers.cgi

 

You might want to read this noting this statement.

Quote

3. The generic name      time.nist.gov      will continue to point to all of our servers on a round-robin basis, and users are encouraged to access the service using this name.

 

Even after taking that into account and making the change, unraid clock still lost 2 hours overnight.

Will verify the BIOS clock again with a reboot and set the unraid clock 1 more time.

I've seen a few of these issues on the board and never a resolution.

 

 

IF you shut the server down overnight, you might want to change the MB battery if your MB is over (say) four years old. 

 

You might also want to check for BIOS updates for that MB that specifically  address this issue.  (I hesitate to tell folks to just apply BIOS updates in hopes that will fix something unless the change notes say it will.)