Proxmox Only boots into UEFI interactive shell

[rmtx99]

Hello everyone,

I'm having trouble with my proxmox installation, where I have installed HomeAssistant in an VM.
For Installation of HomeAssistant I used the Install Script by tteck.

My HomeAssistant VM is stuck in UEFI Boot Shell when trying to boot.

I don't know for sure, but probably this is because my LVM Storage ran out of memory during an home assistant update (is this possible?).

What I did so far:

1. Updated Proxmox to latest Version and also updated Linux Kernel to 6.5
2. Checked the Secure Boot settings according to various entries here in the forum, e. g. here
   • Sadly, the Secure Boot Option is "disabled" and there is no chance to enable it for me. I'm not sure whether this is supposed to be this way, but this because I also can't edit edit the "Attempt Secure boot" as suggested in various forums.
3. Tried to boot manually by accessing fs0 and run the bootx64.efi
   • Sadly, the command is unsupported and I am really not aware why or whether this might be the root cause
4. I ran gdisk in ordner to rewrite partition table as suggested here. Sadly also this was with no luck.

So currently I really don't have any Idea what exactly is causing the problem or whether there is any other solution approach. Every help is really much appreciated!

Best Regards!

 

[LaurensNL]

Hello rmtx99,

did you find a solution? I am facing the same issue.......

Started after updating Home assistant oparating system to 12.0.
But now also when I make an new install I get the same result. VM hanging in UEFI screen....

Greetings Laurens

 

[rmtx99]

Hi @LaurensNL,

sadly I wasn't able to find any solution. I ended up accessing the disk bei a local debian vm and copying my homeAssistant Backup Files (now I have my Backup on external storage...). Afterwards I changed the hard disk of my server because of limited space and reinstalled proxmox and restored HomeAssistant from HomeAssistant Backup Files.

For my case it is possible, that the hard drive had a physical error but I don't know for sure.

Hope you find a solution soon!

Best Regards

 

[Ralph Schmidt]

Hi everyone,
after converting the virtual disk of a migrated VM from SATA to SCSI, I had a similar problem.
In my case I had to change the boot-order by running following command within EFI shell:

reset -c -fwui