From owner-freebsd-scsi Sat Oct 5 07:21:32 1996 Return-Path: owner-freebsd-scsi Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id HAA19047 for freebsd-scsi-outgoing; Sat, 5 Oct 1996 07:21:32 -0700 (PDT) Received: from irz301.inf.tu-dresden.de (irz301.inf.tu-dresden.de [141.76.1.11]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id HAA19034 for ; Sat, 5 Oct 1996 07:21:24 -0700 (PDT) Received: from sax.sax.de (sax.sax.de [193.175.26.33]) by irz301.inf.tu-dresden.de (8.6.12/8.6.12-s1) with ESMTP id QAA19765; Sat, 5 Oct 1996 16:20:59 +0200 Received: (from uucp@localhost) by sax.sax.de (8.6.12/8.6.12-s1) with UUCP id QAA19820; Sat, 5 Oct 1996 16:20:58 +0200 Received: (from j@localhost) by uriah.heep.sax.de (8.7.5/8.6.9) id QAA00829; Sat, 5 Oct 1996 16:05:06 +0200 (MET DST) From: J Wunsch Message-Id: <199610051405.QAA00829@uriah.heep.sax.de> Subject: Re: verbose but cryptic error To: freebsd-scsi@FreeBSD.org (FreeBSD SCSI list) Date: Sat, 5 Oct 1996 16:05:05 +0200 (MET DST) Cc: hsu@freefall.freebsd.org (Jeffrey Hsu) Reply-To: joerg_wunsch@uriah.heep.sax.de (Joerg Wunsch) In-Reply-To: <199610050853.BAA03934@freefall.freebsd.org> from Jeffrey Hsu at "Oct 5, 96 01:53:13 am" 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 X-Mailer: ELM [version 2.4ME+ PL17 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-scsi@FreeBSD.org X-Loop: FreeBSD.org Precedence: bulk As Jeffrey Hsu wrote: > Sense key is "Illegal request" > The Information field is 00000000 (0). > The Command Specific Information field is 00000000 (0). > Additional sense code: 26 > Additional sense code qualifier: 00 > Illegal value in the parameter list. > Bit 0 of byte 9 (value 00) is illegal. > sense (32 of 48): > f0 00 05 00 00 00 00 0a 00 00 00 00 26 00 00 88 > 00 09 00 00 00 00 00 00 00 00 00 00 00 00 00 00 I'm always having a hard time to figure out what `byte 9' might be. If i'm counting correctly, byte 9 is the MSB byte of the block length parameter in the block descriptor. It is really weird that the drive complains about it being 0. Can you run the following on your drive? scsi -f /dev/rsd2.ctl -v -c "1a 0 0 0 v:i1 0" 12 -i 12 \ "{mode data len} i1 {type} i1 {device-specific} i1 {blkdesc len} i1 \ {density} i1 {numblk} i3 {reserved} i1 {bllen} i3" mode data len: 15 type: 0 device-specific: 16 blkdesc len: 8 density: 0 numblk: 0 reserved: 0 bllen: 512 Btw., what drive (vendor) is it? -- cheers, J"org joerg_wunsch@uriah.heep.sax.de -- http://www.sax.de/~joerg/ -- NIC: JW11-RIPE Never trust an operating system you don't have sources for. ;-)