Bug#756253: Upgrade from 2.02~beta2-10 to 2.02~beta2-11 left grub unbootable

[Colin Watson]

On Mon, Jul 28, 2014 at 09:26:22AM +0900, Mike Hommey wrote:
> After the upgrade from 2.02~beta2-10 to 2.02~beta2-11, a reboot just got
> me under Windows. The EFI boot menu had two entries for Windows (I don't
> think it had two in the past, but maybe it did, and that's not related),
> and one for "UEFI OS" which was set as the default. Choosing that one
> manually in the boot menu still brought Windows up.
> 
> After booting with a USB stick in rescue mode, deleting the duplicate
> Windows entry and the UEFI OS entry, and re-running grub-install, grub
> showed up at reboot. After grub-install, the EFI entry is now named
> "debian".
> 
> Note I haven't run grub-install in a while, so I'm not sure what version
> of grub had done a grub-install last.

Sorry for the delayed response.  I think this is unlikely to have been a
problem introduced by the new version of GRUB as such (unless switching
to GCC 4.9 did this, but that seems a pretty tenuous theory), and
grub-install is run automatically provided that /boot/efi/EFI/debian/
exists.  Could you please post the output of:

  dpkg -l efibootmgr
  sudo efibootmgr
  find /boot/efi -ls

Thanks,

-- 
Colin Watson                                       [cjwatson at debian.org]