kickstart file cannot be found during a network installation

I'm trying to kickstart install several Red Hat Enterprise Server 5 on several computers--their configuration is identical.
I have set up the RHES5 installation tree by copying the contents of an ES5 DVD (made from an ISO file) into an NFS installation directory, in this case /distrib/RH51ES.
I then ran the system-config-netboot utility to set up PXE booting.  The PXE booting itself goes fine and the installation proceeds until I choose the correct network interface.  The install continues a bit after that and then pops up an error message: "Unable to download the kickstart file.  Please modify the kickstart parameter below..."  The line below is usually filled with "garbage" such as !H##<CC><CC><CC> ...etc.  This can be erased and a new parameter entered, so I've tried "ks.cfg",  "/distrib/RH51ES/ks.cfg"  "nfs:" and other variants which didn't work...  
Here is the /etc/dhcpd.conf file that is used:

# DHCP Server Configuration file.
#   see /usr/share/doc/dhcp*/dhcpd.conf.sample  
ddns-update-style interim;
subnet netmask {
  option subnet-mask;
  option broadcast-address;
  option domain-name-servers;

  group {
          # option vendor-class-identifier "PXEClient";
          filename "linux-install/pxelinux.0";
        #  filename "/distrib/RH51ES/ks.cfg";
          host bcc30 {
                hardware ethernet 00:0E:0C:AB:AE:2C;
                #option host-name "bcc30";
                filename "/distrib/RH51ES/ks.cfg";
# End
Some of these lines may be incorrect or meaningless--I'm trying a number of things to try to get this working!
I've tried putting the ks.cfg file into the installation directory and also into the /tftpboot directory with no results.

I'd appreciate any practical experience anyone has had doing network kickstart installs or with this particular error.

Thank you!
Don P.
Who is Participating?
arrkerr1024Connect With a Mentor Commented:
You don't specify the name of the kickstart file in the dhcp configuration, you specify the name of the loader.  The pxelinux.0 is then going to look for a number of standard file names, your ip address converted to hex, and then finally one called "default".  Try just using "default' for starters, but change to the converted IP later so that you can have different KS files for different machines.

When you ran the pxe wizard I think it should have asked you the name of the kickstart file too...?
arrkerr1024Connect With a Mentor Commented:
If you actually got the installed booted up on the client you SHOULD have been able to enter nfs: for your kickstart location though, unless there were problems with NFS or with your network on the client machine.

One tip: instead of using NFS you can use http.  I do this because 1) its almost easier, and probably a lot more secure, and 2) because apache has nice log files.  If  you throw your kickstart and installation tree on an http site you can tail the access and error logs and if you have a typo somewhere you can still see the machine trying to access a file, etc.  Its made my life troubleshooting a LOT easier.
donparAuthor Commented:
Thank you for your rapid response!

I will try your "default" suggestion first.  Yes, when I ran the system-config-netboot, it did prompt for the ks file name.  Don't have the server available at the moment, so don't remember exactly what my entry was.  Probably something like "/distrib/RH51ES/ks.cfg"

Yes, it could be something about the NFS configuration, but successfully mounted the NFS share on another system with no problem.  I did specify the nfs: when the kickstart file location was prompted but it still couldn't find the ks file.

If NFS just will not work, I'll do the http method; had not considered that http will be a lot easier to troubleshoot--that is a good suggestion...

I'll post again when I have some results...

Thanks again,

Don P.

donparAuthor Commented:
Actually BOTH of the comments put me on the right track and the PXE/Kickstart installation completed successfully!

The dhcpd.conf file worked as configured in the question, although I did remove the commented out lines.
What really solved the issue was entering the correct URL for the kickstart file in the system-config-netboot configurator.  The entry here needed to be:  "nfs:".  This entry was placed in a config file in the /tftpboot tree which had a file name equivalent to the MAC address of the client being installed.

A note: strangely, the "nfs:" entry did not work when I was prompted for the kickstart file during installation.

In any case, thank you!

Don P.
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

All Courses

From novice to tech pro — start learning today.