package grub-efi-amd64-signed 1.180+2.06-2ubuntu7 failed to install/upgrade: installed grub-efi-amd64-signed package post-installation script subprocess returned error exit status 32

[Jonas]

Did a do-dist-upgrade and this error came up

ProblemType: Package
DistroRelease: Ubuntu 22.04
Package: grub-efi-amd64-signed 1.180+2.06-2ubuntu7
ProcVersionSignature: Ubuntu 5.13.0-40.45-generic 5.13.19
Uname: Linux 5.13.0-40-generic x86_64
ApportVersion: 2.20.11-0ubuntu82
Architecture: amd64
CasperMD5CheckResult: unknown
Date: Sun May 1 01:40:04 2022
DuplicateSignature:
 package:grub-efi-amd64-signed:1.180+2.06-2ubuntu7
 Setting up grub-efi-amd64-signed (1.180+2.06-2ubuntu7) ...
 mount: /var/lib/grub/esp: special device /dev/sda15 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
ErrorMessage: installed grub-efi-amd64-signed package post-installation script subprocess returned error exit status 32
Python3Details: /usr/bin/python3.10, Python 3.10.4, python3-minimal, 3.10.4-0ubuntu2
PythonDetails: N/A
RebootRequiredPkgs: Error: path contained symlinks.
RelatedPackageVersions:
 dpkg 1.21.1ubuntu2
 apt 2.4.5
SourcePackage: grub2-signed
Title: package grub-efi-amd64-signed 1.180+2.06-2ubuntu7 failed to install/upgrade: installed grub-efi-amd64-signed package post-installation script subprocess returned error exit status 32
UpgradeStatus: Upgraded to jammy on 2022-04-30 (0 days ago)

[Launchpad Janitor (janitor)]

Status changed to 'Confirmed' because the bug affects multiple users.

[Christian Merges (christianmerges)]

My Server is not using efi boot i resolved this by this command:
apt remove shim-signed grub-efi-amd64-bin --allow-remove-essential

[Jonas (jonas-thiele-eisele)]

Thank you, this fixed my issue.
I wonder why they were installed though.

[Bernd Wahlen (qeepcologne)]

i had the same issue upgrading jammy to kinetic on a sofware-raid.

Setting up grub-efi-amd64-signed (1.185+2.06-2ubuntu12) ...^M
mount: /var/lib/grub/esp: special device /dev/sda15 does not exist.^M

Efi is not used and using only grub-pc + remove grub-efi-amd64-bin is working, but the package is installed + not causing this error message with the older version provided in ubuntu22.04. Installation is from hetzner standard image.

I also was scared that grub-emu return errors, i think it is also not working with software-raid.

[Bernd Wahlen (qeepcologne)]

with the latest update, same issue now on 22.04 also: (1.182~22.04.1+2.06-2ubuntu10)

[Steve Langasek (vorlon)]

This partition was created at install time because it is impossible to determine from a CD image booted at install time in BIOS mode whether the system will boot in BIOS mode from an internal disk. We therefore always install BIOS and EFI bootloaders both, when installing on x86.

You have forcibly removed the partition that was created at install time (the partition that grub2-efi-amd64-signed knew it had installed to previously and should update on upgrades). The package then quite reasonably refuses to upgrade since it can't find the target disk to actually install to. That is not a bug in the package.

[Mike Damm (e-mike-u)]

Why is this being marked invalid because of someone else’s random comment?

The issue is /boot filling up. Cleaning up old kernels as a pre-install step would resolve this.

On Mon, Oct 31, 2022, at 5:47 PM, Steve Langasek wrote:
> This partition was created at install time because it is impossible to
> determine from a CD image booted at install time in BIOS mode whether
> the system will boot in BIOS mode from an internal disk. We therefore
> always install BIOS and EFI bootloaders both, when installing on x86.
>
> You have forcibly removed the partition that was created at install time
> (the partition that grub2-efi-amd64-signed knew it had installed to
> previously and should update on upgrades). The package then quite
> reasonably refuses to upgrade since it can't find the target disk to
> actually install to. That is not a bug in the package.
>
> ** Changed in: grub2-signed (Ubuntu)
> Status: Confirmed => Invalid
>
> --
> You received this bug notification because you are subscribed to a
> duplicate bug report (1989300).
> https://bugs.launchpad.net/bugs/1971059
>
> Title:
> package grub-efi-amd64-signed 1.180+2.06-2ubuntu7 failed to
> install/upgrade: installed grub-efi-amd64-signed package post-
> installation script subprocess returned error exit status 32
>
> Status in grub2-signed package in Ubuntu:
> Invalid
>
> Bug description:
> Did a do-dist-upgrade and this error came up
>
> ProblemType: Package
> DistroRelease: Ubuntu 22.04
> Package: grub-efi-amd64-signed 1.180+2.06-2ubuntu7
> ProcVersionSignature: Ubuntu 5.13.0-40.45-generic 5.13.19
> Uname: Linux 5.13.0-40-generic x86_64
> ApportVersion: 2.20.11-0ubuntu82
> Architecture: amd64
> CasperMD5CheckResult: unknown
> Date: Sun May 1 01:40:04 2022
> DuplicateSignature:
> package:grub-efi-amd64-signed:1.180+2.06-2ubuntu7
> Setting up grub-efi-amd64-signed (1.180+2.06-2ubuntu7) ...
> mount: /var/lib/grub/esp: special device /dev/sda15 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
> ErrorMessage: installed grub-efi-amd64-signed package
> post-installation script subprocess returned error exit status 32
> Python3Details: /usr/bin/python3.10, Python 3.10.4, python3-minimal,
> 3.10.4-0ubuntu2
> PythonDetails: N/A
> RebootRequiredPkgs: Error: path contained symlinks.
> RelatedPackageVersions:
> dpkg 1.21.1ubuntu2
> apt 2.4.5
> SourcePackage: grub2-signed
> Title: package grub-efi-amd64-signed 1.180+2.06-2ubuntu7 failed to
> install/upgrade: installed grub-efi-amd64-signed package
> post-installation script subprocess returned error exit status 32
> UpgradeStatus: Upgraded to jammy on 2022-04-30 (0 days ago)
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/ubuntu/+source/grub2-signed/+bug/1971059/+subscriptions

[Markku Tikkanen (matikka76)]

This happens in our env when installing a new system from scratch.
There are no sd[ab] devices installed (and hasn't ever been), only drives are /dev/nvme[01]n1. This system is also using bios boot, no EFI around.
Like said, removing shim-signed grub-efi-amd64-bin gets rid of the issue.
Boot partition is not filled up.