From owner-freebsd-scsi Wed Nov 20 6: 0:23 2002 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 4D40C37B401 for ; Wed, 20 Nov 2002 06:00:22 -0800 (PST) Received: from c0mailgw04.prontomail.com (mailgw.prontomail.com [209.185.149.10]) by mx1.FreeBSD.org (Postfix) with ESMTP id 0CEA943E42 for ; Wed, 20 Nov 2002 06:00:22 -0800 (PST) (envelope-from xxxlucasxxx@canoemail.com) Received: from c0web111 (209.185.149.10) by c0mailgw04.prontomail.com (NPlex 6.0.045) id 3DDB91E70000054C; Wed, 20 Nov 2002 06:01:03 -0800 X-Version: canoe 6.2.2329.0 From: "Lucas" Message-Id: <86DBB58B94E51AB4B949DFDE68EE2952@xxxlucasxxx.canoemail.com> Date: Wed, 20 Nov 2002 09:00:19 -0500 X-Priority: Normal Content-Type: text/plain; charset=iso-8859-1 To: freebsd-scsi@freebsd.org Subject: Re: Initializing SCSI drive ST15150W Cc: joerg_wunsch@uriah.heep.sax.de X-Mailer: Web Based Pronto Mime-Version: 1.0 Content-Transfer-Encoding: 7bit Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org Just to note. I have figured out the problem. The SCSI controller I am using is an ASUS SC875 (which if I put in the post probably would have helped some). The sym driver recognizes it, but really isn't able to play with the devices attached to it. I tried the ncr driver which recognizes the controller and the hd attached to it. As noted the sym driver will require some patch for the drive to play with the hd which currently is a bit beyond my abilities (and time). Lucas ---- Begin Original Message ---- From: j@uriah.heep.sax.de (Joerg Wunsch) Sent: Tue, 19 Nov 2002 08:01:23 +0100 (MET) To: freebsd-scsi@freebsd.org CC: xxxlucasxxx@canoemail.com Subject: Re: Initializing SCSI drive ST15150W xxxlucasxxx@canoemail.com wrote: > Waiting 15 seconds for SCSI devices to settle > (noperiph:sym0:0:-1:-1): SCSI BUS reset delivered. > (probe2:sym0:0:2:0): extraneous data discarded. > (probe2:sym0:0:2:0): COMMAND FAILED (87 0 1). > (probe2:sym0:0:2:0): ODD transfer in DATA IN phase. ISTR that you can patch the sym driver to not complain about this. However, last time we've been discussing it, it turned out that this is usually an indication of a firmware bug in the drive. Is it possible for you to upgrade the drive firmware? -- cheers, J"org .-.-. --... ...-- -.. . DL8DTL http://www.sax.de/~joerg/ NIC: JW11-RIPE Never trust an operating system you don't have sources for. ;-) ---- End Original Message ---- Sign up today for your Free E-mail at: http://www.canoe.ca/CanoeMail To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message