Armbian Home Assistant Supervised Docker install nocht possible

Hello everybody,

for years now I was running HA in a Docker environment on an Armbian Debian OS.

But for some weeks now, it turned out to be impossible to reinstall HA with a Supervisor.

I installed HA using following manual GitHub - home-assistant/supervised-installer: Installer for a generic Linux system

But in always get this error message

AddonManager.install’ blocked from execution, system is not healthy

The System log has following to say

2022-10-21 10:32:17.863 ERROR (MainThread) [homeassistant.components.websocket_api.http.connection] [281473056931648] Error updating Home Assistant Core 'HomeAssistantCore.update' blocked from execution, system is not healthy

Traceback (most recent call last):

File "/usr/src/homeassistant/homeassistant/components/hassio/update.py", line 303, in async_install

await async_update_core(self.hass, version=version, backup=backup)

File "/usr/src/homeassistant/homeassistant/components/hassio/handler.py", line 45, in _wrapper

raise HassioAPIError(data["message"])

homeassistant.components.hassio.handler.HassioAPIError: 'HomeAssistantCore.update' blocked from execution, system is not healthy

The above exception was the direct cause of the following exception:

Traceback (most recent call last):

File "/usr/src/homeassistant/homeassistant/components/websocket_api/commands.py", line 202, in handle_call_service

await hass.services.async_call(

File "/usr/src/homeassistant/homeassistant/core.py", line 1738, in async_call

task.result()

File "/usr/src/homeassistant/homeassistant/core.py", line 1775, in _execute_service

await cast(Callable[[ServiceCall], Awaitable[None]], handler.job.target)(

File "/usr/src/homeassistant/homeassistant/helpers/entity_component.py", line 207, in handle_service

await service.entity_service_call(

File "/usr/src/homeassistant/homeassistant/helpers/service.py", line 678, in entity_service_call

future.result() # pop exception if have

File "/usr/src/homeassistant/homeassistant/helpers/entity.py", line 931, in async_request_call

await coro

File "/usr/src/homeassistant/homeassistant/helpers/service.py", line 715, in _handle_entity_call

await result

File "/usr/src/homeassistant/homeassistant/components/update/__init__.py", line 154, in async_install

await entity.async_install_with_progress(version, backup)

File "/usr/src/homeassistant/homeassistant/components/update/__init__.py", line 413, in async_install_with_progress

await self.async_install(version, backup)

File "/usr/src/homeassistant/homeassistant/components/hassio/update.py", line 305, in async_install

raise HomeAssistantError(

homeassistant.exceptions.HomeAssistantError: Error updating Home Assistant Core 'HomeAssistantCore.update' blocked from execution, system is not healthy

2022-10-21 10:32:30.319 ERROR (MainThread) [homeassistant.components.hassio] Failed to to call /addons/a0d7b954_unifi/install - 'AddonManager.install' blocked from execution, system is not healthy

I already used two different SBCs Helios64 and rock64, no success and during the installation i get these messages

[warn] Could not find /etc/default/grub or /boot/firmware/cmdline.txt failed to switch to cgroup v1

/var/lib/dpkg/info/homeassistant-supervised.postinst: line 150: update-grub: command not found
dpkg: error processing package homeassistant-supervised (--install):
 installed homeassistant-supervised package post-installation script subprocess returned error exit status 127
Errors were encountered while processing:
 homeassistant-supervised

Does anybody know a solution to this?

Regards

The problem is that the script in the debian package cannot find the kernel parameters for disabling cgroups v2 and switching to cgroups v2. In the selection of which hardware to use I selected qemu armv7 for a Orange Pi PC plus. For the 64 bit chips you should probably select the arm64 qemu.

You can then switch to cgroups v1 by adding the following line to /boot/armbianEnv.txt:

extraargs=systemd.unified_cgroup_hierarchy=false

I still got the same warning you got but after a reboot everything started working.