Hide Forgot
Description of problem: The kickstart files contain: bootloader --location=mbr --driverorder=cciss/c0d0 This works fine until the system being kickstarted has a non-cciss san device to the system during an install. It installs where its supposed to but the entry in the hd entry in the grub gets the wrong numbering and the box won't boot. Changing it to hd0,0 fixes the problem. So does this in the kickstart: bootloader --location=mbr --driverorder=cciss/c0d0,sda,sdb,sdc The requested feature would be to automatically append/assume the rest of the drive order from what the computer assumes. Version-Release number of selected component (if applicable): anaconda-11.1.2.168-1 How reproducible: Every time, just need to test it on something without cciss, but have the above bootloader in the kickstart. Steps to Reproduce: 1. find a server without cciss card. 2. kickstart a server with the above line in the kickstart file. 3. Wait. Actual results: When server reboots, grub has been installed to the wrong location.
Wade, I am not able to reproduce the bug with your steps (that is without cciss card). Could you please reproduce and post following files from installed (repaired) system ? /var/log/anaconda.log /root/anaconda-ks.cfg /boot/grub/device.map /boot/grub/grub.conf Even better would be to reproduce with rhel 5.4 using this updates file that contains some patches to get more logging information: http://rvykydal.fedorapeople.org/updates.driveorder.img (you would do it by adding updates=<URL> to anaconda boot parameters). If necessary, I can prepare updates file for rhel 5.3.
Closing per comment 11.