grub-install: error: cannot find EFI directory. package shim-signed 1.12+0.8-0ubuntu2 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1

[telseth]

Setting up shim-signed (1.12+0.8-0ubuntu2) ...
Installing for x86_64-efi platform.
grub-install: error: cannot find EFI directory.
dpkg: error processing package shim-signed (--configure):
 subprocess installed post-installation script returned error exit status 1
Errors were encountered while processing:
 shim-signed

ProblemType: Package
DistroRelease: Ubuntu 16.04
Package: shim-signed 1.12+0.8-0ubuntu2
ProcVersionSignature: Ubuntu 4.2.0-35.40-generic 4.2.8-ckt5
Uname: Linux 4.2.0-35-generic x86_64
ApportVersion: 2.20.1-0ubuntu2
Architecture: amd64
BootEFIContents:
 fw
 fwupx64.efi
Date: Sat Apr 23 08:57:34 2016
ErrorMessage: subprocess installed post-installation script returned error exit status 1
InstallationDate: Installed on 2014-12-17 (493 days ago)
InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Release amd64 (20141022.1)
RelatedPackageVersions:
 dpkg 1.18.4ubuntu1
 apt 1.2.10ubuntu1
SourcePackage: shim-signed
Title: package shim-signed 1.12+0.8-0ubuntu2 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1
UpgradeStatus: Upgraded to xenial on 2016-04-23 (0 days ago)

[Launchpad Janitor (janitor)]

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

[Steve Langasek (vorlon)]

Your bug report shows that you are running on a UEFI system (efibootmgr runs successfully); you previously had Ubuntu 15.10 installed, with all the corresponding UEFI bootloader packages having been installed without problems; and your ESP (EFI system partition) is not mounted at /boot/efi.

So why is /boot/efi not mounted on your system?

[Baruch (baruch-n)]

Not sure how to answer this.

The system worked before mis-fortunately pressing upgrade to 16.04
what happened next was done by the installer and packages so as a user there is very little to do about this.

Anyway here is how my "du /boot" looks like:

4 /boot/efi/EFI/ubuntu/fw
72 /boot/efi/EFI/ubuntu
76 /boot/efi/EFI
80 /boot/efi
3284 /boot/grub/x86_64-efi
2352 /boot/grub/fonts
20 /boot/grub/locale
8080 /boot/grub
166988 /boot

[Steve Langasek (vorlon)]

Baruch, you are not the submitter of this bug. I have no information about what's happening on your system. Why do you believe that you have the same issue? It would be best if you filed a separate bug report.

[Baruch (baruch-n)]

Hi Steve,
Just wanted to avoid duplicates..
Any way' seems very similar, started after upgrade to 16.04 from a working 15.10
Same errors,

Cant work with the system.

Any help will be appreciated..

Thanks

[Steve Langasek (vorlon)]

On Tue, Apr 26, 2016 at 05:11:04PM -0000, Baruch wrote:
> Just wanted to avoid duplicates..
> Any way' seems very similar, started after upgrade to 16.04 from a working 15.10
> Same errors,

Please file a separate bug report with attached logs from your system.

[Baruch (baruch-n)]

opened another report #1575305 https://bugs.launchpad.net/ubuntu/+source/shim-signed/+bug/1575305

I'll try to switch over to the broken system and find logs to send.

Anything in particular?

[Eric Zimmerman (eric-zimtek)]

I get exact same behavior as reporter...and exact same du /boot as baruch reported above. Not sure why this needs separate bug reports for same issue.

[Steve Langasek (vorlon)]

On Thu, May 05, 2016 at 11:38:19PM -0000, Eric Zimmerman wrote:
> I get exact same behavior as reporter...and exact same du /boot as
> baruch reported above. Not sure why this needs separate bug reports for
> same issue.

Because you don't know that it's the same issue. This bug has been marked
incomplete, as it is still awaiting input from the submitter. Whereas
Baruch's bug has been marked as invalid. We can assume that your bug report
is also invalid, but that probably wouldn't help you very much?

[Baruch (baruch-n)]

FYI, I just gave up and changed system. (still some of the functionality is lost)

I assume that the problem is the same (or very similar) and is related to miss-understanding the current hardware configuration by grub or some other configuration program.

The solution would probably be to copy whatever is one the old system working so the change will be from an old working system to a new working system. Breaking the boot should be prevented as first priority.

Only after the system boots properly the installer may offer improved (but risky) boot options.

In short: don't break the computer when doing upgrades.

[R (rprots)]

http://askubuntu.com/a/763984 workaround helped.

[Launchpad Janitor (janitor)]

[Expired for shim-signed (Ubuntu) because there has been no activity for 60 days.]