TOS 5.0.163 (x.86) is Released for Update
Re: TOS 5.0.163 (x.86) is Released for Update
OK so there will never be an automated uptade from 4.2 to 5 ? seriously you have to think about it, every single software i know have automated upgrades...
Re: TOS 5.0.163 (x.86) is Released for Update
Muy buenas, he instalado desde cero de la 4 ala 5.0.158 y de ahi a la 5.0.163.
Todo bien, pero pasado un rato me llega un email de que hay una aplicación ralentizando el equipo ya no deja entrar, no deja apagarse y hay que apagarlo con pulsación larga, después no deja entrar se queda TOS LOADING y el TNAS PC no lo reconoce (firewall deshabilitados)
La única opción que me deja es apagar, quitar HDD reinstalar versión 5.0.158, pero al rato vuelve a fallar.
Sugerencias¿?¿¿?
Todo bien, pero pasado un rato me llega un email de que hay una aplicación ralentizando el equipo ya no deja entrar, no deja apagarse y hay que apagarlo con pulsación larga, después no deja entrar se queda TOS LOADING y el TNAS PC no lo reconoce (firewall deshabilitados)
La única opción que me deja es apagar, quitar HDD reinstalar versión 5.0.158, pero al rato vuelve a fallar.
Sugerencias¿?¿¿?
Re: TOS 5.0.163 (x.86) is Released for Update
{L_BUTTON_AT}ibero2000
Maybe your system is busy in checking fils system, reconfiguration and mounting your storage pool, Please wait for 30~40 munites after updating.
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)
Support team: support(at)terra-master.com (for technical support only)
Service team: service(at)terra-master.com (for purchasing, return, replacement, RMA service)
Re: TOS 5.0.163 (x.86) is Released for Update
After my experience with installing 5.0.160 I was expecting the worst but the upgrade to 5.0.163 went smoothly. Took less than 7 minutes and all settings intact.
Re: TOS 5.0.163 (x.86) is Released for Update
@TMroy muchas gracias, me llega un email con esto:
¡El funcionamiento del sistema es lento! Vaya al panel del Monitor de recursos para verificar si algún proceso se está ejecutando de manera anormal.
¡El funcionamiento del sistema es lento! Vaya al panel del Monitor de recursos para verificar si algún proceso se está ejecutando de manera anormal.
Re: TOS 5.0.163 (x.86) is Released for Update
Scorp wrote:
> After update Virtualbox machine doesn't start from script (or ssh shell)..
> The error:
>
> (C) 2008-2021 Oracle Corporation
> All rights reserved.
>
> VBoxHeadless: ERROR: failed to create the VirtualBoxClient object!
> VBoxHeadless: error: Code NS_ERROR_FACTORY_NOT_REGISTERED (0x80040154) -
> Class not registered (extended info not available)
> Most likely, the VirtualBox COM server is not running or failed to start.
>
> Tried to reinstall vbox - it didn't help.
Hi!
Oh, I have almost the same situation!
I installed the TOS version 5.0.171 system on an empty device F2-423. Then I installed Virtualbox. When I run the #VBoxManage command, I get an error:
-bash: VBoxManager: command not found.
I found the following commands that don't give this error:
/Volume1/@apps/virtualbox/bin/VBoxManage
/usr/lib64/virtualbox/VBoxManage
/usr/lib/virtualbox/VBoxManage
However, when I enter any of them, I get the same error as you:
# /usr/lib64/virtualbox/VBoxManage list ostypes
VBoxManage: error: Failed to create the VirtualBox object!
VBoxManage: error: Code NS_ERROR_FACTORY_NOT_REGISTERED (0x80040154) - Class not registered (extended info not available)
VBoxManage: error: Most likely, the VirtualBox COM server is not running or failed to start.
Two questions:
1. Which script (or ssh shell) have you applied?
2. How to fix the above errors when working in the CLI?
> After update Virtualbox machine doesn't start from script (or ssh shell)..
> The error:
>
> (C) 2008-2021 Oracle Corporation
> All rights reserved.
>
> VBoxHeadless: ERROR: failed to create the VirtualBoxClient object!
> VBoxHeadless: error: Code NS_ERROR_FACTORY_NOT_REGISTERED (0x80040154) -
> Class not registered (extended info not available)
> Most likely, the VirtualBox COM server is not running or failed to start.
>
> Tried to reinstall vbox - it didn't help.
Hi!
Oh, I have almost the same situation!
I installed the TOS version 5.0.171 system on an empty device F2-423. Then I installed Virtualbox. When I run the #VBoxManage command, I get an error:
-bash: VBoxManager: command not found.
I found the following commands that don't give this error:
/Volume1/@apps/virtualbox/bin/VBoxManage
/usr/lib64/virtualbox/VBoxManage
/usr/lib/virtualbox/VBoxManage
However, when I enter any of them, I get the same error as you:
# /usr/lib64/virtualbox/VBoxManage list ostypes
VBoxManage: error: Failed to create the VirtualBox object!
VBoxManage: error: Code NS_ERROR_FACTORY_NOT_REGISTERED (0x80040154) - Class not registered (extended info not available)
VBoxManage: error: Most likely, the VirtualBox COM server is not running or failed to start.
Two questions:
1. Which script (or ssh shell) have you applied?
2. How to fix the above errors when working in the CLI?