Can't boot HA now

Installation
1

I’ve been running a docker installation of HA on a Raspberry Pi 3b for a few years, but now it’s not booting. I suspect that the problem has started after recent Core updates (but I’m guessing!).

I’m now in a situation where I can’t access the HA web page and also can’t ssh into HA (getting connection refused). All I can do is ping the Pi - so I’m stuck!

(I understand that the Pi 4 is a better choice for HA, but the migration is not straightforward and would need a complete new installation)

I’d be grateful for any sugesstions.
Jim

2

Attach a screen and keyboard and see what is going on ? Docker, so your SSH problem is not related to HA, unless HA eats all your CPU cycles or memory.

3

If you can’t get 3b up and running then it’s relatively straight forward to migrate to RPI4. I just installed the HA to the 4 and restored a backup from the 3 to it. I had no problems that I can remember at all.

4

Good idea Francis - I’ll give it a try tomorrow.
I’m not sure if it’s maxing out the CPU, as the heatsink is not very hot.
Jim

5

Thanks Spiro - your reply is encouraging. I’ll shop around for a RPI4.
Jim

6

I attached a screen and keyboard as Francis suggested and got a screenful of information relating to the Linux system booting. There appeared to be no errors.

The screen then cleared and displayed:

Waiting for the Home Assistant CLI to be ready…
[WARN] Home Assistant CLI not starting! Jump into emergency console…

I then have access to the OS file system.
If I then do:

ha

I get:

Error response from daemon: container (very long string) is not running

(I guess that the container refereed to is the one providing the CLI)

I’ve got no idea as to where I go now - but feel that there may be a possibility of recovery, but that if I’m not careful I can completely wreck the system!
I really ought to get up to speed with Docker, but I’m 85 years old and new concepts aren’t absorbed so easily!

BTW: I’ve got full backups on an external cloud account.

Jim