grub-efi-amd64-signed not recognizing drives

Bug #1872889 reported by Nicholas Sharp
14
This bug affects 3 people
Affects Status Importance Assigned to Milestone
grub2-signed (Ubuntu)
Confirmed
Undecided
Unassigned

Bug Description

Ubuntu 20.04 (updated to 4-14 from daily build 4-11
grub-efi-amd64-signed: 1.141+2.04-1ubuntu25

Details: So, here's the issue. I just did a dist-upgrade (apt) and got a pop up stating that the device grub was installed on was not available. It only listed the EFI partition. After selecting the partition, I looked at the verbose log. Here's the output from that:

Setting up grub-efi-amd64-signed (1.141+2.04-1ubuntu25) ...
Unknown device "/dev/": Inappropriate ioctl for device
Unknown device "/dev/": Inappropriate ioctl for device
Unknown device "/dev/": Inappropriate ioctl for device
Unknown device "/dev/": Inappropriate ioctl for device
Installing grub to /boot/efi.
Installing for x86_64-efi platform.
Installation finished. No error reported.

Grub was previously installed to /dev/sda. If you need more info, please let me know.

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: grub-efi-amd64-signed 1.141+2.04-1ubuntu25
ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27
Uname: Linux 5.4.0-21-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion: 2.20.11-0ubuntu26
Architecture: amd64
CasperMD5CheckResult: skip
CurrentDesktop: Budgie:GNOME
Date: Tue Apr 14 23:22:28 2020
InstallationDate: Installed on 2020-04-12 (2 days ago)
InstallationMedia: Ubuntu-Budgie 20.04 LTS "Focal Fossa" - Beta amd64 (20200411)
SourcePackage: grub2-signed
UpgradeStatus: No upgrade log present (probably fresh install)

Revision history for this message
Nicholas Sharp (nsharpent) wrote :
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
Nicholas Sharp (nsharpent) wrote :

Just for prosperity, the fix in bug 1872077 has fixed this problem.

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.