Please help: Botched supervisor to appliance install

I have an install of home assistant that has been 5 years old at this point. It has seen the early days, and all the rough edges and the last several years of high quality releases and it has been a core and indispensable part of my life. It was installed with a supervisor because back then, it used to be the only way to get an install and for a long time, it was the recommended way to install.

Given that supervisor is getting deprecated this year end, I figured this weekend is a great time to do this upgrade. My home assistant resides on a small amd thin client, so I took one last backup of home assistant to my synology before I rekicked. I also rsynced over the entire contents of

/usr/share/hassio

I booted into an ubuntu live image and dd-ed over the contents of https://github.com/home-assistant/operating-system/releases/download/15.2/haos_generic-x86-64-15.2.img.xz to the root drive. My plan is to restore with the latest backup because I’ve heard how everyone has had a pleasant experience.

I am at the page to restore the backup and I am staring at a dialog that is asking me for an encryption key. I don’t recall setting one, though I am sure the reason why I am asked for one is because I set one. I have been looking around the usual locations to see where I might have placed a backup key, but I don’t know if I did that. I’ve been complacent about maintenance for a while and I am now deeply regretting it.

I am largely to blame for this. The last couple of years have been so smooth with hass that I’ve been going through releases without thinking too much and I haven’t reimaged in years and forgotten all the tiny details. I know my way around a linux install and I’ve been happily running the supervised install with zero complaints. Can I get the install to a point where I can ssh in and copy over the database and addon list? I realize it might be hacky, but my install has a dozen or more hacs repos, 30-40 integrations and three dozen small automations that would be hard to recreate.

ETA: I have backups in a three tier solution - stored on the disk, stored on the local nas, and also stored in google drive. The problem is that I never tested restoring the backup and I didn’t realize that I am missing the encryption key until the time I had to restore it. From what I am reading the only way to pull the encryption key was from the original install before I wiped the disk.

You should be able to use these to get up and running again. Install the Samba add-on and copy everything over again.
Once Samba is running, first do a

ha core stop

and after copying, a full host restart

(And disable encryption if you just backup to your NAS)

Thank you. I’ll give this a try and report back on the status

Forgot : don’t forget to copy the hidden files and directories.

Indeed. I am rsync-ing the entire contents over to skip that hassle. Looks like this is going to take overnight, so I’ll know the results after waking up.

Everything apart from the addons have been copied over, and I think I should be able to restart home assistant while that copy happens in the background, but I’ve had enough fun for one day :smiley:

@francisp I did a slight improvement over your suggestion. My first attempt didn’t work because I had some missing yaml files - I had split things into multiple sub yamls to make my configuration.yaml simpler to manage and forgot to copy everything over.

When I rebooted, I saw an option to go into recovery mode. That gave me shell access with root without docker running. Poking around, I saw that /mnt/data/supervisor was the equivalent to supervised install’s /usr/share/hassio. I removed the new directory and copied everything over from my snapshot. One reboot later, I have my old install again. Thank you so much for nudging me along in the right direction.

1 Like