TerraMaster Forum

Target Users:
Users currently running TOS 7.0.0746 or later versions.

Note:
If your TOS version is TOS 6, please refer to the TOS 7 update instructions first.
Important: This update is only applicable to TOS 7.0.0746 and newer. Users with older versions must first update to 7.0.0746 before applying this update.

Here, we sincerely thank @crisisacting, @nitzer71, @ambul, @DCCentR, @Lex, @Gremlin, @sianderson, @brunix86, @rfbjr, @snapsh0t, @Nitrokalel, @storageninja, @apvm, @OttO1916, @joka388, @evgennsib and others for your sharing and feedback. Your support helped us quickly identify and fix multiple issues.

Release Notes:
This update adopts a phased gray release strategy to ensure stability across different device models and network environments.
Phase 1 (Starting Today): The manual update package is now available for download on our forum. It will be rolled out in batches based on system version, device model, and region.
Phase 2 (In One Week): The full online push will officially begin. At that time, all users will receive an update notification and can complete the update by following the on-screen prompts.

Update Notes
Bug Fixes:
1. Fixed the issue where some applications could not scan USB device data.
2. Fixed the issue where MIB files could not be downloaded.
3. Fixed the issue where NFS mounting failed when the remote directory contained spaces.
4. Fixed the issue where the SMB mount prohibition rule became invalid after enabling the Guest user.
5. Fixed the issue where sssd.service would automatically start upon system reboot when no domain was configured.
6. Fixed the issue where the local clock was assigned an excessively high priority, causing NTP to be unable to retrieve a valid time source from external servers.
7. Fixed the issue where interface information was incorrectly displayed after selecting CHAP authentication when creating or editing a virtual disk.
8. Fixed the issue where, during SMART testing on all disks, the failure of some tasks to be created caused the status of the remaining tasks to display abnormally.
9. Fixed various other known issues.

Important Information:
1.Updating the system theoretically will not affect the data on your hard drives, but for safety, please make sure to back up your data in advance.
2.Before updating, ensure that your primary volume (usually volume1) has at least 3GB of available space. Insufficient storage space may cause the update to fail.
3.After the update, the IP address of your TNAS may change. Please use the TNAS PC desktop client to search for and reconnect to the device.

Update Procedure:
1.Download TOS 7.0.1163 update package (MD5: 7c5b4a5b2377607b66d8133c315b8c9e);
2.Go to TOS > Control Panel > General Settings > System > Update;
3.Select "Manual Update" and upload the downloaded update package file;
4.Follow the prompts to complete the update;
5.After the system update is complete, please refresh your browser;
6.The TNAS IP address may change after the update. If you cannot connect to your TNAS using the previous IP address, use the TNAS PC client to search for the new IP address;

Client Downloads:
1. Download TNAS PC 5.2.548 for Windows OS.
- MD5: 72701b52336af9fd8b97a6be9d5d5a7c
2. Download TNAS PC 5.2.548 for macOS (x86 architecture).
- MD5: baa63a179c43f73965ea9c31eeb9d61e
3. Download TNAS PC 5.2.548 for macOS (ARM architecture).
- MD5: bb933da867058884c4adfe44ead24afc
4. Download TNAS PC 5.2.548 for Linux.
- MD5: 06fe93f9ffe47147854a34f28d57fcc2
5. TNAS mobile for Android: Please search for "TNAS mobile" in the app store to install.
6. TNAS Mobile for iOS: Please search for "TNAS mobile" in the App Store to install.

Is the NTP configuration issue resolved in this build? Are more of the NTP settings exposed in the TOS web GUI?

crisisacting wrote: ↑Yesterday, 12:54

Yes, this issue has been fixed in this version.

I can confirm that the NTP issue appears to be fixed in TOS 7.0.1163.

After updating, the LOCAL(0) server is no longer present in the NTP configuration, and there is no longer a `prefer` setting associated with it.

The NTP configuration is now generated by the TOS time setting module rather than using the previous configuration.

NTP is correctly synchronizing with an external NTP server, and `ntpq` shows the external server as the selected peer (`*`).

The system status also reports:
This appears to resolve the previous issue where LOCAL(0) could be selected instead of an external NTP server.

Thank you for fixing this.

One question regarding the new NTP configuration in 7.0.1163:

After selecting a custom NTP server in Control Panel > Region & Language > Time, `/etc/ntp.conf` now contains only a single `server` entry for the configured NTP source.

Previously, `ntpq -pn` showed multiple NTP servers.

Is this intentional in the new NTP implementation, or does TOS handle additional/fallback NTP servers internally when only one server is configured in the GUI?

The current configuration is working correctly, but I would like to understand whether having only one upstream server is the expected behaviour.

updated ok

nitzer71 wrote: ↑Yesterday, 14:35

In the current 7.0.1163 implementation, configuring an NTP server via the GUI directly writes a single server entry into /etc/ntp.conf.

However, for pool domain names (such as pool.ntp.org), utilizing pool syntax or resolving multiple upstream IPs via DNS is indeed a better and more stable approach for redundancy.

We have logged this as an optimization request and submitted it to our product team to refine in a future update (e.g., adapting the directive to pool for domain-based time servers).

Thank you for bringing this to our attention!

RyanYang wrote: ↑Yesterday, 14:06

Great.

Updating stand-alone TNAS & testbed manually now; if nothing jumps out as problematic, will update clients' TNASes over upcoming long weekend via SD-VPN.

No issues during the updates.

updated from TOS 7.0.1130, did not update to 1140 and then this one, hope it work fine.