Re: update to Centos7.4: Failed to open \EFI\BOOT\grubx64.efi - Not Found

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]





On 01/12/2018 08:24 PM, johan.vermeulen7@xxxxxxxxxx wrote:


----- Oorspronkelijk bericht -----
Van: "Adrian Jenzer" <a.jenzer@xxxxxxxxxxxxxxxxxx>
Aan: "CentOS mailing list" <centos@xxxxxxxxxx>
Verzonden: Dinsdag 9 januari 2018 16:56:57
Onderwerp: Re:  update to Centos7.4: Failed to open \EFI\BOOT\grubx64.efi - Not Found

-----Original Message-----
From: CentOS [mailto:centos-bounces@xxxxxxxxxx] On Behalf Of johan.vermeulen7@xxxxxxxxxx
Sent: Dienstag, 9. Januar 2018 16:34
To: CentOS mailing list
Subject:  update to Centos7.4: Failed to open \EFI\BOOT\grubx64.efi - Not Found

Hello All,

updating from Centos7.3 to Centos7.4 rendered one of our laptops unbootable.
EM:
Failed to open \EFI\BOOT\grubx64.efi - Not Found
Failed to load image \EFI\BOOT\grubx64.efi: Not Found
start_image() returned Not Found

How could this occur because of an update and how to fix this?

What I tried is booting from centos usb, chroot to /mnt/sysimage and gave command:
efibootmgr --create --label CentOS --disk /dev/sda1 --loader "\EFI\centos\shim.efi"

This gave no EM, but booting remains impossible.

I have to say I don't know whether to try grub2 of efibootmgr commands.

Any help would be very much appreciated.

Greetings, J.
_______________________________________________
CentOS mailing list
CentOS@xxxxxxxxxx
https://lists.centos.org/mailman/listinfo/centos



Hi Johan

I remember I had a similar issue and I resolved it by copying grubx64.efi from /centos :
cp /boot/efi/EFI/centos/grubx64.efi /boot/efi/EFI/BOOT


regards
Adrian

Adrian,

thanks for helping me out.
That didn't fix the system. The EM has changed though, it now simply says " no bootable device".

Greetings, J.

_______________________________________________
CentOS mailing list
CentOS@xxxxxxxxxx
https://lists.centos.org/mailman/listinfo/centos
_______________________________________________
CentOS mailing list
CentOS@xxxxxxxxxx
https://lists.centos.org/mailman/listinfo/centos


Hi Johan
appart from the above copy of the boot file, would you probably need something like this:

efibootmgr -b xxxx -l EFI/BOOT/grubx64.efi

i.e. tell BOOTxxxx to use the intended boot file.

xxxx may be found out via

efibootmgr -v
BootCurrent: 0000
Timeout: 0 seconds
No BootOrder is set; firmware will attempt recovery
Boot0000* Notebook Hard Drive BBS(HD,,0x0)....................................................................... Boot0001* Notebook Ethernet BBS(128,,0x0)........................E.............................................. Boot0002* Centos HD(1,GPT,068e45cc-b2b6-4688-9974-ad7d27e419f8,0x800,0x7a000)/File(EFIcentosgrubx64.efi)

xxxx by default is 0000

suomi

_______________________________________________
CentOS mailing list
CentOS@xxxxxxxxxx
https://lists.centos.org/mailman/listinfo/centos



[Index of Archives]     [CentOS]     [CentOS Announce]     [CentOS Development]     [CentOS ARM Devel]     [CentOS Docs]     [CentOS Virtualization]     [Carrier Grade Linux]     [Linux Media]     [Asterisk]     [DCCP]     [Netdev]     [Xorg]     [Linux USB]


  Powered by Linux