package shim-signed 1.6+0.4-0ubuntu4 failed to install/upgrade: ErrorMessage: subprocess installed post-installation script returned error exit status 1

[Robert Collins]

Upgrading a saucy fresh installed machine to trusty and boom :(.

ProblemType: Package
DistroRelease: Ubuntu 14.04
Package: shim-signed 1.6+0.4-0ubuntu4
ProcVersionSignature: Ubuntu 3.11.0-18.32-generic 3.11.10.4
Uname: Linux 3.11.0-18-generic x86_64
ApportVersion: 2.14-0ubuntu1
Architecture: amd64
Date: Tue Apr 1 22:52:13 2014
DuplicateSignature: package:shim-signed:1.6+0.4-0ubuntu4:ErrorMessage: subprocess installed post-installation script returned error exit status 1
ErrorMessage: ErrorMessage: subprocess installed post-installation script returned error exit status 1
InstallationDate: Installed on 2013-12-09 (113 days ago)
InstallationMedia: Ubuntu-Server 13.10 "Saucy Salamander" - Release amd64 (20131016)
SourcePackage: shim-signed
Title: package shim-signed 1.6+0.4-0ubuntu4 failed to install/upgrade: ErrorMessage: subprocess installed post-installation script returned error exit status 1
UpgradeStatus: Upgraded to trusty on 2014-04-01 (0 days ago)

[Robert Collins (lifeless)]

It seems to be looking for /boot/grub/x86_64-efi/load.cfg - a file that doesn't exist:

# apt-get upgrade
Reading package lists... Done
Building dependency tree
Reading state information... Done
Calculating upgrade... Done
The following packages were automatically installed and are no longer required:
  libamd2.2.0 libboost-iostreams1.53.0 libgee2 libkadm5clnt-mit8 libkadm5srv-mit8 libkdb5-6 libumfpack5.4.0 linux-headers-3.11.0-15
  linux-headers-3.11.0-15-generic linux-image-3.11.0-15-generic linux-image-extra-3.11.0-15-generic linux-signed-image-3.11.0-15-generic
Use 'apt-get autoremove' to remove them.
0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
3 not fully installed or removed.
After this operation, 0 B of additional disk space will be used.
Do you want to continue? [Y/n] y
Setting up grub-efi-amd64 (2.02~beta2-7) ...
Replacing config file /etc/default/grub with new version
Installing for x86_64-efi platform.
File descriptor 3 (pipe:[19279994]) leaked on vgs invocation. Parent PID 19829: grub-install
File descriptor 5 (/dev/sde1) leaked on vgs invocation. Parent PID 19829: grub-install
  /dev/loop0p1: read failed after 0 of 512 at 32201900032: Input/output error
  /dev/loop0p1: read failed after 0 of 512 at 32201961472: Input/output error
  /dev/loop0p1: read failed after 0 of 512 at 0: Input/output error
  /dev/loop0p1: read failed after 0 of 512 at 4096: Input/output error
  /dev/loop0p1: read failed after 0 of 2048 at 0: Input/output error
File descriptor 3 (pipe:[19279994]) leaked on vgs invocation. Parent PID 19829: grub-install
File descriptor 5 (/dev/sde1) leaked on vgs invocation. Parent PID 19829: grub-install
  /dev/loop0p1: read failed after 0 of 512 at 32201900032: Input/output error
  /dev/loop0p1: read failed after 0 of 512 at 32201961472: Input/output error
  /dev/loop0p1: read failed after 0 of 512 at 0: Input/output error
  /dev/loop0p1: read failed after 0 of 512 at 4096: Input/output error
  /dev/loop0p1: read failed after 0 of 2048 at 0: Input/output error
grub-install: error: cannot open `/boot/grub/x86_64-efi/load.cfg': No such file or directory.
dpkg: error processing package grub-efi-amd64 (--configure):
 subprocess installed post-installation script returned error exit status 1
dpkg: dependency problems prevent configuration of grub-efi-amd64-signed:
 grub-efi-amd64-signed depends on grub-efi-amd64 (= 2.02~beta2-7); however:
  Package grub-efi-amd64 is not configured yet.

dpkg: error processing package grub-efi-amd64-signed (--configure):
 dependency problems - leaving unconfigured
Setting up shim-signed (1.6+0.4-0ubuntu4) ...
No apport report written because the error message indicates its a followup error from a previous failure.

[Steve Langasek (vorlon)]

Hmm. The file does exist here; and shim-signed depends on grub-efi-amd64-bin, so it shouldn't be the case that we're calling grub-install before grub is configured. Colin, do you know what's going on here?

[Colin Watson (cjwatson)]

Already reported as bug 1298399, and fixed in grub2 2.02~beta2-8, which is making its way into trusty at the moment.