Will not sync time at first boot

[keithg]

Trying to set up a new Truenas, but scale this time instead of core. I have the install completed, but before I move over my zfs volume, I want to make sure it is all up and happy. I cannot get it to sync time:

admin@truenas[~]# timedatectl
Local time: Mon 2023-01-30 19:08:49 CST
Universal time: Tue 2023-01-31 01:08:49 UTC
RTC time: Tue 2023-01-31 01:08:49
Time zone: America/Chicago (CST, -0600)
System clock synchronized: no
NTP service: n/a
RTC in local TZ: no
admin@truenas[~]# sudo systemctl stop ntp
admin@truenas[~]# sudo ntpd -qg
30 Jan 19:09:01 ntpd[8645]: ntpd 4.2.8p15@1.3728-o Wed Sep 23 11:46:38 UTC 2020 (1): Starting
30 Jan 19:09:01 ntpd[8645]: Command line: ntpd -qg
30 Jan 19:09:01 ntpd[8645]: ----------------------------------------------------
30 Jan 19:09:01 ntpd[8645]: ntp-4 is maintained by Network Time Foundation,
30 Jan 19:09:01 ntpd[8645]: Inc. (NTF), a non-profit 501(c)(3) public-benefit
30 Jan 19:09:01 ntpd[8645]: corporation. Support and training for ntp-4 are
30 Jan 19:09:01 ntpd[8645]: available at https://www.nwtime.org/support
30 Jan 19:09:01 ntpd[8645]: ----------------------------------------------------
30 Jan 19:09:01 ntpd[8645]: proto: precision = 0.040 usec (-24)
30 Jan 19:09:01 ntpd[8645]: basedate set to 2020-09-11
30 Jan 19:09:01 ntpd[8645]: gps base set to 2020-09-13 (week 2123)
30 Jan 19:09:01 ntpd[8645]: Listen and drop on 0 v6wildcard [::]:123
30 Jan 19:09:01 ntpd[8645]: Listen and drop on 1 v4wildcard 0.0.0.0:123
30 Jan 19:09:01 ntpd[8645]: Listen normally on 2 lo 127.0.0.1:123
30 Jan 19:09:01 ntpd[8645]: Listen normally on 3 eno1 192.168.1.165:123
30 Jan 19:09:01 ntpd[8645]: Listen normally on 4 lo [::1]:123
30 Jan 19:09:01 ntpd[8645]: Listen normally on 5 eno1 [fe80::e6b9:7aff:fef3:6e2f%2]:123
30 Jan 19:09:01 ntpd[8645]: Listening on routing socket on fd #22 for interface updates
30 Jan 19:09:08 ntpd[8645]: ntpd: time slew +0.002271 s
ntpd: time slew +0.002271s
admin@truenas[~]# sudo systemctl start ntp
admin@truenas[~]# timedatectl
Local time: Mon 2023-01-30 19:09:17 CST
Universal time: Tue 2023-01-31 01:09:17 UTC
RTC time: Tue 2023-01-31 01:09:17
Time zone: America/Chicago (CST, -0600)
System clock synchronized: no
NTP service: n/a
RTC in local TZ: no

What am I doing wrong? All other linux devices seem to be able to get time synced, but all use systemd-timesyncd.

admin@truenas[~]# sudo systemctl status ntp
● ntp.service - Network Time Service
Loaded: loaded (/lib/systemd/system/ntp.service; enabled; vendor preset: enabled)
Active: active (running) since Mon 2023-01-30 19:30:45 CST; 1s ago
Docs: man:ntpd(8)
Process: 23397 ExecStart=/usr/lib/ntp/ntp-systemd-wrapper (code=exited, status=0/SUCCESS)
Main PID: 23402 (ntpd)
Tasks: 2 (limit: 37939)
Memory: 1.0M
CPU: 25ms
CGroup: /system.slice/ntp.service
└─23402 /usr/sbin/ntpd -p /var/run/ntpd.pid -c /etc/ntp.conf -u 114:119

Jan 30 19:30:45 truenas ntpd[23402]: Listen and drop on 0 v6wildcard [::]:123
Jan 30 19:30:45 truenas ntpd[23402]: Listen and drop on 1 v4wildcard 0.0.0.0:123
Jan 30 19:30:45 truenas ntpd[23402]: Listen normally on 2 lo 127.0.0.1:123
Jan 30 19:30:45 truenas ntpd[23402]: Listen normally on 3 eno1 192.168.1.165:123
Jan 30 19:30:45 truenas ntpd[23402]: Listen normally on 4 lo [::1]:123
Jan 30 19:30:45 truenas ntpd[23402]: Listen normally on 5 eno1 [fe80::e6b9:7aff:fef3:6e2f%2]:123
Jan 30 19:30:45 truenas ntpd[23402]: Listening on routing socket on fd #22 for interface updates
Jan 30 19:30:45 truenas ntpd[23402]: kernel reports TIME_ERROR: 0x41: Clock Unsynchronized
Jan 30 19:30:45 truenas ntpd[23402]: kernel reports TIME_ERROR: 0x41: Clock Unsynchronized
Jan 30 19:30:45 truenas systemd[1]: Started Network Time Service.

 

[keithg]

I finally got sync.

 

[doug123]

I finally got sync.

I seem to be having the same issue. What was the solution for you?

 

[keithg]

I set the time as best I could in bios to UTC time. Then I set my time zone to Chicago in the UI and waited and it finally got sync.

 

[jgreco]

I seem to be having the same issue. What was the solution for you?

The usual answer is to replace your CMOS battery and then make sure BIOS time is properly set to UTC.

 

[doug123]

That was it, I went straight into software setup didn't check my bios thank you.