I know that. That's a debian/ubuntu command. I was wrong. He passed that along and I posted it without thinking. It isn't the issue.avij wrote: ↑2018/10/03 19:18:07The kicker is that there's no grub-install in CentOS 7. If you have been using someone else's grub-install that does not know about CentOS paths to manage CentOS boot configuration, I'm not surprised that there are issues. I don't know what your grub-install binary does, but it could, conceivably, use some other path than /boot/efi/EFI/centos for the UEFI boot config. You may be able to get some information about your grub-install if you run rpm -qif $( which grub-install ) but chances are that your grub-install is not packaged into a rpm. In that case which grub-install may show something, like an unusual path for the binary.enseva wrote: ↑2018/09/29 21:46:57It 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.
The issue is, if you read through the countless EFI bugs posted since the beginning of the year (we'll give a pass on all the ones I found from last year, too) that CentOS has changed the default location for it's boot files in various updates, at least that's what appears to be happening.
It seems that since 1708 there have been various updates (and I'm not sure if this is related to the shim file) that have defaulted the boot configuration location from /boot/efi/EFI/BOOT to /boot/efi/EFI/centos and back.
I have a working, non-updated VM I just created from a template created from a 1708 ISO which has ZERO files in /boot/efi/EFI/centos - and it boots fine.
As soon as I update that, there are seven files, all dated Aug 24, 2018, added to the /boot/efi/EFI/centos directory:
Of course, this means three critical files are missing from that directory. Which would be fine if the Grub configuration hadn't been somehow magically updated (which it is, per my error) to look in this directory.
Post-boot, of course I get the error you see on the previous screen shot.
Booting into rescue, copying the missing files from /boot/efi/EFI/BOOT to /boot/efi/EFI/centos resolves the issue.
The question is: Why the hell did it work just fine without any files in the ..../centos directory prior to update?