Date: Wed, 13 Jul 2005 14:44:22 -0600 From: Scott Long <scottl@samsco.org> To: Rainer Duffner <rainer@ultra-secure.de> Cc: freebsd-scsi@freebsd.org Subject: Re: FreeBSD 5.4-i386, isp(4) and an EVA3000 Message-ID: <42D57D26.3010705@samsco.org> In-Reply-To: <42D404CC.4010703@ultra-secure.de> References: <42D404CC.4010703@ultra-secure.de>
next in thread | previous in thread | raw e-mail | index | archive | help
Rainer Duffner wrote: > Hi, > > I've just installed FreeBSD 5.4 on a HP blade, connected to our EVA 3000 > SAN. > > The sysinstall-kernel doesn't have the ispfw-module and it didn't > recognize the LUNs - is there a way to load that module from the > original install-medium or do I have to bake my own? > OK, so this is the test-blade that has a hard-disk inside and I > installed on that, built my own kernel that had ispfw(4), booted and ... > couldn't get to FreeBSD, because it had now found the SAN and moved the > "old" da0 to da8 or so... > > Didum...Re-install, this time I see a lot of LUNs from the SAN, and > install on da0, all went well, I can boot that - beautiful, compared to > the likes of RHEL... Read the section in /sys/conf/NOTES that talks about wiring down SCSI IDs and LUNs to particular device numbers. Scott
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?42D57D26.3010705>