Comment 3 for bug 1780187

Hi Steve,

Thanks for your answer.

I don't know how my system got to this state, I'm just a user.

I simply installed Ubuntu 18.04 as a new system (no dual boot) on my
laptop computer and then copied relevant parts of my data back onto my
/home and /etc partition.

I do recall I had an issue because at one point I replaced /etc/fstab
with the one from my old installation so the system did not boot any longer.

I followed instructions I found somewhere (it might be
https://askubuntu.com/questions/83172/repairing-the-fstab, but I'm not
sure) to rebuild it, so maybe that's where things got out of hand...

Let me know if you need any further information.

Best regards,

Steven

On 05/07/2018 17:58, Steve Langasek wrote:
> 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
>