From owner-freebsd-scsi Tue Jan 14 5:40:12 2003 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 960C337B401 for ; Tue, 14 Jan 2003 05:40:11 -0800 (PST) Received: from sax.sax.de (sax.sax.de [193.175.26.33]) by mx1.FreeBSD.org (Postfix) with ESMTP id 1EAF643F18 for ; Tue, 14 Jan 2003 05:40:10 -0800 (PST) (envelope-from j@uriah.heep.sax.de) Received: (from uucp@localhost) by sax.sax.de (8.9.3/8.9.3) with UUCP id OAA09436; Tue, 14 Jan 2003 14:40:03 +0100 (CET) Received: from uriah.heep.sax.de (localhost.heep.sax.de [127.0.0.1]) by uriah.heep.sax.de (8.12.6/8.12.6) with ESMTP id h0EDZ5m8012383; Tue, 14 Jan 2003 14:35:05 +0100 (MET) (envelope-from j@uriah.heep.sax.de) Received: (from j@localhost) by uriah.heep.sax.de (8.12.6/8.12.6/Submit) id h0EDZ5YF012382; Tue, 14 Jan 2003 14:35:05 +0100 (MET) Date: Tue, 14 Jan 2003 14:35:05 +0100 From: Joerg Wunsch To: "Justin T. Gibbs" Cc: freebsd-scsi@freebsd.org Subject: Re: quirk candidate: SEAGATE ST52160N Message-ID: <20030114143505.A12331@uriah.heep.sax.de> Reply-To: Joerg Wunsch Mail-Followup-To: Joerg Wunsch , "Justin T. Gibbs" , freebsd-scsi@freebsd.org References: <20030113220055.D50550@uriah.heep.sax.de> <147830000.1042501904@aslan.btc.adaptec.com> <20030114074853.A71485@uriah.heep.sax.de> <774150000.1042549034@aslan.scsiguy.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <774150000.1042549034@aslan.scsiguy.com>; from gibbs@scsiguy.com on Tue, Jan 14, 2003 at 05:57:14AM -0700 X-Phone: +49-351-2012 669 X-PGP-Fingerprint: DC 47 E6 E4 FF A6 E9 8F 93 21 E0 7D F9 12 D6 4E 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 As Justin T. Gibbs wrote: > >> It would be interesting to know the full content of the sense data. > > > > uncle# camcontrol cmd da1 -v -c '35 0 0 0 0 0 0 0 0 0' > > camcontrol: error sending command > > (pass1:ahc0:0:3:0): SYNCHRONIZE CACHE. CDB: 35 0 0 0 0 0 0 0 0 0 > > (pass1:ahc0:0:3:0): CAM Status: SCSI Status Error > > (pass1:ahc0:0:3:0): SCSI Status: Check Condition > > (pass1:ahc0:0:3:0): ILLEGAL REQUEST asc:20,0 > > (pass1:ahc0:0:3:0): Invalid command operation code: Command byte 0 is > > invalid > > So your disk doesn't always butcher byte zero of the sense data? Isn't byte 0 the `35' for the command? I. e., it is complaining that it doesn't understand the SYNCHRONIZE CACHE cmd at all. > This looks like a perfectly valid response. The response might be valid, but the request isn't (for that device). ;-) Not that i'd care much about this drive (it's experimental only, and i know they are crap), but message like this one IMHO confuse the users. SYNCHRONIZE CACHE is marked optional in the standard, i thought we'd automatically detect the non-support of this command by a target, and silently ignore it? -- cheers, J"org .-.-. --... ...-- -.. . DL8DTL http://www.sax.de/~joerg/ NIC: JW11-RIPE Never trust an operating system you don't have sources for. ;-) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message