RHEL 5.1 Installations: isolinux cfg issue

[Richard Pomerleau]

We have been building RHEL3 and RHEL4 Linux servers successfully for some time using ISO images mounted on an NFS server. The custom ISO image we generate for a server contains in the isolinux.cfg file lines like:

kernel vmlinuz
append ks=hd:scd0:/ks.cfg initrd=initrd.img ramdisk_size=8192

Now on the same test build server with RHEL 5.1, the build progresses to a point where the "append ks=hd:scd0:/ks.cfg" is displayed as not valid.

"fdisk -l" on the server yeilds "/dev/cciss/c0d0".

I did a manual RHEL 5.1 installation to capture the anaconda-ks.cfg file but that doesn't contain any info I need for the "isolinux.cfg" file.

Anyone else run into this and find a solution?

[Stuart Browne]

If your media is all on the NFS server, why not put the KS configuration there as well? It'll allow for easier changes to the kickstart in future.

append ks=nfs:server:/path/to/ks.cfg

should work.

[Richard Pomerleau]

Thanks for the reply.

The ks.cfg file is on the NFS server. Booting off the custom ISO file and connecting to the NFS server is not the issue. The build boots off the NFS server, gets so far and then says in the TUI window that the "hd:scd0:/ks.cfg" is not valid. The entry is in "isolinux.cfg" not the "ks.cfg" file.

This methodology has worked well for over 2 years and hundreds of RHEL3 and RHEL4 builds - now it does not.

So, what changed with RHEL5 (anaconda?). Will keep digging about and experimenting in the lab.

[Richard Pomerleau]

The installation menu continues to stop at the build point shown in the attachment. However, by tabbing forward to highlight OK and pressing Enter, the build continues. Things after that fail here and there but that appears to be a local network issue at the moment. Closing Thread.