Hello everyone, I am trying to get my scsi tape drive to work. Not matter what I do I get I/O errors. for example:
mt -f /dev/st0 status /dev/st0: Input/output error
mt -f /dev/nst0 status /dev/nst0: Input/output error
when I run command without a tape in I get: mt -f /dev/nst0 status
SCSI 2 tape drive: File number=-1, block number=-1, partition=0. Tape block size 0 bytes. Density code 0x0 (default). Soft error count since last status=0 General status bits on (50000): DR_OPEN IM_REP_EN
-Tape drive: HP SureStore T4i
-Linux 2.6.9-1.667 i686 GNU/Linux
______________________________________________________________________________________ Command dmesg | grep scsi, shows: scsi: ***** BusLogic SCSI Driver Version 2.1.16 of 18 July 2002 ***** scsi: Copyright 1995-1998 by Leonard N. Zubkoff lnz@dandelion.com scsi0: Configuring BusLogic Model BT-930 PCI Ultra SCSI Host Adapter scsi0: Firmware Version: 5.02, I/O Address: 0x2400, IRQ Channel: 11/Level scsi0: PCI Bus: 0, Device: 16, Address: 0x41300000, Host Adapter SCSI ID: 7 scsi0: Parity Checking: Enabled, Extended Translation: Enabled scsi0: Synchronous Negotiation: Fast, Wide Negotiation: Disabled scsi0: Disconnect/Reconnect: Enabled, Tagged Queuing: Enabled scsi0: Driver Queue Depth: 255, Scatter/Gather Limit: 128 segments scsi0: Tagged Queue Depth: Automatic, Untagged Queue Depth: 3 scsi0: SCSI Bus Termination: Enabled, SCAM: Disabled scsi0: *** BusLogic BT-930 Initialized Successfully *** scsi0 : BusLogic BT-930 Attached scsi tape st0 at scsi0, channel 0, id 4, lun 0 ------------------------------------------------------------------------------------Command lsmod, reveals: Module Size Used by parport_pc 24705 1 lp 11565 0 parport 41737 2 parport_pc,lp autofs4 24005 0 i2c_dev 10433 0 i2c_core 22081 1 i2c_dev sunrpc 160421 1 md5 4033 1 ipv6 232577 12 uhci_hcd 31449 0 e100 39364 0 mii 4673 1 e100 floppy 58609 0 st 34781 0 BusLogic 71645 0 scsi_mod 118417 2 st,BusLogic dm_snapshot 17029 0 dm_zero 2369 0 dm_mirror 23341 2 ext3 116809 2 jbd 74969 1 ext3 dm_mod 54741 6 dm_snapshot,dm_zero,dm_mirror -------------------------------------------------------------------------------- /proc/scsi/scsi:
Attached devices: Host: scsi0 Channel: 00 Id: 04 Lun: 00 Vendor: HP Model: T4000s Rev: 1.07 Type: Sequential-Access ANSI SCSI revision: 02
--------------------------------------------------------------------------------
If you need any more info, please let me know. Any ideas greatly appreciated.ERS
On Thursday 03 March 2005 15:14, Eric Shibata wrote:
Hello everyone, I am trying to get my scsi tape drive to work. Not matter what I do I get I/O errors.
[...]
------------ /proc/scsi/scsi:
Attached devices: Host: scsi0 Channel: 00 Id: 04 Lun: 00 Vendor: HP Model: T4000s Rev: 1.07 Type: Sequential-Access ANSI SCSI revision: 02
Ghaack! That drive is now around 9 years old, and the plastics its made of will have warped enough to put it out of commission by now even if it was sitting on the shelf in a sealed box till now.
I have experience with 3 of them, one sat in an NT box and backed it up for almost 4 years on the same tape, but when it died, it ate the next 3 $50 tapes we put in it by ripping them in two. Also the cleaning tape after I had hand cleaned it.
Of the other 2, one never was able to complete a backup run. HP recycled it a couple of times without fixing it, we tried 3 controller cards etc, couldn't make it work more than 2 or 3 nights in a row, ripping up a $50 tape everytime it failed. The last one ran about 4 months, ripped up a tape, came out and never went back into anything but the out bin.
We saw the handwriting on the wall very clearly, built a half a terrabyte raid and fired up rsync. The raid has been expanded to about 1.5 terrabytes now, but the script hasn't changed other than adding new machines from time to time, and we've had to do several near bare metal recoveries from it, 3-5x faster than tape would be. Its almost a routine when box so-and-so fries a cpu or drive. Fix whatever fried, fire up the inverse rsync script to restore that machine and haul it back to the desk it belongs on, all in the same day.
HP T4000s's, like any DDS2's are to be avoided, they are simply too long in the tooth to be 100% functional in the YOOL 2005.