I have been running HA on bare metal for many years, and after an update back in july timeframe, the installation states its runing as an OVA and not bare metal x64.
I have just installed a new SSD and post native install, it shows x64 however, once I restored my backup - it reverted to OVA!
How can I get HA to realise its bare metal?!?!
The main issue I have with this is that all the native USB devices fail to work as they dont make it over to the “vm”.
ha os info on proxmox returns ova, which is correct
Welcome to Home Assistant OS.
Use `ha` to access the Home Assistant CLI.
# os info
-sh: os: not found
# ha os info
board: ova
boot: B
boot_slots:
A:
state: inactive
status: good
version: "16.1"
B:
state: booted
status: good
version: "16.2"
data_disk: QEMU-QEMU-HARDDISK-drive-scsi0
update_available: false
version: "16.2"
version_latest: "16.2"
WHich disk image did you use for the ssd? And what type of baremetal you use. There is few flags that makes HA detect a installation type and the way the OS is packed on either disk image might be a player. (but also bios settings and possibly other things).
In the end i doubt that the installation type indicator has influence on the USB behavior.
From the HAOS console linux shell (or SSH) type dmesg. There will be a lot of output, but it should provide some indications as to whether your USB devices are showing up and then maybe dropping out.
BTW I’m running a VM and my UI->Settings->System->Hardware is showing it as “Generic Hardware”, so seems this particular method may not be reliable.
very true, not easy for finding everything if system is up long time
sudo dmesg -c
to clear the log and then run it again to see it empty. Take out USB device and re plug it. Then dmesg again you’ll find the involved log little easier and details if it mounted properly or somthing else (like drivers missing )
I followed the instructions in the link above, which worked fine and reported as generic x86. It was fine until I restored my backup, then it reverted to ova.
The tin is an HP ProDesk micro boxes… gen 7 or 8 cpu.
Thanks for your advice chaps.
I will check what it says in dmesg and report back.
NOW…here may be a big clue…so need to investigate…when looking at disk, the geometery of the partitions have changed…see below … disks when booting as a VM…
the boot slots are in boot managere (not sure if its ‘grub’ still). Dealing with boot tools like that broke my brain before (wanted to deal with some cpu feature flag). It should be possible to
pause booting before a slot is chosen
modify boot options then and there with some special CLI for grub (if its still grub that HAOS uses for booot manager)
but i cant help you on the how, as i failed myself doing so
