Date: Sat, 25 Jan 1997 15:58:26 +0100 From: j@uriah.heep.sax.de (J Wunsch) To: chris@bb.cc.wa.us (Chris Coleman) Cc: freebsd-scsi@FreeBSD.org (FreeBSD SCSI list) Subject: Re: Tape Backup Drive Not working. Message-ID: <Mutt.19970125155826.j@uriah.heep.sax.de> In-Reply-To: <Pine.NEB.3.94.970123182738.16725A-100000@aries.bb.cc.wa.us>; from Chris Coleman on Jan 23, 1997 18:36:01 -0800 References: <Mutt.19970123203514.j@uriah.heep.sax.de> <Pine.NEB.3.94.970123182738.16725A-100000@aries.bb.cc.wa.us>
next in thread | previous in thread | raw e-mail | index | archive | help
As Chris Coleman wrote: > > (Btw., your mail was mis-referenced. I've also moved this to the > > SCSI list.) > Thanks, i didnt even think of that, I only subscribe to -hackers. No deal, we can Cc you. > > Which one? (Probe string) > > "Conner CTT8000-S 1.17" Type 1 removable SCSI2 > st0(ahc:0:3:0):Sequential-Access Density Code 0x45, Drive Empty Never heard of such a beast. The density code is far beyond those mentioned in the SCSI-2 specs. I assume this is something only compatible to itself? > > > /kernel st0 (ahc:0:3:0): ILLEGAL REQUEST asc: 24,0 Invalid field in CDB > > > /kernel st0: bad request, must be between 0 and 0 > > > /kernel st0 (ahc:0:3:0): ILLEGAL REQUEST asc: 24,0 Invalid field in CDB > > > > Which blocksize setting? (output of `mt status') > > -- > mt status: > > Present Mode: Density = 0x00 Blocksize Variable Do you have any kind of doc for it? Is variable blocking even supported for that model? If not, try to wire down the drive to 512 or 1024 bytes per block, e.g. mt blocksize 512 (This will only last for one mount-session.) I'm not sure how recent your system is. If it's not from the 2.2 line, you might give the 2.2 boot+fixit combo a try as well. I remember that the ``must be between 0 and 0'' bogosity happend often previously, and seemingly has been fixed since. If all this is of no help, you need to turn on SCSIDEBUG (kernel option), and dive into all of this. Unfortunately, SCSI debug messages are fairly verbose, and i haven't found a good model yet to trim them down to something useful, you best turn everything on and just filter ``by brain'' to spot the really important information. You need a bit of understanding about the SCSI command structure. At least, we need to learn which command the drive is complaining about, and what exactly is the invalid field in the CDB (command descriptor block) -- the latter information is called `sks' (sense key specific information). -- 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. ;-)
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?Mutt.19970125155826.j>