I have serious problems connecting to my hassio (RPI3) after a restart do to power failure. When booting up everything seems fine and green OK all over. Then after the boot line Avahi mDNS/DNS-SD Stack - “Welcome to HassIO” and Login is prompted but then the “fun” starts. Lines are just listing up writing something about docker and promiscuous mode entering and leaving and docker port enteres blocking state and forwarding state and this just continues…
I cannot enter with putty (SSH) so now my HASSIO seems doomed and I have lost everything (is my feeling:cold_sweat:) It is like Docker using my TTY so I cannot control anything.
What can I do? Can I somehow interrupt the boot up so it prevents docker from starting or what? It feels like Docker is making things more unstable (and then you lose everything).
Did you set a static IP for your Pi? If not then probably the IP has changed from what you’re expecting.
What you can do at this point is try connecting to hassio.local (if mDNS works normally on your network) or just log in on the console, using root and no password.
OK - it looks to me like something is interrupting my ability to Login. You see the Login line appears and after the first lines I can pres Ctrl C but I cannot enter anything before new lines appear. I have Static IP and I can Ping my RPI but I made a Port Scan and found no open ports.
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.
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).
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 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
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 ).
).