From owner-freebsd-scsi@FreeBSD.ORG Tue Jul 12 17:58:41 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 D4E9516A41C for ; Tue, 12 Jul 2005 17:58:41 +0000 (GMT) (envelope-from rainer@ultra-secure.de) Received: from bsd.ultra-secure.de (bsd.ultra-secure.de [62.146.20.26]) by mx1.FreeBSD.org (Postfix) with ESMTP id 4959343D58 for ; Tue, 12 Jul 2005 17:58:39 +0000 (GMT) (envelope-from rainer@ultra-secure.de) Received: (qmail 99249 invoked by uid 1005); 12 Jul 2005 17:58:38 -0000 Received: from rainer@ultra-secure.de by bsd.ultra-secure.de by uid 89 with qmail-scanner-1.22 (clamdscan: 0.85. spamassassin: 2.64. Clear:RC:1(213.196.191.65):. Processed in 0.033163 secs); 12 Jul 2005 17:58:38 -0000 Received: from unknown (HELO ?192.168.100.179?) (rainer@ultra-secure.de@213.196.191.65) by bsd.ultra-secure.de with (DHE-RSA-AES256-SHA encrypted) SMTP; 12 Jul 2005 17:58:38 -0000 Message-ID: <42D404CC.4010703@ultra-secure.de> Date: Tue, 12 Jul 2005 19:58:36 +0200 From: Rainer Duffner User-Agent: Mozilla Thunderbird 1.0.2 (X11/20050317) X-Accept-Language: en-us, en MIME-Version: 1.0 To: freebsd-scsi@freebsd.org Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Subject: 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: Tue, 12 Jul 2005 17:58:41 -0000 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... But I've still got a question: it finds way to many LUNs: isp0: port 0x3000-0x30ff mem 0xf7dd0000-0xf7dd0fff irq 23 at device 3.0 on pci1 isp1: port 0x3400-0x34ff mem 0xf7dc0000-0xf7dc0fff irq 18 at device 3.1 on pci1 pass0 at isp0 bus 0 target 0 lun 0 pass0: Fixed Storage Array SCSI-2 device pass0: 200.000MB/s transfers, Tagged Queueing Enabled pass1 at isp0 bus 0 target 1 lun 0 pass1: Fixed Storage Array SCSI-2 device pass1: 200.000MB/s transfers, Tagged Queueing Enabled pass4 at isp0 bus 0 target 2 lun 0 pass4: Fixed Storage Array SCSI-2 device pass4: 200.000MB/s transfers, Tagged Queueing Enabled pass5 at isp0 bus 0 target 3 lun 0 pass5: Fixed Storage Array SCSI-2 device pass5: 200.000MB/s transfers, Tagged Queueing Enabled pass8 at isp1 bus 0 target 0 lun 0 pass8: Fixed Storage Array SCSI-2 device pass8: 200.000MB/s transfers, Tagged Queueing Enabled pass11 at isp1 bus 0 target 1 lun 0 pass11: Fixed Storage Array SCSI-2 device pass11: 200.000MB/s transfers, Tagged Queueing Enabled pass12 at isp1 bus 0 target 2 lun 0 pass12: Fixed Storage Array SCSI-2 device pass12: 200.000MB/s transfers, Tagged Queueing Enabled pass13 at isp1 bus 0 target 3 lun 0 pass13: Fixed Storage Array SCSI-2 device pass13: 200.000MB/s transfers, Tagged Queueing Enabled da4 at isp1 bus 0 target 0 lun 1 da4: Fixed Direct Access SCSI-2 device da4: 200.000MB/s transfers, Tagged Queueing Enabled da4: 51200MB (104857600 512 byte sectors: 255H 63S/T 6527C) da5 at isp1 bus 0 target 0 lun 3 da5: Fixed Direct Access SCSI-2 device da5: 200.000MB/s transfers, Tagged Queueing Enabled da5: 1024MB (2097152 512 byte sectors: 64H 32S/T 1024C) da6 at isp1 bus 0 target 3 lun 1 da6: Fixed Direct Access SCSI-2 device da6: 200.000MB/s transfers, Tagged Queueing Enabled da6: 51200MB (104857600 512 byte sectors: 255H 63S/T 6527C) da7 at isp1 bus 0 target 3 lun 3 da7: Fixed Direct Access SCSI-2 device da7: 200.000MB/s transfers, Tagged Queueing Enabled da7: 1024MB (2097152 512 byte sectors: 64H 32S/T 1024C) da0 at isp0 bus 0 target 1 lun 1 da0: Fixed Direct Access SCSI-2 device da0: 200.000MB/s transfers, Tagged Queueing Enabled da0: 51200MB (104857600 512 byte sectors: 255H 63S/T 6527C) da1 at isp0 bus 0 target 1 lun 3 da1: Fixed Direct Access SCSI-2 device da1: 200.000MB/s transfers, Tagged Queueing Enabled da1: 1024MB (2097152 512 byte sectors: 64H 32S/T 1024C) da2 at isp0 bus 0 target 3 lun 1 da2: Fixed Direct Access SCSI-2 device da2: 200.000MB/s transfers, Tagged Queueing Enabled da2: 51200MB (104857600 512 byte sectors: 255H 63S/T 6527C) da3 at isp0 bus 0 target 3 lun 3 da3: Fixed Direct Access SCSI-2 device da3: 200.000MB/s transfers, Tagged Queueing Enabled da3: 1024MB (2097152 512 byte sectors: 64H 32S/T 1024C) da8 at ciss0 bus 0 target 0 lun 0 da8: Fixed Direct Access SCSI-0 device da8: 135.168MB/s transfers da8: 8670MB (17756160 512 byte sectors: 255H 32S/T 2176C) da9 at ciss0 bus 0 target 1 lun 0 da9: Fixed Direct Access SCSI-0 device da9: 135.168MB/s transfers da9: 17359MB (35553120 512 byte sectors: 255H 32S/T 4357C) SMP: AP CPU #3 Launched! SMP: AP CPU #1 Launched! SMP: AP CPU #2 Launched! (da2:isp0:0:3:1): SYNCHRONIZE CACHE. CDB: 35 20 0 0 0 0 0 0 0 0 (da2:isp0:0:3:1): NOT READY info?:9000000 asc:4,2 (da2:isp0:0:3:1): Logical unit not ready, initializing cmd. required sks:0x93,0x100 (da3:isp0:0:3:3): SYNCHRONIZE CACHE. CDB: 35 60 0 0 0 0 0 0 0 0 (da3:isp0:0:3:3): NOT READY info?:9000000 asc:4,2 (da3:isp0:0:3:3): Logical unit not ready, initializing cmd. required sks:0x93,0x100 (da6:isp1:0:3:1): SYNCHRONIZE CACHE. CDB: 35 20 0 0 0 0 0 0 0 0 (da6:isp1:0:3:1): NOT READY info?:9000000 asc:4,2 (da6:isp1:0:3:1): Logical unit not ready, initializing cmd. required sks:0x93,0x100 (da7:isp1:0:3:3): SYNCHRONIZE CACHE. CDB: 35 60 0 0 0 0 0 0 0 0 (da7:isp1:0:3:3): NOT READY info?:9000000 asc:4,2 (da7:isp1:0:3:3): Logical unit not ready, initializing cmd. required sks:0x93,0x100 So, mailtest# camcontrol devlist at scbus0 target 0 lun 0 (pass0) at scbus0 target 1 lun 0 (pass1) at scbus0 target 1 lun 1 (pass2,da0) at scbus0 target 1 lun 3 (pass3,da1) at scbus0 target 2 lun 0 (pass4) at scbus0 target 3 lun 0 (pass5) at scbus0 target 3 lun 1 (pass6,da2) at scbus0 target 3 lun 3 (pass7,da3) at scbus1 target 0 lun 0 (pass8) at scbus1 target 0 lun 1 (pass9,da4) at scbus1 target 0 lun 3 (pass10,da5) at scbus1 target 1 lun 0 (pass11) at scbus1 target 2 lun 0 (pass12) at scbus1 target 3 lun 0 (pass13) at scbus1 target 3 lun 1 (pass14,da6) at scbus1 target 3 lun 3 (pass15,da7) at scbus2 target 0 lun 0 (pass16,da8) at scbus2 target 1 lun 0 (pass17,da9) What I do actually have is a 50 GB LUN ("vdisk" in HPQ-speak) that should be presented as "LUN 1" (da0, I presume) and a 5 GB LUN that should be "LUN 3" (da1). How the hell does it get that 4 times? Can I / should I prevent that? Thanks for your help. cheers, Rainer