From owner-freebsd-scsi Thu Oct 15 15:37:08 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id PAA20862 for freebsd-scsi-outgoing; Thu, 15 Oct 1998 15:37:08 -0700 (PDT) (envelope-from owner-freebsd-scsi@FreeBSD.ORG) Received: from panzer.plutotech.com (panzer.plutotech.com [206.168.67.125]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id PAA20848 for ; Thu, 15 Oct 1998 15:37:03 -0700 (PDT) (envelope-from ken@panzer.plutotech.com) Received: (from ken@localhost) by panzer.plutotech.com (8.9.1/8.8.5) id QAA20556; Thu, 15 Oct 1998 16:36:32 -0600 (MDT) From: "Kenneth D. Merry" Message-Id: <199810152236.QAA20556@panzer.plutotech.com> Subject: Re: Strange error In-Reply-To: from "Matthew N. Dodd" at "Oct 15, 98 05:25:43 pm" To: winter@jurai.net (Matthew N. Dodd) Date: Thu, 15 Oct 1998 16:36:32 -0600 (MDT) Cc: scsi@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL28s (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Matthew N. Dodd wrote... > > eisa-test# dmesg | grep da2 > da2 at bt0 bus 0 target 2 lun 0 > da2: Removable Direct Access SCSI2 device > da2: 5.0MB/s transfers (5.0MHz, offset 8) > da2: Attempt to query device size failed: NOT READY, Medium not present > > (I've booted with no media in the drive.) > > 'chio status' (after a 'chio move slot 15 drive 0') > ... > drive 0: Your changer shouldn't have any effect on a removable media drive... > eisa-test# camcontrol tur -n da -u 2 -v > Unit is not ready > (pass3:bt0:0:2:0): TEST UNIT READY. CDB: 0 0 0 0 0 0 > (pass3:bt0:0:2:0): NOT READY asc:4,2 > (pass3:bt0:0:2:0): Logical unit not ready, initializing cmd. required > > Ok, that seems reasonable enough... Yep, it wants to be spun up. > eisa-test# camcontrol start -n da -u 2 -v > Error received from start unit command > (pass3:bt0:0:2:0): STOP START UNIT. CDB: 1b 0 0 0 1 0 > (pass3:bt0:0:2:0): HARDWARE FAILURE asc:44,0 > (pass3:bt0:0:2:0): Internal target failure sks:80,2 > > WTF does 'sks:80,2' tell me? It's a sense key specific error. In this case, the "0x80" part means that the sense key specific value is valid. The "2" part is the "actual retry count". Here's a quote from the SCSI 2 spec: ================= The actual retry count field returns implementation-specific information on the actual number of retries of the recovery algorithm used in attempting to recover an error or exception condition. NOTE 88 This field should relate to the retry count fields within the error recovery page of the MODE SELECT command. ================= Did you have a disk in the drive at the time? Ken -- Kenneth Merry ken@plutotech.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message