From Bugzilla Helper: User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.7.12) Gecko/20050922 Firefox/1.0.7 (Debian package 1.0.7-1) Description of problem: A server with fiber-hba (driver lpfc) and hardware-raid (driver cciss) get booted by a kickstart-cd (RHEL3u6) and get installed. The drivers are loaded in that order, via lpfc san-storage gets detected and available as /dev/sda, then the hardware-raid is found. ks.cfg has 'part / --fstype ext3 --size=1500 --ondisk=cciss/c0d0 --asprimary' and the system gets installed onto the internal disks, however the bootsector gets written to /dev/sda . After reboot system fails in starting the bootloader. Usage of lilo or grub makes no difference. Version-Release number of selected component (if applicable): How reproducible: Always Steps to Reproduce: 1.boot system from kickstart-cd 2.complete networkinstallation 3.reboot system Actual Results: After reboot system fails in starting the bootloader. System prints the values of cpu-registers and freezes. Expected Results: Start of bootloader. Additional info: Workaround: Configure ks.cfg to use lilo and 'interactive, run installation as usual. When system is installed and waits for the user to hit return for the final reboot change to console2 (<ALT>+<F2>) and: chroot /mnt/sysimage vi etc/lilo.conf # and change '/dev/sda' into '/dev/cciss/c0d0' sbin/lilo # write correct bootblock reboot.
*** Bug 174581 has been marked as a duplicate of this bug. ***
You need to pass the driveorder argument to the boot loader line. PC hardware unfortunately has no reliable way of determining what the boot disk really is.