added systemd.unified_cgroup_hierarchy=0 to kernel parameters.

disabled avahi daemon from starting via systemctl.

I have tried to fix a problem by fixing each of reasons my system was not compliant: Recently i have restarted my system (which previously had an uptime of several hundreds of days) and after the restart supervisor started to die every few minutes and it was not possible to update it to the latest (2022.07) version. Initially hass didn’t recover but I tried a supervisor restart from the local command line and that fixed it. After the SSD flash and I did the initial web login to ha, I restored my configuration from a backup by uploading the most recent backup file from nas. Luck for me I have been using the samba backup addon to save nightly ha backups to my nas. The reflash of the SSD wipes your config. Luckily this update did not cause a bootloader issue for me and my system was already down so I was willing to take the risk since I had nothing to lose. Many of us were not updating the OS because there were bootloader issues with rpi and USB 3 SSD after that version and we were afraid to upgrade. This issue (for users with hass os, not a custom supervisor docker on Linux) was likely caused because I was on an old hass os (v5.13). This didn’t work for me so they suggested downloading the latest hass os image and flashing it to my SSD. The folks on the discord advised me to update hass os from the local command line incrementally (6, then 7 and finally latest 8.x) with ha os update -version 6.0.

Crashplan pro docker