5.8 Install claims to work but get grub prompt on boot

[SpencerArnold]

I perform a standard install from a USB Image to a small Intel NUC box (8GB memory, couple of CPUs) and when it completes its reboot,and goes back to BIOS, I remove the memory stick and I get the grub prompt. Watching the messages, it claims it's doing the mkboot of sda, and claims to be updating grub but won't boot cleanly after install. I have always selected "wipe config".

FAQ
- It's your hardware / check your BIOS - worked the last 12 times I installed the same image on the same hardware. BIOS boot order is correct (hard drive first, USB second)
- Oh that's easy, just perform [insert 50 grillion commands here] - no, this project is for general public release, they do not have the capacity for 50 grillion commands and besides, it worked before; I need this to be consistent.

I am a Redhat Sysadmin for a living for 20+ years, I have made many custom ISOs and PXE/DHCP boot configs; I know the way OS installs are supposed to work. This OS Install is not working.

Any advice would be appreciated. Regards, Spencer

[WytWun]

I perform a standard install from a USB Image to a small Intel NUC box (8GB memory, couple of CPUs) and when it completes its reboot,and goes back to BIOS, I remove the memory stick and I get the grub prompt.

The first part of this post may be helpful, particularly the grub recovery link.

Ignore the "Observations:" section of that posting as that is unrelated to the grub issue.

[trinidad]

when it completes its reboot,and goes back to BIOS, I remove the memory stick

You should have been prompted to remove the install media BEFORE actual reboot begins. That ensures that old installer mods are then cleaned up from RAM and reboot commences afterward.

BIOS boot order is correct (hard drive first, USB second)

Boot order should be USB or CD/DVD first and HDD second. No need to change it prior to rebooting a new install, and doing so during RAM access probably caused grub to not be found. These two things you did during install forced you into the CLI. RAM should always be cleared first and both things went against that. RHEL uses SELinux which is not the same as apparmor and installations work differently even though the commands and intent may be similar. 
TC

[SpencerArnold]

Thanks for feedback. Install doesn't seem to prompt for media removal, but I wait until the BIOS is displayed to be safe.

Too may times been caught with media left in Devices, so I make booting from removable media a specific choice. Personal preference, I suppose.

Did a check on the BIOS and UEFI had become enabled on the Boot Device. I disabled it again and switched to Legacy Boot Protocols and it worked fine. Suspect I have some hardware issues lurking there.

Appreciate the assistance tho, issue resolved. Cheers, Spencer.