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