package shim-signed 1.32~16.04.1+0.9+1474479173.6c180c6-1ubuntu1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1

[Dmytro Yakovenko]

the bug occured on ubuntu startup
no details available

ProblemType: Package
DistroRelease: Ubuntu 16.04
Package: shim-signed 1.32~16.04.1+0.9+1474479173.6c180c6-1ubuntu1
ProcVersionSignature: Ubuntu 4.4.0-98.121-generic 4.4.90
Uname: Linux 4.4.0-98-generic x86_64
.proc.sys.kernel.moksbstate_disabled: 0
ApportVersion: 2.20.1-0ubuntu2.10
Architecture: amd64
BootEFIContents:
 fw
 fwupx64.efi
Date: Sun Nov 12 12:24:01 2017
EFITables:
 лис 15 20:58:32 hp-g5 kernel: efi: EFI v2.40 by INSYDE Corp.
 лис 15 20:58:32 hp-g5 kernel: efi: SMBIOS=0x7a5fb000 ESRT=0x7a5fe818 ACPI 2.0=0x7affe014 PROP=0x62c99238
 лис 15 20:58:32 hp-g5 kernel: esrt: Reserving ESRT space from 0x000000007a5fe818 to 0x000000007a5fe850.
 лис 15 21:03:01 hp-g5 gnome-session[2074]: diff: /boot/efi/EFI/ubuntu/grubx64.efi: No such file or directory
 лис 15 21:03:01 hp-g5 gnome-session[2074]: diff: /boot/efi/EFI/ubuntu/shimx64.efi: No such file or directory
ErrorMessage: subprocess installed post-installation script returned error exit status 1
InstallationDate: Installed on 2017-01-31 (288 days ago)
InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719)
RelatedPackageVersions:
 dpkg 1.18.4ubuntu1.2
 apt 1.2.24
SecureBoot: 6 0 0 0 0
SourcePackage: shim-signed
Title: package shim-signed 1.32~16.04.1+0.9+1474479173.6c180c6-1ubuntu1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1
UpgradeStatus: No upgrade log present (probably fresh install)

[Steve Langasek (vorlon)]

Why is /boot/efi/EFI/ubuntu missing on your system?

[Dmytro Yakovenko (fjfb)]

Steve,

I have this directory but I don't have grubx64.efi and shimx64.efi files in there.
Don't know why.
How can I fix that?

[Steve Langasek (vorlon)]

On Wed, Nov 15, 2017 at 08:54:27PM -0000, Dmytro Yakovenko wrote:
> Steve,

> I have this directory but I don't have grubx64.efi and shimx64.efi files in there.
> Don't know why.
> How can I fix that?

If you run 'sudo apt -f install' from a terminal, this should restore those
files.

That still leaves it unexplained why /boot/efi was not mounted at the time
your upgrades were being applied.

[Dmytro Yakovenko (fjfb)]

I ran this command and got this error:

Reading package lists... Done
Building dependency tree
Reading state information... Done
The following packages were automatically installed and are no longer required:
  libappstream3 libgles1-mesa libllvm3.8 libmircommon5 linux-headers-4.4.0-62 linux-headers-4.4.0-62-generic linux-headers-4.4.0-64 linux-headers-4.4.0-64-generic linux-headers-4.4.0-66
  linux-headers-4.4.0-66-generic linux-headers-4.4.0-70 linux-headers-4.4.0-70-generic linux-headers-4.4.0-72 linux-headers-4.4.0-72-generic linux-headers-4.4.0-77 linux-headers-4.4.0-77-generic
  linux-headers-4.4.0-78 linux-headers-4.4.0-78-generic linux-headers-4.4.0-79 linux-headers-4.4.0-79-generic linux-headers-4.4.0-81 linux-headers-4.4.0-81-generic linux-headers-4.4.0-83
  linux-headers-4.4.0-83-generic linux-headers-4.4.0-87 linux-headers-4.4.0-87-generic linux-headers-4.4.0-89 linux-headers-4.4.0-89-generic linux-headers-4.4.0-92 linux-headers-4.4.0-92-generic
  linux-headers-4.4.0-93 linux-headers-4.4.0-93-generic linux-headers-4.4.0-96 linux-headers-4.4.0-96-generic linux-image-4.4.0-62-generic linux-image-4.4.0-64-generic linux-image-4.4.0-66-generic
  linux-image-4.4.0-70-generic linux-image-4.4.0-72-generic linux-image-4.4.0-77-generic linux-image-4.4.0-78-generic linux-image-4.4.0-79-generic linux-image-4.4.0-81-generic
  linux-image-4.4.0-83-generic linux-image-4.4.0-87-generic linux-image-4.4.0-89-generic linux-image-4.4.0-92-generic linux-image-4.4.0-93-generic linux-image-4.4.0-96-generic
  linux-image-extra-4.4.0-62-generic linux-image-extra-4.4.0-64-generic linux-image-extra-4.4.0-66-generic linux-image-extra-4.4.0-70-generic linux-image-extra-4.4.0-72-generic
  linux-image-extra-4.4.0-77-generic linux-image-extra-4.4.0-78-generic linux-image-extra-4.4.0-79-generic linux-image-extra-4.4.0-81-generic linux-image-extra-4.4.0-83-generic
  linux-image-extra-4.4.0-87-generic linux-image-extra-4.4.0-89-generic linux-image-extra-4.4.0-92-generic linux-image-extra-4.4.0-93-generic linux-image-extra-4.4.0-96-generic
  linux-signed-image-4.4.0-62-generic linux-signed-image-4.4.0-64-generic linux-signed-image-4.4.0-66-generic linux-signed-image-4.4.0-70-generic linux-signed-image-4.4.0-72-generic
  linux-signed-image-4.4.0-77-generic linux-signed-image-4.4.0-78-generic linux-signed-image-4.4.0-79-generic linux-signed-image-4.4.0-81-generic linux-signed-image-4.4.0-83-generic
  linux-signed-image-4.4.0-87-generic linux-signed-image-4.4.0-89-generic linux-signed-image-4.4.0-92-generic linux-signed-image-4.4.0-93-generic linux-signed-image-4.4.0-96-generic snap-confine
Use 'sudo apt autoremove' to remove them.
0 upgraded, 0 newly installed, 0 to remove and 15 not upgraded.
2 not fully installed or removed.
After this operation, 0 B of additional disk space will be used.
Setting up grub-efi-amd64-signed (1.66.14+2.02~beta2-36ubuntu3.14) ...
Installing for x86_64-efi platform.
grub-install: error: cannot find EFI directory.
dpkg: error processing package grub-efi-amd64-signed (--configure):
 subprocess installed post-installation script returned error exit status 1
Setting up shim-signed (1.32~16.04.1+0.9+1474479173.6c180c6-1ubuntu1) ...
Inst...

[Steve Langasek (vorlon)]

On Wed, Nov 15, 2017 at 09:38:40PM -0000, Dmytro Yakovenko wrote:
> Setting up grub-efi-amd64-signed (1.66.14+2.02~beta2-36ubuntu3.14) ...
> Installing for x86_64-efi platform.
> grub-install: error: cannot find EFI directory.

Is /boot/efi a mount point?

Please attach /etc/fstab.

[Dmytro Yakovenko (fjfb)]

Sorry, I'm not strong in using Ubuntu. I've attached the screenshot regarding your question about a mount point. Hopefully it will help.

And here is /etc/fstab:

# /etc/fstab: static file system information.
#
# Use 'blkid' to print the universally unique identifier for a
# device; this may be used with UUID= as a more robust way to name devices
# that works even if disks are added and removed. See fstab(5).
#
# <file system> <mount point> <type> <options> <dump> <pass>
# / was on /dev/sda2 during installation
UUID=5eadcb46-e6cb-4eb4-b36b-658350feb126 / ext4 errors=remount-ro 0 1
# /boot/efi was on /dev/sda1 during installation
# swap was on /dev/sda3 during installation
UUID=aa851e10-8aa4-4e4c-9d70-de826e97fca7 none swap sw 0 0

[Steve Langasek (vorlon)]

Ok, here is the problem:

# /boot/efi was on /dev/sda1 during installation
# swap was on /dev/sda3 during installation

There is no fstab entry for /boot/efi, only a comment for it.

What does 'ls -l /etc/fstab' show? (Specifically, we want to know when this file was last modified)

Do you know why this entry was removed from your fstab? Did you run any third-party commands related to boot or filesystem configuration?

Once you have added this debugging information to the bug, you can repair your system by running the following commands as root:

echo "UUID=$(blkid -ovalue -sUUID /dev/sda1) /boot/efi vfat defaults 0 2" >> /etc/fstab
mount /boot/efi
apt -f install

[Dmytro Yakovenko (fjfb)]

Output of ls -l /etc/fstab
-rw-r--r-- 1 root root 643 Mar 18 2017 /etc/fstab
No, I have no idea why it could have been deleted. I don't remember to had run any commands either.

Is it normal that this part of command ( $(blkid -ovalue -sUUID /dev/sda1) ) gives no output?

[Dmytro Yakovenko (fjfb)]

Steve,
Here is last output of "mount" command after your changes.
sysfs on /sys type sysfs (rw,nosuid,nodev,noexec,relatime)
proc on /proc type proc (rw,nosuid,nodev,noexec,relatime)
udev on /dev type devtmpfs (rw,nosuid,relatime,size=4011260k,nr_inodes=1002815,mode=755)
devpts on /dev/pts type devpts (rw,nosuid,noexec,relatime,gid=5,mode=620,ptmxmode=000)
tmpfs on /run type tmpfs (rw,nosuid,noexec,relatime,size=806324k,mode=755)
/dev/sda2 on / type ext4 (rw,relatime,errors=remount-ro,data=ordered)
securityfs on /sys/kernel/security type securityfs (rw,nosuid,nodev,noexec,relatime)
tmpfs on /dev/shm type tmpfs (rw,nosuid,nodev)
tmpfs on /run/lock type tmpfs (rw,nosuid,nodev,noexec,relatime,size=5120k)
tmpfs on /sys/fs/cgroup type tmpfs (ro,nosuid,nodev,noexec,mode=755)
cgroup on /sys/fs/cgroup/systemd type cgroup (rw,nosuid,nodev,noexec,relatime,xattr,release_agent=/lib/systemd/systemd-cgroups-agent,name=systemd)
pstore on /sys/fs/pstore type pstore (rw,nosuid,nodev,noexec,relatime)
efivarfs on /sys/firmware/efi/efivars type efivarfs (rw,nosuid,nodev,noexec,relatime)
cgroup on /sys/fs/cgroup/devices type cgroup (rw,nosuid,nodev,noexec,relatime,devices)
cgroup on /sys/fs/cgroup/cpu,cpuacct type cgroup (rw,nosuid,nodev,noexec,relatime,cpu,cpuacct)
cgroup on /sys/fs/cgroup/hugetlb type cgroup (rw,nosuid,nodev,noexec,relatime,hugetlb)
cgroup on /sys/fs/cgroup/perf_event type cgroup (rw,nosuid,nodev,noexec,relatime,perf_event)
cgroup on /sys/fs/cgroup/net_cls,net_prio type cgroup (rw,nosuid,nodev,noexec,relatime,net_cls,net_prio)
cgroup on /sys/fs/cgroup/cpuset type cgroup (rw,nosuid,nodev,noexec,relatime,cpuset)
cgroup on /sys/fs/cgroup/memory type cgroup (rw,nosuid,nodev,noexec,relatime,memory)
cgroup on /sys/fs/cgroup/pids type cgroup (rw,nosuid,nodev,noexec,relatime,pids)
cgroup on /sys/fs/cgroup/blkio type cgroup (rw,nosuid,nodev,noexec,relatime,blkio)
cgroup on /sys/fs/cgroup/freezer type cgroup (rw,nosuid,nodev,noexec,relatime,freezer)
systemd-1 on /proc/sys/fs/binfmt_misc type autofs (rw,relatime,fd=27,pgrp=1,timeout=0,minproto=5,maxproto=5,direct)
debugfs on /sys/kernel/debug type debugfs (rw,relatime)
mqueue on /dev/mqueue type mqueue (rw,relatime)
hugetlbfs on /dev/hugepages type hugetlbfs (rw,relatime)
fusectl on /sys/fs/fuse/connections type fusectl (rw,relatime)
/var/lib/snapd/snaps/core_3247.snap on /snap/core/3247 type squashfs (ro,nodev,relatime)
/var/lib/snapd/snaps/core_3440.snap on /snap/core/3440 type squashfs (ro,nodev,relatime)
binfmt_misc on /proc/sys/fs/binfmt_misc type binfmt_misc (rw,relatime)
/var/lib/snapd/snaps/vlc_4.snap on /snap/vlc/4 type squashfs (ro,nodev,relatime)
/var/lib/snapd/snaps/core_3017.snap on /snap/core/3017 type squashfs (ro,nodev,relatime)
tmpfs on /run/user/1000 type tmpfs (rw,nosuid,nodev,relatime,size=806324k,mode=700,uid=1000,gid=1000)
gvfsd-fuse on /run/user/1000/gvfs type fuse.gvfsd-fuse (rw,nosuid,nodev,relatime,user_id=1000,group_id=1000)
/dev/sda1 on /boot/efi type vfat (rw,relatime,fmask=0022,dmask=0022,codepage=437,iocharset=iso8859-1,shortname=mixed,errors=remount-ro)

The last row is new.
I guess the issue is fixed now?

[Steve Langasek (vorlon)]

Yes, it does look like this has fixed the problem for you.

If you can figure out why the line was removed from your /etc/fstab, that would help us understand if there's something that should be done in Ubuntu to prevent this happening to other users.

[Launchpad Janitor (janitor)]

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