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 upgrade to 7.0.0746 before applying this update.

Here, we sincerely thank @crisisacting, @rfbjr, @Nitrokalel, @Alak, @apvm, @Nikdfish, @OttO1916, @vitali, @ambul, @Gremlin, @sianderson, @Arktander 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 (Next Tuesday): 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 an app whose version number contained a “-” symbol could not be updated normally after the new version was released.
2. Fixed the issue where the app name was displayed abnormally in some prompts in the App Center.
3. Fixed the issue where certain APIs did not properly validate path parameters.
4. Fixed the issue where improper permission validation on certain APIs allowed non-admin users to gain unauthorized access to restricted features.
5. Fixed the issue where hidden files were not deleted along with the others when selecting all with Ctrl+A and deleting after the display of hidden files was enabled.
6. Fixed the issue where the “NEW” badge of some newly listed apps extended beyond the display area.

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.1341 update package (MD5: c5497111e8b47b28ee1ff4cfc8bb4658);
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.

Updated and if there is any problem will report here. Thanks.

Successfully updated my F4-425 Plus to TOS 7.0.1341.

After the update, I noticed unusual NTP behaviour. Initially, ntpq -pn showed only one server, and eventually the * indicating the selected server disappeared.

I temporarily changed my customized NTP server setting, saved it, changed it back to au.pool.ntp.org, saved again, and rebooted the NAS.

Since then, ntpq -pn shows multiple server entries, a selected NTP server, and successful synchronisation appears to have resumed. The latest readings look normal, but I'll continue monitoring to see whether the behaviour returns.

Has anyone else noticed similar NTP behaviour with this release?

nitzer71 wrote: ↑Yesterday, 10:28

Thanks for your detailed report. This information is very helpful for us.

The behavior you described (only one server shown in `ntpq`, and the selected `*` marker disappearing after the firmware update) is an intermittent known issue related to NTP service restart. It can be triggered by firmware updates, saving time settings or rebooting. In this short period, the NTP daemon may temporarily have no selected upstream time source, and will stop synchronizing until it re-converges.
Another factor: domain-based NTP pools such as `au.pool.ntp.org` may not always be resolved via DNS into multiple upstream servers. This reduces sync stability and may result in only a single server entry displayed.

Re-saving NTP settings forces the service to reload and re-resolve the pool, and a clean reboot helps network and DNS initialize properly. Seeing multiple servers and selected marker after that is expected.

We have taken note of your feedback.
Thank you.

All four devices updated w/o issue. I checked the NTP on all and they still show the North-America one and that ntpq command all showed just one entry.

both mine have been updated without any noticeable issues

The problem has returned — the web interface won’t load after a firmware update.

I had to completely reinstall the system after this update.


I’ll stick with TOS 7.0.1298.


At the same time, 620 GB of garbage disappeared. There are 6 GB left, and that’s the operating system, instead of 620 GB of junk! Do something about this!

Bonsoir,

Tout s'est bien passé lors de cette mise à jour et tout fonctionne comme avant. Aucune des corrections annoncées n'avaient d'incidence sur mon système.

A noté tout de même les données enregistrées par "Surveillance Manager" dans mon dossier "surveillance". Dans le détail de l'occupation du Volume, elles sont toutes identifiées comme "Autre" alors que dans les faits, il 'agit bien d'un dossier partagé. Ceci dit, tant que tout est bien comptabilisé... Je trouve juste étrange que TOS 7 comptabilise ainsi. Notez également que je n'ai aucune référence de TOS 6 à ce sujet. Je n'ai installé surveillance manager que récemment.



Bonne soirée et merci encore de la réactivité de votre équipe de développement sur TOS 7. Une nouvelle version par semaine avec des corrections, c'est géant

Alak wrote: ↑Yesterday, 23:38 Bonsoir,

Tout s'est bien passé lors de cette mise à jour et tout fonctionne comme avant. Aucune des corrections annoncées n'avaient d'incidence sur mon système.

A noté tout de même les données enregistrées par "Surveillance Manager" dans mon dossier "surveillance". Dans le détail de l'occupation du Volume, elles sont toutes identifiées comme "Autre" alors que dans les faits, il 'agit bien d'un dossier partagé. Ceci dit, tant que tout est bien comptabilisé... Je trouve juste étrange que TOS 7 comptabilise ainsi. Notez également que je n'ai aucune référence de TOS 6 à ce sujet. Je n'ai installé surveillance manager que récemment.



Bonne soirée et merci encore de la réactivité de votre équipe de développement sur TOS 7. Une nouvelle version par semaine avec des corrections, c'est géant

Thank you for your attention to my question! But we have different NAS models.

Merci pour l'intérêt que vous portez à ma question ! Mais nous avons des modèles de NAS différents.