Failed to boot from UEFI VM Disk

[TC_Tecnet]

I just managed to fix this. Looks like the MBR on my boot disk was corrupt.
I discovered this by running

gdisk -l /dev/zvol/rpool/data/vm-101-disk-1

Then I ran

gdisk /dev/zvol/rpool/data/vm-101-disk-1
w

to write the changes. All worked after that.

MBR corruption on the main disk being moved while powered off does seem to be the symptom here as the Add Boot option is blank.

Moving the EFI disks first, powering the machine back on and then moving the boot disk while it's powered on works correctly.

@fiona is it possible there's a similar issue that can affect regular VM disks while the machine is offline?

 

[fiona]

Hi,

MBR corruption on the main disk being moved while powered off does seem to be the symptom here as the Add Boot option is blank.

Moving the EFI disks first, powering the machine back on and then moving the boot disk while it's powered on works correctly.

@fiona is it possible there's a similar issue that can affect regular VM disks while the machine is offline?

haven't heard any similar reports lately. Moving a disk offline preserves it bit-by-bit (except slightly padding it with zeroes at the end for some target storages that have larger allocation granularity, e.g. images on RBD are 4 MiB aligned by default) so that is definitely not expected. What storage are you using? Are your physical disks healthy?

Please share the VM configuration qm config <ID> replacing <ID> with the actual ID and output of pveversion -v.

If you move without deleting the source, what does

qemu-img compare $(pvesm path source:100/vm-100-disk-0.qcow2) $(pvesm path target:100/vm-100-disk-0.qcow2)

say, replacing the volume IDs to match what you actually have?