home *** CD-ROM | disk | FTP | other *** search
- Xref: sparky comp.sys.next.sysadmin:7367 comp.sys.next.misc:23652
- Path: sparky!uunet!europa.asd.contel.com!howland.reston.ans.net!spool.mu.edu!olivea!sgigate!odin!sgihub!zola!zuni!anchor!olson
- From: olson@anchor.esd.sgi.com (Dave Olson)
- Newsgroups: comp.sys.next.sysadmin,comp.sys.next.misc
- Subject: Re: Using tar with a SCSI DAT drive
- Message-ID: <un8fkqo@zuni.esd.sgi.com>
- Date: 10 Jan 93 19:47:53 GMT
- References: <1993Jan10.090824.24470@cs.ucla.edu>
- Sender: news@zuni.esd.sgi.com (Net News)
- Distribution: usa
- Organization: Silicon Graphics, Inc. Mountain View, CA
- Lines: 22
-
- In <1993Jan10.090824.24470@cs.ucla.edu> grw@oahu.cs.ucla.edu (George Wu) writes:
- | I recently installed an Archive Python SCSI DAT drive on my system
- | (NeXTStation Mono running NS 2.1) for backup purposes. However, I
- | have been unable to use tar on the drive. I always get an 'I/O error'
- | when I run tar and the associated SCSI error is as follows.
- |
- | st: cmd = 0x15 sr_io_status = 2H
- | Sense key = 0x5 Sense Code = 0x1a
- |
- | According to scsireg.h the SCSI command causing the problem is MODE
- | SELECT and the sense key (0x5) indicates invalid request. Does anyone
- | know the solution to this problem ? Any help is appreciated.
-
- sense code 1a indicates parameter overrun, which presumably
- means that one of the bytes in the command is out of range.
-
- Perhaps you (or the driver) is trying for a blocksize that the
- drive doesn't support?
- --
- Let no one tell me that silence gives consent, | Dave Olson
- because whoever is silent dissents. | Silicon Graphics, Inc.
- Maria Isabel Barreno | olson@sgi.com
-