Tape Libraries and Drives
cancel
Showing results for 
Search instead for 
Did you mean: 

MSL 6030 LTO 4 Library- Error number=1117 CC =208 TSM

sebastian Koerber
Occasional Advisor

MSL 6030 LTO 4 Library- Error number=1117 CC =208 TSM

I have replaced an old MSL 5000 (SDLT) with a new MSL 6030 Ultrium 4. I have deleted all old paths/library/drives (x.0.0.6) in TSM 5.5 and added the driver in win srv 2003 and added new paths etc. I see the correct HP Ultrium 4-SCSI Device IDs for the 2 drives and 1 library.
Labeling a tape seems to be fine.
But writing to tape fails: I/O error on drive mt1.0.0.6 with vol xyz (OP=Write, error number=1117, CC= 208, Key=0B, ASC=47, ASQ=03, SENSE=70......
Thank you for your help !
9 REPLIES
Curtis Ballard
Honored Contributor

Re: MSL 6030 LTO 4 Library- Error number=1117 CC =208 TSM

Looks like a parallel SCSI cabling problem. The error code you posted is for an "INFORMATION UNIT iuCRC ERROR DECTECTED". Information units are a parallel SCSI feature for wrapping SCSI transfers into blocks with a CRC so that error detection is improved over the standard parallel SCSI parity error detection.

The drive detected a CRC error in a data packet it received which usually means a cable problem but it may also be a terminator or HBA.
sebastian Koerber
Occasional Advisor

Re: MSL 6030 LTO 4 Library- Error number=1117 CC =208 TSM

thanks ! Do you know a link where I can find how to cable the 2 drives + Library onto one HBa although it is not recommened ?

My only ALternative is buy a new server - ML instead of DL 380 G5. All the slots are used .
Víctor Cespón
Honored Contributor

Re: MSL 6030 LTO 4 Library- Error number=1117 CC =208 TSM

The bandwith on a single SCSI channel is not enough for 2 Ultrium 4 drives.
As you say, this is not recomended and not supported by HP.

The connections would be:

Cable from the server HBA to top connector on library controller.
Cable from bottom connector of library controller to top connector of right drive
Cable from bottom connector of right drive to top connector of left drive
Terminator on bottom connector of left drive.
Curtis Ballard
Honored Contributor

Re: MSL 6030 LTO 4 Library- Error number=1117 CC =208 TSM

If you try connecting two drives, keep the cables as short as possible. U320 SCSI requires very clean connections and it is hard to get it running with 3 devices on a bus.
sebastian Koerber
Occasional Advisor

Re: MSL 6030 LTO 4 Library- Error number=1117 CC =208 TSM

thank you all for the answers.
It is working now. The cable to the HBA is quite long (10 feet). The performance right now is writing at 103 GByte/h .
What is the "usual" rate with 2 HBA ?

Curtis Ballard
Honored Contributor

Re: MSL 6030 LTO 4 Library- Error number=1117 CC =208 TSM

103GB/hour is a little slow. That works out to a little less than 30MB/second and it's pretty easy to get the LTO-4 drives running over 100MB/second but it really depends on what you are baking up. Most of the time the rate the data is provided at is the limitation.

Full speed uncompressed for LTO-4 is 120MB/second.
sebastian Koerber
Occasional Advisor

Re: MSL 6030 LTO 4 Library- Error number=1117 CC =208 TSM

I received the same error after some hours. So right now I disabled one drive and do a test with the other and the library.
If that works out better i might have to review our architecture.
The backup server has two FC connections to our SAN but I don't see the reason for a HA for the TSM server. So there might be space for another SCSI HBA.
sebastian Koerber
Occasional Advisor

Re: MSL 6030 LTO 4 Library- Error number=1117 CC =208 TSM

writing to tape is now at 84 MB/sec . (1693958531 kB in 19597 sec) with one HBA on one drive +Library.
Do you think it is worth tuning a bit more to reach 110 - 120 MB/sec ? Or is 120 MB with only one device in the SCSI reachable.

sebastian Koerber
Occasional Advisor

Re: MSL 6030 LTO 4 Library- Error number=1117 CC =208 TSM

Update: Error in performance calc:
It is backing up with 35 MB /sec .(2TB in 15,5 h) That is still a low performance.
Do you know a guide how to troubleshott bottlenecks ?