This started a long time ago, but every time I reboot the OS, or upgrade the OS version, I end up getting stuck on a GRUB screen and have to make a selection.
This time I had to select Slot B in order to it booted up to OS 9.2
I went to the command shell and looked at the environment an it’s set to ORDER=B A
How can I get it to auto select Slot B so I don’t have to on each boot?
I still have found an answer for this. Anyone else see something like this?
I have the same problem, each time I reboot with the app or update or in CLI, the boot sequence gets stuck at GNU GRUB. I even have to reboot the machine manually because it freezes at the GNU GRUB page. I always manage to reboot but its a PITA 
I’m still having this problem years later. I’ve exhausted everything I can think of sans rebuilding my whole home assistant vm.
I had (what I thought was) a similar problem. However, the issue wasn’t actually with the guest OS getting stuck on the Grub boot screen. My issue was with the guest VM auto-starting on boot.
I’m using libvirt/qemu on Linux. Even though I had set the guest to autostart
virsh autostart hass
…my issue was that libvirt itself was starting lazily when triggered by a systemd socket (e.g. when I manually logged in and ran a virsh command). I fixed it by enabling the virtqemud unit
systemctl enable virtqemud.service