search for: bootcurrent

...ill valid. Once booted I then tried going through the process of running efibootmgr 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\bootmg...

...Order Notebook Hard Drive Internal CD/DVD ROM Drive USB Diskette on Key/USB Hard Drive USB CD/DVD ROM Drive ! Network Adapter 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...

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

...uck. 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\Micro...

...s the Windows 8 boot manager. I have managed to boot into a Centos 7 Live KDE 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...

...ve > USB Diskette on Key/USB Hard Drive > USB CD/DVD ROM Drive > ! Network Adapter > > 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)...

...ed to use --bootorder to make > sure the CentOS entry is first. Interesting.. thanks 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...

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

> 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

...can do something like: efibootmgr -c -d /dev/sda -p 1 -L "CentOS" -l '\EFI\centos\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...

...t4 6 213GB 214GB 524MB xfs 7 214GB 978GB 765GB 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* Windo...

Exactly what efibootmgr command are you using? Chris Murphy

...# set the boot order DVD, USB, Centos, Windows efibootmgr -o 2002,2001,0003,0002 # I have also tried 0003,0002,2002 # remove the expired Fedora option efibootmgr -b 0000 -B The output after the last command shows the EFI state exactly as I want it, but unfortunately, it isn't persistant BootCurrent: 0003 Timeout: 0 seconds BootOrder: 0002,3002,0003,2001,2002,2003 Boot0002* Windows Boot Manager Boot0003* CentOS Linux 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

On 1/10/19 8:35 AM, Simon Matter via CentOS 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_...

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

...409600 200M Microsoft basic data /dev/vda2 411648 1435647 1024000 500M Linux filesystem ... Switching from a 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:/...

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

...re the CentOS entry is first. > > Interesting.. thanks 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....

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

Hi there, I despise complexity and Grub has been giving me headaches on Voidlinux.. https://www.reddit.com/r/voidlinux/comments/gk5h5c/everytime_i_update_void_i_need_to_manually/ I've switched to Syslinux, but I have the following queries. ??sda1 vfat FAT32 D91B-36F7 190.7M 61% /boot ??sda2 ext4 1.0 0dd25845-8fa5-41e9-b82c-c63c27cf5d18