Hi there,

I configured the BIOS of the serverˋs mainboard to start at 8 a-m. Using the dynamix sleep plugin, unRaid will shutdown at 11 p.m.

But, there is a problem with the time. After tellijg the BIOS the exact time, all is working as intended. unRaid is showing the correct time. While the day this is changing. Anything sets back the time for exactly 2 hours.

Why is unRaid changing the time for -2 hours within the day ? Is this a problem with the ntp server(s) ?

iirc correctly it sets UTC time upon shutdown and since were in summertime its 2 hours behind in 3 weeks it should be just 1.

Edited October 4, 2025Oct 4 by Mainfrezzer

I do not understand your reply in some parts, but do you know if my setings (for germany) are correct ?

At the momemt I do mot know why unRaid is changing time -2 hours, not right after booting up, but at some point later.

I believe that Unraid, like most Linux systems, keeps the RTC in UTC, the selected timezone set in the webGUI is applied only for display, e.g., the web interface, logs, and CLI commands show local time based on that setting.

So the shutdown time must be based on your local time, the BIOS wakeup time should be based on UTC time.

This is confusing. I do not understand, why the BIOS time is set -2 hours after some time despite configured correctly by me manually.

To me, it looks like unRaid is changing the time.

Is there any solution for both cloks, BIOS and unRaid, to run in sync ? Do I have to make some changes using the terminal ?

Just now, Blebbens said:

To me, it looks like unRaid is changing the time.

Again, this is normal with Linux, system clock is kept in UTC. You should be able to check with the output from hwclock --verbose

It's not a big deal; you can just use the UTC time to set the BIOS wake-up time.

But, I think then unRaid is starting with BIOS-time (-2 hours) and does sync it via ntp after some time.

Should be confusing to some backup solutions like time machine.

13 minutes ago, Blebbens said:

I think then unRaid is starting with BIOS-time (-2 hours) and does sync it via ntp after some time.

Nope,

27 minutes ago, JorgeB said:

keeps the RTC in UTC, the selected timezone set in the webGUI is applied only for display, e.g., the web interface, logs, and CLI commands show local time based on that setting.

1 hour ago, Blebbens said:

I do not understand, why the BIOS time is set -2 hours after some time despite configured correctly by me manually.

It fairly easy to understand, the clock chip of the computer has no idea of locations or timezones. It just stores the hours, mins and seconds.

So if a program sets the time, it has to decide, whether to ignore timezone and so on, or calc it back to UTC and then program this time to the chip.

Neither of one is good or correct, both would work, but one had to decide.

And Linux decided to use UTC, so the clockchips are running with the same values all over the world.

But for automatic power on, it has to compare this time to the stored time, now (in the BIOS) there is no Linux to calc "UTC from local time", its your manual job!

As I said, nothing is wrong or bad, you just have to know and obey.