I remember that as well, but this has never happened to me until RHEL5. I have several machines running RHEL4 with addon raid cards on which this does not happen.
On 9/17/07, Broekman, Maarten <[EMAIL PROTECTED]> wrote: > > Yes. This happens with NIC cards as well. It has to do with > depth-first vs breadth-first device ordering. I can never remember > which was the old way and which is the new way but this was one of the > big changes between the 2.4 kernels (AS 2.1, AS3) and the 2.6 kernels > (RHEL4+). I know that I had requested a boot parameter that would allow > us to switch back to the old-style but that never happened to my > knowledge. > > Anyone know if it's possible to change the ordering algorithm in the 2.6 > kernels so that devices are ordered the same way as they would be on a > RHEL3 system? > > Maarten > > > ________________________________ > > From: [EMAIL PROTECTED] > [mailto:[EMAIL PROTECTED] On Behalf Of Corey Kovacs > Sent: Monday, September 17, 2007 3:02 PM > To: [email protected] > Subject: [rhelv5-list] device ordering on DL360G4 using RHEL5. > > > I have run into a strange issue on an DL360G4 which deals with > the ordering of scsi controllers. The problem is that any add-on cards > cause the embedded "6i" controller to be listed as a secondary device. > So if I have a HP6402 installed, the 6i shows up as /dev/cciss/c1xxxx or > if I have a 6404 (two additional channels), then the embedded 6i gets > /dev/cciss/c2xxxx. The system runs just fine since it's running on LVM > and labels, but this, by far, not desired. I've read in the past about > how certain bios revs don't scan the bus correctly and the kernel > sometimes compensates. > Has anyone else seen this? > > > Corey > > > > > _______________________________________________ > rhelv5-list mailing list > [email protected] > https://www.redhat.com/mailman/listinfo/rhelv5-list >
_______________________________________________ rhelv5-list mailing list [email protected] https://www.redhat.com/mailman/listinfo/rhelv5-list
