search for: boot0000

...ds BootOrder: 0002,3002,0000,0003,0004,0005,2001,2002,2003 Boot0000* Linux Boot0002* Windows Boot Manager...

...image. In this ran efibootmgr which shows the same thing. I can fix the boot sequence, but that will not get me back the Centos entries. Can anyone suggest how I can do that? Gary [root at localhost ~]# efibootmgr BootCurrent: 0000 Timeout: 0 seconds BootOrder: 2002,0002,3002,0001,2001,2003 Boot0000* Internal CD/DVD ROM Drive (UEFI) Boot0001* Fedora Boot0002* Windows Boot Manager 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 localhost ~]#

...If I press <F9> I get the same options as in efibootmgr but the first option > "Windows Boot Manager" is selected. > > > > [root at gary ~]# efibootmgr > BootCurrent: 0004 > Timeout: 0 seconds > BootOrder: 0002,3002,0000,0003,0004,0005,2001,2002,2003 > 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 D...

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

...hanks for your reply! Too bad I never run this command when things were OK (in order to compare), 'cause now, what it says doesn't mention anything that seem related to the CentOS partition or I read wrong: BootCurrent: 0007 Timeout: 0 seconds BootOrder: 0001,0002,0003,0004,0005,0006,0007 Boot0000* Windows Boot Manager HD(1,GPT,a6b87338-9b9c-4a50-8fde-2447e8fdebb6,0x800,0xfa000)/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.}.................... Boot0001* UEFI: A400 NVMe SanDisk 512GB,...

...gr again. Once again, it looked to work perfectly, but for some 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....

...quence. However, when I rebooted the laptop went straight into Win8, and after rebooting back into KDE Live, the option is no longer there. This is the output after rebooting. [root at localhost liveuser]# efibootmgr BootCurrent: 0000 Timeout: 0 seconds BootOrder: 2002,0002,3002,0001,2001,2003 Boot0000* Internal CD/DVD ROM Drive (UEFI) Boot0001* Fedora Boot0002* Windows Boot Manager 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 localhost liveuser]# This is me havin...

At Mon, 28 May 2018 19:30:25 -0400 CentOS mailing list <centos at centos.org> wrote: > > On May 28, 2018, at 18:25, Robert Heller <heller at deepsoft.com> wrote: > > > I tried to run efibootmgr, but it wants a model named efivars loaded, but > > there is no such module available. > > Are you not running a CentOS kernel? That module should be available.

...> can find. > > > It should be the UUID of the partition, not of the VFAT volume. The > partition UUID is stored in the GPT.?? The volume UUID is stored in the > filesystem header (I believe). > > For example, on my laptop: > > # efibootmgr -v | grep Fedora > Boot0000* Fedora > PciRoot(0x0)/Pci(0x17,0x0)/Sata(2,65535,0)/HD(1,GPT,39484dd8-b1d9-47b2-b4d7-89dfe3ce5e09,0x800,0x12c000)/File(\EFI\fedora\shimx64.efi) > > # blkid | grep sda1 > /dev/sda1: LABEL="ESP" UUID="3850-574E" TYPE="vfat" PARTLABEL="EFI > System...

> On 1/9/19 2:30 AM, Gary Stainburn wrote: >> 1) The big problem with this is that it is dependant on sda for booting. >> I >> did find an aritcle on how to set up boot loading on multiple HDD's, >> including cloning /boot/efi but I now can't find it. Does anyone know >> of a >> similar article? > > > Use RAID1 for /boot/efi as well.? The

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

...ntos\shim.efi' there are a couple efi files inside /boot/efi/EFI/centos, but shim is the one to point to for secureboot to work properly. > Gary > > [root at localhost ~]# efibootmgr > BootCurrent: 0000 > Timeout: 0 seconds > BootOrder: 2002,0002,3002,0001,2001,2003 > Boot0000* Internal CD/DVD ROM Drive (UEFI) > Boot0001* Fedora > Boot0002* Windows Boot Manager > 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 local...

...lvm 5 978GB 1000GB 21.8GB ntfs Basic data partition hidden (parted) quit [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(\E...

...what it is -- it does not correspond to anything I > can find. It should be the UUID of the partition, not of the VFAT volume. The partition UUID is stored in the GPT.? The volume UUID is stored in the filesystem header (I believe). For example, on my laptop: # efibootmgr -v | grep Fedora Boot0000* Fedora PciRoot(0x0)/Pci(0x17,0x0)/Sata(2,65535,0)/HD(1,GPT,39484dd8-b1d9-47b2-b4d7-89dfe3ce5e09,0x800,0x12c000)/File(\EFI\fedora\shimx64.efi) # blkid | grep sda1 /dev/sda1: LABEL="ESP" UUID="3850-574E" TYPE="vfat" PARTLABEL="EFI System Partition" PARTUUID...

...to efibootmgr it is trying to boot \EFI\centos\shimaa64.efi, which doesn't exist (EFI\redhat\shimaa64.efi does). Those files are created by shim rpms and they are a total mess. I don't even know where to start or what to look for. `efibootmgr -v` shows 0000 in the beginning of BootOrder Boot0000* CentOS: HD (1,GPT,.......)/File(\EFI\centos\shimaa64.efi). Shim package has the following files/directories: $ rpm -qlp shim-aa64-12-1 /boot/efi/EFI/BOOT/BOOTAA64.EFI /boot/efi/EFI/BOOT/fbaa64.efi /boot/efi/EFI/redhat/BOOTAA64.CSV /boot/efi/EFI/redhat/mmaa64.efi /boot/efi/EFI/redhat/shim.efi /bo...

...entOS wrote: > Are you sure? Yes. > How is the EFI firmware going to know about the RAID1? It doesn't specifically.? Anaconda will create two EFI boot entries, each referring to one of the mirror components: # efibootmgr -v BootCurrent: 0001 Timeout: 1 seconds BootOrder: 0001,0000 Boot0000* CentOS Linux HD(1,GPT,534debcc-f3d6-417a-b5d4-10b4ba5c1f7d,0x800,0x5f000)/File(\EFI\CENTOS\SHIM.EFI) Boot0001* CentOS Linux HD(1,GPT,05883d1e-df21-4938-bfa1-ac11ff376572,0x800,0x5f000)/File(\EFI\CENTOS\SHIM.EFI) # blkid -p? -o value -s PART_ENTRY_UUID /dev/sda1 534debcc-f3d6-417a-b5d4-10b4ba5c1f...

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

...freshly installed system # exit ... disk, and partition number, pass to EFI Boot Manager # efibootmgr -c -d /dev/vda -p 1 -l /EFI/extlinux/syslinux.efi -L "Syslinux efi64" BootCurrent: 0002 Timeout: 0 seconds BootOrder: 0000,0002,0003 Boot0002* EFI DVD/CDROM Boot0003* EFI Internal Shell Boot0000* Syslinux efi64 And finally # reboot SW components & Co.: - QEMU/KVM - edk2.git-ovmf-x64 [2] - libvirt - virt-manager - Rawhide-Xfce-Live-1218.iso - syslinux-efi64 [1] [1] http://goo.gl/Gm4ffO /syslinux efi64 [2] UEFI with QEMU https://www.kraxel.org/repos Rawhide LiveCDVDs http://dl.fedo...

> It doesn't specifically.? Anaconda will create two EFI boot entries, > each referring to one of the mirror components: > > # efibootmgr -v > BootCurrent: 0001 > Timeout: 1 seconds > BootOrder: 0001,0000 > Boot0000* CentOS Linux > HD(1,GPT,534debcc-f3d6-417a-b5d4-10b4ba5c1f7d,0x800,0x5f000)/File(\EFI\CENTOS\SHIM.EFI) > Boot0001* CentOS Linux > HD(1,GPT,05883d1e-df21-4938-bfa1-ac11ff376572,0x800,0x5f000)/File(\EFI\CENTOS\SHIM.EFI) > # blkid -p? -o value -s PART_ENTRY_UUID /dev/sda1 > 534debcc-f3...

...should be the UUID of the partition, not of the VFAT volume. The > > partition UUID is stored in the GPT.?? The volume UUID is stored in the > > filesystem header (I believe). > > > > For example, on my laptop: > > > > # efibootmgr -v | grep Fedora > > Boot0000* Fedora > > PciRoot(0x0)/Pci(0x17,0x0)/Sata(2,65535,0)/HD(1,GPT,39484dd8-b1d9-47b2-b4d7-89dfe3ce5e09,0x800,0x12c000)/File(\EFI\fedora\shimx64.efi) > > > > # blkid | grep sda1 > > /dev/sda1: LABEL="ESP" UUID="3850-574E" TYPE="vfat" PARTLABEL=&q...