Page 2 of 2
Re: TOS 5.0.163 (x.86) is Released for Update
Posted: 08 Sep 2022, 19:47
by Jesuralem
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
Posted: 09 Sep 2022, 02:14
by ibero2000
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¿?¿¿?
Re: TOS 5.0.163 (x.86) is Released for Update
Posted: 09 Sep 2022, 10:10
by TMroy
Maybe your system is busy in checking fils system, reconfiguration and mounting your storage pool, Please wait for 30~40 munites after updating.
Re: TOS 5.0.163 (x.86) is Released for Update
Posted: 09 Sep 2022, 15:24
by chalnoth
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
Posted: 10 Sep 2022, 02:10
by ibero2000
@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.
Re: TOS 5.0.163 (x.86) is Released for Update
Posted: 12 Oct 2022, 16:53
by ivp
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?