Constant reboot after 2026.9 update

Hi all,

Been using Home assistant very successfully over the last few years, and have been expanding my configuration over time. Nothing too fancy, but it’s an essential service in my home.

After installing the latest 2026.9 update, HA will only stay up for about a minute before restarting, it’s in a constant cycle and i’m at a loss as to what to do with it. The system barely lasts long enough to get to the logs, let alone see what happened before i get the ‘Reconnecting’ message again.

I’m running on Lenovo M73, Running Proxmox(9.2.11)
9GB of RAM (i’ve disabled most addons trying to figure out the cause of the issue)

I did also recently add a Thread Border router to the system, but the addon is disabled and the usb device is removed via proxmox.

Not sure what logs i can grab before it restarts, i’ve managed to grab my last backup from a couple days ago, it would seem that i didn’t take one prior to the upgrade… my bad.

Any advice would be great, i’m kind of at a loss.

Hi, try to manually restart and select safe mode.

Still stays up for about a minute, and then ‘Connection lost. Reconnecting…’

Of course it then starts up normally :frowning:

I am also having an issue, slightly slower then you. a few minutes after core starts I get a MASSIVE memory usage spike (my vm has 10gb ram) then its fine for a while then a crash (i think its another spike and ram runs out)

safe mode doesn’t help

Hi, are you also running HAOS, bare metal or virtualized?

@serville are there RAM spikes showing in Proxmox?

Oh yeah, should have mentioned that, virtualised, running HAOS (supervisor and core).

It’s kind of spiky :smiley:

I’ve attempted a restore back to 2026.8.3, will see if that works.

looks like i’m out of RAM:

considering none of my addons are running, this shouldn’t be the case

It looks like we have similar issues. because my system survives the first spike i can see the spike in home assistant not just on hypervisor. Core container suddenly spikes in usage. I can see it on the system monitor and also on glances.

well, looks like that restore failed miserably, i still have access to the supervisor now :frowning:

Can confirm same issue running haos vm on Unraid

Well, looks like i’m quite screwed at the moment, trying to work our how to restore from the CLI at the moment :frowning:

Not having a good day :slight_smile:

Maybe someone jumps in with good suggestions…

It’s a pity that, while using Proxmox, you didn’t use the easy way to make a backup!

I’ve got a very old backup in proxmox, from 2025 :frowning:

it doesn’t look like any of the current backups i have are valid, they are partial :frowning:

Maybe an idea to test your backups after this hiccup…

Also, keep an eye on: Issues · home-assistant/core · GitHub

Almost quite sure, upcoming Friday there will be a minor update that could fix this.

Good idea, i’ll re-enable my proxmox backups too, not sure why they were disabled :frowning:

Backups are one of the strong parts of Proxmox.
I create them manually and every time I install an upgrade, minor or major.

So i suppose for now, i need to reinstall from scratch, and then restore from the automatic backup?

Since you are now not alone with this issue, someone might come to help or a fix is presented.

Depending on whether you can wait and go back to old-fashioned control for a short timeframe, or not, reinstalling can be a way to get your system running again…

that restore attempt completely broke it, i can’t turn my lights on hahahaha :smiley:

Have a fresh build coming up now, will figure it out

A fresh install and backup restore is my fall back, I am trying to avoid doing that for now if only I can just narrow down that the issue is here…