Ubuntu ошибка при установке grub2

5

I got the same issue while installing Ubuntu 18.04 in My brother’s laptop! And I tried to reinstall again! But I got same error! I created 500 MB of /boot partition! Then it solved the issue!

Easiest solution (it just now worked for me):
Once the install fails, you should be taken to a website that attempts to help you.
Immediately exit out of the browser when you see this page.
It will then take you to the “try out Ubuntu” version of the desktop of Ubuntu.
Choose to install Ubuntu, and then once you get to the install type choose “Erase Ubuntu and reinstall”.
Just did it and it worked! You can also choose all of the other same options you’ve already been choosing.

SergPro

На форуме не нашёл такой проблемы, надеюсь правильно создал тему.
Устанавливаю Ubuntu 16.04 рядом с Виндовс 10. Разметил диски и т.п. Но после всей установки вылетает окошко с «Не удалось установить GRUB» Как бы мне эту проблему решить. Второй день мучаюсь. Надеюсь на помощь. Спасибо за ранее.

ТС не появлялся на Форуме более полугода по состоянию на 14/07/2019 (последняя явка: 16/04/2017). Модератором раздела принято решение закрыть тему.
—zg_nico

« Последнее редактирование: 14 Июля 2019, 03:09:21 от zg_nico »

viktor ne perestukin

 Уточни пожалуйста — «Не удалось установить GRUB» во время установки с Live или после установки

SergPro

После установки выдаёт это сообщение.

SergPro

Да, после установки вылетает ошибка с GRUB.

Пользователь добавил сообщение 01 Ноября 2016, 22:23:54:

Только у меня почему-то нету раздела ESP и отформатированного в FAT32.(для корректной установки)

« Последнее редактирование: 01 Ноября 2016, 22:23:54 от SergPro »

Дюшик

Только у меня почему-то нету раздела ESP и отформатированного в FAT32.(для корректной установки)

Загрузитесь с установочного носителя Ubuntu и покажите вывод команды

sudo parted -l
или скрин с разделами из Gparted.
Или загрузитесь в 10-ку, в строке поиска введите diskmgmt.msc -> OK, сделайте скрин открывшегося окна с разделами диска и покажите скрин.

SergPro

« Последнее редактирование: 03 Ноября 2016, 18:17:46 от SergPro »

Дюшик

SergPro,
У вас «простая» разметка диска — MBR. Раздел ESP вам не нужен. Во время установки Ubuntu, вы случайно GRUB устанавливаете не раздел? (и возможно Виндовый). В процессе установки Ubuntu проверьте/установите GRUB на жесткий диск (/dev/sda, а не на /dev/sda1…4). 

SergPro

а как Граб поставить туда,куда нужно.? галочку поставить?

Пользователь добавил сообщение 03 Ноября 2016, 20:03:27:

процессе установки Ubuntu проверьте/установите GRUB на жесткий диск (/dev/sda, а не на /dev/sda1…4).

Т.е. внизу будет «Устройство для установки системного загрузчика»
тут и выбираем /dev/sda     ?

P.S. по умолчанию у меня было /dev/sda

Пользователь добавил сообщение 03 Ноября 2016, 22:51:46:

На старый нетбук 2009 года установился без проблем (рядом с Виндовс 8.1)
А на современный 2015 года рядом с Виндовс 10 не ставится. Буду разбираться.
Нужна помощь.

« Последнее редактирование: 03 Ноября 2016, 22:51:46 от SergPro »

Дюшик

SergPro,
Возможно вы неправильно загружаетесь с установочной флешки (если устанавливаете с флешки, вы не написАли).
1. Если у вас есть выбор загрузочной флешки, например

UEFI: Kinston 4 GB
Kingston 4 GB

то выбирайте флешку без префикса UEFI.

2. Если первого варианта нет, то зайдите в UEFI-BIOS и поищите параметр типа Boot mode и в нём проверьте/поставьте Legacy only или Legacy first. Всё это может называться по-разному, т.к. UEFI-BIOS очень разные. Вообщем вам нужно режим загрузки сделать строго Legacy (CSM и т.п.).
После выполнения первого или второго пунктов, загрузиться с установочной флешки и попробовать установить GRUB
а) вручную

sudo mount /dev/sdaX /mnt     - где Х цифра раздела с Ubuntu
sudo grub-install --root-directory=/mnt /dev/sda
б) через Boot repair https://help.ubuntu.ru/wiki/boot_repair
в) через Grub Customizer https://help.ubuntu.ru/wiki/grub_customizer

Если всё вышепредложеное «мимо», то можно временно организовать загрузку Ubuntu через Виндовый загрузчик с помощью EasyBCD https://forum.ubuntu.ru/index.php?topic=283187.msg2231636#msg2231636. Потом загрузиться в Ubuntu и пробовать установить GRUB из Ubuntu

sudo grub-install /dev/sda

дальше по результатам.

Дюшик

SergPro,
Моё ИМХО. Отделльный раздел boot не нужен и проблему он не решит. Но если вы хотите попробовать установку с разделом boot, то можете поэксперементировать. Моё мнение, что нужно сначала попробовать правильно загрузится с флешки и посмотреть, что получится. Ещё один вариант, который вы можете попробовать, это записать флешку через программу Rufus с настройкой MBR для компьютеров с BIOS и UEFI и установить систему. Есть ещё одна возможная, но маловероятная причина, чтобы её исключить нужен с установочной флешки Ubuntu, вывод команд

sudo parted -l
или
sudo fdisk -l

quatro

SergPro, на старый ноут легко поставил, а на новый не получается?

Так ведь Виндовс-10, а её просто так на диск с разметкой mbr поставить нельзя.Значит либо gpt у тебя, либо Виндовс установлена специальным сложным образом. Какая у тебя разметка? Начни с выяснения этого:

Есть ещё одна возможная, но маловероятная причина, чтобы её исключить нужен с установочной флешки Ubuntu, вывод команд

Код: [Выделить]

sudo parted -l
или
sudo fdisk -l

Вот эту причину считаю наиболее вероятной: незнание того какая разметка диска и из-за этого неправильный способ установки.

Дюшик

anchos,
Про разметку диска сказано в посте №8. 10-ка на MBR диск устанавливается без проблем.

I have been trying to install Ubuntu on a GPT disk, for 2 days, now. The installation goes perfect, no errors, but when I go to boot up, nothing. No bootable media found. I created a bios_grub and an ESP, bootable partition. I am sure it is a x64 usb key. Another querk is the installer will only allow me to put the boot record on /dev/sda, not /dev/sda1, the bootable ESP partition.

The installer, however, puts nothing in the ESP partition and, as far as I can tell, Nothing goes into the bios_grub partition, either, but it shouldn’t need anything in the bios_grub, since this is a UEFI boot, not legacy.

In an attempt to correct the issue, these are the steps I’ve taken, to try to manually install grub.

Code:

[ -d /sys/firmware/efi ] && echo "EFI boot on HDD" || echo "Legacy boot on HDD"
EFI boot on HDD

Code:

sudo gdisk -l /dev/sda
GPT fdisk (gdisk) version 1.0.1

Partition table scan:
  MBR: protective
  BSD: not present
  APM: not present
  GPT: present

Found valid GPT with protective MBR; using GPT.
Disk /dev/sda: 976773168 sectors, 465.8 GiB
Logical sector size: 512 bytes
Disk identifier (GUID): 97F58661-5F72-4C9F-BF37-81D0D0C36643
Partition table holds up to 128 entries
First usable sector is 34, last usable sector is 976773134
Partitions will be aligned on 2048-sector boundaries
Total free space is 2029 sectors (1014.5 KiB)

Number  Start (sector)    End (sector)  Size       Code  Name
   1            2048          391167   190.0 MiB   EF00  
   2          411648         8742911   4.0 GiB     8200  
   3         8742912       218458111   100.0 GiB   8300  
   4       218458112       976773119   361.6 GiB   8300  
   5          391168          411647   10.0 MiB    EF02

Code:

efibootmgr
BootCurrent: 0007
Timeout: 2 seconds
BootOrder: 0001,0002,0007,0005,0006,0000
Boot0000* ubuntu
Boot0001* USB Floppy/CD
Boot0002* USB Hard Drive
Boot0005  USB Floppy/CD
Boot0006  Hard Drive
Boot0007* UEFI: JetFlashTranscend 16GB 1100

Code:

sudo efibootmgr -b 0 -B
BootCurrent: 0007
Timeout: 2 seconds
BootOrder: 0001,0002,0007,0005,0006
Boot0001* USB Floppy/CD
Boot0002* USB Hard Drive
Boot0005  USB Floppy/CD
Boot0006  Hard Drive
Boot0007* UEFI: JetFlashTranscend 16GB 1100

Code:

sudo efibootmgr -c -d /dev/sda -p 1 -w -L ubuntu
BootCurrent: 0007
Timeout: 2 seconds
BootOrder: 0000,0001,0002,0007,0005,0006
Boot0001* USB Floppy/CD
Boot0002* USB Hard Drive
Boot0005  USB Floppy/CD
Boot0006  Hard Drive
Boot0007* UEFI: JetFlashTranscend 16GB 1100
Boot0000* ubuntu

Code:

mount /dev/sda3 /mnt
sudo mkdir /mnt/efi
sodu mount /dev/sda1 /mnt/efi

Code:

sudo apt-get install grub-efi-amd64
Reading package lists... Done
Building dependency tree       
Reading state information... Done
The following additional packages will be installed:
  grub-efi-amd64-bin
The following packages will be REMOVED:
  grub-gfxpayload-lists grub-pc
The following NEW packages will be installed:
  grub-efi-amd64 grub-efi-amd64-bin
0 upgraded, 2 newly installed, 2 to remove and 0 not upgraded.
Need to get 0 B/724 kB of archives.
After this operation, 2,426 kB of additional disk space will be used.
Do you want to continue? [Y/n] y
Get:1 cdrom://Ubuntu 16.04.2 LTS _Xenial Xerus_ - Release amd64 (20170215.2) xenial/main amd64 grub-efi-amd64-bin amd64 2.02~beta2-36ubuntu3.7 [658 kB]
Get:2 cdrom://Ubuntu 16.04.2 LTS _Xenial Xerus_ - Release amd64 (20170215.2) xenial/main amd64 grub-efi-amd64 amd64 2.02~beta2-36ubuntu3.7 [66.1 kB]
Preconfiguring packages ...
(Reading database ... 193482 files and directories currently installed.)
Removing grub-gfxpayload-lists (0.7) ...
Removing grub-pc (2.02~beta2-36ubuntu3.7) ...
Processing triggers for man-db (2.7.5-1) ...
Selecting previously unselected package grub-efi-amd64-bin.
(Reading database ... 193462 files and directories currently installed.)
Preparing to unpack .../grub-efi-amd64-bin_2.02~beta2-36ubuntu3.7_amd64.deb ...
Unpacking grub-efi-amd64-bin (2.02~beta2-36ubuntu3.7) ...
Selecting previously unselected package grub-efi-amd64.
Preparing to unpack .../grub-efi-amd64_2.02~beta2-36ubuntu3.7_amd64.deb ...
Unpacking grub-efi-amd64 (2.02~beta2-36ubuntu3.7) ...
Setting up grub-efi-amd64-bin (2.02~beta2-36ubuntu3.7) ...
Setting up grub-efi-amd64 (2.02~beta2-36ubuntu3.7) ...

Code:

sudo rm -rf /mnt/boot/grub

Code:

sudo grub-install --boot-directory /mnt/boot --bootloader-id=ubuntu --target=x86_64-efi --efi-directory=/mnt/efi/ --recheck --debug /dev/sda1
grub-install: info: adding a relocation entry for 0xcbd8.
grub-install: info: adding a relocation entry for 0xcbe8.
grub-install: info: adding a relocation entry for 0xcbf0.
grub-install: info: adding 192 padding fixup entries.
grub-install: info: writing 904 bytes of a fixup block starting at 0xc000.
grub-install: info: reading /usr/lib/grub/x86_64-efi/fshelp.mod.
grub-install: info: reading /usr/lib/grub/x86_64-efi/ext2.mod.
grub-install: info: reading /usr/lib/grub/x86_64-efi/part_gpt.mod.
grub-install: info: kernel_img=0x236ec10, kernel_size=0x18800.
grub-install: info: the core size is 0x1c5d0.
grub-install: info: writing 0x1d800 bytes.
grub-install: info: copying `/mnt/boot/grub/x86_64-efi/core.efi' -> `/mnt/efi/EFI/ubuntu/grubx64.efi'.
grub-install: info: Registering with EFI: distributor = `ubuntu', path = `EFIubuntugrubx64.efi', ESP at hostdisk//dev/sda,gpt1.
grub-install: info: executing efibootmgr --version </dev/null >/dev/null.
grub-install: info: executing modprobe -q efivars.
grub-install: info: executing efibootmgr -b 0000 -B.
BootCurrent: 0007
Timeout: 2 seconds
BootOrder: 0001,0002,0007,0005,0006
Boot0001* USB Floppy/CD
Boot0002* USB Hard Drive
Boot0005  USB Floppy/CD
Boot0006  Hard Drive
Boot0007* UEFI: JetFlashTranscend 16GB 1100
grub-install: info: executing efibootmgr -c -d /dev/sda -p 1 -w -L ubuntu -l EFIubuntugrubx64.efi.
BootCurrent: 0007
Timeout: 2 seconds
BootOrder: 0000,0001,0002,0007,0005,0006
Boot0001* USB Floppy/CD
Boot0002* USB Hard Drive
Boot0005  USB Floppy/CD
Boot0006  Hard Drive
Boot0007* UEFI: JetFlashTranscend 16GB 1100
Boot0000* ubuntu
Installation finished. No error reported.

Code:

ubuntu@ubuntu:/mnt/boot$ ls
abi-4.8.0-36-generic         memtest86+.bin
config-4.8.0-36-generic      memtest86+.elf
efi                          memtest86+_multiboot.bin
grub                         System.map-4.8.0-36-generic
initrd.img-4.8.0-36-generic  vmlinuz-4.8.0-36-generic

This is the new grub folder…

Code:

ubuntu@ubuntu:/mnt/boot/grub$ ls
fonts  grubenv  locale  x86_64-efi

This is the EFI folder on the ESP partition

Code:

ubuntu@ubuntu:/mnt/efi/EFI/ubuntu$ ls
grubx64.efi

Code:

for i in /sys /proc /run /dev; do sudo mount --bind "$i" "/mnt$i"; done
sudo chroot /mnt
update-grub
Generating grub configuration file ...
Warning: Setting GRUB_TIMEOUT to a non-zero value when GRUB_HIDDEN_TIMEOUT is set is no longer supported.
Found linux image: /boot/vmlinuz-4.8.0-36-generic
Found initrd image: /boot/initrd.img-4.8.0-36-generic
Adding boot menu entry for EFI firmware configuration
done

Code:

[ -d /sys/firmware/efi ] && echo "EFI boot on HDD" || echo "Legacy boot on HDD"
EFI boot on HDD

Results of /etc/fstab:

Code:

UUID=8ad57035-0736-40bd-a119-9bf0f8f9282d /               ext4    errors=remoun$
# /boot/efi was on /dev/sda1 during installation
UUID=0E4C-314A  /boot/efi       vfat    umask=0077      0       1
# /home was on /dev/sda4 during installation
UUID=a30fd7f5-ed94-446a-8835-c896f5403919 /home           ext4    defaults     $
# swap was on /dev/sda2 during installation
UUID=c489e270-c9e1-445e-8e4b-4062b52fb3b0 none            swap    sw           $

Code:

sudo blkid
...
/dev/sda1: UUID="0E4C-314A" TYPE="vfat" PARTUUID="b2953c8b-9474-488d-82bc-982127abb50a"
...

Even after all that, STILL, no boot.

See Boot-Repair in my signature below and follow the instructions there to run the Boot-Info-Script.

Do not run the default repair just yet but simply copy back here the pastebin link you get which will show us a lot more about your system.

Too long to post. Here is the link to Pastebin…

https://paste.ubuntu.com/24453957/

When doing a UEFI install, grub will be installed /dev/sda. The installer will find your ESP partition on sda, and put grub boot files on it in a folder named Ubuntu. In fact, any other selection you make is ignored by the installer.

With UEFI, you don’t need bios grub partition, but it makes no difference if it is there.

efibootmgr should be configured with ‘ubuntu’ entry first in boot order. That also should be automatically handled by the installer.

If you run sudo efibootmgr -v
you can see details, including the partition number the UEFI boot manager it is looking at for EFI system partition, and the specific file.

I would in Boot-Repair’s advanced mode run the full uninstall/reinstall of grub.
Be sure to be in UEFI boot mode as you were when you ran Summary Report.

It does also show grub installed to gpt’s protective MBR for BIOS boot and core.img in first sector of bios_grub. The bios_grub only has to be 1 or 2MB.
Just do not boot in BIOS mode, but it may actually work until updates get thing out of sync.
There are a few threads on making systems boot with both UEFI & BIOS which looks you have have or will have once booting.

What brand/model system or what motherboard?
What video card/chip?

Originally Posted by Dennis N

When doing a UEFI install, grub will be installed /dev/sda. The installer will find your ESP partition on sda, and put grub boot files on it in a folder named Ubuntu. In fact, any other selection you make is ignored by the installer.

With UEFI, you don’t need bios grub partition, but it makes no difference if it is there.

efibootmgr should be configured with ‘ubuntu’ entry first in boot order. That also should be automatically handled by the installer.

If you run sudo efibootmgr -v
you can see details, including the partition number the UEFI boot manager it is looking at for EFI system partition, and the specific file.

Here is the result of sudo efibootmgr -v

Code:

ubuntu@ubuntu:~$ sudo efibootmgr -v
BootCurrent: 0007
Timeout: 2 seconds
BootOrder: 0001,0002,0007,0005,0006,0000
Boot0000* ubuntu    VenHw(99e275e7-75a0-4b37-a2e6-c5385e6c00cb)
Boot0001* USB Floppy/CD    VenMedia(b6fef66f-1495-4584-a836-3492d1984a8d,0500000001)..BO
Boot0002* USB Hard Drive    VenMedia(b6fef66f-1495-4584-a836-3492d1984a8d,0200000001)..BO
Boot0005  USB Floppy/CD    VenMedia(b6fef66f-1495-4584-a836-3492d1984a8d,0500000000)..BO
Boot0006  Hard Drive    VenMedia(b6fef66f-1495-4584-a836-3492d1984a8d,0200000000)..BO
Boot0007* UEFI: JetFlashTranscend 16GB 1100    PciRoot(0x0)/Pci(0x10,0x0)/USB(2,0)/HD(1,MBR,0x32,0x800,0x1d6b800)..BO

Originally Posted by oldfred

I would in Boot-Repair’s advanced mode run the full uninstall/reinstall of grub.
Be sure to be in UEFI boot mode as you were when you ran Summary Report.

It does also show grub installed to gpt’s protective MBR for BIOS boot and core.img in first sector of bios_grub. The bios_grub only has to be 1 or 2MB.
Just do not boot in BIOS mode, but it may actually work until updates get thing out of sync.
There are a few threads on making systems boot with both UEFI & BIOS which looks you have have or will have once booting.

What brand/model system or what motherboard?
What video card/chip?

It is an HP Pavilion 20, all in one.

Can’t I delete bios_grub and use the esp partition? Am I correct that bios_grub is only used for legacy bios installations?

Here is the result of sudo efibootmgr -v

In reference to your display in post #6, it is not what I expected. Some details are missing. So that you can see what I was talking about, all my machines here give an output like this:

Code:

dmn@Sydney:~$ sudo efibootmgr -v
[sudo] password for dmn: 
BootCurrent: 0001
Timeout: 1 seconds
BootOrder: 0001,0000,0007,000A,000B,000D,000C,000E,000F,0010,0011,0005
Boot0000* ubuntu	HD(1,GPT,a1e435e2-5bbe-47f1-af26-a8efc2b58fd1,0x800,0x100000)/File(EFIUBUNTUSHIMX64.EFI)
Boot0001* Manjaro	HD(1,GPT,8e6dba8f-5bdf-4b99-b7a4-2730717b1dba,0x800,0x64000)/File(EFIMANJAROGRUBX64.EFI)
Boot0007* Korora	HD(14,GPT,20ebbadc-6db4-43c6-b77c-ba4c3a6139d1,0x2042c800,0x28000)/File(EFIFEDORASHIM.EFI)
Boot000E* ubuntu	HD(1,GPT,a1e435e2-5bbe-47f1-af26-a8efc2b58fd1,0x800,0x100000)/File(EFIUBUNTUGRUBX64.EFI)..BO
Boot000F* UEFI OS	HD(1,GPT,8e6dba8f-5bdf-4b99-b7a4-2730717b1dba,0x800,0x64000)/File(EFIBOOTBOOTX64.EFI)..BO
Boot0010* UEFI OS	HD(10,GPT,23ba857f-57de-4a5e-ada4-c25ca0f4515a,0x16bac800,0x28000)/File(EFIBOOTBOOTX64.EFI)..BO
Boot0011* UEFI OS	HD(14,GPT,20ebbadc-6db4-43c6-b77c-ba4c3a6139d1,0x2042c800,0x28000)/File(EFIBOOTBOOTX64.EFI)..BO

Some garbage entries omitted here.

From this I can read the partition number of the EFI system partition, and the path to the boot file. For ubuntu, partition is #1 (first number inside the parentheses), and path is EFIUBUNTUSHIMX64.EFI.

This currently boots to Manjaro’s grub (ESP is part 1 on sdb — notice different UUID for the partition), but if I wanted to boot Ubuntu’s grub, I would need to switch boot order to get 0000 first:

sudo efibootmgr -o 0000,0001,0007

Entry 000E should also boot Ubuntu.

Your Ubuntu entry with efibootmgr may be the BIOS boot option. Not exactly sure how BIOS boot shows in efibootmgr.

But as Dennis N shows you do not have the typical UEFI ubuntu boot entries.

And you do not need bios_grub with UEFI boot. But I have most of my drives configured for both the ESP & bios_grub as first two partitions as neither is really large.

But with HP having the Ubuntu UEFI entry may not matter.
HP violates UEFI standards and uses description as part of boot. And only valid description is «Windows Boot Manager» for some reason.
If only booting Ubuntu we can make a UEFI entry that says the Windows description but boots shim or grub.
If dual booting we make a fallback or hard drive UEFI boot entry. Many HP already have the UEFI entry. And now Boot-Repair copies shimx64.efi to /EFI/Boot/bootx64.efi which is a hard drive default or fallback boot.

Run the Boot-Repair full reinstall of grub. And check the «use the standard efi file» option. That does the file copy.
Always check with
sudo efibootmgr -b

sudo efibootmgr -c -L «UEFI Hard drive» -l «EFIBootbootx64.efi»

efibootmgr defaults to sda1, more in case others see thread and ESP is not sda1.
sudo efibootmgr -c -g -w -L «UEFI hard drive» -l ‘EFIBootbootx64.efi’ -d /dev/sdX -p Y
sdX is drive, Y is efi partition , if sda2 for example
sudo efibootmgr -c -g -w -L «UEFI hard drive» -l ‘EFIBootbootx64.efi’ -d /dev/sda -p 2

If that does not work you can add Windows entry the same way.

If Description has to be Windows then change UEFI description. Assumes ESP is sda1.
sudo efibootmgr -c -L «Windows Boot Manager» -l «EFIubuntushimx64.efi»

Copy shimx64.efi to /EFI/Boot/bootx64.efi
http://ubuntuforums.org/showthread.php?t=2247186
Boot-Repair should automatically do copy file with ‘use standard EFI file’:

See also link in my signature for some other alternative ways to get difficult systems to boot. The rEFInd boot manage is also popular.

I’m not disagreeing with you… believe me. The question is, why is it doing that?

I deleted the ubuntu entry, using

Code:

sudo efibootmgr -b 0 - B

, which worked. I then ran the efibootmgr command, used by grub-install,

Code:

sudo efibootmgr -c -d /dev/sda -p 1 -w -L ubuntu -l EFIubuntugrubx64.efi

then ran Here is the output. I’ll reboot and see if that entry stays there.

Code:

sudo efibootmgr -v
BootCurrent: 0007
Timeout: 2 seconds
BootOrder: 0003,0001,0002,0007,0005,0006
Boot0001* USB Floppy/CD    VenMedia(b6fef66f-1495-4584-a836-3492d1984a8d,0500000001)..BO
Boot0002* USB Hard Drive    VenMedia(b6fef66f-1495-4584-a836-3492d1984a8d,0200000001)..BO
Boot0003* ubuntu    HD(1,GPT,b2953c8b-9474-488d-82bc-982127abb50a,0x800,0x5f000)/File(EFIubuntugrubx64.efi) <- Notice how there are no "". I wonder if grub-install is not putting them, as well. I enclosed the path in quotes and it now shows, correctly. 
Boot0005  USB Floppy/CD    VenMedia(b6fef66f-1495-4584-a836-3492d1984a8d,0500000000)..BO
Boot0006  Hard Drive    VenMedia(b6fef66f-1495-4584-a836-3492d1984a8d,0200000000)..BO
Boot0007* UEFI: JetFlashTranscend 16GB 1100    PciRoot(0x0)/Pci(0x10,0x0)/USB(2,0)/HD(1,MBR,0x32,0x800,0x1d6b800)..BO

After a reboot, it’s back to the same thing.

Code:

sudo efibootmgr -v
Timeout: 2 seconds
BootOrder: 0001,0002,0007,0005,0006,0000
Boot0000* ubuntu    VenHw(99e275e7-75a0-4b37-a2e6-c5385e6c00cb)
Boot0001* USB Floppy/CD    VenMedia(b6fef66f-1495-4584-a836-3492d1984a8d,0500000001)..BO
Boot0002* USB Hard Drive    VenMedia(b6fef66f-1495-4584-a836-3492d1984a8d,0200000001)..BO
Boot0005  USB Floppy/CD    VenMedia(b6fef66f-1495-4584-a836-3492d1984a8d,0500000000)..BO
Boot0006  Hard Drive    VenMedia(b6fef66f-1495-4584-a836-3492d1984a8d,0200000000)..BO
Boot0007* UEFI: JetFlashTranscend 16GB 1100    PciRoot(0x0)/Pci(0x10,0x0)/USB(2,0)/HD(1,MBR,0x32,0x800,0x1d6b800)..BO

Here’s something else to ponder… there is an option in the «bios» menu to run an EFI application. When I do that, it asks me to choose a hard drive, then shows the path of the EFI folder and, eventually, the grubx64.efi. When I select it, Ubuntu boots from the hard drive. I suspect the issue is whatever is causing the EFI to re-write the entry.

Oh, I’m manually selecting the UEFI record, «ubuntu» in the boot menu, to make sure I get that one. I didn’t ignore the comment about setting 0000, first in the list of the boot order.