We seem to be hitting the same issue, also on Azure.
It happens when we deploy a VM from a Shared Image gallery and change the OS disk size during deployment. We use a template spec to deploy the VM. If we set diskSizeGB in the storageProfile, the issue appears.
mount: /var/lib/grub/esp: special device /dev/disk/by-id/scsi-14d534654202020203d0cbbcd0bb74669a97057319f6cd140-part15 does not exist.
I does not happen when we keep the original OS size from the image:
ls -al /dev/disk/by-id/ | grep sda15
lrwxrwxrwx 1 root root 11 Sep 14 09:04 scsi-14d534654202020203d0cbbcd0bb74669a97057319f6cd140-part15 -> ../../sda15
lrwxrwxrwx 1 root root 11 Sep 14 09:04 scsi-3600224803d0cbbcd0bb757319f6cd140-part15 -> ../../sda15
lrwxrwxrwx 1 root root 11 Sep 14 09:04 wwn-0x600224803d0cbbcd0bb757319f6cd140-part15 -> ../../sda15
We seem to be hitting the same issue, also on Azure.
It happens when we deploy a VM from a Shared Image gallery and change the OS disk size during deployment. We use a template spec to deploy the VM. If we set diskSizeGB in the storageProfile, the issue appears.
mount: /var/lib/grub/esp: special device /dev/disk/ by-id/scsi- 14d534654202020 203d0cbbcd0bb74 669a97057319f6c d140-part15 does not exist.
ls -al /dev/disk/by-id/ | grep sda15 0202020ad9d6684 20ceb0419516df3 a7418668d- part15 -> ../../sda15 d9d668420cedf3a 7418668d- part15 -> ../../sda15 d9d668420cedf3a 7418668d- part15 -> ../../sda15
lrwxrwxrwx 1 root root 11 Sep 15 10:23 scsi-14d5346542
lrwxrwxrwx 1 root root 11 Sep 15 10:23 scsi-360022480a
lrwxrwxrwx 1 root root 11 Sep 15 10:23 wwn-0x60022480a
I does not happen when we keep the original OS size from the image: 02020203d0cbbcd 0bb74669a970573 19f6cd140- part15 -> ../../sda15 d0cbbcd0bb75731 9f6cd140- part15 -> ../../sda15 d0cbbcd0bb75731 9f6cd140- part15 -> ../../sda15
ls -al /dev/disk/by-id/ | grep sda15
lrwxrwxrwx 1 root root 11 Sep 14 09:04 scsi-14d5346542
lrwxrwxrwx 1 root root 11 Sep 14 09:04 scsi-3600224803
lrwxrwxrwx 1 root root 11 Sep 14 09:04 wwn-0x600224803