Red Hat Bugzilla – Bug 174580
Bootsector written to device first detected by anaconda, not root-partition chosen by kickstart-option 'part --ondisk'
Last modified: 2007-11-30 17:07:09 EST
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):
Steps to Reproduce:
1.boot system from kickstart-cd
Actual Results: After reboot system fails in starting the bootloader. System prints the values of cpu-registers and freezes.
Expected Results: Start of bootloader.
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:
vi etc/lilo.conf # and change '/dev/sda' into '/dev/cciss/c0d0'
sbin/lilo # write correct bootblock
*** 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.