TOS 6.0.460 (X86) Beta is Released for Update

[RyanYang]

Applicable Models:
F2-221, F2-223, F2-422, F2-423, F2-424
F4-221, F4-223, F4-421, F4-422, F4-423, F4-424, F4-424 Pro
F5-221, F5-421, F5-422
T6-423
F8-421, F8-422
T9-423, T9-450
T12-423, T12-450

Bugs Fixed:

1. Fixed some issues with File Manager.
2. Fixed some issues with Network Services.
3. Fixed some issues with App Center.
4. Fixed some issues with Storage Pool.
5. Fixed some issues with File Service.
6. Fixed some issues with Remote Folder.
7. Fixed some issues with the fan control.
8. Fixed some issues with Shared Folder.
9. Fixed some issues with UPS.
10. Fixed some issues with OTP two-factor authentication.
11. Fixed some issues with System Information.

Warning!

1. Due to the change in the configuration file storage path for TNAS.online, devices with TOS versions below 6.0.436 will have the TNAS.online service automatically stopped after an update. It will need to be manually re-enabled.
2. This update is only applicable to TOS 6.0.420 or later versions.
3. Due to hardware limitations, some older models are unable to update to TOS 6. Users of these models are advised not to attempt the update to TOS 6. The specific models include: F2-220, F4-220, F2-420, F4-420, F5-420, as well as the 221 series with a manufacturing date in Jun 2020 or earlier, which includes: F2-221, F2-421, F4-221, F5-221, F5-421.

Precautions:

1. The Beta version is an early version of the program, containing most major functions but not yet completed, and may have some defects. This version is only released to specific groups or the general public for testing and feedback collection; the Beta version should not be used in work or production environments. If your TNAS device is running business operations or storing important data, please refrain from participating in this test.
2. Updating the system theoretically will not affect the data on your hard drive, but for safety reasons, please be sure to back up your data in advance.
3. After the update, download the latest version of TNAS PC for Windows or TNAS PC for macOS from the TOS App Center to avoid compatibility issues.
4. 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.
5. The IP address of your TNAS may change after the update. Use the TNAS PC desktop client to search and connect to the device again.

How to Update to TOS 6 Beta?
The official TOS 6 update package will be released soon. Stay tuned.

Other Software Downloads:

1. Download TNAS PC 5.1.632 for Windows OS
2. Download TNAS PC 5.1.202 for macOS(x86 architecture and ARM architecture)
3. Download TNAS PC 5.1.202 for macOS(ARM architecture)
4. Download TNAS Mobile 3.2.47 for Android
5. TNAS Mobile for iOS: Download from the iOS App Store

Bug Reporting
As the Beta version is an early version of the program, it may contain some defects. Please refrain from disseminating bugs found in the Beta version to the public to avoid causing unnecessary inconvenience to others.
If you need to report a bug, please send a description of the bug, reproduction steps, and screenshots to the designated email: [email protected].

[DCCentR]

Update stuck at 4, when updating via file or online update

[RyanYang]

Do you have enough capacity in your volume?

[solovei2]

Update stuck at 4, when updating via file or online update

The same goes for me F2-423.

[Gremlin]

Updated. Quick - less than time allocated for browser refresh

Still does not show nvme drives as "system" drives, although included in system raid array with hdds on boot (via console)

Still showing "Failed to start 'Network UPS tools - power device monitor and shutdown controller' on boot (via console)

[RyanYang]

You can go to the task scheduling module in the control panel to create a custom task and run the following command:

Code: Select all

rm -rf /etc/upslog

and try updating again.

[Alex281]

You can go to the task scheduling module in the control panel to create a custom task and run the following command:

Code: Select all

rm -rf /etc/upslog

and try updating again.

I was also stuck at 4% until I ran the above command (carefully via ssh, not sure about scheduling a task).

[imranalam]

After its not logging in via windows app, it shows this error via web

[DCCentR]

Do you have enough capacity in your volume?

Yes

You can go to the task scheduling module in the control panel to create a custom task and run the following command:

Code: Select all

rm -rf /etc/upslog

and try updating again.

This one works, but should be "rm -rf /etc/upslog"

[Gremlin]

Multimedia Server will not stay enabled
ClamAV -> Realtime protection will not stay enabled.