Failed to open \EFI\centos\grubx64.efi - Not Found
Re: I believe CentOS repos have been compromised
Please don't resort to insults.
I am asking about the iso filename as, at the present time it appears to me that you have some sort of problem with a UEFI install. Since the problem only occurs after updating the install, it is necessary to know which iso you installed from so that someone trying to replicate your problem can start from the same place. If you did your install with the 7.4 minimal iso and then updated to 7.5 then it's extremely possible that my install with the 7.5 iso and an update to a later 7.5 set of packages might not hit the same bug - if bug it is.
And, yes, given that I've been doing computers since 1981 and have variously been involved in low level systems programming all the way through to systems adminstration, I think I know what a VM is. I also know what Hyper-V is though I do not have access to a hypervisor that can be used to replicate your exact install. My install was also to a VM though of a different type to yours.
Thank you for the screenshot showing the problem. This pretty firmly narrows it down to being a problem with the latest grub and/or shim packages IMO.
I am asking about the iso filename as, at the present time it appears to me that you have some sort of problem with a UEFI install. Since the problem only occurs after updating the install, it is necessary to know which iso you installed from so that someone trying to replicate your problem can start from the same place. If you did your install with the 7.4 minimal iso and then updated to 7.5 then it's extremely possible that my install with the 7.5 iso and an update to a later 7.5 set of packages might not hit the same bug - if bug it is.
And, yes, given that I've been doing computers since 1981 and have variously been involved in low level systems programming all the way through to systems adminstration, I think I know what a VM is. I also know what Hyper-V is though I do not have access to a hypervisor that can be used to replicate your exact install. My install was also to a VM though of a different type to yours.
Thank you for the screenshot showing the problem. This pretty firmly narrows it down to being a problem with the latest grub and/or shim packages IMO.
The future appears to be RHEL or Debian. I think I'm going Debian.
Info for USB installs on http://wiki.centos.org/HowTos/InstallFromUSBkey
CentOS 5 and 6 are deadest, do not use them.
Use the FAQ Luke
Info for USB installs on http://wiki.centos.org/HowTos/InstallFromUSBkey
CentOS 5 and 6 are deadest, do not use them.
Use the FAQ Luke
Re: I believe CentOS repos have been compromised
What is the output from rpm -q grub2-efi-x64 both immediately post-initial-install and then again post-update but prior to the reboot that gets the error?
The future appears to be RHEL or Debian. I think I'm going Debian.
Info for USB installs on http://wiki.centos.org/HowTos/InstallFromUSBkey
CentOS 5 and 6 are deadest, do not use them.
Use the FAQ Luke
Info for USB installs on http://wiki.centos.org/HowTos/InstallFromUSBkey
CentOS 5 and 6 are deadest, do not use them.
Use the FAQ Luke
Re: I believe CentOS repos have been compromised
Second minimal install done. This time from the 7.5.1804 minimal iso itself and installed in UEFI mode. Changed the CentOS-Base.repo urls to point to the {os,updates} directories on the second mirror in your list prior to yum update - 84 packages updated, 1 newly installed kernel. Reboots fine.
The future appears to be RHEL or Debian. I think I'm going Debian.
Info for USB installs on http://wiki.centos.org/HowTos/InstallFromUSBkey
CentOS 5 and 6 are deadest, do not use them.
Use the FAQ Luke
Info for USB installs on http://wiki.centos.org/HowTos/InstallFromUSBkey
CentOS 5 and 6 are deadest, do not use them.
Use the FAQ Luke
Re: I believe CentOS repos have been compromised
Can you update the topic title to reflect something re: grub issues?
I've found that it appears the grubx64.efi may have changed locations, but not sure. If this is the case I'm not clear why a symlink or something to resolve backward compatibility wouldn't have been used.
I'll try the commands you asked and report back in a few.
I've found that it appears the grubx64.efi may have changed locations, but not sure. If this is the case I'm not clear why a symlink or something to resolve backward compatibility wouldn't have been used.
I'll try the commands you asked and report back in a few.
Re: Failed to open \EFI\centos\grubx64.efi - Not Found
In the meantime I have completed re-installs and updates from the 3rd and 4th mirrors on your list and have no problems.
The future appears to be RHEL or Debian. I think I'm going Debian.
Info for USB installs on http://wiki.centos.org/HowTos/InstallFromUSBkey
CentOS 5 and 6 are deadest, do not use them.
Use the FAQ Luke
Info for USB installs on http://wiki.centos.org/HowTos/InstallFromUSBkey
CentOS 5 and 6 are deadest, do not use them.
Use the FAQ Luke
Re: Failed to open \EFI\centos\grubx64.efi - Not Found
Post-install, no update, rebooted:
[root@localhost ~]# rpm -q grub2-efi-x64
grub2-efi-x64-2.02-0.65.el7.centos.2.x86_64
After update install:
[root@localhost ~]# rpm -q grub2-efi-x64
grub2-efi-x64-2.02-0.65.el7.centos.2.x86_64
It appears this issue is related to Hyper-V and the creation of templates which require the following to be run before using that VM as a base for the template:
grub-install --target=x86_64-efi --efi-directory=/boot/efi --no-nvram --removable
I'm not clear why a yum update would result in breaking the EFI config in that case, though.
Installing directly from ISO does not have the issue. It would appear then that something in the latest update still changed something with grub, but I think your rpm query suggests otherwise.
Thoughts?
[root@localhost ~]# rpm -q grub2-efi-x64
grub2-efi-x64-2.02-0.65.el7.centos.2.x86_64
After update install:
[root@localhost ~]# rpm -q grub2-efi-x64
grub2-efi-x64-2.02-0.65.el7.centos.2.x86_64
It appears this issue is related to Hyper-V and the creation of templates which require the following to be run before using that VM as a base for the template:
grub-install --target=x86_64-efi --efi-directory=/boot/efi --no-nvram --removable
I'm not clear why a yum update would result in breaking the EFI config in that case, though.
Installing directly from ISO does not have the issue. It would appear then that something in the latest update still changed something with grub, but I think your rpm query suggests otherwise.
Thoughts?
Re: Failed to open \EFI\centos\grubx64.efi - Not Found
Especially since, unless it's my eyes, your rpm -q output appears to be the same for both queries.I'm not clear why a yum update would result in breaking the EFI config in that case, though.
The future appears to be RHEL or Debian. I think I'm going Debian.
Info for USB installs on http://wiki.centos.org/HowTos/InstallFromUSBkey
CentOS 5 and 6 are deadest, do not use them.
Use the FAQ Luke
Info for USB installs on http://wiki.centos.org/HowTos/InstallFromUSBkey
CentOS 5 and 6 are deadest, do not use them.
Use the FAQ Luke
Re: Failed to open \EFI\centos\grubx64.efi - Not Found
So, after looking through the list of packages that you get to update, the only 2 there that look like they might be relevant to this problem are mokutil and shim-x64 and the latter would be my guess. Try recreating the problem only this time, instead of running a yum update run yum --exclude=shim-x64 update and then reboot and see if it still does.
The future appears to be RHEL or Debian. I think I'm going Debian.
Info for USB installs on http://wiki.centos.org/HowTos/InstallFromUSBkey
CentOS 5 and 6 are deadest, do not use them.
Use the FAQ Luke
Info for USB installs on http://wiki.centos.org/HowTos/InstallFromUSBkey
CentOS 5 and 6 are deadest, do not use them.
Use the FAQ Luke
Re: Failed to open \EFI\centos\grubx64.efi - Not Found
Thank you for the help, and sorry if I was a jerk.TrevorH wrote: ↑2018/09/29 21:57:43So, after looking through the list of packages that you get to update, the only 2 there that look like they might be relevant to this problem are mokutil and shim-x64 and the latter would be my guess. Try recreating the problem only this time, instead of running a yum update run yum --exclude=shim-x64 update and then reboot and see if it still does.
I'm testing this now.