From owner-freebsd-scsi@FreeBSD.ORG Wed Jul 13 20:44:27 2005 Return-Path: X-Original-To: freebsd-scsi@freebsd.org Delivered-To: freebsd-scsi@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id BD9EA16A41C for ; Wed, 13 Jul 2005 20:44:27 +0000 (GMT) (envelope-from scottl@samsco.org) Received: from pooker.samsco.org (pooker.samsco.org [168.103.85.57]) by mx1.FreeBSD.org (Postfix) with ESMTP id 5AC4443D48 for ; Wed, 13 Jul 2005 20:44:24 +0000 (GMT) (envelope-from scottl@samsco.org) Received: from [192.168.254.11] (junior.samsco.home [192.168.254.11]) (authenticated bits=0) by pooker.samsco.org (8.13.3/8.13.3) with ESMTP id j6DKncw8072485; Wed, 13 Jul 2005 14:49:40 -0600 (MDT) (envelope-from scottl@samsco.org) Message-ID: <42D57D26.3010705@samsco.org> Date: Wed, 13 Jul 2005 14:44:22 -0600 From: Scott Long User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; en-US; rv:1.7.8) Gecko/20050615 X-Accept-Language: en-us, en MIME-Version: 1.0 To: Rainer Duffner References: <42D404CC.4010703@ultra-secure.de> In-Reply-To: <42D404CC.4010703@ultra-secure.de> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-Spam-Status: No, score=-2.8 required=3.8 tests=ALL_TRUSTED autolearn=failed version=3.0.2 X-Spam-Checker-Version: SpamAssassin 3.0.2 (2004-11-16) on pooker.samsco.org Cc: freebsd-scsi@freebsd.org Subject: Re: FreeBSD 5.4-i386, isp(4) and an EVA3000 X-BeenThere: freebsd-scsi@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: SCSI subsystem List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 13 Jul 2005 20:44:27 -0000 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