TOS 7.0.1169 (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, @nitzer71, @ambul, @DCCentR, @Lex, @Gremlin, @sianderson, @brunix86, @rfbjr, @snapsh0t, @Nitrokalel, @storageninja, @apvm, @OttO1916, @joka388, @evgennsib, @EgorA, @Lucero84, @Pe6yc, @mnewland, @powerQ, @Alak, @Patchoro, @ruzaj, @zelluloid 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 the page might load an old cached version after updating when using the Safari browser.
2. Fixed the issue where downloading large files during remote access might stop after a period of time.
3. Fixed the issue where a folder named "usr appeared in the root directory after system update.
4. Fixed the issue where regular users failed to save files to their user directory via the text editor in File Manager.
5. Fixed the issue where the primary group of the guest user had no corresponding group name.

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.1169 update package (MD5: 942778ee26af631c6bace39e3ed8028f);
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]

Successfully updated my F4-425 Plus to TOS 7.0.1169.

The update completed successfully and the NAS is operating normally so far. No issues noticed after the update.

Shortly after updating, I was also pleasantly surprised to see a major Jellyfin update available in the App Center. Thank you TerraMaster for making this update available — it's great to see Jellyfin being kept up to date.

[Alak]

J'ai effectué la mise à jour. Il existe toujours des instabilités dans le partage "SMB" pour les utilisateurs "Guest".
A noter aussi que les connexions "SMB" avec le compte "super administrateur" ne sont plus possibles. Seul un compte "administrateur" classique permet de se connecter.
En finalité, les partage "SMB" sont toujours aussi instables et compliqués depuis le passage à TOS 7. Que ce soit depuis des machines Windows que depuis d'autres NAS (Qnap et Synology dans mon cas). Je suis obligé régulièrement de refaire des partages "personnalisés" et de cocher la case "droits hérités aux sous-dossiers" pour retrouver des accès, comme si tout était volatile.Il y a visiblement des incohérences dans le code de TOS 7.0 et le programmeur semble complètement perdu. Renforcer la sécurité, c'est bien. Mais si cela se traduit par des instabilités constantes, c'est franchement agaçant.
Le module "SMB" est à remettre à plat..

[crisisacting]

Applied to stand-alone TNAS (remains most up to date) & will install to testbed TNAS units during phase 2 if no issues are observed.

Haven't allowed production units @ clients to accept any of the recent updates since the NTP issues.

[ambul]

The update completed successfully, everything is running as normal.

[rfbjr]

All three devices updated w/o issue. Although there seems to be a math issue on the processes screen

[nitzer71]

Successfully updated my F4-425 Plus to TOS 7.0.1169.

The update completed successfully and the NAS is operating normally so far. No issues noticed after the update.

Shortly after updating, I was also pleasantly surprised to see a major Jellyfin update available in the App Center. Thank you TerraMaster for making this update available — it's great to see Jellyfin being kept up to date.

I regret that I updated to the new Jellyfin. Is there a way to rollback to the old version?

[TMroy]

J'ai effectué la mise à jour. Il existe toujours des instabilités dans le partage "SMB" pour les utilisateurs "Guest".
A noter aussi que les connexions "SMB" avec le compte "super administrateur" ne sont plus possibles. Seul un compte "administrateur" classique permet de se connecter.
En finalité, les partage "SMB" sont toujours aussi instables et compliqués depuis le passage à TOS 7. Que ce soit depuis des machines Windows que depuis d'autres NAS (Qnap et Synology dans mon cas). Je suis obligé régulièrement de refaire des partages "personnalisés" et de cocher la case "droits hérités aux sous-dossiers" pour retrouver des accès, comme si tout était volatile.Il y a visiblement des incohérences dans le code de TOS 7.0 et le programmeur semble complètement perdu. Renforcer la sécurité, c'est bien. Mais si cela se traduit par des instabilités constantes, c'est franchement agaçant.
Le module "SMB" est à remettre à plat..

Unfortunately, we have not been able to reproduce the issue you reported in our lab, and no other users have reported anything similar. Could you try clearing the SMB cache, checking whether your network connection is stable, and verifying if there are any applications running with high I/O load?

[Archivist]

Successfully updated my F4-425 Plus to TOS 7.0.1169.

The update completed successfully and the NAS is operating normally so far. No issues noticed after the update.

Shortly after updating, I was also pleasantly surprised to see a major Jellyfin update available in the App Center. Thank you TerraMaster for making this update available — it's great to see Jellyfin being kept up to date.

I regret that I updated to the new Jellyfin. Is there a way to rollback to the old version?

Same! My disks have been chattering away in what I assume is metadata refresh related. My entire system has crawled to 99% utilization. It's been 30 minutes

[apvm]

Updated Jellyfin right before upgrading to 1169, did not know Jellyfin is running migration, lucky after the reboot Jellyfin starts continue working with running migaration. Let me see if there is any problem after the upgrade. Anyway my machines are F4-424 traid with one D4-320 Traid 2 and another D4-320 with four single volume drives. BTW the migration took about 10 minutes and Jellyfin works fine. Keep up the good work Terramaster.