Public Beta Testing for TOS 6 ARM Version

[RyanYang]

Dear TerraMaster Users,
Since the official release of TOS 6 for x86 architecture, we have been honored to witness the groundbreaking progress of this milestone system in terms of stability, functional innovation, and user experience. Over the past six months, more than 50,000 devices worldwide have completed the upgrade, achieving an average system availability of 99.98% and a 32% year-on-year increase in user satisfaction. We sincerely thank all users for their trust and support in the TOS ecosystem!

Staying true to our product philosophy of "Continuous Evolution, Leading the Future with Intelligence," we are proud to announce that the ARM architecture version of TOS 6 has now entered the public beta testing phase!

TOS 6 Basic Introduction
Know More About TOS 6



Applicable Models:
F2-211, F2-212, F4-212

WARNING!
1. TOS 6.0.585 adopts a new root file system, achieving full compatibility with Ubuntu 22.04. However, please note that all your previous system configurations will be erased after the update. If you wish to keep your current settings, DO NOT proceed with this update!
2. This update is only applicable to TOS 5.1.73 or later versions.
3. The entire update process takes approximately 10 minutes. Please be patient and DO NOT force a shutdown or unplug the power during the update.
4. This version no longer supports domain/LDAP, SNMP, Hyper Cache, Hyperlock-WORM file system, or SPC-related features.
5. Surveillance Manager, iSCSI Manager, Portainer, Docker Manager, and developer tools will not be available in this version. If you have related data, back it up before updating.
6. No TOS 6 installation package will be released in the future - only update packages for iterative upgrades.
7. Due to differences in mounting mechanisms between TOS 6 and TOS 5.1, downgrading is not recommended. If you downgrade to TOS 5.1, you must update back to TOS 6 to access your apps and data properly.
8. Since TOS 6.0 requires more space, you will not be able to update to TOS 6 if your TNAS hard drive initially runs TOS 4 and your system partition has less than 3 GB of available space.
To check the available space on your system partition, go to ‘TOS > Control Panel > System Information > Overview’ and look at the "/" entry.

Important Notes:
1. Beta versions are early-stage releases containing most core features but may still have defects. This version is intended only for testing and feedback collection and should NOT be used in production environments. If your TNAS device is handling business operations or critical data, DO NOT participate in this test.
2. The update should not affect your hard drive data, but always back up your data beforehand as a precaution.
3. The update resets the system partition entirely, wiping all previous configurations. Even if you backed up system settings, they cannot be restored after the update.
4. After updating, download the latest TNAS PC for Windows/Mac from the TOS App Center to avoid compatibility issues.
5. Post-update, you must register a TerraMaster account in the Remote Access module of the Control Panel to reconfigure TNAS.online.
6. Ensure at least 3GB of free space in your main volume (usually “volume1”) before updating - insufficient space may cause update failure!
7. After updating, you must rebuild the media index and re-enable apps like Photos and Media Server to use their features.
8. Some apps may require updates or reconfiguration to function properly under the new system. For community apps, you may need to reinstall the latest version.
9. After updating, you must go to the Shared Folders module in the Control Panel and edit the application user permissions for the shared folders corresponding to Aria2, MariaDB, Plex, and Transmission in order to properly enable or use these applications.
10. VPN Server and Media Server settings will be reset - you must reconfigure them after updating.
11. Update the TFM Backup app to the latest version before proceeding. Otherwise, your app settings will be erased, requiring manual reconfiguration post-update.
12. Apps relying on databases must be reconfigured after the update.
13. After the update, app initialization may take 1-3 minutes - wait before launching or installing applications.
14. After updating, the photo backup settings in TNAS Mobile need to be reconfigured.
15. After updating, Emby requires an official compatible version release to function properly (current version is temporarily incompatible).
After updating, the photo backup settings in TNAS Mobile need to be reconfigured.
16. The device’s IP address may change after the update. Use the TNAS PC client to search and reconnect.

How to Update to TOS 6?
1. If there is an SSD Cache, first disable the SSD Cache.
2. Download the TOS 6.0.585 update package (MD5:c27856f92ff01c1ae4781ec66ec9efd7). Only for TOS 5.1.73 or later - DO NOT update from other versions.
3. Go to TOS > Control Panel > General Settings > System.
4. Under “Manual Update”, select the downloaded package.
5. Click “Apply” once and wait - DO NOT click repeatedly.
6. After completion, refresh your browser.
7. If the TNAS IP changes, use TNAS PC to locate the new address.

Other Software Downloads:
1. Download TNAS PC 5.2.092 for Windows OS
2. Download TNAS PC 5.2.072 for macOS(x86 architecture and ARM architecture)
3. Download TNAS PC 5.2.072 for macOS(ARM architecture)
4. Download TNAS Mobile 3.3.057 for Android
5. TNAS Mobile for iOS: Download from the iOS App Store[/list]

Bug Reporting:
To report bugs, please email [email protected] with a description, reproduction steps, and screenshots.

[sianderson]

so F2-210 is still out of luck then?

[crisisacting]

so F2-210 is still out of luck then?

Yes.

There's no longer official support for the SoC from its manufacturer, Realtek, that's in the 210 series devices.

It's stuck on a previous kernel & wouldn't be able to gain any newer TOS beyond 4.2.×.

[King7]

oh, finally, here it is!

[Captain8836]

I would like to install the new TOS6 on my F2-212, to anyone that has installed it, how is it working? Is it working well or should I wait. I do have have backup data on it as I backup data from my F2-223 which has raid1. Just like my data on 2 separate devices just in case.

[Peterlll06]

Has anyone run it successfully?

[impaladb]

Just setup a new F4-212 2GB. So far all is working well. The 212 is an offsite location to backup an onsite F4-423. Duple backup is still not working between ARM and x86 so have to use RSYNC. I'm not using docker or any media sharing as this is strictly standard file services.

[GevinKe]

Just setup a new F4-212 2GB. So far all is working well. The 212 is an offsite location to backup an onsite F4-423. Duple backup is still not working between ARM and x86 so have to use RSYNC. I'm not using docker or any media sharing as this is strictly standard file services.

Hi! Are you planning to back up the data from the F4-212 device to the F4-423 device using Duple Backup? To provide more accurate advice, could you please share the following details:

1. The TOS version number of both the F4-212 and F4-423 devices.
2. The version numbers of Duple Backup and Duple Backup Vault on both devices.

Additionally, could you clarify the specific issue you are facing? Are the two devices unable to establish a connection, or have they connected but the backup process is failing?

[RayKah]

I am so glad that F2-212 users can have the TOS6 version. That is great!

[JohnS]

Upgraded my F2-212 to this beta version. So far so good.