From owner-freebsd-scsi@FreeBSD.ORG Sun Jul 25 05:41:33 2004 Return-Path: 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 8AA8816A4CE for ; Sun, 25 Jul 2004 05:41:33 +0000 (GMT) Received: from pimout1-ext.prodigy.net (pimout1-ext.prodigy.net [207.115.63.77]) by mx1.FreeBSD.org (Postfix) with ESMTP id 8F82943D48 for ; Sun, 25 Jul 2004 05:41:32 +0000 (GMT) (envelope-from julian@elischer.org) Received: from elischer.org (adsl-68-121-219-69.dsl.snfc21.pacbell.net [68.121.219.69])i6P5fVDi046658 for ; Sun, 25 Jul 2004 01:41:31 -0400 Message-ID: <4103480A.40309@elischer.org> Date: Sat, 24 Jul 2004 22:41:30 -0700 From: Julian Elischer User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; en-US; rv:1.4b) Gecko/20030524 X-Accept-Language: en, hu MIME-Version: 1.0 To: scsi@freebsd.org Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Subject: odd scsi behaviour. X-BeenThere: freebsd-scsi@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: SCSI subsystem List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 25 Jul 2004 05:41:33 -0000 A new raid array has teh following odd behaviour. 1/ old array in same spot worked. 2/ new array shows up in adaptec bios 3/ FreeBSD finds NOTHING on scsi bus. any suggestions as to how to convince FreeBSD to find the device? (target 1 LUN 0) Bios and device set to 80MB/s 160MB/s acts the same Julian From owner-freebsd-scsi@FreeBSD.ORG Sun Jul 25 10:51:12 2004 Return-Path: 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 007FB16A4CE for ; Sun, 25 Jul 2004 10:51:12 +0000 (GMT) Received: from pooker.samsco.org (pooker.samsco.org [168.103.85.57]) by mx1.FreeBSD.org (Postfix) with ESMTP id 8F8A143D2D for ; Sun, 25 Jul 2004 10:51:11 +0000 (GMT) (envelope-from scottl@freebsd.org) Received: from [192.168.0.12] (g4.samsco.home [192.168.0.12]) (authenticated bits=0) by pooker.samsco.org (8.12.11/8.12.10) with ESMTP id i6PAvhQI078304; Sun, 25 Jul 2004 04:57:44 -0600 (MDT) (envelope-from scottl@freebsd.org) Message-ID: <4103905A.6010701@freebsd.org> Date: Sun, 25 Jul 2004 04:50:02 -0600 From: Scott Long User-Agent: Mozilla/5.0 (Macintosh; U; PPC Mac OS X Mach-O; en-US; rv:1.7) Gecko/20040514 X-Accept-Language: en-us, en MIME-Version: 1.0 To: Julian Elischer References: <4103480A.40309@elischer.org> In-Reply-To: <4103480A.40309@elischer.org> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-Spam-Status: No, hits=0.0 required=3.8 tests=none autolearn=no version=2.63 X-Spam-Checker-Version: SpamAssassin 2.63 (2004-01-11) on pooker.samsco.org cc: scsi@freebsd.org Subject: Re: odd scsi behaviour. X-BeenThere: freebsd-scsi@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: SCSI subsystem List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 25 Jul 2004 10:51:12 -0000 Julian Elischer wrote: > > A new raid array has teh following odd behaviour. > > 1/ old array in same spot worked. > 2/ new array shows up in adaptec bios > 3/ FreeBSD finds NOTHING on scsi bus. > > any suggestions as to how to convince FreeBSD to find the device? > (target 1 LUN 0) > > Bios and device set to 80MB/s > 160MB/s acts the same > > Julian > Uh, what controller are you talking about? scott From owner-freebsd-scsi@FreeBSD.ORG Mon Jul 26 13:46:32 2004 Return-Path: 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 E5C0216A4CE for ; Mon, 26 Jul 2004 13:46:32 +0000 (GMT) Received: from www.reppep.com (www.reppep.com [66.92.104.200]) by mx1.FreeBSD.org (Postfix) with ESMTP id 802DD43D46 for ; Mon, 26 Jul 2004 13:46:28 +0000 (GMT) (envelope-from pepper@reppep.com) Received: from [129.85.219.160] (salt.rockefeller.edu [129.85.219.160]) by www.reppep.com (Postfix) with ESMTP id 58CD9FDC4; Mon, 26 Jul 2004 09:46:25 -0400 (EDT) Mime-Version: 1.0 Message-Id: In-Reply-To: <20040724003645.V18285@gaff.hhhr.ision.net> References: <20040723112232.D909@ganymede.hub.org> <20040724003645.V18285@gaff.hhhr.ision.net> Date: Mon, 26 Jul 2004 09:46:00 -0400 To: Olaf Hoyer From: Chris Pepper Content-Type: text/plain; charset="us-ascii" ; format="flowed" cc: freebsd-scsi@freebsd.org Subject: Re: Intel SCRZCR Controller on Tyan K7XPro Motherboard ... X-BeenThere: freebsd-scsi@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: SCSI subsystem List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 26 Jul 2004 13:46:33 -0000 At 12:39 AM +0200 2004/07/24, Olaf Hoyer wrote: >On Fri, 23 Jul 2004, Marc G. Fournier wrote: > >> >> According to the Tyan web site "Adaptec and Intel Zero-Channel RAID ready" >> ... has anyone successfully gotten the above MB working with the above >> controller? >> >> We just built a new system, everything appears to work great until we plug >> in the ZCR, at which point, as the techie describes: "When I boot the >> server up with that raid card in the proper slot, it just powers itself >> off immediately." >> >> Now, I'm pretty much ready to say to hell with it and go with s/w RAID, >> but I want to make sure we haven't overlooked something obvious here first >> ... > >Hmm, a quick shot: Is it the same zero-Channel card that Intel also >sells for the Sun Fire 65x series? > >Then its basically a ICP-Vortex design, and I remember, that on Intel >Mainboards you need to plug it in a special slot, because it only works >in that slot properly. > >Got some time ago a 65x for a short time to test, and that card worked >properly with 4.9R and 5.2.1R. For reference, here's a snip from "pciconf -l" on a SF V65x running RH Enterprise Linux 3 with the Intel ZCR card (bought from Sun): 04:08.0 RAID bus controller: Intel Corp. RAID Controller Subsystem: Intel Corp.: Unknown device 01af Flags: bus master, 66Mhz, slow devsel, latency 64, IRQ 48 Memory at fa000000 (32-bit, prefetchable) [size=32M] Expansion ROM at fe9f8000 [disabled] [size=32K] Capabilities: [80] Power Management version 2 Chris -- Chris Pepper: Rockefeller University: From owner-freebsd-scsi@FreeBSD.ORG Tue Jul 27 18:15:19 2004 Return-Path: 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 E97A216A4CE; Tue, 27 Jul 2004 18:15:19 +0000 (GMT) Received: from mail.vicor-nb.com (bigwoop.vicor-nb.com [208.206.78.2]) by mx1.FreeBSD.org (Postfix) with ESMTP id D274643D31; Tue, 27 Jul 2004 18:15:19 +0000 (GMT) (envelope-from julian@elischer.org) Received: from elischer.org (julian.vicor-nb.com [208.206.78.97]) by mail.vicor-nb.com (Postfix) with ESMTP id EE0B47A489; Tue, 27 Jul 2004 11:15:15 -0700 (PDT) Message-ID: <41069BB3.7060702@elischer.org> Date: Tue, 27 Jul 2004 11:15:15 -0700 From: Julian Elischer User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; en-US; rv:1.3.1) Gecko/20030516 X-Accept-Language: en, hu MIME-Version: 1.0 To: Scott Long References: <4103480A.40309@elischer.org> <4103905A.6010701@freebsd.org> In-Reply-To: <4103905A.6010701@freebsd.org> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit cc: scsi@freebsd.org Subject: Re: odd scsi behaviour. X-BeenThere: freebsd-scsi@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: SCSI subsystem List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 27 Jul 2004 18:15:20 -0000 Scott Long wrote: > Julian Elischer wrote: > >> >> A new raid array has teh following odd behaviour. >> >> 1/ old array in same spot worked. >> 2/ new array shows up in adaptec bios >> 3/ FreeBSD finds NOTHING on scsi bus. >> >> any suggestions as to how to convince FreeBSD to find the device? >> (target 1 LUN 0) >> >> Bios and device set to 80MB/s >> 160MB/s acts the same >> >> Julian >> > > Uh, what controller are you talking about? it's a adaptec 29160 the disk is a chaparral raid, and the on eits replacing was a chaparral raid.. the bios sees it and reports back various info about it but freebsd doesn't even find it on the bus. > > > scott From owner-freebsd-scsi@FreeBSD.ORG Wed Jul 28 01:47:48 2004 Return-Path: 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 634FF16A4D6; Wed, 28 Jul 2004 01:47:48 +0000 (GMT) Received: from pooker.samsco.org (pooker.samsco.org [168.103.85.57]) by mx1.FreeBSD.org (Postfix) with ESMTP id AE89843D60; Wed, 28 Jul 2004 01:47:47 +0000 (GMT) (envelope-from scottl@samsco.org) Received: from [192.168.2.73] (cpe.125.wat.v126.packetworks.net [64.235.97.125] (may be forged)) (authenticated bits=0) by pooker.samsco.org (8.12.11/8.12.10) with ESMTP id i6S1sUs9089565; Tue, 27 Jul 2004 19:54:31 -0600 (MDT) (envelope-from scottl@samsco.org) Message-ID: <41070544.4040609@samsco.org> Date: Tue, 27 Jul 2004 19:45:40 -0600 From: Scott Long User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; en-US; rv:1.7) Gecko/20040702 X-Accept-Language: en-us, en MIME-Version: 1.0 To: Julian Elischer References: <4103480A.40309@elischer.org> <4103905A.6010701@freebsd.org> <41069BB3.7060702@elischer.org> In-Reply-To: <41069BB3.7060702@elischer.org> X-Enigmail-Version: 0.84.2.0 X-Enigmail-Supports: pgp-inline, pgp-mime Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-Spam-Status: No, hits=0.0 required=3.8 tests=none autolearn=no version=2.63 X-Spam-Checker-Version: SpamAssassin 2.63 (2004-01-11) on pooker.samsco.org cc: Scott Long cc: scsi@freebsd.org Subject: Re: odd scsi behaviour. X-BeenThere: freebsd-scsi@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: SCSI subsystem List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 28 Jul 2004 01:47:48 -0000 Julian Elischer wrote: > > > Scott Long wrote: > >> Julian Elischer wrote: >> >>> >>> A new raid array has teh following odd behaviour. >>> >>> 1/ old array in same spot worked. >>> 2/ new array shows up in adaptec bios >>> 3/ FreeBSD finds NOTHING on scsi bus. >>> >>> any suggestions as to how to convince FreeBSD to find the device? >>> (target 1 LUN 0) >>> >>> Bios and device set to 80MB/s >>> 160MB/s acts the same >>> >>> Julian >>> >> >> Uh, what controller are you talking about? > > > > it's a adaptec 29160 > the disk is a chaparral raid, and the on eits replacing was a chaparral > raid.. > > the bios sees it and reports back various info about it > but freebsd doesn't even find it on the bus. > Maybe the chaparral box isn't responding to our scsi probe correctly. have you tried turning on scsi debugging and seeing what that shows? I haven't played with a chaparral box in several years, so I have no idea what their design is based on these days. They might have switched to a really poor/buggy scsi target emulation package. Scott