armhold@constance.rutgers.edu (George Armhold) (10/13/90)
I've just downloaded the "BTN" SCSI tape handler from the net, but have not been able to get it to work. I'm using a "MaxStream" SCSI streaming tape, hung off of the A2091's external port. When I mount TAPE:, it tells me "Please insert volume TAPE:", and popping a tape into the drive and clicking retry satisifies the requester. But when I try to write to the drive, (say using 'tar', or the formattape file,) I get an I/O error. The tapemon program reports error code 45. I have the SCSI address of the tape drive set to 1, and the mountlist ID number set appropriately. Is there anything blatantly wrong that I'm doing here? Has anyone had any luck with this hardware combination? Any hints or suggestions greatly apprecited. Thanks, -George
DrBob@cup.portal.com (Robert A Rethemeyer) (10/13/90)
Can you provide a bit more information? The error code 45 is a generic
error reported by the hd driver which means the drive responded with
unit error status. To find the exact cause of the error, the handler
does a SENSE. That should have been reported on the same line with
the error code 45. What were the sense codes??
Next, when did the error occur? Tapemon prints what it is doing for
each tape operation. Was it "Writing block xxx" or "Capacity"?
Other people are reporting problems with the capacity determination
because apparently not many drives support the READ_CAPACITY command,
and will reject it with "illegal command" sense status. It's not clear
if that will prevent you from using the drive, though. Does the
tape move at all?
Send email if you would like to discuss this in a more timely fashion.
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
Bob Rethemeyer //"This is obviously some strange
DrBob@cup.portal.com -or- // usage of the word 'safe' that I hadn't
..!sun!portal!cup.portal.com!DrBob // previously been aware of." - A. Dentbillsey@agora.uucp (Bill Seymour) (10/15/90)
In article <Oct.12.18.55.52.1990.26131@constance.rutgers.edu> armhold@constance.rutgers.edu (George Armhold) writes:
:I've just downloaded the "BTN" SCSI tape handler from the net, but
:have not been able to get it to work. I'm using a "MaxStream" SCSI
:streaming tape, hung off of the A2091's external port.
:
:When I mount TAPE:, it tells me "Please insert volume TAPE:", and
:popping a tape into the drive and clicking retry satisifies the
:requester. But when I try to write to the drive, (say using 'tar', or
:the formattape file,) I get an I/O error. The tapemon program reports
:error code 45. I have the SCSI address of the tape drive set to 1,
:and the mountlist ID number set appropriately.
:
:Is there anything blatantly wrong that I'm doing here? Has anyone had any
:luck with this hardware combination?
:
:Any hints or suggestions greatly apprecited.
:
:Thanks,
:-George
I'm getting the same types of errors with the Adaptec 3530, Emulex
MT-02 and Archive Viper. I believe it has something to do with the command
for READ_CAPACITY that's sent out. Possibly that puts the drive into some
mode it shouldn't be in. (Note that none of those controllers support that
command.) It's possible that just commenting out that portion of the source
and recompiling will allow it to work with your hardware. You might also
check out the tape handler from Markus Wandel that Larry posted.
--
-Bill Seymour billsey@agora
***** American People/Link Amiga Zone Hardware Specialist NES*BILL *****
Bejed, Inc. NES, Inc. Northwest Amiga Group At Home Sometimes
(503) 281-8153 (503) 246-9311 (503) 656-7393 BBS (503) 640-0842goldstein@arrods.enet.dec.com (Steve Goldstein) (10/16/90)
In article <1990Oct15.154914.11593@agora.uucp>, you write... > I'm getting the same types of errors with the Adaptec 3530, Emulex >MT-02 and Archive Viper. I believe it has something to do with the command >for READ_CAPACITY that's sent out. Possibly that puts the drive into some >mode it shouldn't be in. (Note that none of those controllers support that >command.) It's possible that just commenting out that portion of the source >and recompiling will allow it to work with your hardware. You might also >check out the tape handler from Markus Wandel that Larry posted. > >-- > -Bill Seymour billsey@agora >***** American People/Link Amiga Zone Hardware Specialist NES*BILL ***** >Bejed, Inc. NES, Inc. Northwest Amiga Group At Home Sometimes >(503) 281-8153 (503) 246-9311 (503) 656-7393 BBS (503) 640-0842 I'm also getting errors But IO_error = 42 (Phase error) using a Hardframe and a TEAC MT-2ST/45S Digital Cassette tape drive. I sent the info to DrBob and he is looking in to removing the READ_CAPACITY at some time...??!! The HardFrame is at 1.5 and I hope to have the new Eprom Sometime in the future.. Steve Goldstein Digital Equipment Co England. goldstein@arrods.enet.dec.com Steve Goldstein Digital Equipment Co England. goldstein@arrods.enet.dec.com
osymh@msu2.oscs.montana.edu (10/17/90)
In article <Oct.12.18.55.52.1990.26131@constance.rutgers.edu>, armhold@constance.rutgers.edu (George Armhold) writes: >I've just downloaded the "BTN" SCSI tape handler from the net, but >have not been able to get it to work. I'm using a "MaxStream" SCSI >streaming tape, hung off of the A2091's external port. > >When I mount TAPE:, it tells me "Please insert volume TAPE:", and >popping a tape into the drive and clicking retry satisifies the >requester. But when I try to write to the drive, (say using 'tar', or >the formattape file,) I get an I/O error. The tapemon program reports >error code 45. I have the SCSI address of the tape drive set to 1, >and the mountlist ID number set appropriately. > >Is there anything blatantly wrong that I'm doing here? Has anyone had any >luck with this hardware combination? > >Any hints or suggestions greatly apprecited. > >Thanks, >-George And in article <1990Oct15.154914.11593@agora.uucp> billsey@agora.uucp (Bill Seymour) replies: > I'm getting the same types of errors with the Adaptec 3530, Emulex >MT-02 and Archive Viper. I believe it has something to do with the command >for READ_CAPACITY that's sent out. Possibly that puts the drive into some >mode it shouldn't be in. (Note that none of those controllers support that >command.) It's possible that just commenting out that portion of the source >and recompiling will allow it to work with your hardware. You might also >check out the tape handler from Markus Wandel that Larry posted. I ran into the same problem the first time I tried to use that tape handler. The problem is that the handler is written for a 3-M MCD-40 tape drive. From looking at the source, it looks like the 3-M tape drive is block-addressable, since a block number is inserted into the SCSI command sent to the drive. Also, the command does not have the "fixed" bit set in byte 1, which may cause the command to be rejected if the tape drive does not support variable length blocks. The Wangtek drive I am using only supports a fixed-length block. I was able to patch the read command setup to set cdb[1] to 0x01 and not store the block number in cdb[2] and cdb[3]. Then the driver was able to read the tape. I did not do anything more with that driver, but the same thing could be done with the write command setup. I'm not sure what affect the READ_CAPACITY command would have, since the command would fail and could come up with garbage for the capacity of the tape. That could cause the end of tape to occur anywhere. The write would need to be modified to detect the End-of-Medium sense status to trigger a new tape. --- Michael L. Hitch OSYMH@MTSUNIX1.BITNET Computer Services Consultant osymh@msu2.oscs.montana.edu Office of Systems and Computing Services Montana State University Bozeman, MT USA
ridder@elvira.enet.dec.com (Hans Ridder) (10/24/90)
In article <0093E482.AA8FD220@msu2.oscs.montana.edu> osymh@msu2.oscs.montana.edu writes: > I ran into the same problem the first time I tried to use that tape >handler. The problem is that the handler is written for a 3-M MCD-40 >tape drive. From looking at the source, it looks like the 3-M tape >drive is block-addressable, since a block number is inserted into the >SCSI command sent to the drive. Yes, the BTN tape handler was written for the 3M MCD-40 which is a block addressed device. Sorta like a very slow disk. It does *not* act like a normal SCSI tape drive acts (or a normal SCSI disk, for that matter.) The handler doesn't look like it would deal with a normal SCSI tape very well either. Just like the MCD-40, it doesn't know about variable length records, file marks, logical EOT, etc. NOTE: All the folks with drives other than the MCD-40 who are having trouble with BTN-Tape might want to try the tape handler by Markus Wandel (?) It was posted a few days after BTN-Tape. I haven't tried it, but it looks like it was made for *real* SCSI tape drives (variable length records, file marks, etc.) >Michael L. Hitch OSYMH@MTSUNIX1.BITNET -hans ------------------------------------------------------------------------ Hans-Gabriel Ridder Digital Equipment Corporation ridder@elvira.enet.dec.com Customer Support Center ...decwrl!elvira.enet!ridder Colorado Springs, CO