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

[Michal Zimen]

Hi,

I'm facing the same problem caused most probably by the latest grub update.
Any issue how  to fix or hack to have bootable laptop?

Here are some of my logs:

# efibootmgr -c -l "\\EFI\\debian\\grubx64.efi" -L "Debian"
efibootmgr: Could not set variable Boot0000: No space left on device
efibootmgr: Could not prepare boot variable: No space left on device
#


/dev/sda2          256M   27M  230M  11% /boot/efi


# dpkg -l efibootmgr grub-efi grub2-common
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.12-4 amd64                  
Interact with the EFI Boot Manager
ii  grub-efi                           2.02~beta2-35 amd64               
GRand Unified Bootloader, version 2 (dummy package)
ii  grub2-common                       2.02~beta2-35 amd64       GRand 
Unified Bootloader (common files for version 2)


#efibootmgr
BootCurrent: 0001
Timeout: 0 seconds
BootOrder: 2001,0002,0005,0004,2002,2003
Boot0001* EFI USB Device (USB FLASH DRIVE)
Boot0002* Windows Boot Manager
Boot0004* Network Boot: Realtek PXE B01 D00
Boot0005* ATA HDD     : ST500LM000-1EJ162
Boot2001* EFI USB Device
Boot2002* EFI DVD/CDROM
Boot2003* EFI Network
    ---> my debian entry has completely lost from the list of boot 
devices. I can boot only via USB.

Thanks for any help,

     Michal


On Mon, 24 Aug 2015 22:51:09 +0200 Felix Zielcke <fzielcke at z-51.de> wrote:
 > Am Montag, den 24.08.2015, 10:28 +0200 schrieb Giorgio Valocchi:
 > > The problem was that the nvram entry wasn't properly created under
 > > sid.
 > >
 > > I managed to login in a stable distribution I have on the same system
 > > to
 > > create it.
 >
 > In that case it would be a bug either in efibootmgr or the Linux
 > Kernel.
 > grub-install just calls efibootmgr to create the entry
 >
 >

-- 
~Epitheton s.r.o./AMDG


-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.alioth.debian.org/pipermail/pkg-grub-devel/attachments/20160209/17e51932/attachment.html>