TOS 7.0.1130 (x86) Official Release Update

[RyanYang]

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, @snapsh0t, @greentower, @DCCentR, @apvm, @nitzer71, @sianderson, @joka388, @Gremlin, @thomass112, @Claus, @Pe6yc, @rfbjr 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
Reminder:If you notice that CPU usage is occasionally high after the update, please go to App Center to update the Global Search app.

Bug Fixes:
1. Fixed the issue where local SMTP email notifications failed to send in some scenarios.
2. Fixed the issue where the Thunderbolt interface status was not refreshed promptly after plugging or unplugging the Thunderbolt cable.
3. Fixed the issue where the configured NFS domain did not take effect.
4. Fixed the issue where opening Docker Manager might incorrectly jump to App Center.
5. Fixed the issue where browser memory usage was too high when uploading large files.
6. Fixed the issue where domain group permissions could not be set properly in File Manager.
7. Fixed the issue where IPv6 was not disabled when the network interface was disabled.
8. Fixed the issue where the details page was not automatically refreshed after installing or uninstalling an app.
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.1130 update package (MD5: 0f7c688d818446e475e4ac7ade7ef9c3);
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.

[nitzer71]

NTP issue still present in TOS 7.0.1130

After updating to TOS 7.0.1130, the previously reported NTP issue still appears to be present. The NAS continues to select LOCAL(0) instead of an external NTP server, even though the external servers are reachable.

Code: Select all

ntpq -p

shows:

Code: Select all

*LOCAL(0)

Could you please confirm whether the NTP issue is not yet fixed in TOS 7.0.1130 and is still planned for a future update?

[TMroy]

Yes, the fix is not included in this version. Please wait for future new updates.

[DCCentR]

Thank you for your feedback. We have successfully reproduced the issue based on the information provided. Our team is currently discussing a fix. Please keep an eye on the release notes for future updates.

Has this been fixed since then?

[nitzer71]

Yes, the fix is not included in this version. Please wait for future new updates.

Additional finding regarding NTP:

I checked the NTP configuration on the NAS and noticed that LOCAL(0) is explicitly configured as the preferred source:

Code: Select all

server 127.127.1.0 minpoll 6 maxpoll 10 iburst prefer
server 0.pool.ntp.org iburst
server 1.pool.ntp.org iburst
server 2.pool.ntp.org iburst
server 3.pool.ntp.org iburst

Could you please confirm whether this prefer setting for LOCAL(0) is intentional and related to the NTP issue you've acknowledged?

[snapsh0t]

Updated easily enough but it hasn't restored the smartd service and I'd appreciate some help to get it back. Smartmontools, however, is present and I suspect is up to its usual tricks. I've set debug mode so should have more details in a couple of hours.

Code: Select all

Adm1n@Therver2:/# systemctl status smartd.service
Unit smartd.service could not be found.
Adm1n@Therver2:/# systemctl status smartmontools.service
● smartmontools.service - LSB: SMART monitoring daemon
     Loaded: loaded (/etc/init.d/smartmontools; generated)
     Active: active (running) since Tue 2026-08-11 06:25:08 BST; 2h 9min ago
       Docs: man:systemd-sysv-generator(8)
      Tasks: 1 (limit: 18631)
     Memory: 2.1M (available: 13.8G)
        CPU: 56ms
     CGroup: /system.slice/smartmontools.service
             └─14572 /usr/sbin/smartd --pidfile /var/run/smartd.pid

Aug 11 06:25:08 Therver2 smartmontools[14506]:    ...done.
Aug 11 06:25:08 Therver2 systemd[1]: Started LSB: SMART monitoring daemon.
Aug 11 06:55:12 Therver2 smartd[14572]: Device: /dev/sda [SAT], SMART Usage Attribute: 194 Temperature_Celsius changed from 62 to 57
Aug 11 06:55:12 Therver2 smartd[14572]: Device: /dev/sdb [SAT], SMART Usage Attribute: 194 Temperature_Celsius changed from 60 to 55
Aug 11 07:25:07 Therver2 smartd[14572]: Device: /dev/sda [SAT], SMART Usage Attribute: 194 Temperature_Celsius changed from 57 to 63
Aug 11 07:25:16 Therver2 smartd[14572]: Device: /dev/sdb [SAT], SMART Usage Attribute: 194 Temperature_Celsius changed from 55 to 60
Aug 11 07:55:07 Therver2 smartd[14572]: Device: /dev/sda [SAT], SMART Usage Attribute: 194 Temperature_Celsius changed from 63 to 57
Aug 11 07:55:07 Therver2 smartd[14572]: Device: /dev/sdb [SAT], SMART Usage Attribute: 194 Temperature_Celsius changed from 60 to 55
Aug 11 08:25:07 Therver2 smartd[14572]: Device: /dev/sda [SAT], SMART Usage Attribute: 194 Temperature_Celsius changed from 57 to 64
Aug 11 08:25:16 Therver2 smartd[14572]: Device: /dev/sdb [SAT], SMART Usage Attribute: 194 Temperature_Celsius changed from 55 to 62
Adm1n@Therver2:/# 

[CursaYang]

This issue is still under development; please wait for a future update.

[CursaYang]

smartd.service = smartmontools.service
Please execute the following command to re-enable smartd.service:

Code: Select all

systemctl enable smartmontools.init.service

Code: Select all

systemctl start smartmontools.init.service

Code: Select all

ln -s /etc/systemd/system/smartmontools.init.service /etc/systemd/system/smartd.service

Code: Select all

systemctl status smartd.service

[Lex]

After the update, the folder appeared again /"usr/static/images/file_manager

[crisisacting]

9. Fixed various other known issues.

Despite that non-specific & wide casting bug fix, based on the responses of others, neither of the previously observed NTP issue & docker issues are fixed; will only install to a standalone TNAS that's not in testbed nor production use.