I am using VMs on GCP. and sometime I need to restore a the VM disk to an older snapshot. so the way I do it is I create a new disk from the old snapshot. delete the old one. and attach the new one instead. Everything used to run normally. I don't work on the machines normally its an automated pipeline that performs some installation. part of it is upgrading the apt packages. Now the automated build is getting stalled on this step:
Configuring shim-signed-----------------------The GRUB boot loader was previously installed to a disk that is no longer present, or whose unique identifier has changed for some reason. It is importantto make sure that the installed GRUB core image stays in sync with GRUB modules and grub.cfg. Please check again to make sure that GRUB is written to the appropriate boot devices. 1. /dev/sdaxx (111 MB; /boot/efi) on 32212 MB PersistentDisk 2. none of the above(Enter the items you want to select, separated by spaces.)I have read all about the disk UUID and everything about the partitions. I would like to think I know my way around these. tried blkid to see if changes after the snapshot. I even found out this command lately lshw -C Disk. It gets a GUID for the disk. but none of these change. even when I check the /boot/efi/EFI/ubuntu/grub.cfg, the UUID is still the same. and the VM actually launches and everything.
This behavior is new. Yesterday was the first time I observe such an error. although multiple VMs were restored before and had no issue whatsoever.
