4 posts were split to a new topic: Node-red not starting
After a server reboot I did notice that Home Assistant did not start. I checked and it seemed started. Looked via VNC and it shows Welcome to Home Assistant, home assistant login:
Why donĀ“t it fire up like it use to? What can I do?
Its like the supervisor would not start.
I can access with root (no password) but I canĀ“t get it to start. ha check leaves no errors
Did a fresh VM and a snapshot restore and up and running, but IĀ“m not happy if this keeps happening every time I reboot the Unraid server. So if anyone has a good idea what is causing this IĀ“m very happy to hear.
Thereās nothing wrong with what you are describing.
Okej. Then I donāt understand. If I do a new install the vm boots and I can go to ip-adress:8123
But in my scenario above I donāt get a ip adress. The boot stops before.
How do I manually start ha if this happens again?
Iām not sure what you mean by the boot stops. Seeing the login doesnāt mean itās stopped. When you login with root, what happens next?
Sorry for late replay. It happend again
Home Assistant will run for some days. In this case like 2 weeks. Then gets strange.
I stoped the VM and started again and if I look via VNC I gets to a promp with
Welcome to Home Assistant
Homeassistant login.
It do not start and shows the webgui as usaually do.
Just curious have you tried building off of debian instead of ubuntu I think I read that is what your running it on, the reason I asked is my QCOW2 instance has been incredibly stable for 6 months now with a ton of updates and beta but I built it on a debian VM funny thing thats the only VM on unRAID that has been rock solid have always had lag issues with other attempts
Still stuck on this?
I added
sharename /mnt/sharename 9p trans=virtio,version=9p2000.L,_netdev,noauto,nobootwait,rw 0 0
to the hassio /etc/fstab and it seems to be working.
Thereās nothing wrong with seeing
Welcome to Home Assistant
Homeassistant login.
Thatās what it does now.
You would login as ārootā at that point if you want to see whatās going on in the background.
This was after you passed through the Share in the VM right?
Thought IĀ“d leave a comment if anyone else faces the same problem. After several tries I tried to go back to hassos_ova-5.9.qcow2 (The newest is 5.11 but itĀ“s not working for me)
So after trying the 5.9 version it seems to be working. Just restoring from snapshot now so hopefully it will work.
I tried a new VM using 5.11 just now and while I did see the udevd message slip in front of the login as shown in your pic, I left it alone for a while and it finished setup
I can confirm 5.11 worked for me. Just give it a minute after it boots and you can login to the HA cli
Okej - thanks for helping. Is there a big Plus to run 5.11 instead of 5.9? I mean now that I have it working?
I did try now to make a new VM with 5.11 and same thing as in pic. What do I do in the CLI to make it boot?
Okej I could not accept this so did a new try. Not I got it working with 5.11 and restore from snapshot.
I canĀ“t for my life understand why this did not work yesterday. I have stated mining for fun - but hard to see that affect this.