Error in fresh install of Ubuntu 20.10 package grub-efi-amd64-signed 1.155.1+2.04-1ubuntu35.1 failed

Bug #1905522 reported by Dan
192
This bug affects 42 people
Affects Status Importance Assigned to Milestone
grub2-signed (Ubuntu)
Confirmed
Undecided
Unassigned

Bug Description

I was making a fresh install of Ubuntu 20.10 (dual boot with Windows) and, at the final stage, got an error that package grub-efi-amd64-signed 1.155.1+2.04-1ubuntu35.1 failed to install/upgrade: installed grub-efi-amd64-signed package post-installation script subprocess returned error exit status 1

Ubuntu did boot successfully after installing.

ProblemType: Package
DistroRelease: Ubuntu 20.10
Package: grub-efi-amd64-signed 1.155.1+2.04-1ubuntu35.1
ProcVersionSignature: Ubuntu 5.8.0-29.31-generic 5.8.14
Uname: Linux 5.8.0-29-generic x86_64
ApportVersion: 2.20.11-0ubuntu50
Architecture: amd64
CasperMD5CheckResult: skip
Date: Wed Nov 25 07:14:02 2020
ErrorMessage: installed grub-efi-amd64-signed package post-installation script subprocess returned error exit status 1
InstallationDate: Installed on 2020-11-25 (0 days ago)
InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022)
Python3Details: /usr/bin/python3.8, Python 3.8.6, python3-minimal, 3.8.6-0ubuntu1
PythonDetails: N/A
RelatedPackageVersions:
 dpkg 1.20.5ubuntu2
 apt 2.1.10
SourcePackage: grub2-signed
Title: package grub-efi-amd64-signed 1.155.1+2.04-1ubuntu35.1 failed to install/upgrade: installed grub-efi-amd64-signed package post-installation script subprocess returned error exit status 1
UpgradeStatus: No upgrade log present (probably fresh install)

Revision history for this message
Dan (dleggate) wrote :
tags: removed: need-duplicate-check
Revision history for this message
Launchpad Janitor (janitor) wrote :

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

Changed in grub2-signed (Ubuntu):
status: New → Confirmed
Revision history for this message
rud (jazco) wrote :

Is there a workaround?

Revision history for this message
Carl B. (carlb) wrote :

I'm seeing something similar on an ASUS desktop PC (AMD socket FM2, DDR3) which already has a few dual-boot options installed. I'm trying to install groovy 20.10 using Ubiquity from the live CD/DVD/USB. The installer goes through most of its paces, until it tries to install GRUB. It then dies with a pop-up box:

Error installing grub-efi-amd64-signed

installed grub-efi-amd64-signed package post-installation script subprocess returned error exit status 1

Attempting to install the package manually from a live desktop terminal window also fails, with:

$ sudo su -
# chroot /target
# apt install grub-efi-amd64

giving:

Setting up grub-efi-amd64 (2.04-1ubuntu35.1) ...
Installing grub to /boot/efi.
Installing for x86_64-efi platform.
grub-install: warning: Cannot read EFI Boot* variables.
grub-install: warning: read_file: could not read from file: Input/output error.
grub-install: warning: vars_get_variable: read_file(/sys/firmware/efi/vars/Boot000C-8be4df61-93ca-11d2-aa0d-00e098032b8c/raw_var) failed
: Input/output error.
grub-install: warning: efi_get_variable: ops->get_variable failed: Input/output error.
grub-install: error: failed to register the EFI boot entry: Input/output error.

The workaround seems to be, while the installer is stopped at the error message box but still open, launching a terminal window from the live desktop and mounting efivarfs manually. At that point, apt may be used to install the package, install grub, apt upgrade everything to the current release... whatever.

 sudo su -
 chroot /mount/target
 sh -c "mount -t efivarfs efivarfs /sys/firmware/efi/efivars; grub-install; update-grub;
 apt install --reinstall grub-efi-amd64-signed

After that, I was able to reboot into Ubuntu 20.10 (groovy) from the internal SSD.

Without that, I could try the installer any number of times and it would always fail the same way.

bugs.debian.org/cgi-bin/bugreport.cgi?bug=933523 looks to be related

bugs.launchpad.net/ubuntu/+source/grub2-signed/+bug/1874315 might be as well?

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.