I’m running Home Assistant OS inside a VM and have also been unable to boot now (the VM won’t boot). Am running KVM on OpenMediaVault (so Debian OS) and getting cannot load AppArmor profile 'libvirt-5e32136e-2983-4da3-984b-f93fc4c794c6' in /usr/share/openmediavault/engined/rpc/kvm.inc:2679
Or after uninstalling apparmor (as suggested by someone on OMV forums, because Debian apparently does not use Apparmor, the error changes into:
apparmor upported configuration: Security driver model 'apparmor' is not available in /usr/share/openmediavault/engined/rpc/kvm.inc:2679
I’m not entirely sure the issue is with Home Assistant OS upgrade or an OMV update, but posting this here anyway hoping it helps devs to find the underlying issue @MissyQ
update: got it booting again by removing apparmor security in the KVM settings AND adding security_driver = "none' in qemu.conf on the Debian/OMV OS
Putting this out here for others that might have similar issue.
same problem as you guys here on normal pc x86 running HAOS.
when i try to update to 16.0 it becomes unreachable. hard reseting the pc rolls it back to 15.2 automaticly
Thank you so much for this!!! Went around in circles and then found this fix, regardless of what is being claimed by agners, it’s clear the update does ‘break’ something in the network settings on Hyper-V installs
In this thread I saw that (only?) the version for yellow has been pulled. But I saw a lot of posts here and additional threads around Hyper-V, Blue, … and it is still offered for my Blue. And I don’t see any general waring messages on central pages. Really save at the moment to do the update? My gut feeling is warning me somehow.
Does anyone have any tips for me for how to save my system? It’s been dead since I started this thread and I haven’t had luck connecting to the console (though possible that’s user error in making the connection rather than there being nothing to connect to…)
Do you have a recent full backup of your system? Are you using a CM4 or CM5 with eMMC? If your CM4/CM5 is not using eMMC storage to boot HAOS, then this process is simpler…
If you have a confirmed, good backup and your HA Yellow boots directly off of the NVME drive, then one approach would be to remove your NVME drive from the HA Yellow, install it in a USB enclosure, and then image the NVME drive with the HAOS 15.2 Yellow image. Place the NVME drive back in the HA Yellow, let it boot up, and then restore the Backup file.
NOTE WELL!!! - If your Backup File is encrypted, make sure you have the encryption key to restore it. Otherwise, the above procedure will result in a completely clean HA system, with none of your setup or configuration.
If you’re using a CM4/CM5 with eMMC storage to boot HAOS, then I would recommend you follow the HA Yellow documentation for resetting and reinstalling HAOS 15.2. After you have that up and running, then restore your backup file.
If you do not have a backup file, I do not know what to tell you… I have my HA Yellow backing up to itself, to a local NAS, and to the Nabu Casa Cloud every night.
My system is a CM5 with no built in storage; the entire system is installed on the NVMe (which is very large — 2TB, including lots of history).
I have some old backups but the latest, embarrassingly, are auto stored to that same NVMe. Unless the OS update completely corrupted it, they should still be there — any advice on where to look for the right backup file if I pull it out and mount it via USB to another computer?
Also, I do think it’s possible that I’m just not connecting correctly to the console connection. Any tips there?
The best way to get on the console of the HA Yellow is to wire up a USB-to-UART adapter, so that then any simple serial terminal can be used, like PuTTY. This would be analogous to hooking up a monitor and keyboard to a standard Raspberry Pi.
UPDATE: I just learned that the HA Yellow provides onboard USB-C based console access, if the UART jumper is proper placed. Forget the above and simply follow the instructions mentioned above by agners.
The other method of accessing the HA Yellow is via a SSH session. This requires that you’ve already installed the following HA Add-On.
If you haven’t already installed that Add-On, I am not sure there is any way for you to connect to the HA Yellow via an Ethernet connection.
I am not sure what the current state is of your HA Yellow. So, depending on that, I am not even sure which of the above options are available to you. The HA Yellow’s internal backup files may be readily available if you move the NVME drive to a USB enclosure and open it up on a computer that can read its partitions. Grabbing those files would be a good idea in case you go down the full re-image of the NVME + restore backup route. I am not sure if those files are encrypted or not?
Thanks @ogiewon . I’ve tried following the directions from @agners , above. Basically: connect usb-c-to-usb-c to my MacBook and use the screen command… The instructions did not work directly as written so I tried a variation that did not work. (No luck connecting via Ethernet.)
Separately, @ogiewon I tried pulling the NVMe out, putting it in a USB enclosure and connecting to my Mac, but the format was unrecognized. What filesystem does Home Assistant use?
HAOS is Linux, so one of the Linux filesystems. Do you have a Raspberry Pi or some other computer that you could run Linux on? Maybe run a virtual Linux computer on your Mac? I am not an expert on HAOS, so I really can’t delve much deeper.
Thanks @ogiewon for the suggestion. I was able to pull the NVMe out, put it in a USB enclosure, and successfully mount it on a RPi. So I have access to the most recent automated backup (Yay!!!)… However, now what? Is there any way to, e.g., just replace some portion of the files on the NVMe with the OS15.2 versions, pop it back into my HA yellow, and then be on my way, with everything just as it was right before the upgrade to the disastrous OSv16? (I’m assuming it’s not that easy, but here’s to hoping!)
I would copy the backups from the NVME drive over to the Raspberry Pi for safekeeping.
Then see if you can open up the backup files on the RPi, to know whether or not they are encrypted. If encrypted, do you have your “Home Assistant Backup Emergency Kit”? This is a text file that contains your encryption key, which is needed to restore an encrypted backup file. See Backup emergency kit - Home Assistant for details.
So, assuming you have the ability to restore a backup file (I.e. your backups are not encrypted, or if they are encrypted you have the encryption key), then I would simply wipe the NVME drive clean by imaging it with the HAOS YELLOW 15.2 image. Then put the NVME drive back in the Yellow, boot it up, and then restore the backup file.
I do not know of any way to manipulate the files on the NVME drive to get back to 15.2. Not saying that is not possible - just that I do not personally have that level of expertise to do so.
One more idea… Get a new NVME drive, image it with HAOS YELLOW 15.2, and then restore your backup file to it. this way, you can always simply revert to the original NVME drive should things go terribly wrong with the new drive and restore.
