Hello, this problem hit me out of the blue, and I'm in a time crunch, otherwise I would do more searches on this site.

I was handed a set of HP Proliant DL360p 8-Core Intel servers that I need to install Red Hat 5.9 x64. We use a custom kickstart DVD designed for HP servers. The DVD has the images on it, so the installation is totally local. This method has served us very well on all previous generations of HP Proliant servers. However, the DL360p G8 servers have stonewalled me. The server boots up to the Red Hat kickstart DVD just fine. After launching the installation, immediately after "Loading cciss drivers...", the install fails with a "Unable to download kickstart file. Plese modify the kickstart parameter below or press Cancel to proceed as an interactive installation." The parameter it says to modify is "cdrom:ccissks.cfg" which is obviously our kickstart file. It almost seems as if it has forgotten that there's a media drive in the server. I've tried researching this error some, and it appears that the error is almost exclusively seen during network installations. I could find no reference to anyone having this problem during a local install. These install DVD's work just fine on G7 servers, and even the DL385p G8 servers we just got. But these DL360p G8's are not behaving. I don't see any obvious BIOS settings to adjust. Unfortunately, in my current location, I don't have access to any out-of-the-box Red Hat 5 media that I can try for a totally manual installation, just the custom kickstart DVD.

If anyone has any suggestions, please throw them out there. At this point, I'm willing to try just about anything.

This may seem like an obvious qn, but what happens if you do as asked ie
Can you proceed manually/interactively, or do you get another error and if so what (exactly)?

Any chance you've got a support ctc with RH or HP?

I seem to remember last time I dealt with DL360 v DL380 that the former had IDE drives instead of SAS, so we ended up having to do an install-OS+data restore instead of a clonezilla move from 360->380.
That may not help, but its the best I can do; I suspect a HW/dev driver issue re your kscfg.

Best of luck & do let us know how it turns out.

I have almost the exact same issue.