I recently moved my Ubuntu installation from Parallels to Virtualbox, which naturally resulted in updated disks' UUIDs. Normally that should be a problem as Ubuntu should autodetect such change and act accordingly.
However, upon upgrading grub-efi-amd64-signed, dpkg kept failing with:
Setting up grub-efi-amd64-signed (1.142.4+2.04-1ubuntu26.2) ...
mount: /var/lib/grub/esp: special device /dev/disk/by-id/ata-Ubuntu_Linux-1_SSD_SF74YQ6DP1KMD07F8JED-part1 do
es not exist.
The Parallel's disk ID that it attempts to mount indeed no longer exists. The EFI partition is correctly mounted at /boot/efi, since the /etc/fstab uses partition UUID to mount it and that didn't change, so there's no reason why the script should fail.
Note that it detected the new, correct "/dev/disk/by-id/ata-VBOX_HARDDISK_VB1-1a2b3c4d-part1" UUID of the disk that contains the EFI partition.
I debugged it further and can see that the following happens in /usr/lib/grub/grub-multi-install (which is part of grub-common package):
1) in "# We either migrate /boot/efi over, or we check if we have invalid devices" section, it correctly detects that the Parallels device does not exist ("if [ ! -e "${device%,}" ]", setting the valid=0
2) given that valid=0, my understanding is that at this point the "install_devices_disks_changed" prompt should be triggered, but it is not.
3) the "$RET" variable still contains both of the disks from grub-efi/install_devices
4) in "# Run the installer" section, the script iterates over each of the disks, attempting to mount ("mount $real_device $mntpoint) the non-existing one, which results in the aforementioned script failure.
My understanding here is that there are two problems:
1) "install_devices_disks_changed" prompt was not shown
2) there's no check for whether the device exists at all before the script proceeds with mounting and grub-installation attempt
I recently moved my Ubuntu installation from Parallels to Virtualbox, which naturally resulted in updated disks' UUIDs. Normally that should be a problem as Ubuntu should autodetect such change and act accordingly.
However, upon upgrading grub-efi- amd64-signed, dpkg kept failing with:
Setting up grub-efi- amd64-signed (1.142. 4+2.04- 1ubuntu26. 2) ... by-id/ata- Ubuntu_ Linux-1_ SSD_SF74YQ6DP1K MD07F8JED- part1 do
mount: /var/lib/grub/esp: special device /dev/disk/
es not exist.
The Parallel's disk ID that it attempts to mount indeed no longer exists. The EFI partition is correctly mounted at /boot/efi, since the /etc/fstab uses partition UUID to mount it and that didn't change, so there's no reason why the script should fail.
The debconf shows the following:
dawidw@ubuntu:~$ sudo debconf- get-selections | grep grub-efi cmdline string install_ devices multiselect /dev/disk/ by-id/ata- Ubuntu_ Linux-1_ SSD_SF74YQ6DP1K MD07F8JED- part1, /dev/disk/ by-id/ata- VBOX_HARDDISK_ VB1-1a2b3c4d- part1 efi_extra_ removable boolean false cmdline_ default string quiet splash i8042.nopnp kernels note efi_extra_ removable boolean true map_regenerated note install_ devices_ disks_changed multiselect /dev/disk/ by-id/ata- Ubuntu_ Linux-1_ SSD_SF74YQ6DP1K MD07F8JED- part1, /dev/disk/ by-id/ata- VBOX_HARDDISK_ VB1-1a2b3c4d- part1 install_ devices_ empty boolean false install_ devices_ failed boolean false cmdline_ default string quiet splash
grub-efi-amd64 grub2/kfreebsd_
grub-efi-amd64 grub-efi/
grub-efi-amd64 grub2/force_
grub-efi-amd64 grub2/linux_
grub-efi-amd64 grub2/update_nvram boolean true
grub-efi-amd64 grub2/linux_cmdline string
grub-efi-amd64 grub2/unsigned_
grub-efi-amd64 grub2/no_
grub-efi-amd64 grub2/device_
grub-efi-amd64 grub-efi/
grub-efi-amd64 grub-efi/
grub-efi-amd64 grub-efi/
grub-efi-amd64 grub2/kfreebsd_
Note that it detected the new, correct "/dev/disk/ by-id/ata- VBOX_HARDDISK_ VB1-1a2b3c4d- part1" UUID of the disk that contains the EFI partition.
I debugged it further and can see that the following happens in /usr/lib/ grub/grub- multi-install (which is part of grub-common package): devices_ disks_changed" prompt should be triggered, but it is not. install_ devices
1) in "# We either migrate /boot/efi over, or we check if we have invalid devices" section, it correctly detects that the Parallels device does not exist ("if [ ! -e "${device%,}" ]", setting the valid=0
2) given that valid=0, my understanding is that at this point the "install_
3) the "$RET" variable still contains both of the disks from grub-efi/
4) in "# Run the installer" section, the script iterates over each of the disks, attempting to mount ("mount $real_device $mntpoint) the non-existing one, which results in the aforementioned script failure.
My understanding here is that there are two problems: devices_ disks_changed" prompt was not shown
1) "install_
2) there's no check for whether the device exists at all before the script proceeds with mounting and grub-installation attempt