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

[Steve McIntyre]

[ Hoping to help investigate this... ]

On Fri, Oct 24, 2014 at 07:30:26PM +0900, Mike Hommey wrote:
>On Mon, Oct 13, 2014 at 03:45:31PM +0100, Colin Watson wrote:
>> 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
>
>It happened again today. Grub was not updated, but the kernel was.
>
># dpkg -l efibootmgr
>Desired=Unknown/Install/Remove/Purge/Hold
>|
>Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend
>|/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad)
>||/ Name                        Version            Architecture
>Description
>+++-===========================-==================-==================-============================================================
>ii  efibootmgr                  0.9.0-2            amd64
>Interact with the EFI Boot Manager
>
># efibootmgr
>BootCurrent: 0002
>Timeout: 0 seconds
>BootOrder: 0002,0001,0000
>Boot0000* Windows Boot Manager
>Boot0001* Windows Boot Manager
>Boot0002* grub
>
># # NOTE: the "grub" entry is one I added from the BIOS in order to boot
># # at all. It was *not* there. Both Windows entries were. after re-running
># # grub-install, I get:
>
>BootCurrent: 0002
>Timeout: 0 seconds
>BootOrder: 0003,0002,0001,0000
>Boot0000* Windows Boot Manager
>Boot0001* Windows Boot Manager
>Boot0002* grub
>Boot0003* debian

...

>
>   453    4 drwxr-xr-x   2 root     root         4096  1月  8  2014 /boot/efi/EFI/Boot
>   455 1580 -rwxr-xr-x   1 root     root      1617240  4月 27  2014 /boot/efi/EFI/Boot/bootx64.efi
>   456    4 drwxr-xr-x   2 root     root         4096  1月 22  2014 /boot/efi/EFI/debian
>   458  120 -rwxr-xr-x   1 root     root       119808 10月 18 10:59 /boot/efi/EFI/debian/grubx64.efi

Hi Mike,

Have you seen this again recently? Is it still happening for you?

-- 
Steve McIntyre, Cambridge, UK.                                steve at einval.com
Can't keep my eyes from the circling sky,
Tongue-tied & twisted, Just an earth-bound misfit, I...