Have you run out of space? If so, resize the vmdk, download gparted iso and boot from that. Resize the partition, apply changes, remove the boot cd and reboot…
nb, if gparted is stuck in a boot loop, change the VM to “bios” from “efi”
Hi guys, im a complete newbie on HassIO, I managed to install it on a linux VM with VMware but the web UI won’t load until i hit enter on the VM and type “root” as username, is there anyway to automate this process? Thanks so much in advance for your help
I have plenty of space. When I run the Web Gui update, it pulls the latest docker image. Thinks for about 15 minutes and then comes back up running 0.92.2
I’m running Hass.io on Debian linux inside ESXi 6.5.
None of the hassio cli commands I’ve found are available to me.
I’ve never had a problem upgrading in the past on this system.
sysop@dockmaster : ~/ha $ sudo hassio
sudo: hassio: command not found
During the long wait I run the show images command.
sysop@dockmaster:~/ha$ docker images |grep homeassistant/qemux86-64-homeassistant
homeassistant/qemux86-64-homeassistant 0.95.4 3ec05d57fa7d 11 days ago 1.01GB
homeassistant/qemux86-64-homeassistant latest 3ec05d57fa7d 11 days ago 1.01GB
sysop@dockmaster:~/ha$ docker images |grep homeassistant/qemux86-64-homeassistant
homeassistant/qemux86-64-homeassistant 0.95.4 3ec05d57fa7d 11 days ago 1.01GB
homeassistant/qemux86-64-homeassistant latest 3ec05d57fa7d 11 days ago 1.01GB
sysop@dockmaster:~/ha$ docker images |grep homeassistant/qemux86-64-homeassistant
homeassistant/qemux86-64-homeassistant 0.92.2 0069222f84fb 2 months ago 1.15GB
homeassistant/qemux86-64-homeassistant latest 0069222f84fb 2 months ago 1.15GB
Does it conflict with the ssh daemon of my Debian host? I didn’t see mention of alternate port options in the ssh add-on docs.
On a side note I fixed my upgrading problem. I blew out my config and the upgrade took without auto rolling back. I believe their were changes that now brought errors instead of warnings and hass.io was nice enough to roll back. After putting my old config back in post upgrade it would just hang. Now I’m cleaning it up.
Yes it will conflict. I use port 622 instead of 22 in the addon. The Community SSH & Web Terminal you can do this but not in the core addon. The docs do actually say with a generic linux install you can’t use the core addon.
I’m having the same issue. I’m pretty far into my setup (this is 2.0 for me) but I feel like I need to sort this first before continuing further.
I followed a DrZzz’s video for installation and also must type in “root” before Hassio will finish loading. I want to automate the entire process so the machine will auto load in the event of a power outage.
EDIT: I think my problem was that I was not patient enough for HA to load. It would seem to get stuck, I would type in “root” and it would continue and I could login.
On one of the youtube videos I watched wile trying to solve a different problem, the installer upped the number of cores allocated to the VM. I went ahead and upped mine as well, at least until I’m done setting the machine up and I no longer need to type in “root” to access HA.
Thank you very much for the tip of adding /24. I had followed the video and all had worked for several weeks before stopping. Tried all sorts to get it back for several weeks then I decided to start all over again and had the same issue. Then I found this thread and got it working again. So not only have I got it back working, I have learned so much while trying.