Date: Sat, 20 Jun 2009 12:03:02 +0200 From: Kai Gallasch <gallasch@free.de> To: freebsd-proliant@freebsd.org Subject: Re: ciss and mpt disk devices numbering priority on a DL385 G2 Message-ID: <4A3CB3D6.6040002@free.de> In-Reply-To: <6863f0c90906170836g6ee87f8eq9880a9c462be572b@mail.gmail.com> References: <4A38BAD8.8070900@free.de> <6863f0c90906170836g6ee87f8eq9880a9c462be572b@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
John Cagle wrote: > Have you looked at the options in the BIOS setup utility (RBSU)? There > should be an option to select the boot controller (which should be the > P400 in your case). > > If that is already set to the P400, then the problem may be one of PCI > enumeration. If FreeBSD loads the mpt driver first, then it may grab > da0. Maybe there's a way to force it to load the ciss driver first? Hi John. In the end I came up with some "solution". I built a kernel without support for the LSI HBA (mpt driver). When the server has booted I do a "kldload mpt" and "camcontrol rescan" to bring up the mpt scsi devices. The scsi devices of the mpt controller then show up after those of the smart array (ciss). In my case I need the LSI controller to give me some JBOD devices, so I can go and play with zfs on the server. (hp/compaq smart array offers no jbod) It is easy to patch /etc/rc.d/zfs to load the mpt kernel module and do the rescan of the scsi bus: Index: zfs =================================================================== RCS file: /common/config/server/ROOT/etc/rc.d/zfs,v retrieving revision 1.1 retrieving revision 1.2 diff -r1.1 -r1.2 15c15 < required_modules="zfs" --- > required_modules="mpt:zfs" 25a26,29 > # required module mpt is on bus 2. do a rescan, so the > # devices are found and become available. > camcontrol rescan 2 So when zfs starts, the rest happens automatically. --Kai.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?4A3CB3D6.6040002>