TOS 7.0.0333 Beta (X86) is Released for Update

[RyanYang]

Target Users:
Users currently running TOS 7.0.0299 beta or later versions.

Note:
If your TOS version is TOS 6, please refer to the TOS 7 beta update instructions first

Here, we sincerely thank user @JSCFORCE, @jdcesari, @rfbjr, @ruzaj, @Lex, @HeliaWu, @jpeckinp, @OttO1916,@RandallFlagg and others, for their sharing and feedback. It is your support that has enabled us to quickly identify and resolve some issues.

Update Notes
Bugs fixed:
1. Fixed an issue where interface information remained after unplugging a USB network adapter with OVS enabled.
2. Fixed an issue where OVS could not be successfully enabled after installing VMs.
3. Fixed an issue where refreshing the page while multiple cloud drives were mounted could cause File Manage to load slowly.
4. Fixed an issue where domain users might be unable to access their personal directories.
5. Fixed an issue where the Wake-on-LAN feature failed to work after a system update.
6. Fixed an issue that could cause an incomplete display during the first load of the TOS desktop after an update.
7. Fixed an issue where incorrect logs were generated when enabling or disabling SNMP.
8. Fixed an issue where some user settings were not successfully restored after a system configuration restore.
9. Fixed an issue where the App Center might automatically exit due to an interface error during app installation.
10. Fixed an issue where traffic rules for corresponding ports could not be deleted after unplugging a USB or Wi-Fi network adapter.
11. Fixed an issue where default file sharing links still used the DDNS address after the DDNS feature was disabled.
12. Fixed an issue where incorrect permissions were displayed after uploading files to a USB device or a directly attached drive.
13. Fixed other known issues.

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.Go to TOS > Control Panel > General Settings > System > Update, and click "Check for updates."
2.Follow the prompts to update the system.
3.After the system update is complete, you may need to refresh your browser.
4.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.506 for Windows OS.
2. Download TNAS PC 5.2.506 for macOS (x86 and ARM architectures).
3. Download TNAS PC 5.2.506 for macOS (ARM architecture).
4. Download TNAS PC for Linux.
5. Download TNAS Mobile 3.X for Android.
6. For iOS, experience TNAS Mobile 3.X via: https://testflight.apple.com/join/wFWYABJS.

[JSCFORCE]

Updated successfully. Looks good so far, will continue to test. (F4-425 Plus)

[jdubya]

Not a very smooth upgrade - it downloaded fine, but after upgrading I got a message that said the upgrade failed. I waited a few minutes and rebooted the NAS (F4-425 Plus). Then system says the version is correct, but it's ready to upgrade and displays a long file name ending in bz2. When I tried to upgraded it again, it says it failed because it can't unpack the file and to try again later. I rebooted again and now it says current system is at the latest version and it displays the correct version.
So far looks like we're back up and running. Basically I had to reboot it twice.

[athurdent]

Has the docker file access right issue people were posting about in previous releases been fixed?
Would be a showstopper for me.

[Seton]

Still not fixed docker permissions problem

[CursaYang]

Not a very smooth upgrade - it downloaded fine, but after upgrading I got a message that said the upgrade failed. I waited a few minutes and rebooted the NAS (F4-425 Plus). Then system says the version is correct, but it's ready to upgrade and displays a long file name ending in bz2. When I tried to upgraded it again, it says it failed because it can't unpack the file and to try again later. I rebooted again and now it says current system is at the latest version and it displays the correct version.
So far looks like we're back up and running. Basically I had to reboot it twice.

Hello, this is a known issue, and we will fix it in subsequent updates. Please wait for the new version to be released.

[CursaYang]

Still not fixed docker permissions problem

Hello, regarding the Docker permission issue, we have fixed it in the new version. Please wait for the new version to be released.

[rfbjr]

Both (F4-223 and F4-425 Plus) each got to 72% updated, then "Update Failed". I've learned, I just wait for the email from the NAS saying update was successful. Both are running and I'll start testing later. I did get a notification on my phone that the mobile app was updated. Haven't tried that yet.
I'll reboot both NAS later to see if the disk activity spikes for ~2 hours. If this happens, (I will capture logs first) then deleting and re-creating the hyper cache fixes it.

[rfbjr]

Initial note, it does seem that each beta release turns disk and USB disk hibernation back on.

[jdcesari]

Since the update, I have this email
L’appareil TNAS a subi un arrêt anormal, possiblement dû à une panne de courant ou une anomalie du système. Vérifiez l’état de l’appareil et du système dès que possible.

and the nas is in failure

it starded full photos indexing, and it seems that there should be a problem (heating?) during this process.
how to solve ?
it is blocked as this : Indexation en cours... 43537 fichier(s) ( indexing 43537 files).. but it remains as this.
so i think it is heating because it can't check more


------------------------------------------------------------

Device name: TNAS
Model: F4 SSD
TOS version: TOS_X642.0_7.0.0333