Server_home

Thanks for the input 👍 In the end we decided to move away from the HA OS VM and go with Home Assistant running in Docker on Unraid. The VM issues didn’t seem CPU-related indeed, and were most likely tied to the virtual disk / VM layer itself. Rather than spending more time troubleshooting XML / img edge cases, we opted for a setup that is simpler, lighter and more transparent on Unraid. We’re now running: Home Assistant Container (Docker) External MariaDB Dedicated Mosquitto broker VLAN-segmented network (LAN / IoT / isolated devices) This gives us faster restarts, lower resource usage, easier backups and better long-term stability on Unraid. So far the setup has been working well and fits our use case better than a VM-based HA OS. Thanks again for the suggestions.

Summary of the issueAfter migrating my Unraid system to new hardware (Intel Alder Lake), Home Assistant OS (HAOS) no longer boots as a VM. The VM consistently hangs at: Booting from Hard Disk... or drops directly into UEFI Interactive Shell. This happens with: existing HAOS disks (from previous working system) fresh HAOS images SeaBIOS and OVMF Q35 and i440fx machine types The same HAOS VM worked perfectly for years on the previous server. Previous hardware (HAOS VM worked perfectly)Dell PowerEdge T320 CPU: Xeon E5-2470 v2 (8 cores / 16 threads) RAM: 96 GB DDR3 Classic server platform (no hybrid cores) HAOS running as a VM without any issues Unraid 7.2.3 Current hardware (problematic)CPU: Intel Alder Lake (12th gen) Hybrid architecture (P-cores + E-cores) Motherboard: Z690 chipset RAM: DDR4 NVMe: WD_BLACK SN7100 1TB NIC: Intel I225-V Integrated GPU: Intel UHD Graphics 770 Unraid 7.2.3 IOMMU is enabled and working correctly. VM configuration testedI have tested multiple combinations, including: Machine types: Q35 i440fx BIOS: SeaBIOS OVMF (UEFI) Disk formats: .qcow2 .img Images tested: Fresh HAOS x86_64 images downloaded from GitHub releases Boot order: correct (disk first) Network: virtio-net (no IP ever appears) CPU pinning: tested pinned and unpinned vCPU count: 1–4 cores RAM: 4 GB+ Result is always the same: Either stuck on “Booting from Hard Disk…” Or dropped into UEFI shell, even though EFI files exist (bootx64.efi, grub.cfg) Manually launching EFI binaries from the shell results in: Command Error Status: Unsupported Additional confirmationI followed a YouTube tutorial that uses the same VM specs (Q35 + OVMF + HAOS image). On my system, it also drops to the UEFI shell, exactly the same behavior. This suggests the issue is not image-specific and not configuration-specific. Question to the communityIs anyone successfully running Home Assistant OS as a VM on Alder Lake (hybrid P/E cores) on Unraid 7.x? Is this a known incompatibility between HAOS and newer hybrid CPUs? Is there any recommended workaround? Or is the advised path now to run Home Assistant via Docker instead of HAOS VM on this hardware? At this point I am considering moving to Home Assistant (Docker) and restoring my backup there, but I wanted to check with the community first in case this is a known limitation or has a confirmed fix. ThanksThanks in advance for any insight. Happy to provide logs, screenshots, or XML if needed.

Hi Guys I have just bought a Energenie EG-UPS-033. I have try every drivers but I always get this error message in log Is there any way that i can put the nut plugin working ?

I didn't understand what you mean. Can you please explain?

hello again in some files I am geting the error cp: error reading '/temp/domains/hassio/haos_ova-9.3.vmdk': Input/output error is there a solution ?

Now that i already have the vmdk files , how can i put them back on again ?

Do you think that there is a problem with the mvme ? Should I replace it ?

i use this one root@Tower:/temp# mount -o rescue=all,ro /dev/nvme0n1p1 /temp now in /temp I have 3 folders appdata/ domains/ system/ Do I save them, format the MVME and them copy the files to MVME ?

when i do this step mount -o usebackuproot,ro /dev/sdX1 /temp I get this message root@Tower:/temp# mount -o usebackuproot,ro /dev/sdX1 /temp mount: /temp: special device /dev/sdX1 does not exist. dmesg(1) may have more information after failed mount system call.

But the cache drive is Unmountable: Unsupported or no file system so is there a way to recover it ? I have the Vm iso files stored in other avaliable disks , can i recover a vm from a iso file ?

I think that the problem is that cache drive is Unmountable: Unsupported or no file system Can I format it ? All my docker data and vm's are saved and accessible as you can see in the screenshot By the way how can I add my vm's again to the VM tab so I can acess them ?

JorgeB I get this root@Tower:~# btrfs rescue zero-log /dev/nvme0n1p1 Clearing log on /dev/nvme0n1p1, previous log_root 3102204461056, level 0 ERROR: failed to write super block for devid 1: flush error: No data available ERROR: failed to write dev supers: No data available WARNING: fsync on device 1 failed: No data available

Hi Guys I have lost all my VM's and Docker Service failed to start. I saw that my cache drive is Unmountable: Unsupported or no file system I can access to all my discs Can someone help me to repair everything ? tower-diagnostics-20231130-2252.zip

Hi Guys I have lost all my VM's and Docker Service failed to start. I saw that my cache drive is Unmountable: Unsupported or no file system I can access to all my discs Can someone help me to repair everything ? tower-diagnostics-20231130-2252.zip

Hi Guys I have lost all my VM's and Docker Service failed to start. I saw that my cache drive is Unmountable: Unsupported or no file system I can access to all my discs Can someone help me to repair everything ? In attach I send diagnostics tower-diagnostics-20231130-2252.zip