Date: Thu, 14 Jul 2005 12:48:11 +0200 From: Rainer Duffner <rainer@ultra-secure.de> To: Scott Long <scottl@samsco.org> Cc: freebsd-scsi@freebsd.org Subject: Re: FreeBSD 5.4-i386, isp(4) and an EVA3000 Message-ID: <42D642EB.1090405@ultra-secure.de> In-Reply-To: <42D57D26.3010705@samsco.org> References: <42D404CC.4010703@ultra-secure.de> <42D57D26.3010705@samsco.org>
next in thread | previous in thread | raw e-mail | index | archive | help
Scott Long wrote: > 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 OK, I knew that (sort of). But I'm still curious why I am seeing so many ghost-LUNS. Another thing: when I tried to enlarge such a VDISK, it didn't work quite the way I originally thought (which you can blame on my thinking) - it created a 2nd partition on the same LUN with the rest of the space. So I should rather create a new LUN and use vinum to concatenate them together, right? Does that work "online"? But what was more annoying was the fact that when I ran camcontrol rescan, the whole machine just froze. (I had unmounted the slice, AFAICR) Is this normal? cheers, Rainer
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?42D642EB.1090405>