Wow - great help - didn’t know that.
Now I’m in but lines still interrupts me. What should I do now? I can press Help and see the Help list. The response is righter slow from my Pi
Just a comment - I did login with root WITHOUT password - is that safe?
I don’t know if it’s related but hassio 0.93 on rpi 3 b+ stopped working for me about a day ago. It does get the usual fix ip from the router, but I can’t even get to the login screen, it just times out in the browser.
YES - that’s exactly what I experience (0.93.1 on RPI3 here too)
Though it looks to me like an I/O problem somehow even though nothing says that there is an I/O problem other than Docker containers keeps on being created and disappearing and the device never starts really up (cannot get in touch with it).
The console doesn’t display a welcome message - try connecting to the web interface as explained in the install guide.
My system works fine before a energy fail in my city, then the rpi boot and keep in loop in this screen, always the same over and over.
Can’t login on the web interface, can’t say or smb, apparently the docker does not start.
At the beginning of boot said : a Docker container has a start job pending and says something about wait whatever’s take to finish (28s / no limit) think the docker can’t finish the job and keep looping boot.
Update: searching it appears to be a malfunction in the network driver because a corrupt file and NetworkManager could not stablish the bridge between eth0 and docker0 device so the docker containers are running but not linked apparently.
i start everything from zero, flash again, 4 days after, this situation is happening again.
Exactly the same.
Possible causes:
I had a major SD-card crash - so I turned to OpenHab for a while but due to lacking support for my Netatmo thermostats I went back to Hassio/Hassos - but I really wanted to install it on a SSD drive but hassos didn’t support it. So now I’m using a larger SD-card
Same issue for me here. Tried changing SD card and tried reinstalling. Lost my whole config due to this as cannot SSH or SMB in when it does this.
The same happened to me - It’s a major drawback when using Docker (that nobody will admit). If your Docker image is dead - your recovery options is gone.
Did anyone ever sort this? I am facing the same issue with my Intel NUC (NUC10i3). Brand new install (I am moving over from a Pi and it’s been nothing but messy 
).
Well I started all over again - the SD card was corrupt and that was why
I have tried all fixes on here, including rebooting with new SD card etc etc and I still get the same messages.
One thing I have noticed is that after flashing the SD cards they loose all capacity. ie 64GB turns into a 32MB card! Am I missing something?
Oh I have tried that also with a pure delivery of SD-cards - It was broken when I got the card. I tried to use the SD formater software but that didn’t help me
I had the HA working perfect on the RPI4B and all was good till I tried to access via duckdns. Setup seemed to go ok but remote log in failed follow by local log in even using the dns.
Now as you have experienced nothing executes correctly and I cannot open HA. I can ping the IP, even changed the IP using nmcli and could ping that too but no luck with HA.
Thinking of buying a new RPI tomorrow and starting from scratch.
Hi all, hi @Alfonsolsl. Were you able to solve the issue?
I’m experiencing something similar.
Fresh hassOS install on
I tried for several hours. Still I cannot see the “Preparing home assistant” web UI, or any web UI at all. Browser says “connection refused”.
Anyone has a solution?
Thanks!
