TMroy wrote: ↑20 Mar 2024, 19:32
We have recently provided remote support to some users who encountered failures while updating to TOS 6. These users all claimed that they were using TOS version 5.1.123 before the upgrade, but upon our verification, this was not the case. Due to not meeting the update requirements of TOS 6, they all experienced issues such as Nginx not running and the TOS page not loading after the update. Therefore, we strongly recommend once again that before attempting to upgrade to TOS 6, please ensure that your TNAS device meets all the necessary update conditions to avoid any unnecessary troubles.
Even people who have latest version see my screen shot 5.1.123 cannot update. we get massive errors and failure in raids.
i have tried 2 times now. and i get same error.
there is something broken in the TOS6 update process.
TMroy wrote: ↑20 Mar 2024, 19:32
We have recently provided remote support to some users who encountered failures while updating to TOS 6. These users all claimed that they were using TOS version 5.1.123 before the upgrade, but upon our verification, this was not the case. Due to not meeting the update requirements of TOS 6, they all experienced issues such as Nginx not running and the TOS page not loading after the update. Therefore, we strongly recommend once again that before attempting to upgrade to TOS 6, please ensure that your TNAS device meets all the necessary update conditions to avoid any unnecessary troubles.
Well, mine definitely was! and got the same result the second time so there is a problem somewhere! getting heartily sick of problem after problem!
same here i tried a second time same problem.
i been trying to figure out what the issue is but so far no luck.
If you can allow a remote session from our engineer to find out the issues, that will be much appreciated!
So how are you supposed to allow a remote session when you cannot access the desktop to do it?
I have now reverted back to 5.1.123 and wiped the drives at least this version is pretty stable, despite jmaysnc thinking you should expect nothing you should at least expect to be able to access the desktop in order to set up regardless it being a "public" beta version!
If you can allow a remote session from our engineer to find out the issues, that will be much appreciated!
So how are you supposed to allow a remote session when you cannot access the desktop to do it?
I have now reverted back to 5.1.123 and wiped the drives at least this version is pretty stable, despite jmaysnc thinking you should expect nothing you should at least expect to be able to access the desktop in order to set up regardless it being a "public" beta version!
I know for a fact that I went in and clicked on download update and it said no updates available before I installed the TOS 6 Beta. I wish I had take a screenshot of the version number beforehand.
According to our background download statistics, so far, more than 650 users have participated in the installation and testing of TOS 6 beta. This issue is happening to individual users and we will continue to look for the cause. We thank all users for helping us raise bugs during the TOS 6 beta testing phase, and we will resolve these known bugs before the official release.
To contact our team, please send email to following addresses, remember to replace (at) with @:
Support team: support(at)terra-master.com (for technical support only)
Service team: service(at)terra-master.com (for purchasing, return, replacement, RMA service)
what you see 5.1.352 is the version number of the TNAS PC client, if you need to obtain TOS version, you need to log in the TOS web page and check the version from there.
To contact our team, please send email to following addresses, remember to replace (at) with @:
Support team: support(at)terra-master.com (for technical support only)
Service team: service(at)terra-master.com (for purchasing, return, replacement, RMA service)
According to our background download statistics, so far, more than 650 users have participated in the installation and testing of TOS 6 beta. This issue is happening to individual users and we will continue to look for the cause. We thank all users for helping us raise bugs during the TOS 6 beta testing phase, and we will resolve these known bugs before the official release.
Thats is all very well but without being able to access the desktop and system how are you going to diagnose the problem if the user cannot authorise external interrogation?
