search for: bootnum

----- Original Message ----- | On Thu, Aug 18, 2016 at 11:57 AM, James A. Peltier <jpeltier at sfu.ca> wrote: | > Hi All, | > | > I have a Dell R710 that has 6x1TB in a RAID-5 configuration. | | | This is hardware RAID 5? Because it's pretty screwy how this ends up | working when using software RAID and might take additional | troubleshooting. Yes, it's a Dell R710XD |

...stale values because grub2-install also populates NVRAM with what will become the wrong entry. You'll need to use 'efibootmgr -v' to get a listing to find the bogus entry, which will be pointing to a path that includes grubx64.efi, note the boot number and then do 'efibootmgr -b <bootnum> -B' Where bootnum is the four digit value for the bogus entry. What should happen if there are no valid entries is shim.efi will work with fallback.efi to create a proper NVRAM entry. The proper entry can be found with the earlier grep efibootmgr command, and you can just use that, while...

...lues because | grub2-install also populates NVRAM with what will become the wrong | entry. You'll need to use 'efibootmgr -v' to get a listing to find the | bogus entry, which will be pointing to a path that includes | grubx64.efi, note the boot number and then do 'efibootmgr -b <bootnum> | -B' Where bootnum is the four digit value for the bogus entry. | | What should happen if there are no valid entries is shim.efi will work | with fallback.efi to create a proper NVRAM entry. The proper entry can | be found with the earlier grep efibootmgr command, and you can just | use...

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

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

...D(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 b...