package grub-efi-amd64-signed 1.93.4+2.02-2ubuntu8.3 failed to install/upgrade: installed grub-efi-amd64-signed package post-installation script subprocess returned error exit status 1

[Aditya Gannavarapu]

Not able to perform terminal commands.

ProblemType: Package
DistroRelease: Ubuntu 18.04
Package: grub-efi-amd64-signed 1.93.4+2.02-2ubuntu8.3
ProcVersionSignature: Ubuntu 4.15.0-24.26-generic 4.15.18
Uname: Linux 4.15.0-24-generic x86_64
ApportVersion: 2.20.9-0ubuntu7.3
Architecture: amd64
Date: Sat Aug 18 09:51:42 2018
ErrorMessage: installed grub-efi-amd64-signed package post-installation script subprocess returned error exit status 1
InstallationDate: Installed on 2018-01-03 (226 days ago)
InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
Python3Details: /usr/bin/python3.6, Python 3.6.5, python3-minimal, 3.6.5-3ubuntu1
PythonDetails: /usr/bin/python2.7, Python 2.7.15rc1, python-minimal, 2.7.15~rc1-1
RelatedPackageVersions:
 dpkg 1.19.0.5ubuntu2
 apt 1.6.3
SourcePackage: grub2-signed
Title: package grub-efi-amd64-signed 1.93.4+2.02-2ubuntu8.3 failed to install/upgrade: installed grub-efi-amd64-signed package post-installation script subprocess returned error exit status 1
UpgradeStatus: Upgraded to bionic on 2018-05-23 (86 days ago)

[Launchpad Janitor (janitor)]

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

[oldfred (oldfred)]

May be related to this bug.
https://bugs.launchpad.net/ubuntu/+source/grub2-signed/+bug/1753518

[oldfred (oldfred)]

I have been booting with the same version of UEFI from Asus since April.
But now either UEFI or Ubuntu is deleting all UEFI entries and creating multiple new UEFI entries from boot device.

I was having issue of UEFI entry not installing at all.
fred@bionic-z97:~$ sudo grub-install --bootloader-id ubuntu /dev/sda --recheck
Installing for x86_64-efi platform.
Could not prepare Boot variable: No space left on device
grub-install: error: efibootmgr failed to register the boot entry: Input/output error.

I have to boot full install on flash drive and use configfile to boot into working install in sda.
But something is adding entries from flash drive's ESP. And on reboot added a second BIOS/grub entry (which is not used)

I can see UEFI entries come from flash drive as it has extra bionic & copy folders.
I was then able to add an entry for working install on sda, but reboot erased it.

After boot with efi_not_storage_paranoia
And reset of UEFI to defaults & changing back to my preferred settings
fred@bionic-z97:/media/fred/ESP_USB/EFI$ ll
total 24
drwxr-xr-x 6 fred fred 4096 Apr 4 15:34 ./
drwxr-xr-x 4 fred fred 4096 Dec 31 1969 ../
drwxr-xr-x 3 fred fred 4096 Mar 10 17:47 bionic/
drwxr-xr-x 2 fred fred 4096 Apr 21 09:36 Boot/
drwxr-xr-x 3 fred fred 4096 Apr 21 09:37 ubuntu/
drwxr-xr-x 3 fred fred 4096 Apr 2 12:43 'ubuntu (copy)'/
fred@bionic-z97:/media/fred/ESP_USB/EFI$ sudo efibootmgr -v -c -L ubuntu -l \\EFI\\ubuntu\\shimx64.efi
efibootmgr: Warning : Boot0000 has same label ubuntu
efibootmgr: Warning : Boot0001 has same label ubuntu
efibootmgr: Warning : Boot0002 has same label ubuntu
efibootmgr: Warning : Boot0003 has same label ubuntu
BootCurrent: 0004
Timeout: 1 seconds
BootOrder: 0005,0002,0001,0000,0004,0003
Boot0000* ubuntu HD(1,GPT,2a6f47aa-0ae8-42e3-86d8-6463449b2862,0x800,0xfa000)/File(\EFI\ubuntu\shimx64.efi)
Boot0001* ubuntu HD(1,GPT,2a6f47aa-0ae8-42e3-86d8-6463449b2862,0x800,0xfa000)/File(\EFI\bionic\shimx64.efi)
Boot0002* ubuntu HD(1,GPT,2a6f47aa-0ae8-42e3-86d8-6463449b2862,0x800,0xfa000)/File(\EFI\ubuntu (copy)\shimx64.efi)
Boot0003* ubuntu VenHw(99e275e7-75a0-4b37-a2e6-c5385e6c00cb)
Boot0004* UEFI: (FAT) PciRoot(0x0)/Pci(0x1d,0x0)/USB(1,0)/USB(5,0)/HD(1,GPT,2a6f47aa-0ae8-42e3-86d8-6463449b2862,0x800,0xfa000)..BO
Boot0005* ubuntu HD(1,GPT,3195d314-ce88-42ac-beac-d9f80289ac11,0x800,0xf9dcd)/File(\EFI\ubuntu\shimx64.efi)

fred@bionic-z97:~$ sudo efibootmgr -v
[sudo] password for fred:
BootCurrent: 0002
Timeout: 1 seconds
BootOrder: 0002,0001,0000,0004,0005,0003
Boot0000* ubuntu HD(1,GPT,2a6f47aa-0ae8-42e3-86d8-6463449b2862,0x800,0xfa000)/File(\EFI\ubuntu\shimx64.efi)
Boot0001* ubuntu HD(1,GPT,2a6f47aa-0ae8-42e3-86d8-6463449b2862,0x800,0xfa000)/File(\EFI\bionic\shimx64.efi)
Boot0002* ubuntu HD(1,GPT,2a6f47aa-0ae8-42e3-86d8-6463449b2862,0x800,0xfa000)/File(\EFI\ubuntu (copy)\shimx64.efi)
Boot0003* ubuntu VenHw(99e275e7-75a0-4b37-a2e6-c5385e6c00cb)
Boot0004* UEFI: (FAT) PciRoot(0x0)/Pci(0x14,0x0)/USB(9,0)/HD(1,GPT,2a6f47aa-0ae8-42e3-86d8-6463449b2862,0x800,0xfa000)..BO
Boot0005* ubuntu VenHw(99e275e7-75a0-4b37-a2e6-c5385e6c00cb)

[[e-mail] (rpalmer47)]

It claims that a Firewall may be preventing me from getting email.

[oldfred (oldfred)]

Resolved my boot issue, I think. Errors on FAT32 ESP, my sda1.

Issue started with no space left on device.
Then I would add new UEFI boot entry for sda's ESP for 18.04, but on reboot UEFI would not use it, erased it and entries for all the .efi possibilities were added from boot device, my sdc.

Not sure if all fixes required, perhaps it originally was originally error corrupted fat32 ESP. But that error would keep appearing on reboot.

Reinstalled Asus UEFI, same version as one used since April 2018.
Unplugged all drives to get UEFI to reset, removed all entries from UEFI with efibootmgr.
Added UEFI boot entry for 18.04 using efibootmgr to to boot from sda1.
Every reboot, erased entry to boot sda, and only booted with rEFInd on sdc or external drive.
Ran fsck.vfat and it cleared error bit saying it may have not been umounted correctly. It is mounted with fstab in sda's install.
On reboot same issue, all UEFI entries for sda missing, and fsck.vfat showed error bit. I believe that is why UEFI would not use my sda1, ESP for booting.

Using another install so sda1, ESP not mounted.
Then totally reformatted sda1 using command line, mkfs, not gparted.
Updated ESP/efi entry in fstab in Ubuntu 18.04 install with new UUID.
Totally uninstalled & reinstalled grub signed version.
System now boots from ESP on sda again.