Date: Mon, 27 Mar 2006 06:31:45 +1000 From: Tony Maher <anthony.maher@uts.edu.au> To: Claus Guttesen <kometen@gmail.com> Cc: stable@freebsd.org, "kreios@gmail.com" <kreios@gmail.com> Subject: Re: Need help with isp driver and disk arrary Message-ID: <4426FA31.4080806@uts.edu.au> In-Reply-To: <b41c75520603260021p1df17651t@mail.gmail.com> References: <2de4f2a00603251544j55ceab65rb79ebeeb2859188a@mail.gmail.com> <b41c75520603260021p1df17651t@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
Claus Guttesen wrote: >>I am having a problem with the isp driver seeing a StorageTek disk >>array LUNs. I am directly attaching to the array and everything works >>find as long as I plug into the A controller on the array. When I >>connect up to the B controller, I can not see any of the LUNs >>advertised. The QLogic firmware can see the LUNs. The only difference >>I can see are that the LUNs start at 0 on the A side and at 3 on the B >>side. > > > In 5.x (and probably still applies to 6.x) LUN's have to start at 0 in > order to be visible. So you have to change or LUN-mask so they start > at 0. And in 4.x. This behaviour is unlikely to change since the standards only require checking for device at lun 0 (and if found then scanning for more). You can use camcontrol to rescan the bus (or device) to make it visible. -- tonym
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?4426FA31.4080806>