I have same issue. I have configured unattended-upgrades. I have been started receive error mail from Fri, 28 Oct 2022. some instances have same issue. KVM/QEMU + Libvirt environment. I launch instance using following cloud image. https://cloud-images.ubuntu.com/focal/current/focal-server-cloudimg-amd64.img launch server minimal configuration(without virtual cdrom drive). ``` [example.com:~ 2022-10-28 13:56:06]$ ssh example.com Welcome to Ubuntu 20.04.5 LTS (GNU/Linux 5.4.0-131-generic x86_64) * Documentation: https://help.ubuntu.com * Management: https://landscape.canonical.com * Support: https://ubuntu.com/advantage System information as of Fri Oct 28 13:56:11 JST 2022 System load: 0.0 Processes: 180 Usage of /: 22.2% of 19.20GB Users logged in: 0 Memory usage: 28% IPv4 address for enp2s0: x.x.x.x Swap usage: 0% IPv4 address for enp3s0: y.y.y.y * Super-optimized for small spaces - read how we shrank the memory footprint of MicroK8s to make it the smallest full K8s around. https://ubuntu.com/blog/microk8s-memory-optimisation 3 updates can be applied immediately. 3 of these updates are standard security updates. To see these additional updates run: apt list --upgradable Last login: Fri Oct 14 16:39:06 2022 from 10.1.2.200 server:~$ ``` ``` server:~$ sudo less /var/log/unattended-upgrades/unattended-upgrades-dpkg.log Unpacking grub-efi-amd64-signed (1.173.2~20.04.1+2.04-1ubuntu47.4) over (1.167.2+2.04-1ubuntu44.2) ... Preparing to unpack .../grub-efi-amd64-bin_2.04-1ubuntu47.4_amd64.deb ... Unpacking grub-efi-amd64-bin (2.04-1ubuntu47.4) over (2.04-1ubuntu44.2) ... Setting up grub-efi-amd64-bin (2.04-1ubuntu47.4) ... Setting up grub-efi-amd64-signed (1.173.2~20.04.1+2.04-1ubuntu47.4) ... Unknown device "/dev/disk/by-id/*": No such file or directory dpkg: error processing package grub-efi-amd64-signed (--configure): installed grub-efi-amd64-signed package post-installation script subprocess returned error exit status 1 Errors were encountered while processing: grub-efi-amd64-signed Log ended: 2022-10-28 06:16:38 ``` It indicates /dev/disk/by-id/ is missing. ``` [example.com:~ 2022-10-28 14:12:30]$ ssh example.com ls -l /dev/disk/ total 0 drwxr-xr-x 2 root root 80 Oct 20 03:44 by-label drwxr-xr-x 2 root root 100 Oct 20 03:44 by-partuuid drwxr-xr-x 2 root root 280 Oct 20 03:44 by-path drwxr-xr-x 2 root root 120 Oct 20 03:44 by-uuid server:~$ ls -l /dev/disk/by-id/ ls: cannot access '/dev/disk/by-id/': No such file or directory server:~$ ``` ``` [example.com:~ 2022-11-08 00:42:33]$ cat /etc/lsb-release DISTRIB_ID=Ubuntu DISTRIB_RELEASE=20.04 DISTRIB_CODENAME=focal DISTRIB_DESCRIPTION="Ubuntu 20.04.5 LTS" [example.com:~ 2022-11-08 00:42:46]$ df -hT Filesystem Type Size Used Avail Use% Mounted on udev devtmpfs 7.8G 0 7.8G 0% /dev tmpfs tmpfs 1.6G 1.2M 1.6G 1% /run /dev/vda1 ext4 993G 200G 793G 21% / tmpfs tmpfs 7.9G 516K 7.9G 1% /dev/shm tmpfs tmpfs 5.0M 0 5.0M 0% /run/lock tmpfs tmpfs 7.9G 0 7.9G 0% /sys/fs/cgroup /dev/loop2 squashfs 56M 56M 0 100% /snap/core18/2566 /dev/vda15 vfat 105M 5.2M 100M 5% /boot/efi /dev/loop4 squashfs 68M 68M 0 100% /snap/lxd/22526 /dev/loop3 squashfs 64M 64M 0 100% /snap/core20/1623 /dev/loop5 squashfs 68M 68M 0 100% /snap/lxd/22753 /dev/loop7 squashfs 48M 48M 0 100% /snap/snapd/17029 /dev/loop8 squashfs 48M 48M 0 100% /snap/snapd/17336 /dev/loop6 squashfs 64M 64M 0 100% /snap/core20/1634 /dev/loop1 squashfs 56M 56M 0 100% /snap/core18/2620 tmpfs tmpfs 1.6G 0 1.6G 0% /run/user/1000 tmpfs tmpfs 1.6G 0 1.6G 0% /run/user/995 [example.com:~ 2022-11-08 00:42:50]$ ls -l /dev/disk/by-id/ ls: cannot access '/dev/disk/by-id/': No such file or directory [example.com:~ 2022-11-08 00:45:35]$ [example.com:~ 2022-11-08 00:48:47]$ sudo sfdisk -l /dev/vda Disk /dev/vda: 1 TiB, 1099511627776 bytes, 2147483648 sectors Units: sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 512 bytes I/O size (minimum/optimal): 512 bytes / 512 bytes Disklabel type: gpt Disk identifier: 9CEB264D-ECC9-413C-A6DC-180FA42C5342 Device Start End Sectors Size Type /dev/vda1 227328 2147483614 2147256287 1023.9G Linux filesystem /dev/vda14 2048 10239 8192 4M BIOS boot /dev/vda15 10240 227327 217088 106M EFI System Partition table entries are not in disk order. [example.com:~ 2022-11-08 00:48:49]$ ``` Exactly /dev/disk/by-id/ directory is missing. Update successful instances have /dev/disk/by-id/ directory and device entry. - `grub-efi-amd64-signed` package - `/dev/disk/by-id/` is missing - Ubuntu 20.04 LTS So, I injected virtual CD-ROM Drive and reboot instance. Next boot time /dev/disk/by-id/ is created. ``` [example.com:~ 2022-11-08 02:29:38]$ ls -l /dev/disk/by-id/ total 0 lrwxrwxrwx 1 root root 9 Nov 8 02:28 ata-QEMU_DVD-ROM_QM00001 -> ../../sr0 ``` but apt upgrade still fails onother error. ``` Setting up libdbus-1-3:amd64 (1.12.16-2ubuntu2.3) ... Setting up dbus (1.12.16-2ubuntu2.3) ... A reboot is required to replace the running dbus-daemon. Please reboot the system when convenient. Setting up containerd.io (1.6.9-1) ... Setting up libroken18-heimdal:amd64 (7.7.0+dfsg-1ubuntu1.1) ... Setting up sosreport (4.4-1ubuntu0.20.04.1) ... Setting up zlib1g-dev:amd64 (1:1.2.11.dfsg-2ubuntu1.5) ... Setting up docker-ce-cli (5:20.10.21~3-0~ubuntu-focal) ... Setting up libperl5.30:amd64 (5.30.0-9ubuntu0.3) ... Setting up libcurl4:amd64 (7.68.0-1ubuntu2.14) ... Setting up git-man (1:2.25.1-1ubuntu3.6) ... Setting up curl (7.68.0-1ubuntu2.14) ... Setting up ubuntu-advantage-tools (27.11.3~20.04.1) ... Installing new version of config file /etc/apt/apt.conf.d/20apt-esm-hook.conf ... Setting up linux-modules-5.4.0-131-generic (5.4.0-131.147) ... Setting up grub-efi-amd64-bin (2.04-1ubuntu47.4) ... Setting up libheimbase1-heimdal:amd64 (7.7.0+dfsg-1ubuntu1.1) ... Setting up linux-headers-5.4.0-131-generic (5.4.0-131.147) ... Setting up linux-image-5.4.0-131-generic (5.4.0-131.147) ... I: /boot/vmlinuz.old is now a symlink to vmlinuz-5.4.0-128-generic I: /boot/initrd.img.old is now a symlink to initrd.img-5.4.0-128-generic I: /boot/vmlinuz is now a symlink to vmlinuz-5.4.0-131-generic I: /boot/initrd.img is now a symlink to initrd.img-5.4.0-131-generic Setting up grub-efi-amd64-signed (1.173.2~20.04.1+2.04-1ubuntu47.4) ... mount: /var/lib/grub/esp: special device /dev/disk/by-id/virtio-bdd63d32-fc83-443b-9-part15 does not exist. dpkg: error processing package grub-efi-amd64-signed (--configure): installed grub-efi-amd64-signed package post-installation script subprocess returned error exit status 32 Setting up libasn1-8-heimdal:amd64 (7.7.0+dfsg-1ubuntu1.1) ... Setting up libfwupd2:amd64 (1.7.9-1~20.04.1) ... Setting up linux-headers-generic (5.4.0.131.131) ... Setting up libhcrypto4-heimdal:amd64 (7.7.0+dfsg-1ubuntu1.1) ... Setting up dbus-user-session (1.12.16-2ubuntu2.3) ... Setting up perl (5.30.0-9ubuntu0.3) ... Setting up libwind0-heimdal:amd64 (7.7.0+dfsg-1ubuntu1.1) ... Setting up docker-ce (5:20.10.21~3-0~ubuntu-focal) ... Setting up git (1:2.25.1-1ubuntu3.6) ... Setting up docker-ce-rootless-extras (5:20.10.21~3-0~ubuntu-focal) ... Setting up linux-image-virtual (5.4.0.131.131) ... Setting up libfwupdplugin5:amd64 (1.7.9-1~20.04.1) ... Setting up fwupd (1.7.9-1~20.04.1) ... Installing new version of config file /etc/fwupd/redfish.conf ... fwupd-offline-update.service is a disabled or a static unit not running, not starting it. fwupd-refresh.service is a disabled or a static unit not running, not starting it. fwupd.service is a disabled or a static unit not running, not starting it. Setting up snapd (2.57.5+20.04) ... Created symlink /etc/systemd/system/multi-user.target.wants/snapd.aa-prompt-listener.service → /lib/systemd/system/snapd.aa-prompt-listener.service. snapd.failure.service is a disabled or a static unit not running, not starting it. snapd.snap-repair.service is a disabled or a static unit not running, not starting it. Setting up linux-headers-virtual (5.4.0.131.131) ... Setting up libhx509-5-heimdal:amd64 (7.7.0+dfsg-1ubuntu1.1) ... Setting up linux-virtual (5.4.0.131.131) ... Setting up libkrb5-26-heimdal:amd64 (7.7.0+dfsg-1ubuntu1.1) ... Setting up libheimntlm0-heimdal:amd64 (7.7.0+dfsg-1ubuntu1.1) ... Setting up libgssapi3-heimdal:amd64 (7.7.0+dfsg-1ubuntu1.1) ... Processing triggers for initramfs-tools (0.136ubuntu6.7) ... update-initramfs: Generating /boot/initrd.img-5.4.0-128-generic I: The initramfs will attempt to resume from /dev/vdb I: (UUID=b46c31b1-d588-4c7b-9def-09ba965c8fd1) I: Set the RESUME variable to override this. Processing triggers for libc-bin (2.31-0ubuntu9.9) ... Processing triggers for systemd (245.4-4ubuntu3.18) ... Processing triggers for man-db (2.9.1-1) ... Processing triggers for mime-support (3.64ubuntu1) ... Processing triggers for linux-image-5.4.0-131-generic (5.4.0-131.147) ... /etc/kernel/postinst.d/initramfs-tools: update-initramfs: Generating /boot/initrd.img-5.4.0-131-generic I: The initramfs will attempt to resume from /dev/vdb I: (UUID=b46c31b1-d588-4c7b-9def-09ba965c8fd1) I: Set the RESUME variable to override this. /etc/kernel/postinst.d/zz-update-grub: Sourcing file `/etc/default/grub' Sourcing file `/etc/default/grub.d/50-cloudimg-settings.cfg' Sourcing file `/etc/default/grub.d/init-select.cfg' Generating grub configuration file ... Found linux image: /boot/vmlinuz-5.4.0-131-generic Found initrd image: /boot/initrd.img-5.4.0-131-generic Found linux image: /boot/vmlinuz-5.4.0-128-generic Found initrd image: /boot/initrd.img-5.4.0-128-generic Found linux image: /boot/vmlinuz-5.4.0-125-generic Found initrd image: /boot/initrd.img-5.4.0-125-generic done Errors were encountered while processing: grub-efi-amd64-signed E: Sub-process /usr/bin/dpkg returned an error code (1) ``` ``` [example.com:~ 2022-11-10 05:38:00]$ sudo apt upgrade Reading package lists... Done Building dependency tree Reading state information... Done Calculating upgrade... Done The following packages were automatically installed and are no longer required: linux-headers-5.4.0-125 linux-headers-5.4.0-125-generic linux-image-5.4.0-125-generic linux-modules-5.4.0-125-generic Use 'sudo apt autoremove' to remove them. # # News about significant security updates, features and services will # appear here to raise awareness and perhaps tease /r/Linux ;) # Use 'pro config set apt_news=false' to hide this and future APT news. # 0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded. 1 not fully installed or removed. After this operation, 0 B of additional disk space will be used. Do you want to continue? [Y/n] Setting up grub-efi-amd64-signed (1.173.2~20.04.1+2.04-1ubuntu47.4) ... mount: /var/lib/grub/esp: special device /dev/disk/by-id/virtio-bdd63d32-fc83-443b-9-part15 does not exist. dpkg: error processing package grub-efi-amd64-signed (--configure): installed grub-efi-amd64-signed package post-installation script subprocess returned error exit status 32 Errors were encountered while processing: grub-efi-amd64-signed E: Sub-process /usr/bin/dpkg returned an error code (1) [example.com:~ 2022-11-10 05:39:45]$ ``` I've giving up fix this issue. Any ideas? Thanks, Wataru