In our lab we have a set of scripts that automatically configure a kickstart installation for RHEL5 on HP ProLiant DL380p Gen8. Based on data from several configuration files, it does the following steps:
isolinux.cfg accordinglyks.cfg/dev/scd1)Here is the line referring to the kickstart file location :
append initrd=initrd.img ks=hd:scd1:/isolinux/ks.cfg ksdevice=eth4
Everything works well for RHEL5, but there have been requests for RHEL6.
For RHEL6, everything seems to work OK until #7, where it returns the message "unable to download kickstart file". I have commented some lines in the scripts, eliminating the installation part and leaving only the ILO mount part.
The bootdisk is mounted and accessible on /dev/scd1. The ks.cfg file is present there. I have also tested and the files from the Kickstart server are accessible with wget.
I have also tried accessing the ks.cfg file through http :
append initrd=initrd.img ks=http://<ip>:<port>/boot/isolinux/ks.cfg ksdevice=eth4
The above part did not work.
But what really vexes me is that RHEL5 works in the same conditions, but RHEL6 does not.
ks.cfg have a different structure?ks.cfg file declared different from "hd:scd1:/isolinux/ks.cfg" on RHEL6?isolinux.cfg and ks.cfg are both present on the bootdisk, but only isolinux.cfg can be accessed.I have been talking to redhat support for a week and they don't seem to know what is wrong.
Any help would be greatly appreciated.
I have figured out the problem.
There seems to be a difference between RHEL5 and RHEL6 at the installation level.
RHEL5 will detect your physical cdrom and mount it on /dev/scd0, therefore the location of the mount will be /dev/scd1. RHEL6 does not seem to do this, therefore the mount location will be /dev/scd0.
The correct way to declare the ks file location in a case like this is :
append initrd=initrd.img ks=hd:scd0:/isolinux/ks.cfg ksdevice=eth4
I hope someone will find this helpful in the future.
本文收集自互联网，转载请注明来源。
如有侵权，请联系[email protected] 删除。
我来说两句