HAOS has been a nightmare and I am planning on moving off it eventually, but I would really don’t have time and would like to find a temporary fix. It seems a little bit odd that even the console would lock up.
The last logs written before it locks up don’t provide much information.
I think I have a similar issue. HA OS just crashes randomly, sometimes it runs for a week, this weekend it crashes twice, once it worked for two weeks. CPU utilization and RAM usage are completely normal until it happens. Sadly I can’t provide more information, because there just are no logs. I used journalctl with a monitor connected after the reboot, and before HA OS goes down everything is normal, no error messages or anything, and then they just stop. My logs also look similar to the log posted here, but one time I managed to connect a monitor shortly after it crashed, and it showed these messages on the console:
systemd[1]: systemd-hostnamed-service: Watchdog timeout (limit 3min)!
systemd[1]: Failed to start Journal Service.
systemd[1]: Failed to start Network Time Synchronization.
After the reboot, the logs also just stopped at the time it crashed. But that was the only time it displayed something after going down, usually the screen is just black and I also can’t ping HA anymore. Once the PC also beeped for some reason, not sure if that’s related to the issue.
Also running a Generic x86-64 system with OS 14.0, Core 2024.12.1, Supervisor 2024.12.0. I already had the issue with HA OS 13.x though. It originally started when I still ran it on a Pi 4 2GB. I then switched over to this PC, because I thought it crashed because it ran out of memory. Not sure if the crashes on the Pi had the same cause these ones do.
Problem with that approach is that it crashes anywhere between 2 days and 2 weeks. It could take months with that approach to find. I did disable the default_config this round, but it is still discovering devices.