-
Home Assistant VM boots to UEFI shell
Just found that changing the Primary vDisk Bus from VirtIO to SATA solves the issue. Was is always SATA and magically changed to VirtIO due to an update? Or has something in the image changed to that it now requires SATA? I have no way of telling, but right now I'm just happy Home Assistant is running again 😀
-
KaasNAS started following Home Assistant VM boots to UEFI shell
-
Home Assistant VM boots to UEFI shell
Since last week my HA VM has been acting up. Suddenly crashing, but seemed to get back to its feet when started again. Unfortunately right now it can't even seem to figure out what feet are. Reading topics about the issue, the initial instability might have something to do with memory. Increased the memory and to be sure increased disk capacity as well. No go. There are reported issues from the past that the 'disk' part of the XML had the type set to 'raw', but that still shows 'qcow2' as it should. <disk type='file' device='disk'> <driver name='qemu' type='qcow2' cache='writeback' discard='ignore'/> <source file='/mnt/user/domains/homeassistant/haos_ova-9.3.qcow2'/> <target dev='hdc' bus='virtio'/> <boot order='1'/> <address type='pci' domain='0x0000' bus='0x05' slot='0x00' function='0x0'/> </disk> Have copied the XML to a new VM and pointed it to the existing image. Same message, no difference. And as a bonus, now the new VM cannot be removed. It's stopped, select to remove VM... nothing. qemu-img check does not return any errors. The rest of the system is running just fine, updated to 7.2.3, dockers are there... just the HA VM is missing. Can't imagine the image being corrupted all of a sudden... what else can I try? Thanks in advance for the help.
-
Home Assistant VM not mapping disk on boot
Thanks for the quick reply! Great it worked in your case... makes you wonder what the issue was Unfortunately it doesn't change anything on my side. Still stuck in shell. Increased memory, increased disk capacity (just in case), no go. As a wonderful extra issue the copy I created can't be removed. It's stopped, I choose to remove VM (and not the disk 😅), nothing happens. And so the search continues, there has to be a simple fix. Fingers crossed.
-
Home Assistant VM not mapping disk on boot
Did you simply copy the XML from the old VM to a new one? Because I just tried that... same result. Home Assistant will no longer boot, stuck in UEFI. Have found several topics on this issue and tried all suggestions there. All to no avail. From one day to the next, HA is broken. Can't imagine the image being corrupted all of a sudden.
KaasNAS
Members
-
Joined
-
Last visited