I’m on a pi4 with Haos installed, core version 2025.6.1
The installation worked perfectly fine for a few days, even after some restarts for configuration changes.
Yesterday it seemed to have some connectivity problems with my tapo plugs, so I decided to restart again. After that I can’t start it up again.
It crashes with the message:
Home Assistant Core finish process exit code 256
Home Assistant Core finish process received signal 11
It also spits out a warning that the system could not validate that the sqlite3 db was shutdown cleanly, but not sure if this is related.
I’ve had the same problem in the past and removing the database worked for a moment, but the issue keeps coming back. I also don’t want to recreate everything I had all the time.
Kill signal 11 is segmentation fault, which is usually related to memory.
You might be out of memory.
2 Gb is a minimum, but some addons can be memory hogs and less than 4Gb will not do then. 8Gb is preferred.
It can also be that your ram chips or other hardware inside the Pi is defective.
The database warning is a standard line, due to HA not shutting it down correctly.
It will nearly always be there.
Hey Wally, thanks for the reply. I have the 4 GB version. Not a whole lot add-ons installed yet and isn’t it weird that it ran for a few days and now it is not able to start up? Do you reckon it’s defective then?
I tried to remove some add ons and the only ones left i have now is vscode and cloudlared, still the same problem. In the past, I could flash the image again on my stick to reinstall haos, it would work again, but I can’t keep reinstalling every other week.
Maybe switch to a SSD.
I’m also getting this error on 2025.7.2 on a dedicated PC running off an NVMe, system RAM usage was 16% before the crash according to HA’s own System Monitor sensor.
I’m going to try disabling VS Code Add-on as that’s the only thing we have in common and see how it goes.
I got the same issue here on 2025.7.2. I get the container stopped just after a bunch of Moonraker errors (Klipper, 3D printing stuff). Don’t know if it is related but I have created a bug report on their github.
My setup is a proxmox cluster with HAOS in a VM assigned 8gb or RAM (balooning disabled) and 2 cores.
The VS code eats CPU and not ram.
Ram will cause a kill 11, but CPU will just make it lag.