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

Here, we sincerely thank @pjarinov, @ambul, @akaserge, @rfbjr, @Alak, @crisisacting, @apvm, @Nitrokalel, @snapsh0t, @angelor, @OttO1916, @sianderson, @Lavenir, @dnetkach, @Gremlin, @nitzer71, @mnewland 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 system desktop did not refresh automatically after the Desktop directory was deleted.
2. Fixed the issue where the disk's file system might not be displayed properly after a disk was removed and then reinserted.
3. Fixed the issue where removing one disk from a multi-disk array might cause the quantity information to display incorrectly.
4. Fixed the issue where the "-O" parameter was always required when transferring files with the SCP command.
5. Fixed the issue where some terms were improperly translated in Italian.

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.1201 update package (MD5: 51a09e5f77b610fd180e932f5ce15d0f);
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.

[Alak]

Merci.

La mise à jour s'est effectuée rapidement et sans problème. Le NAS semble parfaitement opérationnel pour les usages que j'en fais. Comme avec la version précédente, en fait. Les synchronisations se déroulent correctement et les accès semblent corrects depuis les autres machines. Autant anticiper les versions officielles .

Bonne journée à toute votre équipe.

[rfbjr]

F4-424 Pro, turned on debug mode prior to update to 1201, was attempting to capture data for a different issue.
After system came back and signed on, after just a few minutes CPU temp warning triggered 83c, forced fan to high, after a few minutes temp dropped 40c. The issue was going to capture didn't happen. Rebooted unit again, still with debug mode on, same high temp after a few. This time left fan in auto mode, point being forcing high speed didn't help dropping temp, whatever the system was doing, it finished then temp dropped.
Late here. I turned off debug mode. I'll upload my logs in the morning. Turned off scheduled power on, will do that manually and see if debug mode off, if cpu temp doesn't spike.

Update: Tue AM
Remaining devices (even other F4-424 Pro) all updated w/o issues or any noticeable CPU temp spikes.
Support has been emailed with pictures and links to logs.
So the one F4-424 Pro that has TerraSync installed is having the short CPU temp spike after rebooting. Debug mode on at the time was enough of an extra load to trigger the CPU temp alert.

[ambul]

Done. Success

[Crashoveride]

Could you please explain why the NVMe drive in the second slot is not shown in the Disk Information section of Storage Manager, and why in the Hard Disk section it is named “NVMe Disk_sdzc” instead of “NVMe Disk1” like the other drives? NAS: F2-425 Plus (Intel N95), TOS 7 1201 (the same behavior was present on previous versions as well).

[Gremlin]

Have you previously had an NVME configured as Hyper-Cache?

[Flyingbike]

Hello

Is anything going on regarding this issue :

I run this version.

I recently switched from ISP DNS to self-hosted pihole and I quickly noticed my F2-423 was requesting A LOT

Code: Select all

2026-08-29 18:40:36		AAAA	ipv6.baidu.com.lan	********.lan	25.3 µs	
2026-08-29 18:40:36		AAAA	www.google.com	********.lan	12.9 µs	
2026-08-29 18:40:36		AAAA	ipv6.baidu.com	********.lan	12.9 µs	
2026-08-29 18:40:36		AAAA	www.cloudflare.com	********.lan	65.1 µs	
2026-08-29 18:40:21		AAAA	ipv6.baidu.com.lan	********.lan	55.6 µs	
2026-08-29 18:40:21		AAAA	www.google.com	********.lan	36.5 µs	
2026-08-29 18:40:21		A	www.baidu.com	********.lan	28.6 µs	
2026-08-29 18:40:21		AAAA	ipv6.baidu.com	********.lan	35.8 µs	
2026-08-29 18:40:21		AAAA	www.cloudflare.com	********.lan	56.3 µs	
2026-08-29 18:40:06		AAAA	ipv6.baidu.com.lan	********.lan	52.5 µs	
2026-08-29 18:40:06		AAAA	www.google.com	********.lan	47.9 µs	
2026-08-29 18:40:06		AAAA	ipv6.baidu.com	********.lan	26.7 µs	
2026-08-29 18:40:06		AAAA	www.cloudflare.com	********.lan	42.2 µs	
2026-08-29 18:39:51		AAAA	ipv6.baidu.com.lan	********.lan	50.5 µs	
2026-08-29 18:39:51		AAAA	www.google.com	********.lan	36.7 µs	
2026-08-29 18:39:51		A	www.baidu.com	********.lan	24.6 µs	
2026-08-29 18:39:51		AAAA	ipv6.baidu.com	********.lan	26.5 µs	
2026-08-29 18:39:51		AAAA	www.cloudflare.com	********.lan	50.1 µs	
2026-08-29 18:39:36		AAAA	ipv6.baidu.com.lan	********.lan	53.6 µs	
2026-08-29 18:39:36		AAAA	www.google.com	********.lan	12.4 µs	
2026-08-29 18:39:36		AAAA	ipv6.baidu.com	********.lan	11.7 µs	
2026-08-29 18:39:36		AAAA	www.cloudflare.com	********.lan	34.3 µs	
2026-08-29 18:39:21		AAAA	ipv6.baidu.com.lan	********.lan	61.5 µs	
2026-08-29 18:39:21		A	www.baidu.com	********.lan	27.9 µs	
2026-08-29 18:39:21		AAAA	www.google.com	********.lan	48.2 µs

Every 15 seconds.


Why so frequently ?

And additionally, why AAAA when ipv6 is deactivated on this device ?

This is orchestrated by TOSDaemon through gitlab.local/golibrary/wanip and probed domains are hard coded.


It seems I am not the first one to notice.
viewtopic.php?p=59673#p59673, the explanation of packet loss or timeout in this other topic is incorrect. The DNS answers correctly and the domains are reachable.

It surely needs an explanation and a correction.

THanks

[crisisacting]

Successfully updated stand-alone TNAS.

Will await online update for testbed units.

[Pe6yc]

Updated w/o issues

[mnewland]

T6-423
Upgraded this morning from 1188, at arround 7am

checking this afternoon at 4pm ERRORS:
when accessing settings im getting the error message URL: v2/desktop/recentlyVisited message: Network Error
I cant get into settings currently.

update 1: I came back to it 20 minutes later I can now get back into settings and the error no longer shows.
update 2: kids are complaining Jellyfin no longer works. they can view the library but nothing will play...
Update 3: kids informed me they rebooted - Jellyfin now working..... will try and look further when home from work