Description of problem: In order to install to a disk connected through a Firewire interface, I have to add `expert' to the installer boot command line, but in order to install to the same disk connected through its USB interface, I don't have to. Is that on purpose? Could the need for `expert' be lifted for Firewire disks, at least when searching for existing partitions, RAID devices and/or logical volumes? Version-Release number of selected component (if applicable): anaconda-10.92.4-1 How reproducible: Every time Steps to Reproduce: 1.Boot up the installer with a disk connected to USB 2.Proceed to the disk druid screen 3.Try again with the same disk connected to Firewire 4.Try again, but now with `expert' in the boot cmd line Actual results: The disk is usable in 2. and 4., but not in 3. Expected results: Should be usable in 3. as well, or in none of them. Additional info: The sbp2 module is loaded by the loader regardless of `expert', so that's not it.
Both should be requiring 'expert' since boot loaders with either are a little iffy at best. Can you attach /tmp/scsidisks from the installer?
/tmp/scsidisks does not mention the disk at all when it is connected through the USB port (?!?), but it correctly mentions the disk is on sbp2 when it is connected through the Firewire port.
David -- can you take a look at this.
Fixed in CVS.