Installing Home Assistant OS using Proxmox 7

The Supervisor panel has been merged into the configuration panel. The separate menu item from the sidebar has been removed.

@kanga_who I suggest editing the main post and using @tteck β€˜s script to install HA OS instead. It’s an extremely polished script, and more importantly the author is active both here and on Github, he is actively maintaining and improving the script, and if anyone has a specific issue with it, they will be able to get quick help. Worked like a charm for me, and I think it’s something worth considering, since Whiskerz007 seems to have stopped developing these scripts.

1 Like

It did that some time ago already :wink:

Oh wow sorry, I was deceived by the fact the instructions still credited Whiskerz007 for making the script, I assumed that was the script being installed in the post (I went to the bottom of the thread first and ran my installation directly from tteck’s repo because I assumed the main post was running Whiskerz’s instead. Apologies

Gave it a shot but hafter it extracts the image it errors out.

 βœ“ Downloaded 8.1.qcow2 Disk Image
 βœ“ Extracted Disk Image
 - Creating HAOS VM...β€Ό ERROR [email protected] Unknown failure occured.

That’s usually the storage you’re trying to use

Yeah I have a single β€œlocal” storage, no lvm

What type of file system are you using for β€œlocal”? ext4 | ZFS | BTRFS ?

edit: Just a note… the script doesn’t work with BTRFS or Pimox.

To be honest I can’t tell everywhere i looked it just says lvm. Just used the defaults when installing proxmox. I did combine both partitions into a single local partition.

Did you select the defaults when attempting to create the VM?

Yes I did.

After you combined partitions, did you add Disk image & Container to local?

Screenshot 2022-06-06 4.21.55 PM

As you can see, mine isn’t selected.

Yes all our selected actually.

Here is the error.

Creating HAOS VM…volume β€˜local:100/vm-100-disk-1.qcow2’ does not exist
:bangbang: ERROR [email protected] Unknown failure occured.

Yeah, same as (but had lvm to fallback)
I’m pretty sure it’s caused by the combined partitions. I’ve never tested that.

If I may ask, why did you combine?

fyi… cat /etc/fstab or lsblk -f should tell you


Proxmox creates weird partition sizes and leaves space unusable for certain things… I have been doing it a few years now with no issue.

Edit: I just did it manually and im up and running.

1 Like

Thanks for reminding me I need to update the guide

Looks good, other than β€˜sata0’ should be β€˜scsi0’ :wink:

Changed :+1:

1 Like