View previous topic :: View next topic |
Author |
Message |
guerro Guru
Joined: 21 Jun 2004 Posts: 402 Location: Brescia
|
Posted: Wed Dec 16, 2015 3:43 pm Post subject: efibootmgr doesn't create correct entry in UEFI Boot Menu |
|
|
When I execute
Code: | efibootmgr --create --gpt --disk /dev/nvme0n1 --part 2 --write-signature --label "Gentoo" --loader '\EFI\Boot\bootx64.efi' |
efibootmanager create entry, but with non signature and strange parameter of hard disk
When I reboot , system boot from "UEFI OS" and entry "Gentoo" has only "VenHw(0000000000000000000)", intead entry "UEFI OS" seems to have correct values (again "file")
I don't understand what it's wrong.
Can someone help me? _________________ (.(*. .*).)
.. G u e r r o ..
(.(.* *.).)
Last edited by guerro on Tue Dec 22, 2015 2:44 pm; edited 1 time in total |
|
Back to top |
|
|
khayyam Watchman
Joined: 07 Jun 2012 Posts: 6227 Location: Room 101
|
Posted: Wed Dec 16, 2015 5:02 pm Post subject: |
|
|
guerro ... can you provide the output of the following:
Code: | # gdisk -l /dev/nvme0n1
# efibootmgr -v |
... also, with your command if you add '-v' you should get more verbose messages.
best ... khay |
|
Back to top |
|
|
guerro Guru
Joined: 21 Jun 2004 Posts: 402 Location: Brescia
|
Posted: Wed Dec 16, 2015 11:07 pm Post subject: |
|
|
Code: | gdisk -l /dev/nvme0n1
GPT fdisk (gdisk) version 0.8.10
Partition table scan:
MBR: protective
BSD: not present
APM: not present
GPT: present
Found valid GPT with protective MBR; using GPT.
Disk /dev/nvme0n1: 500118192 sectors, 238.5 GiB
Logical sector size: 512 bytes
Disk identifier (GUID): 45B7C053-FEB8-475D-9941-DA44BBA0FF1B
Partition table holds up to 128 entries
First usable sector is 34, last usable sector is 500118158
Partitions will be aligned on 2048-sector boundaries
Total free space is 4029 sectors (2.0 MiB)
Number Start (sector) End (sector) Size Code Name
1 2048 6143 2.0 MiB EF02 grub
2 6144 268287 128.0 MiB EF00 boot
3 268288 33822719 16.0 GiB 8300 swap
4 33822720 500116143 222.3 GiB 8300 rootfs |
Before reboot:
Code: | efibootmgr --verbose -c -w -d /dev/nvme0n1 -p 2 -L "Gentoo OS" -l '\EFI\Boot\bootx64.efi'
BootCurrent: 0001
Timeout: 1 seconds
BootOrder: 0000,0001
Boot0001* UEFI OS HD(2,GPT,1741bc35-e7a2-4daa-834d-ace0b2d88aba,0x1800,0x40000)/File(\EFI\BOOT\BOOTX64.EFI)..BO
Boot0000* Gentoo OS HD(2,0,00000000000000000000000000000000,0x0,0x0)/File(\EFI\Boot\bootx64.efi) |
...Just a moment.... After reboot
Code: | efibootmgr -v
BootCurrent: 0001
Timeout: 1 seconds
BootOrder: 0001,0000
Boot0000* Gentoo OS VenHw(99e275e7-75a0-4b37-a2e6-c5385e6c00cb)
Boot0001* UEFI OS HD(2,GPT,1741bc35-e7a2-4daa-834d-ace0b2d88aba,0x1800,0x40000)/File(\EFI\BOOT\BOOTX64.EFI)..BO |
_________________ (.(*. .*).)
.. G u e r r o ..
(.(.* *.).) |
|
Back to top |
|
|
khayyam Watchman
Joined: 07 Jun 2012 Posts: 6227 Location: Room 101
|
Posted: Thu Dec 17, 2015 1:07 pm Post subject: |
|
|
guerro ...
I have no idea about what sort of efi executable this "UEFI OS" is, but it seems to be altering the boot entry, you could switch the BootOrder, delete that entry, or install something like rEFInd in its place (after backing up {ESP}\EFI\BOOT\BOOTX64.EFI). Actually, I wonder why you need two ESP's (EFI System Partition), you should be to make an entry pointing the HD rather than the PCIe SSD.
So, rather than I recommend you perhaps break something, I suggest you search for this particular efi executable, and see if there is some reason why you need it. I'd probably just remove it and use some other executable in its place ... but that may be hasty (as, again, I'm not sure what it is or what it does).
best ... khay |
|
Back to top |
|
|
guerro Guru
Joined: 21 Jun 2004 Posts: 402 Location: Brescia
|
Posted: Thu Dec 17, 2015 1:17 pm Post subject: |
|
|
Thx khayyam
I'll try to find out something....
Fortunelly I can wait to resolve this issue. _________________ (.(*. .*).)
.. G u e r r o ..
(.(.* *.).) |
|
Back to top |
|
|
tlix n00b
Joined: 15 Jul 2015 Posts: 8
|
Posted: Wed Feb 05, 2020 3:51 pm Post subject: |
|
|
though this being years old, I came across similar issue recently, but for my case, the direct cause is the small size of efi partition.
From the test on my laptop, so long as the efi partition size <= 32M, the problem happens, with a larger size, it works fine |
|
Back to top |
|
|
|
|
You cannot post new topics in this forum You cannot reply to topics in this forum You cannot edit your posts in this forum You cannot delete your posts in this forum You cannot vote in polls in this forum
|
|