[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#885683: efibootmgr: option delete-bootnum not working

Package: efibootmgr
Version: 14-2
Severity: normal

Dear Maintainer,
I reflashed my firmware (Gigabyte AM3+ motherboard, model ga990fxa-ud3 v4.0, to firmware version 'F3') after a system failure of uncertain cause a few days ago. 
Lost most existing boot entries in the proccess, machine is triple booted with Debian Stretch, CentOS7, and Windows7 all on sda partions. I used a the boot menu of a live Manjaro USB drive to select and boot the existing Debian from sda.
>From within Debian:
I created two bootnums with with the basic comand format 'efibootmgr -c -L Debian -l \EFI\debian\grubx64.efi ' in this case it was entry 0005.
After noticing that backslashes need to be escaped I attempted to delete boot entry 0005 with `efibootmgr -B 0005`, as well as all combinations of short '-B' and long option '--delete-bootnum' with 0005, 5, Boot0005, boot0005, Boot5, boot5, Debian[Label of the entry]. (Manpage is slightly ambiguous about specific syntax details like leading zeros and escapes.)
Attempts to delete 0005 were made both before reboot and again after.
Attempted with both sudo and as root.
No entries were deleted.
In all cases it either returned 'You must specify an entry to delete (see the -b option).' or with the default help menu.

-- System Information:
Debian Release: 9.3
  APT prefers stable-updates
  APT policy: (500, 'stable-updates'), (500, 'stable')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 4.13.0-0.bpo.1-amd64 (SMP w/8 CPU cores)
Locale: LANG=en_US.utf8, LC_CTYPE=en_US.utf8 (charmap=UTF-8), LANGUAGE=en_US.utf8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages efibootmgr depends on:
ii  libc6        2.24-11+deb9u1
ii  libefiboot1  30-2
ii  libefivar1   30-2
ii  libpopt0     1.16-10+b2

efibootmgr recommends no packages.

efibootmgr suggests no packages.

-- no debconf information

Reply to: