Description of problem: In a system with 3ware IDE RAID controller cards and onboard SCSI, the RAID controllers are enumerated first in the device files, i.e. /dev/sda, sdb, then the onboard SCSI, /dev/sdc. Anaconda will only allow you to create /boot on /dev/sda, even if the BIOS is set to boot only from /dev/sdc. This creates a situation where everything must be repartitioned after anaconda finishes using a rescue disk, manually creating /boot on /dev/hdc and rewriting lilo.conf. Anaconda should either allow you to create /boot wherever you want, or detect which disk the bios is seeing as 0x80 correctly. Version-Release number of selected component (if applicable): How reproducible: Always Steps to Reproduce: 1. Install 3ware IDE controllers 2. begin install of RH7.1 with linux expert option to allow the loading of 3ware drivers from floppy at beginning of install 3. Attempt to create a bootable configuration within anaconda. Actual Results: LILO will hang with LI if anaconda is allowed to create /boot on /dev/sda (the 3ware RAID), and the BIOS is set to boot from /dev/sdc, Anaconda will not allow user to create /boot on anything but /dev/sda Expected Results: sucessful boot Additional info: Motherboard in test configuration was Supermicro P3TDE6 with serverworks HE chipset. 3ware controllers were two escalade 7800 cards. On board SCSI is adaptec.
Closely related to bug 10645 among others. Not going to get fixed this go around
You'll be able to reorder what the BIOS ordering for drives is for the next release