Good evening,

I don't know if anyone saw this, but I found my answer at:

https://docs.centos.org/en-US/8-docs/advanced-install/assembly_kickstart-and-advanced-boot-options/

In the note saying:

By default, the inst.stage2= boot option is used on the installation media and is set to a specific label, for example, inst.stage2=hd:LABEL=CentOS-8-BaseOS-x86_64. If you modify the default label of the file system containing the runtime image, or if you use a customized procedure to boot the installation system, you must verify that the inst.stage2= boot option is set to the correct value.

So it was a label problem. I was calling mkisofs with the -V switch and an argument that did not match the label in isolinux.cfg for inst.stage2. This caused the boot stall.

If anyone saw this, thanks for your consideration.

Best Regards,

Dan

On Sat, Mar 4, 2023 at 2:18 PM Dan Davis <davis.dan.c@gmail.com> wrote:

Good Afternoon,

I'm trying to re-roll a RHEL9 iso to remove the media check and 60s timeout that occurs because rd.live.check is baked into the kernel command line and grub menu. I'd like to use the result with an unattended install.

I start by loop mounting the OEM iso image and extracting the contents to a working dir. In the working directory, I've attempted to edit EFI/BOOT/grub.cfg an isolinux/grub.cfg before rerolling the disk with:

mkisofs -o output.iso -b isolinux/isolinux.bin -c isolinux/boot.cat -no-emul-boot -boot-load-size 4 -boot-info-table workingdir

But after editing either or both, I'm still presented with the 60s default timeout and the media check (rd.live.check) in the kernel commandline.

Is there something akin to grub2-mkisofs that I need to do for my changes to the grub.cfg for this iso prior to my re-rolling it?

Thank you,

Dan