Long-time user of Home Assistant running as a VM. Recently started seeing Z-wave connectivity issues and noticed the HA VM console showing lots of "out of memory" errors, so I decided to increase the RAM on this VM from the default 1 GB to 4 GB. The next boot of the HA VM promptly reached the shell prompt, indicating, I assume, that it can't find the bootable disk: "map: No mapping found."

I stumbled across another post where folks were having similar issues (https://forums.unraid.net/topic/102345-tried-to-back-up-my-vm-image-now-it-wont-boot-uefi-shell/), but everything seems to be set fine within my XML for this VM (the disk is labeled as qcow2):

Not really sure where to turn now - the disk file still exists in the unraid file structure. Really hoping there is some simple fix that I'm overlooking! Any help is appreciated.

And with all that being said - I recreated the VM and pointed the new VM to the existing disk which magically resolved the issue *phew*

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.

I just created a new VM with the same settings as before (except increasing memory) and pointed the vDisk to the old qcow2 file.

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.