Need OS updated

I am getting the message “You are running an unsupported installation” on the Supervisor-Assistant tab. I am pretty sure it is because I am not running the latest OS - Debian 11 (Bullseye). My question is this - Is there any way to have the system update the OS, or must I start from scratch with a clean drive (I am running on an SSD, not an SD card).

If I must start with a clean install, what is the easiest way - step by step - to get my Hassio back exactly as it is, without major issues.

Thanks,
Mike

which OS you are running now and which install method? Quiet basic info, or do we have to guess?

I apologize for the lack of info. I am running Debian Buster with a supervised install. Do you need more info?

Thanks
Mike

on what device?

On a Raspberry Pi 3B.

In a console as the unprivileged user (not root) :

sudo sed -i 's/buster/bullseye/' /etc/apt/sources.list
sudo sed -i 's/buster/bullseye/' /etc/apt/sources.list.d/*.list
sudo sed -i 's|bullseye/updates|bullseye-security|' /etc/apt/sources.list

Only if you previously have installed Debian’s MQTT broker (mosquitto) on the OS level (not as a HA Add-on):

sudo sed -i 's/bullseye/buster/' /etc/apt/sources.list.d/*mosquitto*.list

Continue with the OS upgrade:

sudo apt update

Only if you see the following error message after “sudo apt update”:

The value 'buster' is invalid for APT::Default-Release as such a release is not available in the sources

Run:

sudo sed -i 's/buster/bullseye/' /etc/apt/apt.conf
sudo apt update

Now continue with:

sudo apt upgrade
sudo apt full-upgrade
sudo apt autopurge

The above will take some time. After it has finished it’s time to reboot the host:

sudo systemctl reboot

After the system has rebooted, open a new console and execute (again, as non-root):

sudo apt --fix-broken install
sudo apt-get install udisks2 wget
cd /usr/local/src

Now visit the OS Agent page and then replace the version number with the latest available, into the commands below. (i.e. replace all references to 1.2.2 with the latest available release):

If you run 32 bit :

sudo wget https://github.com/home-assistant/os-agent/releases/download/1.2.2/os-agent_1.2.2_linux_armv7.deb
sudo dpkg -i os-agent_1.2.2_linux_armv7.deb

sudo systemctl reboot

if you run 64-bit :

sudo wget https://github.com/home-assistant/os-agent/releases/download/1.2.2/os-agent_1.2.2_linux_aarch64.deb
sudo dpkg -i os-agent_1.2.2_linux_aarch64.deb

sudo systemctl reboot

Credit go to @tamsy

1 Like

Francis,

Thank you so much for such detailed instruction. However, the process seems to be stuck. I had just executed the command “sudo apt upgrade”. After quite a bit of time has passed it seems to stopped as seen in the pic here:

What should I do?

Thanks,
Mike

If there was no question asked, just wait. If there was a question asked, answer it.

Example of question I often get : your smb.conf differs from the maintainers. I always keep mine.

Francis, thanks again. Ok, I have completed down to the reboot. When I run the sudden apt --fix-broken install command I am getting a message that 459 packages were not upgraded. Is that ok and should I proceed, or do I need to go back?

Sorry sudo not sudden

That is no problem.

Francis, I finished the entire set of steps you provided and it all worked out well. My OS now shows Debian 11. However, my system still showed that I am running an unsupported installation. I noticed that my core was not the latest, so I upgraded it from Home Assistant supervisor tab.

Now my HA is not accessible from the web GUI.

image

I am not sure what is the cause. I think everything I run is standard except that I run MariaDB. Do you have recommended next steps?

Thanks for your continued excellent support,
Mike

I need help. I have upgraded to Debian 11 per the above steps and all works well - except AppArmor. When I enter command aa-enabled I get “No - disabled at boot”. I have searched and tried everything I could find on the web and nothing has worked. Can someone help ? This is casing my Home Assistant to show as bein an unsupported install.

Thanks,
Mike

add lsm=“apparmor” apparmor=1 security=apparmor to the line in the /boot/cmdline.txt file.

Francis,

Thanks for the suggestion. I added the line and rebooted. It still says disabled at boot. Any other suggestions?

Thanks,
Mike

on my pi4 I have this :

on my pi2 this :

both cases apparmor is enabled.

What does uname -a return ?

uname -a gives:

Linux hass 5.10.63-v7+ #1459 SMP Wed Oct 6 16:41:10 BST 2021 armv7l GNU/Linux

aa-enabled gives:

No - disabled at boot.