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

[Giorgio Valocchi]

On Sun, 16 Aug 2015 08:42:48 +0200 Felix Zielcke <fzielcke at z-51.de> wrote:
 > Am Mittwoch, den 21.01.2015, 00:58 +0000 schrieb Steve McIntyre:
 > > On Wed, Jan 21, 2015 at 06:55:05AM +0900, Mike Hommey wrote:
 > > > On Tue, Jan 20, 2015 at 01:44:37PM +0000, Steve McIntyre wrote:
 > > > >
 > > > > 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?
 > >
 > > As far back as I remember, yes.
 > >
 > > > > > 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.
 > >
 > > OK, now that's just *weird* and suggests a firmware bug to me. I'd be
 > > tempted to try and create an exact copy with another name and see how
 > > that works, but I'm struggling to understand what's going on here
 > > now!
 > >
 >
 > Is still a problem or got it somehow solved?
 >
 >

Right now my system is unbootable too.
I have debian sid and grub 2.02-beta2-26.

This is my partition table

Konsole output
Device     Start       End  Sectors  SizeType
/dev/sda1        2048     391167    389120   190M EFI System
/dev/sda2      391168  195702783 195311616  93.1G Linux filesystem
/dev/sda3   195702784  973242367 777539584 370.8G Linux filesystem
/dev/sda4  1168472064 1455464447 286992384 136.9G Microsoft basic data
/dev/sda6  1455464448 1465141247   9676800   4.6G Linux swap

I'm able to login through rEFInd on a USB from which I'm able to launch 
even GRUB2 (selecting the EFI partition);
however without an external bootloader the system doesn't find any 
bootable device even if the EFI partition has the boot flag.

During the last login before the problem I upgraded the following packages:

Start-Date: 2015-08-21  12:46:30

Upgrade:
python-pam:amd64 (0.4.2-13.1, 0.4.2-13.2),
sphinx-common:amd64 (1.3.1-4, 1.3.1-5),
sphinx-doc:amd64 (1.3.1-4, 1.3.1-5),
openssh-server:amd64 (6.7p1-6, 6.9p1-1),
openssh-sftp-server:amd64 (6.7p1-6, 6.9p1-1),
libytnef0:amd64 (1.5-6, 1.5-7),
python-sphinx:amd64 (1.3.1-4, 1.3.1-5),
ssh:amd64 (6.7p1-6, 6.9p1-1),
xfig-libs:amd64 (3.2.5.c-4, 3.2.5.c-5),
openssh-client:amd64 (6.7p1-6, 6.9p1-1),
python-xlrd:amd64 (0.9.2-1, 0.9.4-1),
xfig:amd64 (3.2.5.c-4, 3.2.5.c-5),
libapr1:amd64 (1.5.2-2, 1.5.2-3),
libqalculate5-data:amd64 (0.9.7-9, 0.9.7-9.1),
libjs-sphinxdoc:amd64 (1.3.1-4, 1.3.1-5),
libparse-debianchangelog-perl:amd64 (1.2.0-5, 1.2.0-6)

End-Date: 2015-08-21  12:47:48

Start-Date: 2015-08-21  12:49:16
End-Date: 2015-08-21  12:49:17

Start-Date: 2015-08-21  16:38:32

Upgrade:
valac:amd64 (0.28.0-2, 0.28.1-1),
valac-0.28:amd64 (0.28.0-2, 0.28.1-1),
eog:amd64 (3.16.2-1, 3.16.3-1),
console-setup:amd64 (1.131, 1.132),
console-setup-linux:amd64 (1.131, 1.132),
libvala-0.28-0:amd64 (0.28.0-2, 0.28.1-1),
gnome-music:amd64 (3.16.1-2, 3.16.2-1),
keyboard-configuration:amd64 (1.131, 1.132),
valac-0.28-vapi:amd64 (0.28.0-2, 0.28.1-1)

End-Date: 2015-08-21  16:39:06

I can't manage to figure out what is the problem.

Konsole out
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.alioth.debian.org/pipermail/pkg-grub-devel/attachments/20150823/48e6b554/attachment.html>