Cannot Maintain Accurate Clock Settings; Resets Itself At Boot

[vexedoldhag]

Hi guys,
I installed LL yesterday; I am using Mint on other pcs and have not encountered the following problem before.
This is the only issue I am having with the install. All else works well.

The system clock will not maintain the correct time.
Post install, it read Feb 2016 and was hours behind as well.
I have thus far tried:
sync to local server (nothing changes, wrong date/time stays displayed)
resetting manually via gui (corrects for the session but reverts to wrong time after reboot. However time is now only apx 30min behind and date is correct)
switching from UTC to local time via command line (same result as above)
reset clock in BIOS (date stays correct but time back to being hours behind))

This is on a custom built desktop not a laptop, runs like a dream and ran Mint 18.1 without issue so I cannot attribute the issue to hw.

I looked for the problem and found several references to this happening with dual boot setups; LL is currently the only OS on that machine.

Sound familiar to anyone?

[torreydale]

[member=6865]vexedoldhag[/member],

Using Menu, Settings, Time and Date, I don't see sync to local server as an option.  I do see "Keep synchronized with Internet servers" as an option.

[ralphy]

[member=6865]vexedoldhag[/member],

What [member=5239]torreydale[/member] said. Make sure that Time and Date Settings is configured to use the correct Time Zone and to stay synchronized with Internet servers.

From Terminal:

Make sure the timezone is properly set in your system

Code:

cat /etc/timezone
America/New_York   <= that's my timezone

Reconfigure... set your timezone:

Code:

sudo dpkg-reconfigure tzdata

... and reboot.

After reboot, check the NTP service is running...

Code:

systemctl status ntp

If it is running, let's tells the ntp daemon to correct the time regardless of the offset:

Code:

sudo systemctl stop ntp
sudo ntpd -gq
sudo systemctl start ntp

Unless the wrong timezone is set or else you have defined a local ntp server (a switch, a local server) that is forcing the time difference I'm not sure what could be causing such issue.

[Jocklad]

Could it just be a failing Cmos battery....?