package grub-efi-amd64-signed 1.187.6~20.04.1+2.06-2ubuntu14.4 failed to install/upgrade: installed grub-efi-amd64-signed package post-installation script subprocess returned error exit status 32
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
grub2-signed (Ubuntu) |
Confirmed
|
Undecided
|
Unassigned |
Bug Description
Crashed my system, couldn't find the OS to boot. Had to reinstall from an image.
ProblemType: Package
DistroRelease: Ubuntu 20.04
Package: grub-efi-
ProcVersionSign
Uname: Linux 5.15.0-78-generic x86_64
ApportVersion: 2.20.11-
AptOrdering:
grub-efi-
grub-efi-
NULL: ConfigurePending
Architecture: amd64
CasperMD5CheckR
Date: Sat Dec 23 22:19:19 2023
DuplicateSignature:
package:
Setting up grub-efi-
mount: /var/lib/grub/esp: special device /dev/disk/
dpkg: error processing package grub-efi-
installed grub-efi-
ErrorMessage: installed grub-efi-
InstallationDate: Installed on 2021-09-15 (829 days ago)
InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819)
Python3Details: /usr/bin/python3.8, Python 3.8.10, python3-minimal, 3.8.2-0ubuntu2
PythonDetails: N/A
RelatedPackageV
dpkg 1.19.7ubuntu3.2
apt 2.0.9
SourcePackage: grub2-signed
Title: package grub-efi-
UpgradeStatus: No upgrade log present (probably fresh install)
tags: | removed: need-duplicate-check |
Hello!
I believe the relevant line is this:
> mount: /var/lib/grub/esp: special device /dev/disk/ by-id/ata- T-FORCE_ 1TB_TPBF2104090 040102257- part1 does not exist.
Did you clone the Ubuntu installation to a different hard disk compared the one listed above? If not, would you be able to check what the device node for disk in `/dev/disl/by-id/` is currently called?
Unfortunately it seems we that we do not handle such scenarios gracefully enough at the moment, but
improvements to this mechanism are planned.