The error in your log is:
grub-install: error: attempt to install to encrypted disk without cryptodisk
enabled. Set `GRUB_ENABLE_CRYPTODISK=y' in file `/etc/default/grub'.
dpkg: error processing package shim-signed (--configure):
installed shim-signed package post-installation script subprocess returned
error exit status 1
Your attached df output confirms that you have a separate ESP mounted at
/boot/efi, but that your root is on a (presumably encrypted) LVM volume,
and you do not have a separate unencrypted /boot partition. The
question is, how did you only run into this error on upgrade? The
SecureBoot-signed EFI grub has never included cryptodisk support, which
means it would only ever boot if you had an unencrypted /boot since it
would be unable to read the kernel from the encrypted volume. I see
that your system has SecureBoot disabled, so that would not directly
block you from booting, however the error message in grub is also not
new so I don't understand how you got your system into such a state that
you are getting the error message on upgrade.
** Package changed: shim-signed (Ubuntu) => grub2 (Ubuntu)
** Changed in: grub2 (Ubuntu)
Status: New => Incomplete
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1780187
Title:
package shim-signed 1.34.9.1+13-0ubuntu2 failed to install/upgrade:
installed shim-signed package post-installation script subprocess
returned error exit status 1
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1780187/+subscriptions
--
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
