search for: 84ee

...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...

...me reason the changes are not permenant, and if left alone, the laptop boots into Win8. I'm out of ideas now. Gary [root at gary ~]# efibootmgr -v BootCurrent: 0003 Timeout: 0 seconds BootOrder: 0002,3002,0000,0003,2001,2002,2003 Boot0000* Fedora HD(2,145800,64000,14c4ac1d-abd8-4121-84ee-c05a825920de)File(\EFI\fedora\shim.efi)RC Boot0002* Windows Boot Manager HD(2,145800,64000,14c4ac1d-abd8-4121-84ee-c05a825920de)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.}..................

Morning all, I have a HP Envy dual boot system (Win8 for serious stuff, i.e. Train Sim and Flight Sim) and Centos 7 for everything else. In the past I've had the occasional problem where an update on the windows side has updated the UEFI boot sequence but using efibootmgr has always fixed it. On Friday I discovered that my HDD was failing so I tried using Clonezilla to move it on to a new

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 w...

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&quo...

All of the following is still under the Centos 7 KDE Live CD: If I mount /dev/sda2 on /media and have a look, this is the valid EFI filesystem, including the Fedora and Centos entries. If I try to mount /dev/sda6 on /media it looks to be a valid /boot filesystem. If I mount /dev/sda6 as /boot and mount /dev/sda2 as /boot/efi before running Jim's efibootmgr command will I fix the problem

...[root at localhost boot]# efibootmgr -v BootCurrent: 0000 Timeout: 0 seconds BootOrder: 0003,2002,0002,3002,0001,2001,2003 Boot0000* Internal CD/DVD ROM Drive (UEFI) ACPI(a0341d0,0)PCI(1f,2)SATA(2,0,0)CD-ROM(1,2b,272c)RC Boot0001* Fedora HD(2,145800,64000,14c4ac1d-abd8-4121-84ee-c05a825920de)File(\EFI\fedora\shim.efi)RC Boot0002* Windows Boot Manager HD(2,145800,64000,14c4ac1d-abd8-4121-84ee-c05a825920de)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.}..................

Hi Jim, Thanks for this. I looked into what you said, and once happy I ran the command you gave. It appeared to work as it did not come up with any errors, and the output from efibootmgr showed 1) Centos had been added as an option and 2) it was the first in the boot sequence. However, when I rebooted the laptop went straight into Win8, and after rebooting back into KDE Live, the option is

...dden, > diag > 2 683MB 892MB 210MB fat16 EFI System Partition boot The proper command in this case is efibootmgr -c -d /dev/sda -p 2 -L CentOS -l \\EFI\\centos\\shim.efi efibootmgr -v is more rewarding > Boot0001* Fedora > HD(2,145800,64000,14c4ac1d-abd8-4121-84ee-c05a825920de)File(\EFI\fedora\shim.efi)RC Looks fine. But notice the boot order: BootOrder: 0003,2002,0002,3002,0001,2001,2003 That puts Fedora in 5th place. You need to use efibootmgr -n 0001 to do a one time boot of Fedora at next boot; or you need to use efibootmgr -o and explicitly change th...