Thank you for taking the time to respond, jbkt23, I seriously appreciate it! My Main PC is a multiboot monster and has been ever since I was TeamOS2 way back in the day. It currently has 5 internal drives with ~27 partitions on it providing almost a dozen bootable systems.
It now has several defunct partitions that were Rocky Linux install attempts. The only one that ever got past the grub2-common error, completed, booted and ran had all of it’s partitions on a spinner, the 4th drive. However the root partition was both too small and I’m spoiled by the bandwidth of NVME so that minor success motivated me to give Rocky some upgraded importance.
Currently, my latest (attempted but failing on grub2) locations are all on Disk 0 with the single exception of “swap” which is still on the spinner. I’ve tried verifying disk as well as network install and every attempt excepting that on the old spinner fails in precisely the same manner. I vastly prefer rEFInd or elilo as a bootloader but I have had easy success with Mangeia, Arch, CentOS, and OpenSuse to name a few that ultimately get booted for me via rEFInd but began life with Grub2 (and still will work that way)…well… the ones I’ve kept more than a few months.
FWIW I normally set firmware for the highest priority boor order as rEFInd but most, including even Rocky failure’d installs, reset their own boot loaders as Priority 0 and after trying them for Pass/Fail, I reset to rEFInd keeping the Pass’es and efibootmgr delete the Fails.
I totally agree with you that variations in hardware creates so many variables it is exactly that, guesswork, especially when the installer warns about non-critical issues but hasn’t a check or a clue about bootloader Pass/Fail. In my case as an EE and someone who began building PCs with DOS 3, my hardware is pretty much top notch.
My Main (I have several active homebuilt PCs including 3 towers, 2 laptops, and an ARM-based network backup machine) is built on an Asus Hero z490 platform with 16GB top notch RAM, powered by a gold standard Corsair 800 watt PSU, cooled to under 40C average, and all the NVME drives are EVO Pros, with the one I’m trying to install Rocky on in the primary M.2 slot. Just FTR, I wiped the partitions of working other distro systems on that drive to accommodate Rocky. Those installed, booted, and ran just fine, which is why I felt desperate enough to wipe a working system in order to stop the fail. That has not worked for Rocky…yet.
Thanks again for your help but in my view this is some odd bug. My /boot partition is 3GB ext2, /boot/efi is 500MB fat32 (which Rocky install demands be reformatted to “EFI” despite that I know all about “boot,esp” flags) and the installer should be able to determine something as basic as bootloader viability and deny continuation until that is addressed, or better just do what virtually every other distro that has to comply with UEFI standards does, and succeed on a proper setup.