Does the LS-X1 have a battery?

[Kane88]

Since I read the post, I'm trying this on a TS-XEL.
Can someone explain why this tried to set an incorrect time on Debian 10.3?

Also, how can I check to see if the RTC in a TS-XEL unit- is working ok?

root@debian:/# dmesg | grep -i rtc
[    3.397464] rtc_cmos 00:01: RTC can wake from S4
[    3.397776] rtc_cmos 00:01: registered as rtc0
[    3.397842] rtc_cmos 00:01: alarms up to one month, y3k, 114 bytes nvram, hpet irqs
[    3.707613] rtc_cmos 00:01: setting system clock to 2020-03-04 14:57:41 UTC (1583333861)


when I run date, the correct time is reported
root@debian:/# date
Mon 09 Mar 2020 05:21:12 PM CDT

[1000001101000]

are you checking on the nas or on your PC?

You appear to be comparing the rtc time at boot to your current time. Try comparing date to hwclock

[Kane88]

I'm running it on the nas using an ssh session.
And I was wrong, those were for the TS-WVHL, not the TS-XEL.

When I run dmesg | grep -i rtc on the TS-XEL, it just comes back to the prompt, with no info.  Any ideas why?

date and hwclock both display correct info for the TS-XEL though.  Is that all that needs to be checked?

[1000001101000]

dmesg shows the buffer of kernel output, if you've had enough messages rtc initialization might not be there anymore.

If date and hwclock reflect the current time you're in good shape. Honestly, if ntp is working you likely wouldn't notice an rtc problem. In fact in many cases the rtc module isn't loaded until after the clock is set at boot but then gets fixed by ntp a few seconds later.