Learn how to a build a cloud-first strategyRegister Now

x
  • Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 313
  • Last Modified:

Tar to/from Aiwa Travan 20 SCSI Tape drive

The problem has changed.

I terminated both the 2940UW SCSI card and the AIWA Travan 20 (QIC/TR-5) tape drive.  I set the SCSI controller to the lowest transfer rate, 10M/sec, and made it asynchronous.  This was suggested by a respondant.  Here's what I got from the "dmesg"

(scsi0) <Adaptec AHA-294X Ultra SCSI host adapter> found at PCI 13/0
(scsi0) Wide Channel, SCSI ID=7, 16/255 SCBs
(scsi0) Downloading sequencer code... 419 instructions downloaded
scsi0 : Adaptec AHA274x/284x/294x (EISA/VLB/PCI-Fast SCSI) 5.1.10/3.2.4
       <Adaptec AHA-294X Ultra SCSI host adapter>
scsi : 1 host.
  Vendor: AIWA      Model: TD-20001          Rev: 0159
  Type:   Sequential-Access                  ANSI SCSI revision: 02
Detected scsi tape st0 at scsi0, channel 0, id 4, lun 0
(scsi0:0:4:0) Using asynchronous transfers


Now the tape drive keeps blinking orange with a tape and I get this error everytime I try to send a command to the Tape Drive:

/dev/st0: Input/output error

I tried reverting back to the oringinal settings but I keep getting the same error.  If someone has an idea of what is happening, can you share it with me.  Much obliged.



Fustrated Pat








I used Modprobe to install my Adaptec 2940UW and it seems to identify my tape drive too.  When I do a "tar cvf /dev/st0 /bin"  It goes through all the files of the /bin directory, and the tape starts spinning.  Then at the end, I get these error messages:

st0: Error with sense data: Current error st09:00: sense key Medium Error
Additional sense indicates Write error
st0: Error on write file mark
st0: Error with sense data: extra data not valid Current error st09:00: sense key Medium Error
Additional sense indicates Write error
tar: WARNING : Cannot close /dev/st0 (3, -1): Input/Output error

So does anybody know what this means and how I can get my tape drive to wrok properly.


Pat


0
patnut
Asked:
patnut
  • 4
  • 3
1 Solution
 
tzangerCommented:
Try the obvious first: make sure your termination is done properly.  SCSI tapes like to have parity set too (it's usually a jumper option)

after that try mt retention and see if it works.  

You may also wish to try dumping a testfile

dd if=/dev/zero of=myfile bs=1k count=10000  (create a 10 meg file)
tar cvf /dev/st0 myfile

and see if you get the same errors.
0
 
patnutAuthor Commented:
Edited text of question.
0
 
patnutAuthor Commented:
Adjusted points from 100 to 300
0
Concerto's Cloud Advisory Services

Want to avoid the missteps to gaining all the benefits of the cloud? Learn more about the different assessment options from our Cloud Advisory team.

 
tzangerCommented:
Sounds like it is no longer recognizing the tape.  Couple possibilites

- heads dirty (not as uncommon as you think)
- tape wound itself off the spool (happens if the tape drive isn't clean
- bad tape -- have you tried another?
0
 
patnutAuthor Commented:
Comment accepted as answer
0
 
patnutAuthor Commented:
I actually had a bad tape drive
0
 
tzangerCommented:
so are your tape problems over now or are you constantly getting I/O errors?
0

Featured Post

Independent Software Vendors: We Want Your Opinion

We value your feedback.

Take our survey and automatically be enter to win anyone of the following:
Yeti Cooler, Amazon eGift Card, and Movie eGift Card!

  • 4
  • 3
Tackle projects and never again get stuck behind a technical roadblock.
Join Now