A partner has observed some behavior where a disk that has been cloned
from another disk will take an extra reboot compared to the original
disk, seemingly triggered during execution of the grub binary. After
this extra reboot, the boot continues normally.
Generally speaking, is there some process within grub for which this
is the expected behavior? My assumption is that this may be due to
something like a mismatched UUID between the two disks triggering some
autocorrection mechanism, but this is just an educated guess, and I am
not seeing anything in the grub source like this at a quick glance.