Problems with new HP LTO3 Drives and TSM

[TedK_2]

We have a new Library (NEO 8000) with 2 drives. Everything works fine..

But yesterday, we installed two more Drives (HP LTO3), and now I get two kind of error messages while using these drives:

1)
I/O error on drive HPDRIVE2 (mt2.0.0.5) with volume RBN008L3 (OP=READ, Error Number=1117, CC=205, KEY=FF, ASC=FF, ASCQ=FF, SENSE=**NONE**, Description=SCSI adapter failure). Refer to Appendix D in the 'Messages' manual for recommended action. (SESSION: 609, PROCESS: 261)

2)
/O error on drive HPDRIVE4 (mt4.0.0.4) with volume RBN001L3 (OP=WRITE, Error Number=1117, CC=208, KEY=0B, ASC=47, ASCQ=03, SENSE=70.00.0B.00.00.00.00.10.00.00.00.00.47.03.00 .00.00.00.00.00.00.00., Description=Command aborted). Refer to Appendix D in the 'Messages' manual for recommended action. (SESSION: 546, PROCESS: 257


We are using TSM Version 5.3.4, the library is connected via SCSI with Adaptec SCSI Card 29320ALP - Ultra 320 SCSI.

Do have any ideas what I can do?
If you need more information about my settings and hardware, please let me know.

[Curtis Ballard]

The unit attention in your second error message is for an information unit check CRC error. A simplistic description for an information unit (iu) would be a packet of information sent over the bus.

The iu's are given a CRC which is checked by the drive which will return this error if there is an error detected during a command iu or a data out phase. (Blocks of data going to the drive)

I would check the cabling and termination carefully. Remember that LTO3 drives should always be on their own bus. At most 2 drives can be used with possibility of performance problems. Anything more than 2 drives is really difficult to get a clean enough bus at ultra 320 speeds.

[TedK_2]

I changed the adapter speed to 160 mb/s and the error seems to be gone ..

thread can be closed ..

[Jim Miller]

Just wanted to post that I had the exact same ASC=47 ASCQ=03 errors with a fibre connected MSL6030. I called support, and following this document fixed the problem.

http://h20000.www2.hp.com/bizsupport/TechSupport/Document.jsp?lang=en&cc=us&objectID=c00659626