On Wed, Sep 14, 2016 at 9:06 AM, Gary Stainburn <gary@xxxxxxxxxxxxxx> wrote:
> I don't know if this additional information helps. Looking at he efibootmgr
> output, is the centos entry pointing to the right place?
>
> Also, any idea why the update isn't being make permenant?
Probably because the specified file wasn't found by the firmware on
partition 1, so it removed what it thinks is a bogus entry. Just a
guess.
>
> Number Start End Size File system Name Flags
> 1 1049kB 683MB 682MB ntfs Basic data partition hidden,
> 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 the entire boot order, separated
by commas.
I have no idea what RC at the end of these lines means though.
--
Chris Murphy
_______________________________________________
CentOS mailing list
CentOS@xxxxxxxxxx
https://lists.centos.org/mailman/listinfo/centos
