Update 2020.12.7 / 5.9 broke my system

I’ve updated everything to the newest stable.

HA works for about 5-10 minutes, and than stops working. I have a p4, with Home Assistant OS (Hassio/docker).

Before the crash memory seems to go up. Cannot see why, but it might be a memory leak or so…

I’ve did a complete reinstall on a different SD card with restore. Problem is still there.

Funny thing is, the system seems not total stuck. If I leave it, sometimes, an hour later, you can turn on a light. But 2 minutes later it’s gone again. So it seems overly busy or so.

I see this on the console.

Things appear on the console, but I cannot login. The system is inresponsive…

Update, I’ve rebooted again and notice that the memory is really going quick (see the clock)

And at 23:32 the webbrowser is unresponsive…

2020.12.7? the latest update is 2020.12.2! https://www.home-assistant.io/

Version differ for Home Assistant OS and Home Assistant Core.

But - HA OS 5.10 has been released 2 days ago, you might give it a try.

I don’t see that option, and I don’t want to join the beta channel. I prefer stable over new features.

I prefer stable over new features.

I prefer stable over new features.

In Github, it’s marked as stable, latest release. Maybe it takes some hours to become available as Docker image, dunno as I don’t use HASS.IO.

Yea, well, meanwhile, DNS in my entire network is broken, and I cannot control my heating and lights.

Great…

Hopefully I’ll be able to install it before the system crashes…

Is there a away to roll-back updates?

Sorry, I use Home Assistant Core, cannot help on rolling back HASS OS.

Gues it has to do with; https://github.com/home-assistant/operating-system/issues/1119

I’ve tried to downgrade the OS to 5.7 and 5.2, same problems.

Later today I’ll try to downgrade the core.

I wish the ppl in controll here would flag these OS/Core updates as unstable/beta because this causes network wide DNS outage and not being able to control your heating/lights.

I don’t think that your DNS problems are related to the suspected memory leak in Home Assistant OS. Unless the DNS server is running on the same system as Home Assistant and is affected by the lack of memory.

Well, since I run the DNS / Add blocker thingy AdGuard, my DHCP server is pointing to the HA host. And that became unresponsive.

So yes, they are related.

1 Like

That’s why HASS OS is so important: the more core services (DHCP, DNS, Ad-Blocking, FTP, SAMBA, …) you shift to HA the worse are consequences when HA doesn’t work as intended.

To be fair, this applies to all “single all-in-one-server” solutions. If that machine dies (for whatever reason), you’re doomed.

Did you enabled mDNS on your router. Try to disable it. I had the same issues, and disabling this option on my router did fix the issue.

I hope it helps

edit: mdns = multicast DNS

You could set AdGuard filtered DNS on your router in the meantime:

  • “Default” servers: 94.140.14.14 // 94.140.15.15
  • “Family protection” servers: 94.140.14.15 // 94.140.15.16

Ofcourse I’ve changed my DNS option in DHCP to a working one…

Meanwhile, I’ve tried;

  1. Deleting the SQL database
  2. Removed Samba add-on (only file editor en config check left)
  3. Downgraded to core 0.118
  4. Turned off every automation
  5. Basicly deleted everything from my config file (except zwave stick )
  6. Turned off every add-on
  7. Total clean install on a new SD card
  8. Tried downgrading to several HA OS versions

Still stuck within 5 minutes

Have you downgraded the OS?

ha os update --version 4.20

please can someone help me restore boot from USB on RPi3 + … i had an active system for a year i lost everything

So, I’ve learned over the last two years that home assistant is amazing, however…, the upgrade process is a crapshoot, be that the OS, the Supervisor, or Core…, they all suck.

The latest upgrade from core 2020.12 1 to 2020.12.2 nuked my system, booted but no Lovelace. tried a restore from snapshot via the command line, did nothing, tried to manually roll back, did nothing. CPU load average was 11 (normally 0.3), after 6 hours of grief I just wiped and rebuilt the SD card and restored a snapshot. This has become par for the course during the he last 6 months.

My advice, create snapshots and copy them somewhere safe before doing any kind of upgrade (I use this https://github.com/sabeechen/hassio-google-drive-backup ), the roll back system has never worked for me, and restoring from snapshots is very unreliable, unless done during a complete fresh install.

Pi3B+,HA OS 5.9, Supervisor 2020.12.7, Core 2020.12.1

1 Like

nothing to do I followed various guides for modifying the bootloader but they are for rpi4 I use rpi3 … today I installed an image from github with hassos 4.20 and fortunately my snapshot that I had made on December 3rd was successfully loaded. … from now on i think i will no longer update hassOS on my ssd … i will play with other ssd first before putting it into production