[Bug 1575813] Re: Dual boot does not work after upgrade to 16.04\

[Steve Langasek]

On Fri, Apr 29, 2016 at 12:20:05AM -0000, gamx wrote:
> It is in this sense that it might be an Ubuntu bug:  It used to be fine
> and the upgrade has broken things.

> As I mention in a comment above, uncommenting one of the lines in the
> fstab allowed me to finish the upgrade but not to be able to boot the
> windows.

Except that Ubuntu on upgrade does not touch either the Windows boot loader
on disk, or the Windows EFI Boot entry in nvram; per your bug report, the
/boot/efi partition was not mounted during the upgrade, so Ubuntu *couldn't*
touch it; and we know that the EFI Boot entry for Windows (as returned in
your efibootmgr output) points to the correct disk, because it's the same
disk as listed for the Ubuntu entry and that one works.

The Windows boot failure appears to be an unfortunate coincidence.

-- 
You received this bug notification because you are a member of Ubuntu
Foundations Bugs, which is subscribed to shim-signed in Ubuntu.
https://bugs.launchpad.net/bugs/1575813

Title:
  Dual boot does not work after upgrade to 16.04

Status in shim-signed package in Ubuntu:
  Invalid

Bug description:
  I upgraded from 15.10 to 16.04. The process was not completed
  apparently due a problem with shim-signed. I now find the following
  message every time I try to update the system:

  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
  E: Sub-process /usr/bin/dpkg returned an error code (1)

  Furthermore, I have a dual boot system with Windows and Ubuntu but
  only the latter works. Something seems to have gone south with UEFI. I
  attach the efibootmgr output. My /etc/fstab looks as follows

  # <file system> <mount point>   <type>  <options>       <dump>  <pass>
  # / was on /dev/sda10 during installation
  UUID=5cc07bc2-7247-40b6-8290-7edef8b4a39d /               ext4    errors=remount-ro 0       1
  # /boot was on /dev/sda9 during installation
  #UUID=b22addc5-b969-47bf-a154-f91b6a137dd6 /boot           ext4    defaults        0       2
  # /home was on /dev/sda11 during installation
  UUID=0aa517c8-aed2-446f-91c2-ecb573598a6d /home           ext4    defaults        0       2
  # swap was on /dev/sda8 during installation
  #UUID=64342e46-54ea-46bf-826e-5667367e2301 none            swap    sw              0       0
  /dev/mapper/cryptswap1 none swap sw 0 0
  UUID=b22addc5-b969-47bf-a154-f91b6a137dd6	/boot	ext4	defaults	0	2
  #UUID=5251-F902	/boot/efi	vfat	defaults	0	1
  #UUID=b032ab5d-1a06-4b52-afcb-14954b4b6ab8	/boot/efi	/dev/sda1: PARTLABEL=	defaults	0	1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/shim-signed/+bug/1575813/+subscriptions