thr3ads.net - CentOS - [CentOS] UEFI boot manager sequence problems HP Envy [May 2019]

If this information is useful, please help other people find it:
Share via:

Gary Stainburn

2019-May-30 09:50 UTC

[CentOS] UEFI boot manager sequence problems HP Envy

On Tuesday 28 May 2019 19:52:02 Jonathan Billings wrote:> I suggest running 'blkid' and 'efibootmgr -v', and
double-check that
> the UUID for the CentOS boot entry matches the UUID of the EFI disk.
> 
> You can delete and recreate the boot entry with 'efibootmgr', which
> will likely solve the problem.
> 
> It depends on the UEFI implementation, but when all the boot entries
> are wrong (UUID changed due to new disk) sometimes it has a fallback
> to find the Windows bootloader and choose it.
> 
Thanks Jonathan.

You're probably right about this as whever I try to do makes has effect.

I've been looking in to efibootmgr to see what I need to do to get it
working but so far with no luck.

When I run it with -v I don't see any UUID details, nor can i see how I
specify them.  One thing I have noticed is that in the blkid output below
everything refers to HD(2,...... Is that correct?

Below is one of many attempts to set the values correctly.

[root at gary ~]# efibootmgr -v
BootCurrent: 0004
Timeout: 0 seconds
BootOrder: 0002,3002,0000,0003,0004,0005,2001,2002,2003
Boot0000* Linux
HD(2,GPT,14c4ac1d-abd8-4121-84ee-c05a825920de,0x145800,0x64000)/File(\EFI\centos\shim.efi)
Boot0002* Windows Boot Manager 
HD(2,GPT,14c4ac1d-abd8-4121-84ee-c05a825920de,0x145800,0x64000)/File(\EFI\Microsoft\Boot\bootmgfw.efi)WINDOWS.........x...B.C.D.O.B.J.E.C.T.=.{.9.d.e.a.8.6.2.c.-.5.c.d.d.-.4.e.7.0.-.a.c.c.1.-.f.3.2.b.3.4.4.d.4.7.9.5.}....................
Boot0003* Fedora       
HD(2,GPT,14c4ac1d-abd8-4121-84ee-c05a825920de,0x145800,0x64000)/File(\EFI\fedora\shim.efi)
Boot0004* CentOS Linux 
HD(2,GPT,14c4ac1d-abd8-4121-84ee-c05a825920de,0x145800,0x64000)/File(\EFI\centos\shim.efi)
Boot0005* CentOS       
HD(2,GPT,14c4ac1d-abd8-4121-84ee-c05a825920de,0x145800,0x64000)/File(\EFI\centos\shimx64.efi)
Boot2001* USB Drive (UEFI)      RC
Boot2002* Internal CD/DVD ROM Drive (UEFI)      RC
Boot3000* Internal Hard Disk or Solid State Disk        RC
Boot3002* Internal Hard Disk or Solid State Disk        RC
[root at gary ~]# efibootmgr -o 4,2001,2002,2
BootCurrent: 0004
Timeout: 0 seconds
BootOrder: 0004,2001,2002,0002
Boot0000* Linux
Boot0002* Windows Boot Manager
Boot0003* Fedora
Boot0004* CentOS Linux
Boot0005* CentOS
Boot2001* USB Drive (UEFI)
Boot2002* Internal CD/DVD ROM Drive (UEFI)
Boot3000* Internal Hard Disk or Solid State Disk
Boot3002* Internal Hard Disk or Solid State Disk
[root at gary ~]# efibootmgr -v
BootCurrent: 0004
Timeout: 0 seconds
BootOrder: 0004,2001,2002,0002
Boot0000* Linux
HD(2,GPT,14c4ac1d-abd8-4121-84ee-c05a825920de,0x145800,0x64000)/File(\EFI\centos\shim.efi)
Boot0002* Windows Boot Manager 
HD(2,GPT,14c4ac1d-abd8-4121-84ee-c05a825920de,0x145800,0x64000)/File(\EFI\Microsoft\Boot\bootmgfw.efi)WINDOWS.........x...B.C.D.O.B.J.E.C.T.=.{.9.d.e.a.8.6.2.c.-.5.c.d.d.-.4.e.7.0.-.a.c.c.1.-.f.3.2.b.3.4.4.d.4.7.9.5.}....................
Boot0003* Fedora       
HD(2,GPT,14c4ac1d-abd8-4121-84ee-c05a825920de,0x145800,0x64000)/File(\EFI\fedora\shim.efi)
Boot0004* CentOS Linux 
HD(2,GPT,14c4ac1d-abd8-4121-84ee-c05a825920de,0x145800,0x64000)/File(\EFI\centos\shim.efi)
Boot0005* CentOS       
HD(2,GPT,14c4ac1d-abd8-4121-84ee-c05a825920de,0x145800,0x64000)/File(\EFI\centos\shimx64.efi)
Boot2001* USB Drive (UEFI)      RC
Boot2002* Internal CD/DVD ROM Drive (UEFI)      RC
Boot3000* Internal Hard Disk or Solid State Disk        RC
Boot3002* Internal Hard Disk or Solid State Disk        RC
[root at gary ~]# blkid
/dev/mapper/centos-root: UUID="08c18076-37b4-4f65-b550-e2633ac24d5d"
TYPE="xfs"
/dev/sda6: UUID="ifEKlz-O4SM-NevI-X4TQ-lQg2-0lAN-Jb7cZQ"
TYPE="LVM2_member"
PARTUUID="97e93e7c-a6cf-4532-8f7d-5c0e50987350"
/dev/sda1: LABEL="WINRE" UUID="8262E42362E41DA3"
TYPE="ntfs" PARTLABEL="Basic data partition"
PARTUUID="277e20d2-ee46-412b-babb-9b2249324ca4"
/dev/sda2: SEC_TYPE="msdos" UUID="1437-B8F4"
TYPE="vfat" PARTLABEL="EFI System Partition"
PARTUUID="14c4ac1d-abd8-4121-84ee-c05a825920de"
/dev/sda3: LABEL="Windows" UUID="1098EFF798EFD96C"
TYPE="ntfs" PARTLABEL="Basic data partition"
PARTUUID="f7cefd8f-73e7-4956-bb96-0c03ea21bff9"
/dev/sda4: UUID="12DC737EDC735B45" TYPE="ntfs"
PARTUUID="95f8994c-a8ad-48f5-9fbb-eda67c56f6e3"
/dev/sda5: UUID="de45b7f8-d072-4f7e-b9be-a62428db3fbb"
TYPE="xfs" PARTUUID="8c00cc67-1063-4889-bdce-6f6259ba1491"
/dev/sda8: LABEL="RECOVERY" UUID="74CCE22FCCE1EAF6"
TYPE="ntfs" PARTLABEL="Basic data partition"
PARTUUID="7c95ff6d-d945-4479-9100-f66aa81a403e"
/dev/mapper/centos-swap: UUID="30ca7d38-a0df-4473-a1d0-dc7a1fd41458"
TYPE="swap"
/dev/mapper/centos-home: UUID="abcedda1-b69b-441e-bced-23a66b2b85f6"
TYPE="xfs"
[root at gary ~]# df
Filesystem              1K-blocks      Used Available Use% Mounted on
/dev/mapper/centos-root  52403200   7424692  44978508  15% /
devtmpfs                  6016292         0   6016292   0% /dev
tmpfs                     6034084         0   6034084   0% /dev/shm
tmpfs                     6034084      9820   6024264   1% /run
tmpfs                     6034084         0   6034084   0% /sys/fs/cgroup
/dev/sda5                 1038336    229176    809160  23% /boot
/dev/sda2                  204576     85252    119324  42% /boot/efi
/dev/mapper/centos-home 688017172 428947768 259069404  63% /home
tmpfs                     1206820         8   1206812   1% /run/user/42
tmpfs                     1206820         0   1206820   0% /run/user/0
[root at gary ~]#

Jonathan Billings

2019-May-30 12:16 UTC

head link

[CentOS] UEFI boot manager sequence problems HP Envy

On Thu, May 30, 2019 at 10:50:16AM +0100, Gary Stainburn
wrote:> [root at gary ~]# efibootmgr -v
> BootCurrent: 0004
> Timeout: 0 seconds
> BootOrder: 0002,3002,0000,0003,0004,0005,2001,2002,2003
> Boot0000* Linux
HD(2,GPT,14c4ac1d-abd8-4121-84ee-c05a825920de,0x145800,0x64000)/File(\EFI\centos\shim.efi)
> [...]
> [root at gary ~]# blkid
> [...]
> /dev/sda2: SEC_TYPE="msdos" UUID="1437-B8F4"
TYPE="vfat" PARTLABEL="EFI System Partition"
PARTUUID="14c4ac1d-abd8-4121-84ee-c05a825920de"
> [...]
This is all I was asking you to check.  See the PARTUUID in the output
of blkid?  PARTUUID="14c4ac1d-abd8-4121-84ee-c05a825920de"
It matches the UUID of the boot entry:
HD(2,GPT,14c4ac1d-abd8-4121-84ee-c05a825920de,0x145800,0x6400\0)/File(\EFI\centos\shim.efi)

I do see you have 4 separate boot entries for Linux (one oddly called
fedora despite using the CentOS shim), you might do well to narrow
them down to just one. 
(efibootmgr -B -b <bootnum>)

If your BIOS has the ability to choose to boot from a file, I suggest
giving that a try, and try both /EFI/centos/shim.efi and
/EFI/centos/grubx64.efi.  Perhaps one or the other isn't working
anymore. 

-- 
Jonathan Billings <billings at negate.org>

Gary Stainburn

2019-May-30 12:35 UTC

head link

[CentOS] UEFI boot manager sequence problems HP Envy

On Thursday 30 May 2019 13:16:37 Jonathan Billings wrote:
> This is all I was asking you to check.  See the PARTUUID in the output
> of blkid?  PARTUUID="14c4ac1d-abd8-4121-84ee-c05a825920de"
> It matches the UUID of the boot entry:
>
HD(2,GPT,14c4ac1d-abd8-4121-84ee-c05a825920de,0x145800,0x6400\0)/File(\EFI\centos\shim.efi)
> 
> I do see you have 4 separate boot entries for Linux (one oddly called
> fedora despite using the CentOS shim), you might do well to narrow
> them down to just one. 
> (efibootmgr -B -b <bootnum>)
I had already started this process, as I read on a post that deleting an option
(or adding one) could possibly fix a corrupt database. I have now deleted all
unrequired options.
> 
> If your BIOS has the ability to choose to boot from a file, I suggest
> giving that a try, and try both /EFI/centos/shim.efi and
> /EFI/centos/grubx64.efi.  Perhaps one or the other isn't working
> anymore. 
I tried the option to boot from an EFI file.  All I got was:

NO VOLUME LABEL,
[Acpi(PNP0A03,0)/Pci(1F12)/Sata(0,0,0)/HD(Part2,Sig14CAC1D-ABD8-4121-84EE-C05A8259
20DE)]

I had the option to press enter to select an entry, which I did, and navigated
to /EFI/centos/shim.efi.

Doing this saw Centos boot successfully.  Presumably this means that the
selected file is valid, but not being used.

This is the current output from efibootmgr, but still does not give me what I
want, and resets on restart.  The options I deleted have stayed deleted though.

Boot3000* Internal Hard Disk or Solid State Disk
[root at gary ~]# efibootmgr -v
BootCurrent: 0004
Timeout: 4 seconds
BootOrder: 2001,2002,0004
Boot0002* Windows Boot Manager 
HD(2,GPT,14c4ac1d-abd8-4121-84ee-c05a825920de,0x145800,0x64000)/File(\EFI\Microsoft\Boot\bootmgfw.efi)WINDOWS.........x...B.C.D.O.B.J.E.C.T.=.{.9.d.e.a.8.6.2.c.-.5.c.d.d.-.4.e.7.0.-.a.c.c.1.-.f.3.2.b.3.4.4.d.4.7.9.5.}....................
Boot0004* CentOS Linux 
HD(2,GPT,14c4ac1d-abd8-4121-84ee-c05a825920de,0x145800,0x64000)/File(\EFI\centos\shim.efi)
Boot2001* USB Drive (UEFI)      RC
Boot2002* Internal CD/DVD ROM Drive (UEFI)      RC
Boot3000* Internal Hard Disk or Solid State Disk        RC
[root at gary ~]#

Seemingly Similar Threads

Search for more seemingly similar threads

CentOS - May 2019 - UEFI boot manager sequence problems HP Envy

[CentOS] UEFI boot manager sequence problems HP Envy

[CentOS] UEFI boot manager sequence problems HP Envy

[CentOS] UEFI boot manager sequence problems HP Envy

Seemingly Similar Threads