Results 1 to 5 of 5

Thread: efibootmgr could not delete boot variable

  1. #1
    Join Date
    Jul 2017
    Location
    Canada
    Posts
    29

    Default efibootmgr could not delete boot variable

    This morning there have been some strange things happening with this system. When I booted the system this morning the grub menu did not show up and booted straight into windows which was a bit odd.

    So the first I did was to boot into opensuse using F8 / Select EFI entry. Once booted I checked that opensuse was still selected as the default and it was but when I clicked ok I got the message that it could not delete boot variable. Well this is a bit interesting so I then ran the command sudo efibootmgr which showed a list with some older installations of ubuntu.

    Trying to delete these old entries I got the same message. Then I tried changing the boot order using the -o option and got the same error. I then changed the boot priority in Bios and that seemed to fix the MIA grub menu part of the problem. Once booted again I was able to delete the two old ubuntu entries, and Yast is no longer throwing the error when changing the default boot.

    So my question now is why I am getting duplicate entries? I would like to clean this up so that the problem doesn't come back again.

    Code:
    ~> sudo efibootmgr
    [sudo] password for root: 
    BootCurrent: 0003
    Timeout: 1 seconds
    BootOrder: 0002
    Boot0000* Windows Boot Manager
    Boot0001* Windows Boot Manager
    Boot0002* opensuse-secureboot
    Boot0003* opensuse
    Boot0004* Hard Drive 
    Boot0005* CD/DVD Drive 
    Boot0011  CD/DVD Drive 
    Boot0014* opensuse
    Boot0015  Hard Drive 
    Boot0018* opensuse

  2. #2
    Join Date
    Jul 2017
    Location
    Canada
    Posts
    29

    Default Re: efibootmgr could not delete boot variable

    After another boot, the entries changed again and one of the two ubuntu entries came back not sure if this is significant.

    Code:
    sudo efibootmgr
    BootCurrent: 0002
    Timeout: 1 seconds
    BootOrder: 0002,0003,0004,0005,0006,0007,0014,0000,0018,0001,0008,0009,000A
    Boot0000* Windows Boot Manager
    Boot0001* Windows Boot Manager
    Boot0002* opensuse-secureboot
    Boot0003* Windows Boot Manager
    Boot0004* ubuntu
    Boot0005* opensuse
    Boot0006* Hard Drive 
    Boot0007* CD/DVD Drive 
    Boot0008* UEFI:CD/DVD Drive
    Boot0009* UEFI:Removable Device
    Boot000A* UEFI:Network Device
    Boot0011  CD/DVD Drive 
    Boot0014* opensuse
    Boot0015  Hard Drive 
    Boot0018* opensuse

  3. #3
    Join Date
    Jun 2008
    Location
    Podunk
    Posts
    32,349
    Blog Entries
    15

    Default Re: efibootmgr could not delete boot variable

    On Thu 10 Aug 2017 06:06:02 PM CDT, mike1022 wrote:

    After another boot, the entries changed again and one of the two ubuntu
    entries came back not sure if this is significant.


    Code:
    --------------------

    sudo efibootmgr
    BootCurrent: 0002
    Timeout: 1 seconds
    BootOrder:
    0002,0003,0004,0005,0006,0007,0014,0000,0018,0001,0008,0009,000A
    Boot0000* Windows Boot Manager Boot0001* Windows Boot Manager
    Boot0002* opensuse-secureboot
    Boot0003* Windows Boot Manager
    Boot0004* ubuntu
    Boot0005* opensuse
    Boot0006* Hard Drive
    Boot0007* CD/DVD Drive
    Boot0008* UEFI:CD/DVD Drive
    Boot0009* UEFI:Removable Device
    Boot000A* UEFI:Network Device
    Boot0011 CD/DVD Drive
    Boot0014* opensuse
    Boot0015 Hard Drive
    Boot0018* opensuse

    --------------------


    Hi
    Your hardware (and probably windows) insists on Windows Boot Manager
    being the boss.... 0000 and if not adding a new entry.

    How are you deleting the entries, with the -B and -b option.

    Sometimes cleaning them all out and manually adding via efibootmgr
    helps with clean up the NVRAM, in your BIOS can you select an efi file
    to boot from, also your system hardware is?

    --
    Cheers Malcolm °¿° SUSE Knowledge Partner (Linux Counter #276890)
    openSUSE Leap 42.2|GNOME 3.20.2|4.4.74-18.20-default
    If you find this post helpful and are logged into the web interface,
    please show your appreciation and click on the star below... Thanks!


  4. #4
    Join Date
    Jul 2017
    Location
    Canada
    Posts
    29

    Default Re: efibootmgr could not delete boot variable

    Quote Originally Posted by malcolmlewis View Post
    Hi
    Your hardware (and probably windows) insists on Windows Boot Manager
    being the boss.... 0000 and if not adding a new entry.

    How are you deleting the entries, with the -B and -b option.

    Sometimes cleaning them all out and manually adding via efibootmgr
    helps with clean up the NVRAM, in your BIOS can you select an efi file
    to boot from, also your system hardware is?

    --
    Cheers Malcolm °¿° SUSE Knowledge Partner (Linux Counter #276890)
    openSUSE Leap 42.2|GNOME 3.20.2|4.4.74-18.20-default
    If you find this post helpful and are logged into the web interface,
    please show your appreciation and click on the star below... Thanks!
    Yes I did delete the entries via efibootmrg -B entryNum -b

    I haven't booted into Windows since I started to clean this up. I usually only boot into Windows maybe once a month now.

    Here is the system info. The problem is somewhat resolved now, I am just a little puzzled about the duplicates.

    Code:
    System:    Host: linux-0g14 Kernel: 4.11.8-2-default x86_64 (64 bit) Desktop: KDE Plasma 5.10.4
               Distro: openSUSE Tumbleweed 20170808
    Machine:   Device: desktop System: ASUS product: All Series
               Mobo: ASUSTeK model: H97-PLUS v: Rev X.0x UEFI: American Megatrends v: 2603 date: 02/26/2016
    CPU:       Quad core Intel Core i7-4790 (-HT-MCP-) speed/max: 900/4000 MHz
    Graphics:  Card: NVIDIA GT200 [GeForce GTX 260]
               Display Server: x11 (X.org 1.19.3) driver: nvidia tty size: 139x47
    Network:   Card-1: Realtek RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller driver: r8169
               Card-2: ASUSTek USB-N53 802.11abgn Network Adapter [Ralink RT3572] driver: rt2800usb
    Drives:    HDD Total Size: 3000.6GB (16.1% used)
    Info:      Processes: 258 Uptime: 3:23 Memory: 1759.4/15989.2MB Init: systemd runlevel: 5
               Client: Shell (bash) inxi: 2.3.25

  5. #5

    Default Re: efibootmgr could not delete boot variable

    Probably a faulty UEFI firmware ...

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •