Red Hat Bugzilla – Bug 110851
Installer detects scsi_hostadapter in wrong order
Last modified: 2007-11-30 17:06:59 EST
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.5)
Description of problem:
On a machine with more than one scsi_hostadapter the one used for
installing is not entered as first adapter in /etc/modules.conf
This leads to errors after installation with scsi-devices named in the
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. A machine with more tha one scsi_hostadpater (In our case an
onboard Adaptec, an IBM ServeRaid and two FiberChannel QLA2312)
2. The actual scsi disk is attached to the ServeRaid (ips) and some
LUNs on the QLogics (qla2300), nothing attached to the Adaptec (aic7xxx)
3. Install to /dev/sda (harddisk @ ips)
Actual Results: Entries in /etc/modules.conf:
Expected Results: Entries in /etc/modules.conf:
This causes big confusion because according to /etc/modules.conf the
mkinitrd command works.
That leads to a wrong order of loading modules within the initrd in
the script linuxrc.
If I boot after a normal installation the LUNs on the qla2300 are
detected first and get named /dev/sda ... /dev/sdh, my previous
/dev/sda is now /dev/sdi. The normal mounts work mainly because they
are mounted by filesytem label, but my swap is not working and some
other mounts from the LUNs will not work.
I either have to modify that directly befor I reboot after install
oder have to boot from a rescue media oder disconnect my QLogics while
booting. Neither is preferable ;)
Devices are detected in PCI order as presented by the kernel. If you
wish to specify the order by hand, boot with 'linux noprobe' and
manually load modules in the order that you want.
This answer is not satisfying!
RedHat Adv.Server 2.1 was able to do this in the right order, so AS
3.0 should also be able to do this.
I agree this should be fixed. At work we setup an initrd with qla*
modules removed. It would be helpful instead of having "linux
noprobe" a "linux disable=qla2200 disable=qla2100....". Because
noprobe disables *all* probing.
The "right" order is completely arbitrary, there is no "right" order.
If you have a specific reason to load modules in a specific order,
then you need to load them by hand.