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

[Mike Hommey]

On Tue, Jan 20, 2015 at 01:44:37PM +0000, Steve McIntyre wrote:
> On Mon, Jan 19, 2015 at 07:42:37AM +0900, Mike Hommey wrote:
> >On Sun, Jan 18, 2015 at 11:37:28AM +0000, Steve McIntyre wrote:
> >> The ENOSPC handling has been bad in the past, but it's not clear that
> >> was the cause of your original bug. :-/ *Now* it's a very bad state to
> >> be in, and may cause other problems too. On the Dell machine you have,
> >> I'm not personally aware of workarounds/fixes for it, but I know that
> >> on some machines re-flashing the firmware can force fix this by
> >> forcing cleaning of used space.
> >
> >After some googling, I cleaned up /sys/fs/pstore, which contained
> >dmesg-* files, and that cleaned up /sys/firmware/efi/vars/ such that
> >efibootmgr can do its job. 
> 
> Ah, OK. Phew. :-)
> 
> >There are a couple things happening, though.
> >
> >The first one is that it adds a "debian" entry. I'm not sure, though,
> >that the "grub" entry name doesn't just come from me adding it
> >manually with a different name (since, iirc, this very bug left me
> >with no grub entry at all) than it had in the first place or if it
> >/was/ named grub originally. So I do end up with 3 entries: "grub",
> >"debian" and "Windows Boot Manager" listed by efibootmgr.
> 
> The automatic setup of grub-install calling efibootmgr won't be
> touching the "grub" entry at all - it's set up to only play with
> "debian" entries. So that should be safe.

Was it always a "debian" entry?

> >But then comes the second thing: when I reboot, the "debian" entry is
> >lost. Poof, disappeared. And I do wonder if the initial problem is not
> >related to that.
> 
> That is still happening? Can you successfully re-create it each time?

It happens reliably. efibootmgr displays it, but after a reboot, it's
gone.

Mike