TerraMaster Forum

Fixed?? OK, but not syncing with another local tnas configured as ntp server.
Error when setting server address in client "Operation Failed. Please ensure the server address is entered correctly. (or something like that.)
ntp.conf is written correctly as per earlier observation(s).
ntpq -p reports the server as the target, BUT NOT ACTIVE.
From previous comment I am guessing that the syncing process on the client is reaching out to DNS and obviously failing because it is on the local private network.
I will be checking other machines on the local network to see what they offer.

Update: APC Smart-ups quite happy with Tnas ntp server on local network. (Utilising network cards for comms) These devices were happily showing "ntp update failure" when I took the local ntp protocol off line.

Alak wrote: ↑27 Aug 2026, 19:22

So far, we have not received any other reports of this issue from customers, and we were also unable to reproduce it during our internal upgrade testing.

Please locate the upgrade logs in the `homes` directory using File Manager and send them to our technical support team at [support(at)terra-master.com]. Once we receive the logs, we will analyze them and investigate the issue further.

Gremlin wrote: ↑28 Aug 2026, 05:42

Thank you for your detailed feedback and testing!

We have confirmed this issue. Changing the NTP server address restarts the NTP service. For about 1‑2 minutes after restart, the service is temporarily unavailable for time sync, resulting in the "Operation Failed" prompt on the client. Please wait 1‑2 minutes and retry your configuration or synchronization.

We have reported this to our development team for optimization. Thanks again for your contribution!

LorenGuo wrote: ↑28 Aug 2026, 15:07

Noted. I have observed some odd results.
For example (on Tnas client) Where it drops into ntpq shell.
This is immediately after "successfully" reporting the server connection as "inactive". This appears to be random wrt timing and which Tnas client is being queried

Update - Windows (11 Pro) will not sync with Tnas. This is after the ntp service has been running for several hours on Tnas overnight. Windows "does it's thing" and eventually fails to update (and it will not allow the server address to be changed unless sync succeeds).

I would expect some more dialog towards a user, just to verify if he/she wants to execute right now.
Downloading the file to the NAS (F4 425Pro), immediately resulted in a system update (no chance for me to first close stuff I was engaged in, which I would have preferred to close down).

Then again, no issues during update. Pretty smooth.

One question, looking at the log, what is this about after a System boot?
Eject usb disk_sbd

Gremlin wrote: ↑28 Aug 2026, 15:48

Thank you for your logs and observations. Our team will reproduce and follow up on this issue locally. We will keep you updated.

Patchoro wrote: ↑28 Aug 2026, 17:56

On the update page, we provide two options: “Download” and “Download and Update.” If you do not want to update the system immediately, you can select “Download” to download the update package and install it later when needed.

The log message “Eject usb disk_sbd” usually indicates that TOS performed an eject or unmount operation on a USB disk during system startup.

This log entry alone does not provide enough information to determine the cause of the issue. Please provide the complete log context before and after this message, along with more details about the current symptoms or issue, so that we can investigate it further.

Thanks for the quick response. Since I have no USB devices connected I was wondering what this was about.
Does this refer to an onboard USB?

Regarding logs, these are very limited in the GUI. Sudo is also quite limited in the default OS.
I have now enabled debugging, so I can fetch the system log for better insight in future events.

online update not possible and why manual download speed is so slow? its not because of my download speed. I am located in austria.

Patchoro wrote: ↑28 Aug 2026, 18:57

Yes, your guess is correct.

In the hardware design of TerraMaster NAS, identifiers like "disk_sbd" typically point to an internal USB port on the motherboard, not the front or rear USB port you plug in.

This internal USB port may be used for:
Booting the system (for example, in some models, the TOS bootloader resides in the onboard USB storage).

Therefore, even if no external USB device is physically connected, the system may still attempt to detect or unmount this onboard USB device during startup, resulting in this log generation.

Regarding log acquisition:
The limited GUI logs and restricted sudo privileges you mentioned are indeed common in TOS's default configuration. Enabling debug mode for more detailed system debug logs in the future is perfectly correct.

In TOS 7, sudo is not required when executing commands. TOS 7 runs terminal sessions with administrator privileges by default; simply enter the command without additional privilege escalation.