If the ZimaOS Web UI shows the wrong date after a BIOS reset, check the hardware clock, timezone and NTP state separately before replacing components. In this 1.4.1 Beta thread, timedatectl showed that the system clock was not synchronized and the NTP service was inactive.
This is the same forum thread previously processed from page 2 in Batch 34. This file is an updated replacement built from the full thread, not a second article with a new search intent.
What the Thread Actually Confirmed
The user had reset BIOS settings and changed RAM. The Web UI briefly displayed the correct time, then reverted to an old date. IceWhale first suggested checking the CMOS/BIOS battery, but another user reproduced the issue with a new battery, so battery failure was not proven as the only cause.
The most useful diagnostic evidence was timedatectl: timezone and RTC values were present, but synchronization was off and NTP was inactive.
Check RTC, Timezone and NTP as Separate Layers
First set the BIOS/RTC to a sane value, then boot ZimaOS and run timedatectl. Compare local time, UTC time, RTC time, timezone, “System clock synchronized” and “NTP service.”
If the hardware clock resets again after the machine has been unplugged, the CMOS battery or firmware configuration remains relevant. If the RTC is stable but NTP is inactive, treat that as an operating-system time-sync problem instead.
Do Not Assume the 1.4.1 Beta Behavior Is Current
The report came from a 2025 beta build. The current ZimaOS 1.7.1 release notes is many releases newer, so reproduce the problem on the current stable version before applying an old workaround.
The current ZimaOS terminal guide provides the supported terminal access path.
Why Wrong Time Can Break More Than the Clock
Incorrect system time can make HTTPS certificates, package downloads, Docker registries and scheduled jobs fail in ways that appear unrelated. The app failure checklist uses system time as an early diagnostic gate.
If only one container shows the wrong timezone while the host clock is correct, use the container timezone guide instead of changing the NAS clock.
Bottom Line
The forum thread did not prove a single permanent fix. It showed a useful diagnostic split: firmware/RTC state, NTP state and Web UI behavior can fail independently. On a current ZimaOS release, verify all three before replacing the battery, reinstalling the OS or manually compensating the clock.
