2024年11月6日发(作者：须艳丽)
IBM磁带机及磁带库日常工作手册
第一章：日常基本问题的处理 .......................................................................................................... 3
磁带卡在磁带机里不能够弹出： .............................................................................................. 3
磁带有关的故障： ...................................................................................................................... 4
磁带机读/写有关的故障： ......................................................................................................... 5
磁带机和主机连接的问题： ...................................................................................................... 5
第二章：磁带机（库）相关的信息： .............................................................................................. 8
LTO和3592磁带机最新的微码信息： ................................................................................... 8
LTO磁带机的数字信息（SCD code） ..................................................................................... 8
3580磁带机（TS22x0、TS23x0） ........................................................................................... 9
3581磁带库（L13、H13、L17、H17、L23、L23） ............................................................. 9
3581 2U磁带库（L28、L38、L3H、F28、F38、F3H） ..................................................... 10
3583磁带库 ............................................................................................................................... 11
3584磁带库 ............................................................................................................................... 12
3573 LTO磁带库（TS3100、TS3200） ................................................................................. 13
3576 LTO 磁带库（TS3310） ................................................................................................. 13
3590 磁带驱动器（Bxx、Exx、Hxx） .................................................................................. 14
第三章：相关数据的收集 ................................................................................................................ 17
附录A：LTO和3592磁带机微码详细信息。 .............................................................................. 18
附录B：LTO的SCD code详细说明。 ......................................................................................... 45
第一章：日常基本问题的处理
磁带卡在磁带机里不能够弹出：
1．在磁带使用之前检查磁带引导针的位置：
在新磁带使用之前，应该检查所有LTO或3592磁带的引导针。确保它在正确的位置。
如果发现其位置不正确，应该将其调整倒正确的位置（如下图）。可以使用人工卷带工具（
P/N
LTO=08L9129 3592=18P888）来调整。
具体操作步骤，可以参照《TS2340 3580 L43S43 Setup Operator Service
Guide>> GC27-2103中的第4章的：
Using Ultrium Media --
Repositioning or
Reattaching a Leader Pin
.。
<=== 正确的位置
2．检查是否主机曾经发过“PREVENT MEDIUM REMOVAL”的命令
这个命令通常是由主机端的某些应用程序发出的。如果有类似的问题，可以先从应
用程序端发出包含有“ALLOW MEDIUM REMOVAL”的命令，然后再从主机端去EJECT
磁带。如果磁带还是不能弹出来，则将磁带机重起。然后再手工方式弹出磁带。
3．当需要人工方式取出磁带机理的磁带时
当需要人工方式取出磁带机理的磁带时，根据情况使用以下的步骤：
1） 从主机端发出EJECT磁带的命令。
2） 按磁带机上的蓝色unload按钮1秒钟。
3） 按磁带机上的unload按钮15秒钟，磁带机会reset，然后再按unload按钮1秒
钟。
4） 将磁带机或磁带库下电/上电，然后再按unload按钮1秒钟。
磁带有关的故障：
1．一些磁带机进带故障和磁带的引导针的位置不正确有关系。可以参照前一节的介绍检
查和调整引导针的位置。
2．关于处理磁带问题，遵循以下的步骤：
1）尝试再另一个磁带机load/unload怀疑有问题的磁带。
2）检查磁带是否有物理的损坏。
3) 检查磁带引导针的位置是否正确。
4）如果怀疑有问题的磁带是空白的或者里面的数据不再需要的情况下，可以使用磁
带机对磁带进行诊断：
在LTO磁带机的面板上“Maintenance Mode”
drive diagnostic option '1' +
Diagnostic option 'E' (Test Cartridge & Media )
具体步骤参照《
IBM TS2340 3580-L43 S43 Gen4 Tape Drive Tape Drive
Setup, Operator, and Service Guide
》 GC27_2103 Appendix B.
Diagnostic and Maintenance Functions.
3．磁带的运输和储存：
如果客户需要储存或者运输磁带，要使用符合规定的储存箱储存和运输，参
照以下的weblink：
/support/?uid=ssg1S1001388&rs=546
符合标准的储存箱的信息参照一下的weblink：
4．LTO磁带机的兼容性：
LTO的磁带机可以读/写前一代的磁带（例如LTO4代磁带机可以读/写 LTO4和LTO3
代的磁带）。
LTO磁带及可以读前2代的磁带（例如LTO4代磁带机可以读LTO4、LTO3和LTO2
代的磁带）。
所以LTO1代的磁带是不可以在LTO4代的磁带机中使用的。
磁带机读/写有关的故障：
1． 确保磁带机的firmware是最新推荐的版本：
通过RMSS PFE的weblink查找firmware信息：
/tape//pages/opensystems
/tape//pages/codematrix
通过Internet查找firmware的信息：
/systems/support//selectproduct?brandind=500003
4&familyind=0&oldbrand=0&oldfamily=0&oldtype=0&taskind=2&psid=ap
SSR可以通过ITDT（IBM Tape Diagnostic Tool）的工具或磁带机的驱动程序的工具
在主机端进行firmware的升级。
ITDT v2.0：
不再支持
3580 GEN1 and GEN2, 3581, 3582, and 3583
/support/?rs=543&context=STCVQ6R&dc=D400&q1=
3580+firmware&uid=ssg1S4000662&loc=en_US&cs=utf-8&lang=en
ITDT v1.2：
/support/?rs=1140&context=STCXRHW&dc=D410&q1
=ssg1*&uid=ssg1S4000338&loc=en_US&cs=utf-8&lang=en
2． 隔离是否是磁带的问题：
1）尝试用磁带机load/unload，read/write一盘全新的磁带来隔离问题。
2）参照第一章中的有关磁带的问题的方法隔离问题。
3． 隔离磁带机硬件方面的问题：
1）尝试将用另一个磁带机对磁带进行读/写操作来隔离问题。
2）使用ITDT的工具进行磁带机的诊断测试。
3）尝试用磁带机（库）操作面板上的maintenance菜单进行诊断测试。
如果以上的硬件测试能够通过，证明磁带没有问题，不需要更换磁带机。
磁带机和主机连接的问题：
1． 磁带机和主机通过SCSI连接：
1）检查SCSI连接头的针和孔是否有异常，特别是68针的接头。针脚是否有过短、
弯曲等问题。
2）简化SCSI的连接方式进行测试。例如在一个SCSI的总线上只接一个磁带机。
3）检查LVD/HVD SCSI终结器（terminator），确保终结器正确地使用。
4）尝试更换SCSI电缆和SCSI的终结器来检查问题。
5）检查主机端的SCSI卡是否和磁带机兼容，或尝试更换主机端的SCSI卡来检查问
题。
6）在磁带机（库）上运行SCSI连接接口的诊断：
-运行基本的SCSI诊断
-在LTO磁带机（库）的“
Maintenance mode”下运行“Host Interface Wrap
test diagnostic”（参照《IBM TS2340 3580-L43 S43 Gen4 Tape Drive Tape Drive
Setup, Operator, and Service Guide》 GC27_2103的附录B）
7）如果已经完成了以上的诊断工作，而且更换过SCSI的电缆，运行ITDT工具的
磁带机诊断扫描操作，验证SCSI的连接是否正常。
如果完成了以上的操作，而且“Host Interface Wrap test diagnostic”是正
常的，但和主机端的连接还是有问题，不要更换更换磁带机（库）。参照以下的章节，
收集相关的数据，向上一级技术支持寻求帮助。
2． 磁带机和主机通过SAN/FC连接：
1） 简化FC的连接，尝试将由问题的磁带机（库）直接和主机进行连接。
2） 更换FC的光纤电缆。
3） 检查主机的FC卡是否设置了更长时间的timeout以适应和磁带机设备连接。
4） 检查主机端的FC卡是否和磁带机兼容，或尝试更换主机端的FC卡来检查问题。
5） 在磁带机（库）上运行FC连接接口的诊断。（方法同上）
6）
如果已经完成了以上的诊断工作，而且更换过FC的电缆，运行ITDT工具的
磁带机诊断扫描操作，验证FC的连接是否正常。
如果完成了以上的操作，而且“Host Interface Wrap test diagnostic”是正
常的，但和主机端的连接还是有问题，不要更换更换磁带机（库）。参照以下的章节，
收集相关的数据，向上一级技术支持寻求帮助。
3． AIX服务器直接连接LTO磁带机（库）重起后设备成“define”状态：
IBM的LTO3或LTO4代的磁带机（库）和AIX服务器直接连接。当服务器power
off/power on或重起后，磁带机（库）的设备rmtX和smcX不能够在设备配置中找到。
用lsdev –Cc命令查看时，没有显示或成define的状态。这时需要重新启动或power
off/power on磁带机（库），重新初始化FC连接。
4． LTO磁带库（LUN-1磁带机）连接的问题：
在绝大部分的LTO或3592的磁带中，都有机械抓手（autochanger）设备通过FC或
SCSI和主机连接。它是通过有Control Path的磁带机的LUN-1被主机识别的。当磁
带库和主机连接时，磁带机设备能正常地连接，但机械抓手设备不正常时：
如果是3581 3582 3583 3573．．．．．．的磁带库，设置成了“Sequential mode”。磁带库
则不会将LUN-1给机械抓手，让主机认到。3582 + 3581 (2U models)出厂时就是
“Random mode”，所以可以被主机认到。
所以当需要由主机来控制机械抓手时，磁带库应设置成为“Random mode”。
5． 磁带机（库）设备和磁盘设备要使用不同的FC连接：
在有SAN交换机连接的环境中，确保磁带机（库）设备和磁盘设备没有共享一块FC
卡。
对于磁带机（库）和磁盘设备的连接，FC和SCSI卡会有包括timeout值在内的不同
的参数设置。如果共享，这个参数设置通常对磁带机（库）和磁盘的访问都会产生问
题。
6． 多个主机连接访问同一个磁带机：
对于多个主机连接访问同一个磁带机，如果他们通过SAN交换机连接，而且在同一
个ZONE里，会产生问题：
如果多个主机在同一个zone里面，当其中一个主机重起时，它会发起一个“IOINIT”
的操作。会使得整个ＨＢＡ的总线reset。而位于整个总线上的设备对于reset会有不
同的反应。磁带机中如果有磁带，当收到这个reset时，会执行一个倒带（rewind）
操作。无论此时磁带机在作什么操作此时都会中止。因为reset是更高级别的命令。
如果此时另一个连接此磁带机的主机正在对磁带进行读/写操作，这个主机不会收到
倒带的信息。当磁带倒到开始时，它会继续从磁带的开始部位进行读/写操作。这样
将会导致数据的丢失。
7． iSeries主机不能识别TS3310的磁带库：
当3576磁带库power off时，和iSeries主机连接的IOP将会被reset。为了保证3576
能被正常地使用，当iSeries主机的IOP要reset时，确保3576是power on的状态。
8． Xseries Configuration and Option Guide (COG)
Xseries Configuration and Option Guide (COG)里面可以查到和xSeries主机兼容的磁带
机（库）的信息：
/systems/xbc/cog/
System Storage InterOperationCenter （SSIC）
System Storage InterOperationCenter （SSIC）里面可以查到所有IBM的存储产品的兼
容性信息：
/systems/support/storage/config/ssic/
s?start_over=yes,
第二章：磁带机（库）相关的信息：
LTO和3592磁带机最新的微码信息：
3592-E06 GEN3 ----- D3I2_47E
3592 E05 GEN2 ----- D3I1_DA0
3592 J1A GEN1 ----- D3I0_C90
LTO4 GEN4 ----- 85V8
LTO3 GEN3 ----- 85P1
LTO2 GEN2 ----- 73V1
LTO1 GEN1 ----- 5AU1
所有最新的LTO的微码可以在以下的weblink查找下载：
/servers/storage/support/lto/
关于所有微码版本的信息参照附录A。
LTO磁带机的数字信息（SCD code）
0：没有错误，不需要干预
1：散热问题
2：电源问题
3：微码相关的问题
4：需要收集磁带机的DUMP
5：磁带机的硬件问题
6：磁带机或则磁带介质问题
7：磁带介质问题
8：磁带机或SCSI总线问题
9：磁带机或LDI（RS-422）通讯问题
o、c、b、h：保留
A：磁带机的硬件问题
B：保留
C：磁带机需要清洗
D：保留
详细的SCD code描述及相应的action参照附录B。
3580磁带机（TS22x0、TS23x0）
1． 确保3580的微码是最新的版本：
通过IBM的RMSS weblink查找：
/tape//pages/opensystems
/tape//pages/codematrix
通过Intranet或Internet下载3580的微码：
/systems/support//selectproduct?brandind=50
00034&familyind=0&oldbrand=0&oldfamily=0&oldtype=0&taskind=2&psid=ap
/tape//pages/3580page00
/support/?rs=543&context=STCVQ6R&dc=D400
&q1=3580+firmware&uid=ssg1S4000055&loc=en_US&cs=utf-8&lang=en
2． 通过使用ITDT的工具测试诊断和相应的微码升级工作
ITDT工具的下载和使用参照前一章节。
3． 隔离是否是由于磁带的故障导致的问题：
参照第一章的有关磁带的故障诊断方法。
4． 隔离是否是磁带机硬件的故障
尝试对同一盘磁带在其他的磁带机上进行读/写操作。
5． 对磁带机做基本的诊断：
使用ITDT工具进行诊断
使用磁带机操作面板上的“Maintenance Mode”进行诊断：
'Maintenance mode' drive diagnostics option '1' + Diagnostic option 'H' (Head
Test)
参照《IBM TS2340 3580-L43 S43 Gen4 Tape Drive Tape Drive Setup, Operator,
and Service Guide》 GC27_2103 Appendix B. Diagnostic and Maintenance
Functions.
如果诊断测试是通过的，而故障依然存在，这时不要马上更换磁带机，请向你
的上一级技术支持（CAG或TSG）寻求帮助。同时收集相应得数据。
3581磁带库（L13、H13、L17、H17、L23、L23）
1. 3581 LVD磁带库L13、L17、L23不能够上电的故障：
检查LVD的terminator （P/N 19P0481）是否正确地安装了。
如果3581的磁带库没有正确地安装terminator，当上电的时候，操作面板上会
显示'LdR INIT'。而系统不会进行自检操作。
2. 3581 LVD HVD磁带库 x13、x17、x23弹簧故障：
某些3581磁带库德弹簧系统会发生故障。这时不要更换整个磁带库。可是根据ECA017
订购EC备件（发邮件给
MPCECPOC/Australia/IBM，提供客户信息，ECA017信息，
H28058 B/M18P6885）参照HSF tips H177257。或者直接定备件18P6885）
3. 检查并确认3581磁带库德微码是最新推荐使用的版本：
1） 通过一下网址查找相关信息：
/tape//pages/opensystems
/tape//pages/codematrix
2） 3581磁带库德微码下载网址：
/tape//pages/3581page00
/support/?rs=541&context=STCVQ6N&dc
=D420&uid=ssg1S4000042&loc=en_US&cs=utf-8&lang=en
4. 使用ITDT工具进行诊断和微码升级
5. 隔离是否是由于磁带的故障导致的问题：
参照第一章的有关磁带的故障诊断方法。
6. 隔离是否是磁带机硬件的故障
尝试对同一盘磁带在其他的磁带机上进行读/写操作。
7. 对磁带机做基本的诊断：
使用ITDT工具进行诊断
使用磁带机操作面板上的"Maintenance Mode"进行诊断：
'Maintenance mode' drive diagnostics option '1' + Diagnostic option 'H' (Head
Test)。SSR must reach inside 3581 enclosure to see the (Black) unload button.
Open the Autoloader door and remove any cartridges from the front slots.
With a flashlight and a pencil, press the Unload button on the drive face plate with
the eraser end of the pencil. The round Unload button is located near the base of the
drive in the second grid from the right (facing the drive). The Unload button is
directly under the right cartridge guide of the loader opening near the base of the
drive.
如果诊断测试是通过的，而故障依然存在，这时不要马上更换磁带机，请向你
的上一级技术支持（CAG或TSG）寻求帮助。同时收集相应得数据。
3581 2U磁带库（L28、L38、L3H、F28、F38、F3H）
1. 3581 2U磁带库（L28、L38、L3H、F28、F38、F3H）磁带机故障A9 39：
在3581 2U磁带库上电的过程中通常会报A9 39的故障。
原因：
The lock block sensor is set on the drive, (tripped lock block) Drive
incorrectly appears as if there is a tape loaded. This is usually found on a new
installation, or a new FRU that has been treated a little rough in transit. The drives
loader Assm is shaken backwards a little tripping the lock block sensor.
解决方案：
Install latest (minimum level 2.20) Library code. Then run the Drive Calibrate
Test under Drive Diagnostics. This test will have you insert a scratch tape, it will try
to load the tape in the drive and fail (probably with 94 74 error), but when the tape is
extracted from the drive, it will reset the lock block sensor and on the retry it will
work.
2. 检查并确认3581磁带库德微码是最新推荐使用的版本：
/tape//pages/opensystems
/tape//pages/codematrix
/systems/support//selectproduct?brandind=50
00034&familyind=0&oldbrand=0&oldfamily=0&oldtype=0&taskind=2&psid=ap
/tape//pages/3581-2u
3. 使用ITDT工具进行诊断和微码升级
4. 隔离是否是由于磁带的故障导致的问题：
参照第一章的有关磁带的故障诊断方法。
5. 隔离是否是磁带机硬件的故障
尝试对同一盘磁带在其他的磁带机上进行读/写操作。
6. 对磁带机做基本的诊断：
使用ITDT工具进行诊断
如果诊断测试是通过的，而故障依然存在，这时不要马上更换磁带机，请向你的上
一级技术支持（CAG或TSG）寻求帮助。同时收集相应得数据。
3583磁带库
1. 3583 picker 故障（SAC 73、7C、81、82．．．．．．）
1) Library, drive, RMU and SDG F/W should be at the latest level.
2) Aug 2008 => Have a PFE version of Library code
- 6.11.0001 for Multipath
- 3.42.0002 for Non-Multipath ==> Picker powers down after 10 minutes
of inactivity , On the first Library motion command, picker powers back up
and continues with the command request
3) Check that all 3583 magazine '6-packs' are revision B -> P/N 19P4529
magazines, Revision A or B is printed on rear magazines. Remove each mag
and check that "Rev-B" should be stamped on rear of each magazine. Please
check to see if ground wire is connected between picker control board and frame.
Please try to manually PUT and GET customer's cartridges from all slots.
4) If you have picker GET failure from LTO-1 drive, please install drive clips 3584
ECA009. (Retain tip H021381, P/N 18P7835 )
5) ASAP Collect library log data. Monitor> SHOWPOS to see if the exact slot/s
having issues can be identified. Also collect >PERR and >PLOG
6) Remove top cover from 3583 to carefully observe picker movements and actions
following a door open/closed operation. Use the 3583 MI Chapter 9. "Service
Procedures" section 'Observing Library Robotics' for reference details.
7) Check Y-axis for any binds by moving it up and down. The binding can be
between picker assembly and Y shaft. If any binds exist, replace appropriate
FRU. Repeat SAC 81 ?? Replace Y-axis motor assembly. Replace
power distribution board. Replace Y-axis drive belt.
8) If SAC 73 or picker finger issues are suspected, then from the SAC 73 section of
the MI .. " Run Grip finger diagnostics (Main Menu —>More —>Service
—>Library —>Diags —>Fingers —>Step —>Open/Close): Only if diagnostic
failed: replace Picker Carriage Assembly P/N 18P7450. If diagnostic passed,
retry it several times. If it fails during successive retries or if intermittent failures
continue to occur during normal operations, replace the Picker Carriage
Assembly P/N 18P7450. Always replace "Picker Carriage Arm Assm" (not
just picker - but the 'Picker Carriage Assembly' this includes picker + board +
carrier bearing .. - part number 18P7450)
9) 3583 S/N prior to 78-16127. SAC 73 00 or 81 00 if a PUT or GET failure
occurs at column 4 and/or 5, please install column magazine spacer kit
10) To reproduce the failure or verify the fix, please remove 3583 top cover & run a
long DEMO test from the 3583 operator panel. Use the 3583 MI Chapter 9.
"Service Procedures" section 'Observing Library Robotics' for reference details
11) Run “>unlearn" and then “>calibrate 300" from library serial port, Follow
command line 'calibrate 300' support procedure ; Error still occurring -
replace Y-axis motor and belt ; Replace Picker Carriage ASSM - part
number 18P7450.
12) If the situation is critical, Install laptop on back of 3583 and run a command line
'library trace' with session capture from 3583 serial. This may need to run for
days/weeks to trace a failure event.
2. 检查并确认3581磁带库德微码是最新推荐使用的版本：
Multipath /tape//pages/3583Mpath
Singlepath /tape//pages/3583Spath
3. 使用ITDT工具进行诊断和微码升级
4. 隔离是否是由于磁带的故障导致的问题：
参照第一章的有关磁带的故障诊断方法。
5. 隔离是否是磁带机硬件的故障
尝试对同一盘磁带在其他的磁带机上进行读/写操作。
6. 对磁带机做基本的诊断：
使用ITDT工具进行诊断
如果诊断测试是通过的，而故障依然存在，这时不要马上更换磁带机，请向你的上
一级技术支持（CAG或TSG）寻求帮助。同时收集相应得数据。
3584磁带库
1. 3584磁带库的Universal Gripper Assembly如果没有物理上的顺坏，不需要更换：
Library Firmware should be updated + potential library re-calibratrion prior to any
non damaged gripper replacement. The library code should get updated along with
any damaged Gripper replacement.
ALMS libraries - a minimum library code level of 8150 should be installed to resolve
gripper reliability & collision detection.
Libraries with ALMS feature disabled - a minimum library code level of 7363
should be installed to resolve gripper reliability & collision detection
2.
3573 LTO磁带库（TS3100、TS3200）
1. 6．70版本的微码能够解决以太网和磁带hung的问题。
2. 2008年4季度的微码将解决和多关于磁带加密的问题。
3. 确保3573的微码是最新的版本：
通过IBM的RMSS weblink查找：
/tape//pages/opensystems
/tape//pages/codematrix
通过Intranet或Internet下载3573的微码：
/systems/support//selectproduct?brandind=5
000034&familyind=0&oldbrand=0&oldfamily=0&oldtype=0&taskind=2&psid=ap
/support/?rs=1154&context=STCZU45&dc=D4
20&uid=ssg1S4000497&loc=en_US&cs=utf-8&lang=en
4. 通过使用ITDT的工具测试诊断和相应的微码升级工作
ITDT工具的下载和使用参照前一章节。
5. 隔离是否是由于磁带的故障导致的问题：
参照第一章的有关磁带的故障诊断方法。
6. 隔离是否是磁带机硬件的故障
尝试对同一盘磁带在其他的磁带机上进行读/写操作。
7. 3573基本数据收集：
LCD: Error Code details
From Eth Web interface :
Service Library -> view logs
Service Library -> view drive logs
Service Library -> save drive dump
On a 3573 there is no WEB / GUI library log collection tool for the client. They
have to telnet into the 3573 and run the FLMON> DPA command and collect CLI
output from the
3576 LTO 磁带库（TS3310）
1. 使用500G和82F0的微码版本，可以解决很多加密和磁带机相关的问题。
2. 确保3576的微码是最新的版本：
通过IBM的RMSS weblink查找：
/tape//pages/opensystems
/tape//pages/codematrix
通过Intranet或Internet下载3580的微码：
/systems/support//selectproduct?brandind=5
000034&familyind=0&oldbrand=0&oldfamily=0&oldtype=0&taskind=2&psid=ap
/support/?rs=1140&context=STCXRHW&dc=D
420&q1=ssg1*&uid=ssg1S4000445&loc=en_US&cs=utf-8&lang=en
3. 3576磁带机清洗所产生的问题：ASC/ASCQ 3BA0
禁止使用有
CLNxxxL1标签的清洗带在LTO4的磁带机中使用。
如果需要清洗，使用没有L1标签的“universal cleaning cartridge”进行
清洗。可以使用CLNxxxL4或CLNxxx的清洗带清洗。
4. 3576磁带库不能在iSeries的主机上被识别：
参照第一章的四、7节
5. 3576 L5B报T020、T007、T083的错误：
3576磁带库在校准I/O station（0，6 location）时，报T007、T083的错误。
原因：The Picker Locking mechanism (slide The Picker Locking mechanism
(slide out metal lever) was left sticking out in the aisle.
3590 磁带驱动器（Bxx、Exx、Hxx）
1. 3590磁带机最新推荐的微码版本：
3590-Hxx and 3590 Exx and Common cardpack F_2FB
3590-Bxx
non
Ultra SCSI cardpack A_593
3590-Bxx Ultra SCSI cardpack B_93C
2. 更换HGA的问题：
在任何更换HGA之前请先更换HGA brush或作extended clean HGA。
更换下来的退旧的备件请将新备件上桔黄色的磁头保护的夹子夹到退旧的备
件上，同时，所有的电缆请保护好。这样更换下来的备件可以被维修后再次被
使用。
3. 如何做extended clean：
在3590的操作面板上将磁带机置于“
CE offline”的模式。
Select 'Config/Install' - Select 'DRV' Options - Select 'Enab
Extended Cln' - "Wrench" to back out to 'Operator' mode. The next
cleaning cartridge - and ONLY the next cleaning cartridge - loaded on the
drive elected to perform an extended cleaning will run for about 50-80
minutes without unloading.
4. 读/写错误，FID F6，FSC 7038报错信息。
产生读/写错误的原因通常是由于HGA brush顺坏、没有按时清洗磁带机和
没有按时PM所导致。最新的3590的微码将磁带机的清洗时间间隔有300GB
减少到150GB。FSC7036是由于磁带机的使用而需要清洗。FSC7038是由于读
/写错误而要求清洗。
1) Upgrade code to F_2FB or B_93C or A_593
2) Review the drive error logs from the 3590 drive Operator panel,
list down all FID/FSC's, clear the error logs.
3) Use lint free gloves when PM-ing 3590 drives - P/N 0461621, do
not touch the tape path with bare hands, even if they are clean.
4) Replace HGA brush assembly P/N 35L1569.
5) Check brush has a firm and level contact with 3590 HGA
6) Whilst the cleaning arm is removed for brush replacement, clean
the tape path with slightly water moistened lint free cloth. I
would recommend leaving the tape guides in place as removing and
replacing them can damage the HGA if your not very careful.
Cleaning of the two HGA 'D' air bearings can still be done with
these guides in place. Also clean the inside of the Machine reel
hub, the tension transducer, decoupler ...
7) Do not touch the surface of actual HGA head with the cleaning
cloth.
8) Run a normal Clean tape mount twice. Use account SSR cleaning
tape or new cleaning tape ! Ensure the usage dots on top of the
SSR Cleaner tape are filled in with each use, we must ensure that
at least the SSRs clean cart is doing a good job. Clean cart P/N
05H7540.
9) Check for visible debris on HGA, do not remove - allow Extended
clean to remove any debris
10) Use the 3590 drive MI procedure for FID D4 and do all of the
documented steps including operator panel FRU replace menu -
'Tape Path Repaired'' to clear the SARS and then the 'End Call'
procedure
11) Use 3590 MI to run Vacuum check/adjustment " Measurement and
Adjustment of Pneumatic System "
12) After completing Pneumatic system use the mounted CE cart (known
good media hopefully) to run drive R/W diagnostics. If the client
used 'K' tape you should use a 'K' tape for the Read/Write
diagnostic
13) Listen for noisy file reel and machine reel motors whilst running
above diagnostic. Replace motors if noisy - do not replace HGA
at this point!
14) If diagnostic fails, run an Extended clean as per MI. - details
also below. Note this will take 50-60 minutes to run
15) Review the drive error logs from the drive Operator panel, list
down all FID/FSC's, action all FID/FSC's listed
16) Clear the error logs once all FID's have been resolved and any
additional diagnostics have been run successfully
17) Run 3590 diagnostic ; Fix Verify - Test Head Using know
good 3590 media See details below
18) If HGA diagnostic still fails check again for visible debris on
HGA, gently manually clean off with another HGA brush using
up/down motion ONLY. If debris is still not moving moisten HGA
brush with clean water and carefully brush with same up/down
motion. Do NOT use isopropyl alcohol or other solvents - these
will dissolve the head materials.
19) Run another extended clean if debris was detected and removed
20) Re-run 3590 diag - Fix Verify - Test Head Using know good
3590 media
21) Whilst unloading the tape used above review the drive error logs
from the drive Operator panel, action all FID/FSC's listed
22) Clear the error logs once all FID's have been resolved and any
additional diagnostics have been run successfully
23) Replace drive covers carefully.
第三章：相关数据的收集
在前面的章节已经提到。当遇到读/写或其它与磁带机相关的问题时，已经做过诸如ITDT等
测试，而且测试是通过的，但问题依然存在。这时不要马上更换磁带机，请向你的上一级技
术支持（CAG或TSG）寻求帮助。
在寻求帮助的时候，因该做好以下的工作：
1． 详细地描述问题的现象。做过哪些诊断测试工作，详细地步骤和结果如何。
2． 主机上的相应的配置和错误信息。如AIX系统得snapshot，Windows的event log．．．．．．
3．
收集详细的磁带机（库）的service
Reference Codes。例如磁带库的SCSI/FSCSI Sense
Key + ASC/ASCQ + HEC/HECQ … 磁带机的FSC, FID, SCSI/FSCSI Sense Key +
ASC/ASCQ…
4． 系统环境的描述。包括所连接的主机类型，磁带机（库）的配置，所使用的备份软件及版
本，SAN配置情况．．．．．．
5． 磁带机（库）的微码版本，主机驱动程序类型和版本。
6． 磁带机（库）的error log、磁带机的DUMP。可以使用ITDT-SE、ITDT0-XD或cetool收
集。
附录A：LTO和3592磁带机微码详细信息。
1． 3592-E06：
1. Support 3592 E06 drives in all configurations
- 3494, 3584, 3577, and Silo libraries
- tabletop or rackmount
- CU, Hydra, or open system attach
2． 3592-E05：
3592 E05 D3I1_DA0
Summary list of major enhancements and fixes:
1. Support recognition and tape reformat from E06 to E05
3592 E05 D3I1_D16
Summary list of major enhancements and fixes:
1. Prevent FSC D12E errors due to CSP update of brick s/n
2. Support the # character when using Internal Label Encryption mode
3592 E05 D3I1_D15
Fixes encryption authentication failures on CSP drives running D3I1_D12 code
3592 E05 D3I1_D12
Summary list of major enhancements and fixes:
1. Additional FIPS Crypto support features
a. Generate GCM IV per NIST 800-38D
b. Indicate FIPS mode to controller and library interfaces
2. Prevent false call homes from incorrect FID on FSC 5066 errors
3. Additional rolling calibration changes
a. Improved ERP handling of write or read temp error bursts
b. Fix more cases of FSC 6017 caused by ERPs during Locate/Space commands
4. Add a slow speed retry during read ERPs
5. Fixes the 'zero key for all records' problem for TSM AME configurations
Detailed list of all changes/fixes:
3088 6017: Extend upif timeout for Space request to 45 minutes
3109 ETH: Disable Link LED on old DCJ cards
3058.1 CRYPTO: Fix infinite EKM failure retry loop
3124 SARS: Support send diag to clear HSARS
3126 NEW: Read redrive FSC4601 (C2 miscorrect EM)
3156 Unexpected POR (op panel interrupt panic)
23218 J2: Create new release for J2 PGA7
23220 J2: Fix Load for deck test
23303 J2: MED: Reduce FSC 5020 temp error
22608 Write filemark failed running Sctape fsc 6000
23355 Add thermal sensor diag on POST
23396 J1,2: change page id for tape directory page on reformat
23401 Add CHN_HW_CALIB_READ_OP command
23416 Raise off-bias to 5mA when tape unloaded
23425 Change FID for 5066 to 86 from 83
23427 J1/J2: Add Drh_Change_Tape_Dir_Format
23406 RABF(80840000-Otr): UNEXP_PERM (1318s)
23426 MED: Try another velocity in read ERP
23452 RW:default- 0933 JBD254JB 9712
23531 Split CALIB_ROLL into CALIB_ROLLW & CALIB_ROLLR cal reasons
23463.5 Connect CALIB_ROLLR, CALIB_ROLLW to rolling calib invocations
23532 J1-FIELD 970D/4601
3224 NEW: Add FIPS flag to library msgs (FCR 3154)
3592 E05 D3I1_C93
Summary list of major enhancements and fixes:
1. Add slow speed read ERP step
2. Fix RABF degraded writing problem
3592 E05 D3I1_C91
EC Contents:
Summary list of major enhancements and fixes:
1. Rolling calibration phase 2 changes
a. Improved ERP handling of write or read temp error bursts
b. Fix some cases of FSC 6017 caused by ERPs during Locate/Space commands
c. Fix some cases of FSC 5066 read perms
d. Add max C2 correction as rolling cal option
2. Fix false Write Protect error caused by load retry
Detailed list of all changes/fixes:
2755.9 CRYPTO: FIPS: support algorithm cert vectors
2968 EVT-J2: FSC D133 ( crypto fail test automatic )
2755.10 CRYPTO: More FIPS cert vector work
2971 WRONG: LDI SCSI_ABORT does not send a response
2967 HANG: Some errors (9711) can cause cmd hangs
2978 CRYPTO: Handle perm during rekey correctly
2979 CAM:tc-3777 0636 J11435 5070
2981 WRONG: CM page table needs to cross-reference actual page
2755.12 CRYPTO: FIPS: Insure initial PRNG Xkey!=Xseed
2755.13 CRYPTO: FIPS: Disable data output on failure
2901 RABF(44010000-Rd2): TIMEOUT (1003s)
2967.1 HANG: Some errors (9711) hang write cmds
3046 PANEL: Fix hole in panel reset debounce
3053 ADI - fix sense data masking after unload error
2954.1 FIBRE: Independent write/read burst sizes
3088 6017: Extend upif timeout for Space request to 45 minutes
22902 J2-EVT: FSC8C00 ( STA_Update_CM() returned 5 )
22914 J1J2:Create new release for J1P12 and J2P6
22940 J2 Field: Slow performance (PMH 20038-660-706)
22944 J2: FSC4600 is returned due to unexpected encryption mod exit
22698 LocShortTypical (346s) WRITE_PERM
22922 RWEodTypical (50646s) READ_PERM
23048 MED: Reduce velo logging in cal trigger log
23050 J2 FIELD FSC 5051 EOT encountered during write
23085 MED: J2: Add new debug command for ERP history
23102 Program INDY voltage based on data rate
23110 MED: Some 7834/5834 ERPs are wrongly triggered
23113 MED: Rolling calib Phase 2
23124 MED: Rolling calib Phase 2
23127 J2: Ingore sticky velocity setting in constant vel mode
22794 WORM:Fail-safe for invalid OPP updating
22982 J1 FIELD 83 5066 0000 2A0F
23168 J2: MED: Fix Build Break
23172 SRV: Disable stepper at POR explicitly
23185 J1/J2: append error is returned by write perm@ABF on WORM
23042 Handle CHN_ErrorInject better in CAL and adaptive settings
23126.1 Rolling Calib Phase 2-existing logic fixes and enhancements
23179 LocLongTypical (7089s) TIMEOUT-10 (old tape, FFP=2368)
23212 RWShortAggressive (1126s) TIMEOUT-08
23126.1 Rolling Calib Phase 2-existing logic fixes and enhancements
23126.2 MED review changes added to base rolling phase 2 work
23126.3 Correct for dsnum corruption during write rolling cali
23227 LocMediumFixed (2399s) READ_PERM
23126.4 Fix loop index problem
23126.6 Rolling calib fix: last-best-option not held at EOW if burst
3592 E05 D3I1_C15
Summary list of major enhancements and fixes:
1. Support LME (library managed encryption) method in 3494 libraries
2. Improve fibre channel transmit signal quality (jitter fix)
3. Drive diagnostic improvements (use correct pattern)
4. Fix write inhibit problem with multi-volume Worm tape application
5. Set Media Life TapeAlert based on lifetime bytes processed
6. ERP enhancements for read interchange problems and long mounts (rolling
calibration changes)
3592 E05 D3I1_B25
Summary list of major enhancements and fixes:
1. FCR 3095 - Support for T10/SSC-3 Encryption method
2. Implementation of required functions for FIPS certification
3. FCR 3118 - Support immediate command termination for Long Erase command
4. Support locate past EOD (convert to linear read)
5. Clear DUC on retry of load error
6. Fix for No Response msgs during clean cycle
7. FCR 3129 - Allow library to clear Flash dump
8. Improvements to Read error recovery procedures aka "slow read/long recall"
Detailed list of all changes/fixes:
21831 FSC 7265 on Write
21858 perm 7282 read error
2738 JAG-1 FIELD DUC not handled by as400
21834 Jag2E: EOD detected is returned instead of FM detected
21762 EVT: FSC6353/7537 on Space EOD
21555 FSC 5475 Cannot get LPOS
21664 BENCH:TDRV 0012 JBC160JB B340 J2E FID 85 B340 029E
21469 Cartridge appears "stuck" due to long CM retries
2659 F016: Double message received caused F016
2662 Bench: FSC 9999 Check_1 w A16
2640 F00B w 942 code
2845 Jag2-Field 9713 28410,442
22257 58B0 Srv over rotation at stop
22263 CAM:tc-10566 3007 JBX076 5475
22291 RVT: FID1 E5 6017 0000 when running host jobs
22352 Jag2: do not write J1 format with speed1 on all of J2 drive
2838 JAG1-Field: Not reporting error (SRR's)
22117 Jag2-Field 6017 1_A27 22337,122
2817 RAS: Make Key Path Config menu options like library options
22176 Jag2: Disable write speed1 on J1 format for specific J2 drives
22099 4353: HS locate to EOT w est LPOS
2800 F027 Check_1 A38 Code
22094 JAG2-FIELD: FSC 4022/970D
22145 JAG: Change cleaning tape speed to 6mps
18484 Speed matching performance
22101 EOD entry of HRTD is cleared before unload
21920 Perm 58B5
21905 J2E: Enhance feature bits for recovered eHKDS
2771 CRYPTO: Simplify zero key transition rules
21989 J2: Disable Speed6 for JB Cartridge
2853 FC Jitter fix: Change Pre-Emphasis Level to 0 (22399)
22438 Revert to previous PLL settings for JA media
2881 Fix F027 Chk_1 w B1D code (break in 2830)
2884 BUILD: Official rj070509a
2876 CRYPTO: PRNG is not connected correctly
2838.2 SARS: temporarily remove SRR FID F5
2883 Fix breakage of Get VPD cmds
3592 E05 D3I1_A38
EC Contents:
Summary list of major enhancements and fixes:
1. Support attachment of the TS3400 (3577 autoloader) for the 3592 tape drive
Detailed list of all changes/fixes:
2639.3 NEW: More ITD changes for 3577 library
2756 CAM:Oracle:Mode Pagex25 Encrypt bits incrctly set to changeable
2759 NEW: Pass all Write buffers to the library
2760 CryRWMediumAggressive (1354s) READ_PERM
2761 BENCH:/gsa/tuc 0909 JJX199JJ 0000 J2N
3592 E05 D3I1_A33
EC Contents:
Summary list of major enhancements and fixes:
1. EEDK writing performance improvement (improve time to 'Ready' for encryption
scenarios)
2. Improved PES acquire method
3. Miscellaneous field problem fixes
Detailed list of changes/fixes:
21664 FID 85 B340 029E
21761 Motor stuck check trace is logged more than expected.
21792 Support new format of Physical Position of
21822 Loosen tape slack detection threshold
21834 Jag2E: EOD detected is returned instead of FM detected
3592 E05 D3I1_A27
EC Contents:
Summary list of major enhancements and fixes:
1. Fix sequence problem with SRR during RES command
3592 E05 D3I1_A21 What’s Fixed
EC Contents:
Summary list of major enhancements and fixes:
1. Support new extended length JB/JX cartridge types
2. Support Encryption Pool ID method
3. HSARS Quick Check
4. Miscellaneous field problem fixes
Detailed list of changes/fixes:
2631 HSARS Quick Check
19712 7A00 loses segment-reusable flag after sns xfr
2591 FSC9712 on write
2541 Fail when library sends message out of order
2513.1 Indicate emulation model on icon
20728 Cartridge initialize fail
20735 J2E: MED: Check EncryptionFlags of EOD, FID and [se]HKDS on rea
20531 Jag2: Add new FSC 4702(WRITE_APPEND_ALL_EHKDS_INVALID)
2662 FSC 9999 Check_1 w A16
21328 5064 is reported on unload in NULL err-inj.
2659 Double message received caused F016
2654 Dump flag clears on reading descriptor data
21430 J2E: MED: Report inconsistency between CM and eHKDS
21441 FSC 4353 on A0B code
21534 FSC 4410 - Buffer Empty
3592 E05 D3I1_942
EC Contents:
Summary list of major enhancements and fixes:
1. Support these tape encryption methods
- SME (system managed encryption)
- LME (library managed encryption)
2. Miscellaneous field problem fixes
3592 E05 D3I1_733
Detailed track list of changes/fixes:
2352 9999-C00C: Fix hang in port switch w/Ayame
2389 F016: Report error w/FID for no BVPD in 3584
2394 Change DLR_MAX_PARM_SIZE to multiple of 4
2425 FCR 3090 - Cross EOD setting
19399 E5 6017 (CM read)
3592 E05 D3I1_72E
EC Contents:
Summary list of major enhancements and fixes:
1. Important field problem fixes
a. Fixes for correctly setting and clearing TapeAlert 18
c. Fix problem where code info header can be corrupted in dumps
d. Fix problem when ATS received before FCP_CONF (could cause hang)
2. FCR's and other functional changes
a. FCR 3026 - LDI Get-Set Behavior (Baud Rate)
b. FCR 3026 - LDI Get-Set Behavior (Emulation Mode)
c. FCR 3062 - LDI SCSI Commands
d. FCR 3065 - LDI Pause Command
e. FCR 3066 - Force ERP (TM Portion)
f. FCR 3068 - LDI Supported Features
g. FCR 3076 - Allow LogSense to be forwarded to LIB when Not Ready
h. Support J1A emulation control from the 3584 library interface
i. Correct problem with Auto(NL) configs to L-Port instead of N-Port
Detailed list of changes/fixes:
2134 NEW: always report E05 to 3584 on E05 drives
2131 9999-A101: String Search integrity check during error
2183 JAG1-FIELD: F008-2707 Chk1
19032 JAG2: FSC4700 after NULL DS failure
19049 E5 970C
19104 JAG1 FIELD E5 6017 and 970C multiple accounts
19207 JAG2: 9702 0003
19243 Split 5060 into 2 fsc's, add flag data
3592 E05 D3I1_6E1
Summary list of major enhancements and fixes:
1. Support J1A Static Emulation
2. Prevent incorrect FRU replacement of Jag1 drive with Jag2
3. Improvements to ERPs when reading Jag1 format
4. Miscellaneous problem fixes
Detailed list of changes/fixes:
Fix problem with default density panel select
Interface for emulation and density controls
always report E05 to 3584 on E05 drives
Reject serial num update if drv model different
Allow selection of FRU Jag2 when emulating Jag1
Fix missing cases of emulated Jag1 FRU cases
FSC 5012 on write,read,rabf
Treat fsc 5800 as non-fatal and cause ERP
3． 3592-J1A：
3592 J1A D3I0_C90
Summary list of major enhancements and fixes:
1. Support recognition and tape reformat from E06 to J1A
2. Rolling Cal Phase 3 changes
a. Additional ERP improvements for write or read temp error bursts
3. More slow speed retries during read ERPs
4. Improved spd1 writing evaluation during diag routines
Detailed list of all changes/fixes:
3171 BUILD: Use unique link space for j1PGA14
3174 FIBRE: hung, transfer permission held by MC
3177 BUILD: Official e080116e
3179 DIAG: rcv diag results Engineering (xE001)
3165.1 Move AF/AE workaround to support debug
3188 HANG: Fix hole in uPIF critical logic
3140 WRONG: need to reset baud rate when go interface down
3195 BUILD: Official e080130e
2927 Support ISOCM/DSOCM (performance)
3236 PANEL: Fix date/time formatting for logs
3300 Hung drive after write perm after turbo SRRs
23592 SRR recovery fails with FSC7070
23608 MED: Change DSS cal log for better FA
22660 FID is not re-write when FMR cartridge is created
23903 CAM:tc-1317 6703 JBA179 5060
23501 LocMediumTypical (1644s) OTHER_PERM (old tape, FFP=665)
23911 6017 error, a buffer image was taken.
23646 Rolling Calib Phase 3 Changes
24001 MED: Repeat slow speed ERP to recover intermittent c2 unco
3346 Modify diag evaluation for new J1 Diag
23614 Dataset transfer cntr on Log Page 38 not updated on temp
24058 New Diag Test for Poor Speed1 Write Drive
24390 CryRWMediumTypical (911s) WRITE_PROT
3592 J1A D3I0_C0D
Summary list of major enhancements and fixes:
1. Fix false FSC 3820 diagnostic errors
2. Prevent false call homes from incorrect FID on FSC 5066 errors
3. Additional rolling calibration changes
a. Improved ERP handling of write or read temp error bursts
b. Fix more cases of FSC 6017 caused by ERPs during Locate/Space commands
4. Add a slow speed retry during read ERPs
5. Fix repeated FSC 8C00 errors following FSC 8E19
Detailed list of all changes/fixes:
3124 SARS: Support send diag to clear HSARS
2818.4 RAS: Fix false FSC 3820 from diag threshold scaling
3126 NEW: Read redrive FSC4601 (C2 miscorrect EM)
3156 Unexpected POR (op panel interrupt panic)
23233 J1: Create the new release for J1 PGA13
23284 MED: minor fix in trace
23126.7 Streaming DSS Capture problems cause DSS failure in rolling cal
23300 MED: RABF cycle clears CQ hist buff unexpectedly
23296 J3: MED: Retention History Page in sHKDS support
22608 Write filemark failed running Sctape fsc 6000
23355 Add thermal sensor diag on POST
23383 MED: Reduce J1 ROM size
23396 J1,2: change page id for tape directory page on reformat
23425 Change FID for 5066 to 86 from 83
23328 J1-Field: Repeated FSC 8C00 following FSC 8E19 error
23426 MED: Try another velocity in read ERP
23472 J1: Read hang without resume when C1 error happens
23531 Split CALIB_ROLL into CALIB_ROLLW & CALIB_ROLLR cal reasons
23463.5 Connect CALIB_ROLLR, CALIB_ROLLW to rolling calib invocations
23532 J1-FIELD 970D/4601
23468.1 J1: SM does not notice tape stop motion in ERP
3197 DUMP: Fix dump tracing for unhandled interrupt (ymt 23675)
2838.3 J1-RAS: Re-enable reporting of too many SRRs FID2 F5 FSC 3826
23794 J1: Fix the check routine for unexpected endmarker detection
23789 Read Position error, buffer image taken..
23671 J1 : drv 5491 : FSC 6017
3592 J1A D3I0_B95
Summary list of major enhancements and fixes:
1. Add FSC 3826 for excessive fibre errors (SRR)
3592 J1A D3I0_B93
Summary list of major enhancements and fixes:
1. Present correct FID code for FSC 5066 (prevent unnecessary Call Home)
2. Fix false FSC 3820 when running drive diagnostics
3. Fix problems with phase 2 rolling cal write/read ERPs
4. Add slow speed read ERP step
5. Fix RABF degraded writing problem
3592 J1A D3I0_B8B
EC Contents:
Summary list of major enhancements and fixes:
1. Rolling calibration phase 2 changes
a. Improved ERP handling of write or read temp error bursts
b. Fix some cases of FSC 6017 caused by ERPs during Locate/Space commands
c. Fix some cases of FSC 5066 read perms
d. Add max C2 correction as rolling cal option
Detailed list of all changes/fixes:
2965 BUILD: Use unique link space for j1PGA12
2967 HANG: Some errors (9711) can cause cmd hangs
2981 WRONG: CM page table needs to cross-reference actual page
2901 RABF(44010000-Rd2): TIMEOUT (1003s)
2967.1 HANG: Some errors (9711) hang write cmds
2996 FIBRE: Read abort [FCRC on read] due to race
3002 SCSI: Sense bit pos valid explicity set (not clr)
3042 BUILD: Fix image size overflow in j1PGA12
3046 PANEL: Fix hole in panel reset debounce
2954 LocRWShort (992s) DATA_MISCOMP (old tape, FFP=1069)
2954.1 FIBRE: Independent write/read burst sizes
3061 WORM: CM update failure is ignored
3088 6017: Extend upif timeout for Space request to 45 minutes
23089 RWLongTypical (1250s) TIMEOUT-0A
23113 MED: Rolling calib Phase 2
23124 MED: Rolling calib Phase 2
23147 WormLabel (1674s) TIMEOUT-2B
22982 J1 FIELD 83 5066 0000 2A0F
23150 J1: Remove codes to check c1c2 and decode error
23185 J1/J2: append error is returned by write perm@ABF on WORM
23212 RWShortAggressive (1126s) TIMEOUT-08
23126.1 Rolling Calib Phase 2-existing logic fixes and enhancements
23126.6 Rolling calib fix: last-best-option not held at EOW if burst
3592 J1A D3I0_B07
EC Contents:
Summary list of major enhancements and fixes:
1. Improve fibre channel transmit signal quality (jitter fix)
2. Drive diagnostic improvements (use correct pattern and threshold scaling)
3. Fix write inhibit problem with multi-volume Worm tape application
4. Set Media Life TapeAlert based on lifetime bytes processed
5. ERP enhancements for read interchange problems and long mounts (rolling
calibration changes)
3592 J1A D3I0_A13
False Diagnostic FSC 3823
3592 J1A D3I0_A0F
Slow read / long recall
3592 J1A D3I0_A0D
EC Contents:
Summary list of major enhancements and fixes:
1. FCR 3118 - Support immediate command termination for Long Erase command
2. Support locate past EOD (convert to linear read)
3. Clear DUC on retry of load error
4. Fix for No Response msgs during clean cycle
5. FCR 3129 - Allow library to clear Flash dump
Detailed list of all changes/fixes:
2738 JAG-1 FIELD DUC not handled by as400
2845 Jag2-Field 9713 28410,442
22291 RVT: FID1 E5 6017 0000 when running host jobs
2838 JAG1-Field: Not reporting error (SRR's)
22117 Jag2-Field 6017 1_A27 22337,122
22181 Jag1-Field 970C 45817,227
2818 RAS: Make diags to wrt/read and inb/outb same amount of data
2822 WRONG: FC settings not correct on 3584 FRU
22145 JAG: Change cleaning tape speed to 6mps
2800 Fix F027 Check_1 A38 Code
22123 Jag1-Field Fix 6017 54888,49R
22101 EOD entry of HRTD is cleared before unload
2684 PERF: Do not rescale/erase if unchanged value
2696 WRONG: Inquiry commands not forwarded to library
2881 Fix F027 Chk_1 w B1D code (break in 2830)
2883 Fix breakage of Get VPD cmds
3592 J1A D3I0_904
EC Contents:
Summary list of major enhancements and fixes:
1. Fix sequence problem with SRR during RES command
3592 J1A D3I0_902
What’s Fixed
EC Contents:
Summary list of major enhancements and fixes:
1. HSARS Quick Check
2. Improved calibration selection during diags
3. Miscellaneous field problem fixes
Detailed list of all changes/fixes:
2630 Drive Reset on Write(ymt21117)
2631 HSARS Quick Check
2640 F00B w 942 code
2659 F016: Double message received caused F016
2625 Drive reset in send diag for reset error injection
2581 F01C-0022: Memory access panic on flash erase
2591 FSC9712 on write
19712 7A00 loses segment-reusable flag after sns xfr
2541 NEW: Fail when library sends message out of order
20995 JAG1-FIELD 970C 000B 283C
3592 J1A D3I0_85A
EC Contents:
Summary list of major enhancements and fixes:
1. Support recognition and tape reformat from E05 encrypted to J1A
2. Miscellaneous field problem fixes
Detailed list of all changes/fixes:
2352 9999-C00C: Fix hang in port switch w/Ayame
2389 F016: Report nicer error w/FID for no BVPD in 3584
2448 F008-47D9: Misrouted unload response (multiple)from the lun
2496 9710: Switch precedence of 9710/9711 on writes only
20430 Add Sticky-Servo ERP
2530 BENCH: Chk-1 F010, Event Queue Full (ymtstor 20725
3592 J1A D3I0_847
EC Contents:
Summary list of major enhancements and fixes:
1. Fix problem with LUN1 read buffer x0A
2. Fix problem with adding fill bytes prior to last fibre frame
3. FCR 3090 - add support for Cross EOD and Cross Perm Mode Select controls
4. Fix 9999-C00C Chk-1 which caused loss of library control path drive
Detailed list of all changes/fixes:
2345 TRACE: Trace full 16 byte CDB
2346 TRACE: Trace queue/abort in summary area
2352 9999-C00C: Fix hang in port switch w/Ayame
2389 F016: Report nicer error w/FID for no BVPD in 3584
2393 DUMP: Do not dump drive on redrivable read perm
2394 Change DLR_MAX_PARM_SIZE to multiple of 4
2425 FCR 3090 - Cross EOD setting
3592 J1A D3I0_83C
EC Contents:
Summary list of major enhancements and fixes:
1. Important field problem fixes
a. Fixes for correctly setting and clearing TapeAlert 18
b. Fix Report LUNs allocation length problem (could cause protocol errors)
c. Fix problem where code info header can be corrupted in dumps
d. Fix problem when ATS received before FCP_CONF (could cause hang)
2. FCR's and other functional changes
a. FCR 3026 - LDI Get-Set Behavior (Baud Rate)
b. FCR 3065 - LDI Pause Command
c. FCR 3066 - Force ERP (TM Portion)
d. FCR 3068 - LDI Supported Features
e. FCR 3076 - Allow LogSense to be forwarded to LIB when Not Ready
f. Correct problem with Auto(NL) configs to L-Port instead of N-Port
Detailed list of all changes/fixes:
2038.1 9999-C00C: Fix hang in turbo counts
2081.3 FIBRE: Fix speed issue by disabling int xcvr on reset
2081.4 FIBRE: Handle path where LIPs can be missed
2139 JAG2-FIELD: Reject serial num update if drv model different
19104 JAG1 FIELD E5 6017 and 970C multiple accounts
2131 9999-A101: String Search check during error
19049 E5 970C
2094.1 F008-4342: Clean TSLLE on unusual error cases
2249 FC cable pull fail:Nport
3592 J1A D3I0_830
19049 E5 970C
19104 JAG1 FIELD E5 6017 and 970C multiple accounts
2183 JAG1-FIELD: F008-2707 Chk1
1871.1 Fix RLUNs allocation length
3592 J1A D3I0_825
Summary list of major enhancements and fixes:
1. Fix problem with incorrect FRU replacement of Jag2 drive with Jag1
2. Prevent false report of TapeAlert 18 to library during load sequence
Detailed list of changes/fixes:
7063 trigger fix
FSC 5012 on write,read,rabf
JAG2-FIELD: Reject serial num update if drv model different
3592 J1A D3I0_81F
Summary list of major enhancements and fixes:
1. Improve drive read ERPs to prevent certain long ERP scenarios
2. Miscellaneous field problem fixes
Detailed list of changes/fixes:
18956 JAG: DSS waveform capture - fix slow read
18972 JAG1: Slow Read Problem - Sticky Temps ERP
2094 F008-4342
2097 Add trace for CM protected and unprotected page tables
2102 FCS 6017
3592 J1A D3I0_81A
1. Miscellaneous field problem fixes, including slow locate. More detailed list not
available at this time.
3592 J1A D3I0_805
Summary list of major enhancements and fixes:
1. 4022 on read
2. 3823: Increase Jag1 Wrt Skip threshold for diags
3. Write failure FSC7888
4. FSC 5012/4401 perms
5. F010 on many repeated perm hidden dumps (inc#21768)
6. FSC 7060 code hole
7. Fix for FSC7520 write perm after rechuck.
8. Misdetect consistency of TapeDir and EOD
9. E5 F010 FFFF 2515
4． LTO4 GEN4：
Drive Code Level: 85V8 (TS2900 Library only)
Fixes:
LUN1: TS2900 library use mode 2 in LUN1 write buffer command
Drive Code Level: 85V6 (TS2240 Standalone Drives only)
Fixes:
Open neg. friction limit for HH due to circuitry offset
Drive Code Level: 85V2 (TS2240 Standalone Drives only)
Fixes:
Tracing and Dump Enhancement
U320 -All FF CDB causes Overlapped command
Enable C1IBC ERP on LTO - ERP enhancement to reduce write/read perms
U320 - Residual count is not reported when EOD detected during tape locate
U320 - Mode Page 19h/Subpage 03h not reporting correctly
ADI - LUN1 queue is hung with RES command.
Write perm ERP enhancements
Auto unthread after 20 minutes of non-activity to drive when media loaded
No indication for temperature error on SCD
Enhancement to Read ERP structure during C2 correction (706x FSCs)
G4HH - Need serial command to disable brush when extruded
SCSI PRIMARY PORT Enable/Disable VIA ADI
Code enhancement physical thread/unthread can be a solution to unthread/thread
failures
eServer: 'J' for invalid cartridge type at any case
Define SCD display for temperature failure in NEC/CAS mode
New POST check for open writer cable to head
SAS - Cable pull caused queue hang
ADI to detect framing and line breaks, hdwre workaround, can cause communication
failure without indication
Log page 0x11, log parm 0x8001, MES value for uninitialized cartridges
Unable to unload tape
U320 - Drive hangs with Bus Reset
Enhancement in Channel code to improve general write and read operational
performance
Improvement to the retention of statistical data stored in VPD/EEPROM
U320 - Multi-initiator Invalid Reselection
Fix for FSC1602 occurrence
U320 - Wrong session may be used when turbo exit
FSC 6000 on SCSI load after FSC 2E05 failure
FCR 3155 - Drive Pass IES Vendor Specific Bits
FCR 3155 - change for all LUN1 commands
Cleaning twice without 2nd load
U320 - Exception on Read FM
U320 - handle sense data for error response on TM
U320 - extra one byte is padded on HP-UX (N138)
Encryption enhancements
Post 7904 even if tape is unloaded after auto unthread
Panic when LDI command read tape with long length
LDI - change method for 3572 inquiry string machine type/number
High-speed refreshes the cartridge to EOT, then to BOT when media debris signature
is detected
Wave motion ERP enhancement - enhancement to greatly reduce stiction
Creep motion improvement for a-unthread (local ERP) - enhancement to greatly
reduce stiction
VFO Detection enhancement - greatly reduce read degradation and perm errors
Accept uninitialized cart which has CM TA page
ADI - Fix mode page 0e 01, display current wwnn
ADI - Fix mode page 19h - data in mode page 0x0e 01
Flashing Activity light on recovery
SAS - Incorrectly aborted command should have sent up a check condition
U320 - Handling delayed scsi response for TM IUs
LDI - Not cleaning up LUN1 cmds properly during login
U320 - Drive hangs with Bus Reset at reselection timing
Auto unthread hang after unthread error - can result in a tape not able to be unloaded
Fix for failure to unload
Fix for a Drive panic during a locate command
Add MAM attribute 80B Application Format Version
Allow return of saved values for modes pages 0x0e 0x
ADI - wrong frame number after login process
ADI - mode page 0x0e 02 (ADI) enable/disable ports separately changed to match
specification
Auto unthread: drive hang with unload request - can result in media unable to be
unloaded
SAS Drive panics on PRO
ADI - Add EPP and ESR bits to VHF data
Support Legato NetWorker (NW) ILEP
FCR 3156 - add correct ITD pages for 3572 (1U) library
Timeout on Locate command
Channel enhancement to ACOMP registers. Resulted in slightly degraded channel
performance
Added check cleaning criteria at boot
Support vendor-specific INIT ELEMENT STATUS(E7h) cmd
MED: med_compare_pos() is called with a wrong argument order
Drive returns 2 5904s
Out-of-range indexing in Error Burst Log, burst detect probs
ADI-FC Race condition creating SIOP, resulted in a no response to RES command
ADI No response after command - framing errors and aborts
Bursting temps for Servo errors can cause excessive backhitching
I/O error on read can cause a Drive Hang
FSC 6000 during data operations
U320 - I/O error causes drive to not respond
Short locate timeout
ADI - No response when using NOP and PAUSE ADI commands
Fix for Mode page 0x1e
Drive Code Level: 82F0 (TS2240 Standalone Drives only)
Fixes:
During a write filemark an FSC 6000 is experienced
When running Diags the drive must clear all reservations when taking the port offline
Fix for an infinite loop retry breakage- When incorrect setup on the EKM causes a
retry, the drive will stop retrying after 3 incorrect keys with correct alias are returned
When media is partially ejected and power is pulled, there is a small possibility for a
hang in the drive on power up
During an SME usage where the EKM is removed from the network, the drive can
post an SCD'3'
On an attempt to mount, the drive fails the mount and incorrectly reported a FSC
2C51
ADI drive communication failure during internal library check. Results in the
appeared hang of the drive/library
In certain environments the FSC 1606 has been seen. This fixes this particular
interface error
Fix planned command
During diagnostics, need to change the help response during the ras diagnostics
Drive did not handle Initiator detected Error msg properly. This results in an interface
error at the host. (U320)
SAS Block length must be a multiple of 4 per the SSC specification
Implement FCR 3146/3147 for High Density 3584 support
After a write error, the drive returns a FSC 605E incorrectly
During write or read operation, the Fibre Channel interface would experience a panic
causing a failure in the customer job
Selection Timed out for TUR during Multiple burst transfer
Added new FSCs with ASC/ASCQs to the drive reporting for IU mode errors (U320)
During a write or read operation, the drive could detect a motor driver failure. When
the motor driver failure occurs (reported as FSC 7875)
The correct ERP needs to be invoked to ensure the integrity of the tape
Change the write attribute command structure to allow the writing of the Cleaner CM
Support the writing of the label to a cleaner CM over LDI interface
If DISCPriv is off the bus, it is disconnected incorrectly by the drive causing a
communication error with the host (U320)
TA16 was being set when the unload button was pushed
When in a non-IU mode, a drive code error was being returned to the host (resulting
in a communication error with the host) U320
Cleaning operation would be executed twice in a row (U320)
FSC 78B5 Beginning of Tape shutdown is experienced as a result of LPOS estimation.
This failure is on LTO4 tapes
Integrate Read and Write channel enhancements
Due to a tray position error, the drive would not load a tape after unload
Added Support for the DTD Port Status Log Page (U320)
The ADC mode page for port status reports the incorrect LVD mode
The Drive Panics on a Write. This results in a communication error with the host, job
failure. This is a result of an incorrect queued command count
Read/Write Channel enhancements for LTO4
Change the point at which the drive reports a failure for the retraction of the head
brush. Experienced as a load failure in the drive
Drive fails as a result of the handling of many commands coming into the drive in a
multi-LUN environment
Assign a unique reporting sense for error relating to tape failure with head interface
Encryption enhancements to FIPS capable code areas
Fix for FSC 7865 permanent error on LTO4 media
Selection Timeout due to Long Bus Reset Assertion (U320)
Sense Key for write protected uninitialized cartridge load should be 07 - it was set at
05
In a SAN environment with link failures, the drive incorrectly fails with FSC 7070 on
the recovery of the link failure
Read after write failed with SK/ASC/ASCQ 04 44 00 and FSC 6410
FSC 1605 reported by the drive as a result of link level errors on the bus in a write
command (U320)
Implement a Tape Alert for FSC 2C3A
ADI reporting of FC status for supported features has an incorrect length
ERP enhancement for high friction media events
Incorrect value in Log Page 0x0C Parameter Code 0x02 (compressed data bytes) at
read operation
Add FSC for safety unthread/rethread and high friction media events
FSC 7133 failure as a result of beginning of wrap Data check ERP
When compression is selected, a faster write speed will be selected
During drive detection, a physical link error may cause the HBA to not respond. This
works around the HBA failure
ADI fix for display message on LUN2 requests
New cleaner tapes can have a CM entry that will cause the Cleaner cartridge to not be
ejected
Under the multi-initiator environment, LTO4 U320 hung up during a write operation
when the other drive issued Reset on the bus. (U320)
In Multi-LUN condition. LUN1 commands that invoke data transfer are issued while
Read/Write in turbo mode
Implement Tape Alert for FSC's 1224 -1227 (RAS failures)
Write timeout on Fibre Channel drives
Unload failure with FSC 2E09 and the Drive posts a SCD '5'. This can be caused by
powering off the drive with tape mounted or at load point
FSC 1606 Fibre Channel DMA FIFO fix
Fix frame number in error recovery for ADI communication - Customer would see a
drive and library failure
ADI disabling of the primary SCSI port prevent selection of the primary port, but
does not correctly prevent bus reset processing
When more than 16 LUNs are connected, the drive did not properly return the correct
LUN
Do not set WP in VPD for mode page 0x03 (ADI)
Library initiation failure over ADI - task management IU should not come during
login process
A Control Path SAS drive can fail for a microcode error as a result of handling abort
requests. This happens mainly on non-TLR supported Host Bus Adapters
SAS change for handling an abort request with iSeries and pSeries SAS adapters
When over temp occurred there was no indication on the SCD in certain cases
Drive Code Level: 8192 (for TS3100/TS3200 at this time)
Fixes:
During reselection in non-IU mode the drive experienced an issue with the reselection.
This resulted in a communication failure between the drive and Host.
After a send diagnostics, drive returns check condition on release (U320)
FSC 78B5 returned to the host with LTO4 media
Drive unable to load a tape manually after it was eject
Cleaning operation twice in a row with U320 drive
Implement Support DTD Port Status Log Page
Drive failure as a result of Queued command count being invalid.
Changed read CRC error sense code (U320)
Sense Key for write protected uninitialized cartridge loaded should be x07 not x05
Fix frame number in error recovery for ADI communication (ADI)
Added iuCRC error FSC to the FSC table in the drive
Read operation stopped due to FSC 7865 error
Need to move brush retract detection from unmount to mount.
Need to invoke GDB when motor driver error happens (Half High drive only)
Drive Code Level: 7BG5
Fixes:
Need to move brush retract failure from unmount to mount
Drive Code Level: 7BG3
Fixes:
Encryption EKM loop fix with EKM
FC only changes to the clock timing on the drive internal bus
Fix calculations of read attributes 0x222 and 0x223
Releveling for FIPS qualification
False excessive read recovery timeout (Read ERPs with slow host)
FSC 2C51 is reported after mount fail
Change FAS Buffer Clock and DMA Clock to avoid FSC1606
FAS timing change previously applied to FC for FSC1605 applied to SAS and U320
Fix TD Sta_Check_Dataset_Number_Consistency()
Return "all pages" for LUN2 for mode sense command
Encryption Loop Fix for EKM interfacing
Incorrect WWNN sent to EKM from Drive in LME mode
Log page length incorrectly reported in the log page header
Need to enable brush extension on rechuck
Improper handling of Proxy(library) termination of the key acquisition
GEN2 tape issue in manufacturing caused by calibration in certain region of tape
Fix reporting of Write protect WORM media sense data from Sense key=03 to Sense
Key=07
Tape breaking scenario at Beginning of tape with unload
T021 error on LUN1 commands causing hang in library in TS3310
MAM attribute 0007 not returned with correct value
Implement head brush on every 5 loads
Implement New MAM attribute 0x224 when G3 cartridge is loaded
Read Attribute needs to support x224 as a first attribute
SCD H on Send Diag fail after FMR fail
Small distance margin for UCC cleaning at 1st cleaning
RW diagnostics with ITDT application fails when using a GEN3 media
Band Change Timeout
Drive Code Level: 7A31 (for TS3310/TS3500 at this time)
Fixes:
LDI Enable Drive_MD messages for LTO
Abort task no status frame received
Update motor limits due to clock frequency change
Fix for long locate due to CQs
Fix for Read Perm
Adjustment for cleaning Algorithm - was too frequent
Invalid SK0 with LTO4 and LME enabled on 3584
Data Path failover failure on rewind with Linux
Expand tolerance on Post motor test
Fix for logical unit reset in ADI mode
Fix for E0 and EF with read and write of encrypted data
Support CALIB_SARS as a valid calibrate reason for LTO drives
Copy comp block to RAM before creating plain block
Speed boundary condition inhibits FSC 7063
Fix for FSC 1012 failure in Library environments
Fix for Mode Page 0x19
Failure with WORM media for OPP
Drive FCE Panic 0xFCFF on Inquiry (Non-IU)
Overlapp command resulting from read buffer on IU mode
U320 Changed default SyncOffset Value
Drive FCE_Panic(0x1111) on Recovered Error
Hang resulting from Exception with Parity Error @ U160
Residual Count is not correctly returned in 160 mode
Multi Initiator does not work correctly in 160
U320 adapter *** Panic on FixedMult w LUN1
Changed Slew Rate Control value (u160 in multipath env)
FSC1017 is returned to TUR and other commands
Fix for one flavor of FSC 1605
AME - IBM proactive key set for read not recognized
U320: need to clear uninitialized variables
ORC check fences drive on illegally written carts
Change timing of checking WP switch- Possible incorrect WP surfaced
FSC2E05->FSC2E19 after Drive Reset -> Overlapped command
Drive FCE Panic FCFF on Write
Data Path Failover Failure on Rewind failover failed
U320 Drive FC Panic 0xFCFF on Read in IU mode with Attn
Fix for MTR sense is reported as recovered when it is not
Data Path Failover fails for Read operation on SAS
Mode page 0e_04 serial number not from VPD on power up
Fix for Read compare error
ModePage 0x19 subpage 0x3
FSC 605E when attempting to read Ultrium2 tapes in LTO GEN4 drive
Residual counter in sense is wrong when Filemark is detected causing EOD detected
incorrectly
Change initial value of INTMSK1 register
Drive FC Panic 0xFCFF on Write in IU mode
Encryption device causes panic in drive (u320)
Reading last block on a pre written GEN2 tape failed FSC 605E
Fix for FSC 2E04 resulting in a unloadable tape
Fix LUN1 Standard Inquiry for U320
Fix for SCSI slow negotiation when in ADI mode
No disconnection during TUR/RSNS/INQ in Non IU mode
If quality of lowest drive speed is bad, the drive selects next speed up only
LDI License Keys for EKM usage
Encryption Regen'd key on EKM creates loop in drive/EKM KEY exch
FMR cartridge cannot be used (SCD 6 FSC 5911)
FMR image is different from original ROM image after ROM recovery will result in
'e' on SCD
Panic on Multi-LUN command (u320)
FCH: Relevel with tapedrv (includes FSC 1605 and FSC 1606 improvements)
Incorrect FSC 1133 during encryption
Exception when running u320 in ADI mode
Servo support of 7 drive speeds
Fix Read FSC 1605 in MultiLUN with u320 drives
Read T/O while the drive detects a FM.
FSC7530 reported as a result of EOT fast locate
Device Not Ready on TURs ( MultiLUN ) (I/U mode)
Fix for Drive panic during write/read operation
SAS Hang in error scenario with expander cable
Media slow recovery enhancement
Servo enhancement for FSC 7834
Bus Reset Problem ( MultiLUN and Daisy Chain )
Calibration Enhancement Phase 2 change
Drive Code Level: 77B1 (for TS3100/TS3200 at this time)
Fixes:
Optimize Speed selection
FSC 6037 Fix during MTR
Enhance LPOS registration
Fibre Channel enhancements
FIPS Certification
SCSI Reset enhancement
Data path failover with Linux
LDI drive status reports wrong value for FMR cart
Sense reporting enhancement
Tracing for LDI/ADI
Encryption enhancement
Dump enhancements
Append mode enhancement
Encryption enhancement with EKM interface
Encryption management failure fix
Unload response failure
Reboot by reading corrupted rom dump
LDI encryption enhancement
U160 incorrect reporting of encryption state
Encryption Auto set to T10
Locate Timeout fix
Encryption enhancement- ADI EKM interfacing
Reservation Check enhancement
FSC 1017 load enhancement
Drive Code Level: 75X2 (for TS3310 at this time)
Fixes:
Image Enhancement
Fix status reporting on FMR
Sense reporting enhancement
ADI/LDI tracing enhancement
Format enhancement when in append mode
Relevel of FCH code
Encryption enhancement
Encryption enhancement - EKM interfacing
Encryption enhancement sense over LDI
Drive Code Level: 7590 (for 3584 at this time)
Fixes:
Fix for EOT shutdown
Dump to Flash enhancement
Remove LUN1 requirement on Poll Queue handling
Library Encryption Enhancement
Tape alert posted on new WORM media
Certain new WORM Cartridges fail with Tempering Check
Drive Code Level: 74H4
Fixes:
No CM Cart failed
Error on Space to EOD
Fix for Servo Write error
MED: Failsafe for a panic which is caused by STICKY_WSRV_TEMP
Fix for encryption Validation
Enhancement for VPD Encryption certificate
Library Interface: LogSns command incorrectly checking for NRD
Fix for Load Failure in certain circumstances
Increment thread count for brand new WORM
Fix 1st encrypted record number in CM status page
Library Interface - Added Clear Flash Dump to supported features in read
SAS Speed Negotiation enhancement
ADI (library fix) for space/no Op
Fix inquiry pages 0x83 and 0x88 for ADT port responses
Library Interface: commands are not forwarded after PAUSE state
Enhancement for Drive Write Fencing on certain perm errors
Enhancement for Link Initialization
Enhancement to persistent reserve
New Function for Encryption with Branded products
Control path drive may not be able to be seen by host
ccSARs enhancement
Deferred SNS reported on recovered ERP
Logical Write Protect should work in all load states
Fix for occasional panic resulting from timed out exchange
SAS Enhancements
Change for protecting sessions w/reservations from implicit logout
Serial number inquiry fix
Fix For invalid field in parameter data on Mode Page x0E
Enhancement of POST error reporting
Fix for FSC that triggers when Clean for usage is required
Match SCSI reference with new log page x3C
Dump dot indicator fix
New PLL settings to improve read/write error rates
Microcode update resets VPD replica
SAS performance compensation for TLR performance on the HBA
Fibre Channel Link enhancement
ILI Sense over written by recovered error
Control and Data path Failover fix for SAS
Initialize element status fix
Properly reject G4 cart in G3 drive when in Library
Fix Frequently requested cleaning
Drivecode Level: 7384
Base Code
5． LTO3 GEN3：
Drivecode Level: 85P1
Release Date: 06/18/08
Fixes:
23932.1 ADI - Fix mode page 0e 01, WWNN
23741 ADI - Detect framing and line breaks, hdwre workaround
23932.2 Fix mode page 19h - data in mode page 0e 01
23977 Handling delayed scsi response for TM IUs
23978 ADI - not cleaning up LUN1 cmds properly during login
24007 ADI - Wrong frame number after login process
24005 add MAM attribute 80B Application Format Version
24016.2 ADI - Mmode page 0e 02 (ADI) enable/disable ports separately
24081 ADI - No response after command - framing errors and aborts
24102 Fix for breakage of config DPF with the new method
24112 ADI - correct scsi id if not in library for ADI 0e_02 mode page
23848 U320 - RAS test failed
24146 ADI: No response when using NOP and Pause ADI commands
24158 Fix for Mode page 0x1e
Drivecode Level: 73P5
Release Date: 05/24/07
Fixes:
21122 Servo Acquire enhancement
21157 Error Reporting enhancement
21232 Data protection mechanism enhancement
21234 Fix for unload error on 5v power interuption
21334 Log page 16 enhancement
21354 Fix For Error Recovery on Fibre Channel
21351 Log Page 16 not saving SK/ASC/ASCQ of 03/53/00
21367 Log page 16 enhancement to compliance
21415 Media Buffer Header data flow fix
21444 Remove iop on reselection timeout
21445 Write Buffer command did not work on ADI
21471 Fix for Cartridge memory corruption recovery
21472 Enhancement for soft error recovery
21480 Fix for WORM corruption on writing the volser
21496 Fix for primary interface not going offline
21507 In certain circumstances TA32 should be turned off
21545 HIB interrupt was kept disabled forever.
21558 Log Page 16 Enhancement
21578 Unexpected media write protect
21617 Drive offline after Fibre Channel wrap test
21831 OEM ADIC - FSC 7265 on Write
21940 VPD life time is updated incorrectly
21972 Fibre Channel link down fix
22000 Log Page 14 enhancement
22011 Enhancement for Append failure due to media degradation
22014 Log Page 38 parms 4-7 not logging
22091 SCSI wrap test fix when over Library interface (LDI)
22141 Write Buffers fix for ADI library interface
22178 Update counters in Log Page x3Ch when unload occurrs
22184 ADI (library fix) for space/no Op
22234 ERP enhancement related to speed selection
22261 Reservation enhancements
22304 Addition of Log Page x3Ch in LTO3
22217 Drive fence enhancement for perm on locate scenario
22399 Fibre Channel Link enhancement
22400 ILI Sense over written by recovered error
6． LTO2 GEN2：
Drivecode Level: 73V1
Release Date: 04/30/07
Fixes:
19363 keep drv OFFLINE until told ONLINE by LDI
19513 TA22 clearing behavior change
19687 Notify lib of aborted LUN1 host command
20128 Set appropreate TA on 2E02 load failure
21090 Fix for incompatible Dataset Identification
21117 Fix for Drive Reset on Write
21221 Fix for Drive Reset for Fibre Channel drives
21617 Fix for Drive offline after FC wrap test
21789 Error Log not cleared by Maint Mode A
21940 VPD life time is updated incorectly
21962 Enhanced reservation implementation
22186 Fix for persistant Reserve
22217 Drive fence enhancement for perm on locate scenario
22219 Persistant reserve enhancement
22244 Power on hours not being updated correctly
22256 End of wrap shut down could cause stuck tape
22261 Protect sessions w/reservations from implicit logout
Drivecode Level: 67U1
Release Date: 11/01/06
Fixes:
17484.1 "FC If the host or switch sends the drive a frame in the wrong class of
service, the drive will correctly send P_RJT, but then the drive will incorrectly
send LIP(F8). LIP(F8) will cause a new loop initialization."
17773 FC Protocol- Drive does not LIP soon enough for missing LIPA
17930 Drive may hang during write at Wrap due to ERP infinite loop
17946 Write permanent error (FSC 7475 or 7115) during attempt toappend at
position other that EOD
18317 When an expired cleaning cartridge is not ejected and seats at themount
position, ready status is reported. Although ready status should not be reported
for a cleaner cartridge.
18772 FC Drive will not recover from a cable pull while data xfer is in progress:
Error recovery does not ever complete and job appends.
18956 Intermittent lower performance on locate/space or read.
19083 FC: drive configures to L-Port instead of N-Port when in Auto(NL)
19120 Read timeout in overrun condition
19138 Enable LDI Supported Features
19141 Enable LDI Get-Set Behavior Baud Rate
19166 Log sense timeout problem during cleaning
19173 FC Drive goes offline due to panic reset in multi-initiator environment
( Panic xFCD0 )
19181 Some drive diagnostics initiated over the host interface hang the drive and
fail the test
19198 Asynchronous Unit Attention was not reported to host.
19225 New tape (not end point tested) used to make a FMR tape the does not
complete successfully.
19053 FC - RR_TOV timeout (SRR fail) / not validating fcp2tag
19062 FC - Detect hardware problem that may cause register mis-writes
19197 FC - No Check Condition for an invalid task attribute
19296 Non zero byte count in RES response
19328 FC Wrap Test Failure on 2GB drives
19339 Null Sense reported after Thermal sensor failure
19350 LDI Pause Command Enabled
19394 Gen2 Drive writing Gen1 cart did not increment Tape Write Pass
19399 ERP’s were improved to recover from a CM read error which would cause
FSC 6017.
19408 Fix for Drive resets when large amounts of data are transferred via LDI
19417 TA18 incorrectly posted when cartridge is loaded – The drive incorrectly
detected a corrupt CM and posted a TA18.
19439 FC Drive, intermittently, does not recover from a cable pull when set to
Nport
19601 Incorrect truncation of cartridge Serial Number in engineering log
19646 Add conditional checking to detect suspected rare off-track condition.
19685 Write FM failed when FC linkdown occurred due to drive panic
19786 Invalid FSC 1042 for invalid field in param list
19835 5 is displayed in the single character display upon receipt of Clear Task Set
message
19858 2nd FM lost in error recovery on Space to BOT.
19953.2 Add Long Erase progress indication
19967 Enable LDI Reset - add Abort Task Set
19979 Added Read Buffer Size Maint_Command to LDI
19993 Inquiry with Invalid field does not set field pointer info
20146 Drive Diagnostic ‘F’ fails on a good drive:
20281 Unexpected Device Driver I/O on mode Select
20330 Added LDI Supported Functions (Read Buffer Size)
20341 In library environment, unload a cartridge without unmounting and load the
cartride. Then next write command is hanged
20398 Bus reset due to bus scan can cause a drive reset
20398 intermittent drive panic in LDI transmit due to bus reset
20419 False detection of Endmarker at DS Boundary
20490 Wrong bit/byte pointers may be reported in sense data, when an invalid
CDB is issued for SCSI Report LUNs command
20509 FC: drive L-port participates while offline
20725 FC drive panics when initiators that rapidly and repeatedly send frames in
the wrong class of over flow a queue
7． LTO1 GEN1:
Drivecode Level: 5AU1
Release Date: 12/20/2005
Fixes
14665 Command time out due to holding of SCSI bus phase unchanged for more
than 2 Seconds
15146 Fix for FSC 4001/2080 due to abundance of write skipped datasets on tape
15511 Implement ERP to detect servo during lateral tape shift is occurring to prevent
degraded performance and FSC 3111
15611 FC Drive panic due to access invalid address while performing force log
capture
15626 Fix for FSC 20C0
15930 Enhance drive diagnostics
15965 Corrupted CM cartridge hangs drive during load
15968 Tape Alert flag 22 is not cleared when cartridge is removed
16104 Abort to CMD causes SCD 4 FSC 219D
16189 Drive Status message to library on Fibre channel drives does not reflect if
drive offline
16204 On Control Path enable drive corrupted Read Element Status data causes
drive to panic
16922 Added ERP for writing block 1 protection flag in Cartridge Memory
16941 On Fibre Channel drives when checking for valid SRR add specific relative
offset
16968 Fibre Channel drive hang when LIP during data transfer
17048 RBL and RDS commands incorrectly return reservation conflict
17516 Internal Locate issue with Read Command on FC Drive
17593 iSeries: Download ITD records not correct
17614 TLWR fails after drive code update by AS/400
17896 Workaround for the CM read timeout during thread operation
17951 FC drive Reboot by exception 0100
18759 Intermittent Read time out on SCSI drives
18034 Report Density data is padded with zero (00h) instead of ASCII space (20h)
Drivecode Level: 53J1
Release Date: 4/13/2005
Fixes
15146 Fix for Perm during read operation
15511 Implement ERP to better detect servo
15611 Fibre Channel drive Panic during force dump processing
15626 Fix for FSC20C0 during write operation
15930 Enhance drive diagnostics
15965 Corrupted CM cartridge hangs drive during load.
15968 Clear TA flag 22 when cartridge is removed from drive
16104 Abort to CMD causes SCD 4 FSC 219D
16189 Fibre Channel Drive Status does not reflect if drive offline over LDI
16204 Control Path Read Element Status data corruption causing panic
16922 Added ERP for writing block 1 protection flag in CM
16941 Improve Latchable SRR redrive on Fibre Channel
16968 Fix Fibre Channel Drive hang when LIP during data transfer
17048 Incorrect reservation behavior for RBL and RDS comm.
17516 Internal Locate issue with Read Command on FC Drive
17593 Fix iSeries Download ITD records
17614 TLWR fails after ucode update by AS/400
17896 Workaround for the CM read timeout during thread
17898 SCSI bus is hold during LUN1 Mode Sense command
附录B：LTO的SCD code详细说明。
Code Cause and Action
SCD 0
No error occurred and no action is required. This code displays:
- When power is cycled (turned off, then on) to the tape drive.
- When diagnostics have finished running and no error occurred.
Note : The single-character display is blank during normal operation of the tape drive.
SCD 1
Cooling problem. The tape drive detected that the recommended operating temperature
was exceeded. Perform the following action:
1. If a fan is present in the enclosure, ensure that it is rotating and is quiet. If not, replace
the fan (for instructions about replacing the fan, see your enclosure’s documentation).
2. Remove any blockage that prevents air from flowing freely through the tape drive.
3. Ensure that the operating temperature and airflow is within the specified range (see
“Specifications” on page 1-19).
4. If the operating temperature is within the specified range and the problem persists,
replace the tape drive.
The error code clears when you power-off the tape drive or place it in maintenance
mode.
SCD 2
Power problem. The tape drive detected that the externally supplied power is either
approaching the specified voltage limits (the drive is still operating) or is outside the
specified voltage limits (the drive is not operating). Perform the following action:
1 . Ensure that the power connector is properly seated.
2 . Ensure that the proper dc voltages are being applied within the tolerances allowed
(see “Specifications” on page 1-19).
3. If the proper voltages are being applied but the problem persists, replace the tape
drive.
The error code clears when you power-off the tape drive or place it in maintenance
mode.
SCD 3
Firmware problem. The tape drive determined that a firmware error occurred. Perform
the following action:
1 . Collect a drive dump from one of the following: Note: Do not force a new
dump; the tape drive has already created one.
- Server’s SCSI or Fibre Channel interface by using a device driver utility or system tool.
To obtain a dump, determine whether your server is installed with a utility that can read
files from the server’s memory. If it is, use that utility to obtain the dump. For information
about using IBM’s utility programs to obtain drive dumps, see the IBM Ultrium Device
Drivers Installation and User’s Guide. To determine where to send a file that contains a
drive dump to be analyzed, contact your Support Center.
- Ultrium Tape Drives (to copy a drive dump, refer to the section about copying a drive
dump in the library’s operator guide).
2. Power the tape drive off and on, then retry the operation that produced the error.
3 . If the problem persists, download new firmware and retry the operation.
4 . If the problem persists, send the drive dump that you collected in step 1 to your
Support
Center.
The error code clears when you power-off the tape drive or place it in maintenance
mode.
Firmware or tape drive problem. The tape drive determined that a firmware or tape drive
hardware
failure occurred. Perform the following action:
SCD 4
1 . Collect a drive dump from one of the following: Note : Do not force a new dump;
one already exists.
-Server’s SCSI or Fibre Channel interface by using a device driver utility or system tool.
To
obtain a dump, determine whether your server is installed with a utility that can read files
from the server’s memory. If it is, use that utility to obtain the dump. For information
about
using IBM’s utility programs to obtain drive dumps, see the IBM Ultrium Device Drivers
Installation and User’s Guide. To determine where to send a file that contains a drive
dump
to be analyzed, contact your Support Center.
- Ultrium Tape Drives (to copy a drive dump, refer to the section about copying a drive
dump
in the library’s operator guide).
2. Power the tape drive off and on, then retry the operation that produced the error. The
error
code clears when you power-off the tape drive or place it in maintenance mode.
3 . If the problem persists, download new firmware and retry the operation; if new
firmware is not
available, replace the tape drive.
SCD 5
Tape drive hardware problem. The drive determined that a tape path or read/write error
occurred.
To prevent damage to the drive or tape, the drive will not allow you to insert a cartridge if
the
current cartridge was successfully ejected. The error code may clear when you cycle
power to the
tape drive or place it in maintenance mode. If the problem persists, replace the tape
drive.
SCD 6
Tape drive or media error. The drive determined that an error occurred, but it cannot
isolate the
error to faulty hardware or to the tape cartridge. Perform the following action:
For Problems with Writing Data:
If the problem occurred while the drive was writing data to the tape, and if you know the
volume
serial number (located on the cartridge label) of the tape cartridge loaded in the drive
when the
problem occurred, retry the operation with a different cartridge:
- If the operation succeeds, the original cartridge was defective. Copy data from the
defective
cartridge and discard it.
- If the operation fails and another drive is available, insert the cartridge into the other
drive and
retry the operation.
------If the operation fails, discard the defective cartridge.
------If the operation succeeds, insert a scratch cartridge into the first drive and run drive
------diagnostics (refer to the appropriate section in the library’s operator guide).
-------------If the diagnostics fail, replace the drive.
------------- If the diagnostics succeed, the error was temporary.
- If the operation fails and another drive is not available, insert a scratch cartridge into
the drive
and run the tape drive diagnostics (refer to the appropriate section in the library’s
operator
guide).
------ If the diagnostics fail, replace the drive.
------ If the diagnostics succeed, discard the cartridge.
If the problem occurs with multiple tape cartridges or if you do not know the tape
cartridge’s
volume serial number, run the tape drive diagnostics (refer to the appropriate section in
the library’s
operator guide):
- If the diagnostics fail, replace the tape drive.
- If the diagnostics succeed, run the Head Read/Write test (refer to the appropriate
section in the
library’s operator guide).
------ If the Test Head diagnostic fails, replace the tape drive.
------ If the Test Head diagnostic succeeds, replace the cartridges that caused the
problem.
The error code clears when you remove the tape cartridge or place the drive in
maintenance mode.
For Problems with Reading Data:
If the problem occurred while the drive was reading data from the tape, and if you know
the volume
serial number of the tape cartridge, perform one of the following procedures:
- If another drive is available, insert the cartridge into the other drive and retry the
operation:
------ If the operation fails, discard the defective cartridge.
------ If the operation succeeds, insert a scratch cartridge into the first drive and run the
tape drive
-------diagnostics (refer to the appropriate section in the library’s operator guide):
------ If the diagnostics fail, replace the drive.
------ If the diagnostics succeed, the error was temporary.
- If another drive is not available, insert a scratch cartridge into the drive and run the
tape drive
diagnostics (refer to the appropriate section in the library’s operator guide):
------If the diagnostics fail, replace the drive.
------If the diagnostics succeed, discard the cartridge.
If the problem occurs with multiple tape cartridges or if you do not know the tape
cartridge’s
volume serial number, run the tape drive diagnostics (refer to the appropriate section in
the library’s
operator guide):
- If the diagnostics fail, replace the tape drive.
- If the diagnostics succeed, run the Head Read/Write test (refer to the appropriate
section in the
--library’s operator guide guide):
------ If the Test Head diagnostic fails, replace the tape drive.
------ If the Test Head diagnostic succeeds, replace the cartridges that caused the
problem.
The error code clears when you remove the tape cartridge or place the drive in
maintenance mode.
SCD 7
A high probability of media error. The tape drive determined that an error occurred
because of a
faulty tape cartridge, and expired cleaning cartridge, or the insertion of an FMR cartridge
as a data
cartridge.
- Try another tape cartridge. If the problem occurs with multiple tape cartridges, see
“Resolving
Media-Related Problems” on page A-14.
- Dispose of the current cleaning cartridge and insert a new cleaning cartridge.
- If the FMR cartridge is no longer needed, go to to the section about erasing an FMR
tape in the
IBM TotalStorage Ultrium Scalable Tape Library 3583 Maintenance Information.
The error code clears when you remove the tape cartridge or place the drive in
maintenance mode.
SCD 8
For SCSI drive:
Tape drive or SCSI bus failure. The tape drive determined that a failure occurred in the
tape drive’s
hardware or in the SCSI bus. See “Fixing SCSI Bus Errors” in the MI. The error code
clears 10
seconds after the drive detected the error or when you place the drive in maintenance
mode.
For Fibre Channel drive:
Tape drive or Fibre Channel failure. The tape drive determined that a failure occurred in
the tape
drive’s hardware or in the Fibre Channel. It detects light through the fiber cable but
cannot perform
data communication properly. The length of the cable between the devices should not
exceed 500
m (1640 ft). See “Fixing Fibre Channel Errors” in the MI. The error code clears when the
drive
detects light and can communicate, or when you place the drive in maintenance mode.
SCD 9
Tape drive or LDI (RS-422) error. The tape drive determined that a failure occurred in
the tape
drive hardware or in the LDI (RS-422) connection.
- Power cycle the drive. If the power-on self test is successful, the problem is resolved.
- If the problem persists, replace the tape drive sled (see “Tape Drive Sled” on page
7-3).
- If the problem persists after replacing the drive, the problem is with the cable between
the drive
sled and the power distribution board, the power distribution board itself, or the main
board.
The error code clears when you place the drive in maintenance mode.
SCD o, c, b, or h
No error or message assigned. There may be a problem with the single-character
display. Turn the
power off, then on and determine whether all segments on the single-character display
are lit. If so,
you may have a down-level version of both your library’s firmware and documentation
(the
documentation may not describe all of the available error codes). Refer to the latest
version of the
firmware or documentation.
SCD A
Tape drive hardware problem. The tape drive determined that a problem occurred which
degraded
the operation of the tape drive, but it did not restrict continued use. If the problem
persists, replace
the tape drive. The drive is usable, though the single-character display continues to
indicate an
error and the status light flashes amber.
The error code may clear when you cycle power to the tape drive or place it in
maintenance mode.
SCD B
No error or message is assigned. See error code 8 in this table.
SCD C
The tape drive needs to be cleaned. Clean the tape drive. See the section about
cleaning drives in
the IBM TotalStorage Ultrium Scalable Tape Library 3583 Setup and Operator Guide.
The error code clears when you clean the tape drive or place it in maintenance mode.
d Fibre Channel AL_PA conflict. More than one device has the same address. Each
device must
have its own unique AL_PA address. See the section about setting Loop IDs in the IBM
TotalStorage Ultrium Scalable Tape Library 3583 Setup and Operator Guide.
SCD D
No error or message assigned. See error code in this table.
2024年11月6日发(作者：须艳丽)
IBM磁带机及磁带库日常工作手册
第一章：日常基本问题的处理 .......................................................................................................... 3
磁带卡在磁带机里不能够弹出： .............................................................................................. 3
磁带有关的故障： ...................................................................................................................... 4
磁带机读/写有关的故障： ......................................................................................................... 5
磁带机和主机连接的问题： ...................................................................................................... 5
第二章：磁带机（库）相关的信息： .............................................................................................. 8
LTO和3592磁带机最新的微码信息： ................................................................................... 8
LTO磁带机的数字信息（SCD code） ..................................................................................... 8
3580磁带机（TS22x0、TS23x0） ........................................................................................... 9
3581磁带库（L13、H13、L17、H17、L23、L23） ............................................................. 9
3581 2U磁带库（L28、L38、L3H、F28、F38、F3H） ..................................................... 10
3583磁带库 ............................................................................................................................... 11
3584磁带库 ............................................................................................................................... 12
3573 LTO磁带库（TS3100、TS3200） ................................................................................. 13
3576 LTO 磁带库（TS3310） ................................................................................................. 13
3590 磁带驱动器（Bxx、Exx、Hxx） .................................................................................. 14
第三章：相关数据的收集 ................................................................................................................ 17
附录A：LTO和3592磁带机微码详细信息。 .............................................................................. 18
附录B：LTO的SCD code详细说明。 ......................................................................................... 45
第一章：日常基本问题的处理
磁带卡在磁带机里不能够弹出：
1．在磁带使用之前检查磁带引导针的位置：
在新磁带使用之前，应该检查所有LTO或3592磁带的引导针。确保它在正确的位置。
如果发现其位置不正确，应该将其调整倒正确的位置（如下图）。可以使用人工卷带工具（
P/N
LTO=08L9129 3592=18P888）来调整。
具体操作步骤，可以参照《TS2340 3580 L43S43 Setup Operator Service
Guide>> GC27-2103中的第4章的：
Using Ultrium Media --
Repositioning or
Reattaching a Leader Pin
.。
<=== 正确的位置
2．检查是否主机曾经发过“PREVENT MEDIUM REMOVAL”的命令
这个命令通常是由主机端的某些应用程序发出的。如果有类似的问题，可以先从应
用程序端发出包含有“ALLOW MEDIUM REMOVAL”的命令，然后再从主机端去EJECT
磁带。如果磁带还是不能弹出来，则将磁带机重起。然后再手工方式弹出磁带。
3．当需要人工方式取出磁带机理的磁带时
当需要人工方式取出磁带机理的磁带时，根据情况使用以下的步骤：
1） 从主机端发出EJECT磁带的命令。
2） 按磁带机上的蓝色unload按钮1秒钟。
3） 按磁带机上的unload按钮15秒钟，磁带机会reset，然后再按unload按钮1秒
钟。
4） 将磁带机或磁带库下电/上电，然后再按unload按钮1秒钟。
磁带有关的故障：
1．一些磁带机进带故障和磁带的引导针的位置不正确有关系。可以参照前一节的介绍检
查和调整引导针的位置。
2．关于处理磁带问题，遵循以下的步骤：
1）尝试再另一个磁带机load/unload怀疑有问题的磁带。
2）检查磁带是否有物理的损坏。
3) 检查磁带引导针的位置是否正确。
4）如果怀疑有问题的磁带是空白的或者里面的数据不再需要的情况下，可以使用磁
带机对磁带进行诊断：
在LTO磁带机的面板上“Maintenance Mode”
drive diagnostic option '1' +
Diagnostic option 'E' (Test Cartridge & Media )
具体步骤参照《
IBM TS2340 3580-L43 S43 Gen4 Tape Drive Tape Drive
Setup, Operator, and Service Guide
》 GC27_2103 Appendix B.
Diagnostic and Maintenance Functions.
3．磁带的运输和储存：
如果客户需要储存或者运输磁带，要使用符合规定的储存箱储存和运输，参
照以下的weblink：
/support/?uid=ssg1S1001388&rs=546
符合标准的储存箱的信息参照一下的weblink：
4．LTO磁带机的兼容性：
LTO的磁带机可以读/写前一代的磁带（例如LTO4代磁带机可以读/写 LTO4和LTO3
代的磁带）。
LTO磁带及可以读前2代的磁带（例如LTO4代磁带机可以读LTO4、LTO3和LTO2
代的磁带）。
所以LTO1代的磁带是不可以在LTO4代的磁带机中使用的。
磁带机读/写有关的故障：
1． 确保磁带机的firmware是最新推荐的版本：
通过RMSS PFE的weblink查找firmware信息：
/tape//pages/opensystems
/tape//pages/codematrix
通过Internet查找firmware的信息：
/systems/support//selectproduct?brandind=500003
4&familyind=0&oldbrand=0&oldfamily=0&oldtype=0&taskind=2&psid=ap
SSR可以通过ITDT（IBM Tape Diagnostic Tool）的工具或磁带机的驱动程序的工具
在主机端进行firmware的升级。
ITDT v2.0：
不再支持
3580 GEN1 and GEN2, 3581, 3582, and 3583
/support/?rs=543&context=STCVQ6R&dc=D400&q1=
3580+firmware&uid=ssg1S4000662&loc=en_US&cs=utf-8&lang=en
ITDT v1.2：
/support/?rs=1140&context=STCXRHW&dc=D410&q1
=ssg1*&uid=ssg1S4000338&loc=en_US&cs=utf-8&lang=en
2． 隔离是否是磁带的问题：
1）尝试用磁带机load/unload，read/write一盘全新的磁带来隔离问题。
2）参照第一章中的有关磁带的问题的方法隔离问题。
3． 隔离磁带机硬件方面的问题：
1）尝试将用另一个磁带机对磁带进行读/写操作来隔离问题。
2）使用ITDT的工具进行磁带机的诊断测试。
3）尝试用磁带机（库）操作面板上的maintenance菜单进行诊断测试。
如果以上的硬件测试能够通过，证明磁带没有问题，不需要更换磁带机。
磁带机和主机连接的问题：
1． 磁带机和主机通过SCSI连接：
1）检查SCSI连接头的针和孔是否有异常，特别是68针的接头。针脚是否有过短、
弯曲等问题。
2）简化SCSI的连接方式进行测试。例如在一个SCSI的总线上只接一个磁带机。
3）检查LVD/HVD SCSI终结器（terminator），确保终结器正确地使用。
4）尝试更换SCSI电缆和SCSI的终结器来检查问题。
5）检查主机端的SCSI卡是否和磁带机兼容，或尝试更换主机端的SCSI卡来检查问
题。
6）在磁带机（库）上运行SCSI连接接口的诊断：
-运行基本的SCSI诊断
-在LTO磁带机（库）的“
Maintenance mode”下运行“Host Interface Wrap
test diagnostic”（参照《IBM TS2340 3580-L43 S43 Gen4 Tape Drive Tape Drive
Setup, Operator, and Service Guide》 GC27_2103的附录B）
7）如果已经完成了以上的诊断工作，而且更换过SCSI的电缆，运行ITDT工具的
磁带机诊断扫描操作，验证SCSI的连接是否正常。
如果完成了以上的操作，而且“Host Interface Wrap test diagnostic”是正
常的，但和主机端的连接还是有问题，不要更换更换磁带机（库）。参照以下的章节，
收集相关的数据，向上一级技术支持寻求帮助。
2． 磁带机和主机通过SAN/FC连接：
1） 简化FC的连接，尝试将由问题的磁带机（库）直接和主机进行连接。
2） 更换FC的光纤电缆。
3） 检查主机的FC卡是否设置了更长时间的timeout以适应和磁带机设备连接。
4） 检查主机端的FC卡是否和磁带机兼容，或尝试更换主机端的FC卡来检查问题。
5） 在磁带机（库）上运行FC连接接口的诊断。（方法同上）
6）
如果已经完成了以上的诊断工作，而且更换过FC的电缆，运行ITDT工具的
磁带机诊断扫描操作，验证FC的连接是否正常。
如果完成了以上的操作，而且“Host Interface Wrap test diagnostic”是正
常的，但和主机端的连接还是有问题，不要更换更换磁带机（库）。参照以下的章节，
收集相关的数据，向上一级技术支持寻求帮助。
3． AIX服务器直接连接LTO磁带机（库）重起后设备成“define”状态：
IBM的LTO3或LTO4代的磁带机（库）和AIX服务器直接连接。当服务器power
off/power on或重起后，磁带机（库）的设备rmtX和smcX不能够在设备配置中找到。
用lsdev –Cc命令查看时，没有显示或成define的状态。这时需要重新启动或power
off/power on磁带机（库），重新初始化FC连接。
4． LTO磁带库（LUN-1磁带机）连接的问题：
在绝大部分的LTO或3592的磁带中，都有机械抓手（autochanger）设备通过FC或
SCSI和主机连接。它是通过有Control Path的磁带机的LUN-1被主机识别的。当磁
带库和主机连接时，磁带机设备能正常地连接，但机械抓手设备不正常时：
如果是3581 3582 3583 3573．．．．．．的磁带库，设置成了“Sequential mode”。磁带库
则不会将LUN-1给机械抓手，让主机认到。3582 + 3581 (2U models)出厂时就是
“Random mode”，所以可以被主机认到。
所以当需要由主机来控制机械抓手时，磁带库应设置成为“Random mode”。
5． 磁带机（库）设备和磁盘设备要使用不同的FC连接：
在有SAN交换机连接的环境中，确保磁带机（库）设备和磁盘设备没有共享一块FC
卡。
对于磁带机（库）和磁盘设备的连接，FC和SCSI卡会有包括timeout值在内的不同
的参数设置。如果共享，这个参数设置通常对磁带机（库）和磁盘的访问都会产生问
题。
6． 多个主机连接访问同一个磁带机：
对于多个主机连接访问同一个磁带机，如果他们通过SAN交换机连接，而且在同一
个ZONE里，会产生问题：
如果多个主机在同一个zone里面，当其中一个主机重起时，它会发起一个“IOINIT”
的操作。会使得整个ＨＢＡ的总线reset。而位于整个总线上的设备对于reset会有不
同的反应。磁带机中如果有磁带，当收到这个reset时，会执行一个倒带（rewind）
操作。无论此时磁带机在作什么操作此时都会中止。因为reset是更高级别的命令。
如果此时另一个连接此磁带机的主机正在对磁带进行读/写操作，这个主机不会收到
倒带的信息。当磁带倒到开始时，它会继续从磁带的开始部位进行读/写操作。这样
将会导致数据的丢失。
7． iSeries主机不能识别TS3310的磁带库：
当3576磁带库power off时，和iSeries主机连接的IOP将会被reset。为了保证3576
能被正常地使用，当iSeries主机的IOP要reset时，确保3576是power on的状态。
8． Xseries Configuration and Option Guide (COG)
Xseries Configuration and Option Guide (COG)里面可以查到和xSeries主机兼容的磁带
机（库）的信息：
/systems/xbc/cog/
System Storage InterOperationCenter （SSIC）
System Storage InterOperationCenter （SSIC）里面可以查到所有IBM的存储产品的兼
容性信息：
/systems/support/storage/config/ssic/
s?start_over=yes,
第二章：磁带机（库）相关的信息：
LTO和3592磁带机最新的微码信息：
3592-E06 GEN3 ----- D3I2_47E
3592 E05 GEN2 ----- D3I1_DA0
3592 J1A GEN1 ----- D3I0_C90
LTO4 GEN4 ----- 85V8
LTO3 GEN3 ----- 85P1
LTO2 GEN2 ----- 73V1
LTO1 GEN1 ----- 5AU1
所有最新的LTO的微码可以在以下的weblink查找下载：
/servers/storage/support/lto/
关于所有微码版本的信息参照附录A。
LTO磁带机的数字信息（SCD code）
0：没有错误，不需要干预
1：散热问题
2：电源问题
3：微码相关的问题
4：需要收集磁带机的DUMP
5：磁带机的硬件问题
6：磁带机或则磁带介质问题
7：磁带介质问题
8：磁带机或SCSI总线问题
9：磁带机或LDI（RS-422）通讯问题
o、c、b、h：保留
A：磁带机的硬件问题
B：保留
C：磁带机需要清洗
D：保留
详细的SCD code描述及相应的action参照附录B。
3580磁带机（TS22x0、TS23x0）
1． 确保3580的微码是最新的版本：
通过IBM的RMSS weblink查找：
/tape//pages/opensystems
/tape//pages/codematrix
通过Intranet或Internet下载3580的微码：
/systems/support//selectproduct?brandind=50
00034&familyind=0&oldbrand=0&oldfamily=0&oldtype=0&taskind=2&psid=ap
/tape//pages/3580page00
/support/?rs=543&context=STCVQ6R&dc=D400
&q1=3580+firmware&uid=ssg1S4000055&loc=en_US&cs=utf-8&lang=en
2． 通过使用ITDT的工具测试诊断和相应的微码升级工作
ITDT工具的下载和使用参照前一章节。
3． 隔离是否是由于磁带的故障导致的问题：
参照第一章的有关磁带的故障诊断方法。
4． 隔离是否是磁带机硬件的故障
尝试对同一盘磁带在其他的磁带机上进行读/写操作。
5． 对磁带机做基本的诊断：
使用ITDT工具进行诊断
使用磁带机操作面板上的“Maintenance Mode”进行诊断：
'Maintenance mode' drive diagnostics option '1' + Diagnostic option 'H' (Head
Test)
参照《IBM TS2340 3580-L43 S43 Gen4 Tape Drive Tape Drive Setup, Operator,
and Service Guide》 GC27_2103 Appendix B. Diagnostic and Maintenance
Functions.
如果诊断测试是通过的，而故障依然存在，这时不要马上更换磁带机，请向你
的上一级技术支持（CAG或TSG）寻求帮助。同时收集相应得数据。
3581磁带库（L13、H13、L17、H17、L23、L23）
1. 3581 LVD磁带库L13、L17、L23不能够上电的故障：
检查LVD的terminator （P/N 19P0481）是否正确地安装了。
如果3581的磁带库没有正确地安装terminator，当上电的时候，操作面板上会
显示'LdR INIT'。而系统不会进行自检操作。
2. 3581 LVD HVD磁带库 x13、x17、x23弹簧故障：
某些3581磁带库德弹簧系统会发生故障。这时不要更换整个磁带库。可是根据ECA017
订购EC备件（发邮件给
MPCECPOC/Australia/IBM，提供客户信息，ECA017信息，
H28058 B/M18P6885）参照HSF tips H177257。或者直接定备件18P6885）
3. 检查并确认3581磁带库德微码是最新推荐使用的版本：
1） 通过一下网址查找相关信息：
/tape//pages/opensystems
/tape//pages/codematrix
2） 3581磁带库德微码下载网址：
/tape//pages/3581page00
/support/?rs=541&context=STCVQ6N&dc
=D420&uid=ssg1S4000042&loc=en_US&cs=utf-8&lang=en
4. 使用ITDT工具进行诊断和微码升级
5. 隔离是否是由于磁带的故障导致的问题：
参照第一章的有关磁带的故障诊断方法。
6. 隔离是否是磁带机硬件的故障
尝试对同一盘磁带在其他的磁带机上进行读/写操作。
7. 对磁带机做基本的诊断：
使用ITDT工具进行诊断
使用磁带机操作面板上的"Maintenance Mode"进行诊断：
'Maintenance mode' drive diagnostics option '1' + Diagnostic option 'H' (Head
Test)。SSR must reach inside 3581 enclosure to see the (Black) unload button.
Open the Autoloader door and remove any cartridges from the front slots.
With a flashlight and a pencil, press the Unload button on the drive face plate with
the eraser end of the pencil. The round Unload button is located near the base of the
drive in the second grid from the right (facing the drive). The Unload button is
directly under the right cartridge guide of the loader opening near the base of the
drive.
如果诊断测试是通过的，而故障依然存在，这时不要马上更换磁带机，请向你
的上一级技术支持（CAG或TSG）寻求帮助。同时收集相应得数据。
3581 2U磁带库（L28、L38、L3H、F28、F38、F3H）
1. 3581 2U磁带库（L28、L38、L3H、F28、F38、F3H）磁带机故障A9 39：
在3581 2U磁带库上电的过程中通常会报A9 39的故障。
原因：
The lock block sensor is set on the drive, (tripped lock block) Drive
incorrectly appears as if there is a tape loaded. This is usually found on a new
installation, or a new FRU that has been treated a little rough in transit. The drives
loader Assm is shaken backwards a little tripping the lock block sensor.
解决方案：
Install latest (minimum level 2.20) Library code. Then run the Drive Calibrate
Test under Drive Diagnostics. This test will have you insert a scratch tape, it will try
to load the tape in the drive and fail (probably with 94 74 error), but when the tape is
extracted from the drive, it will reset the lock block sensor and on the retry it will
work.
2. 检查并确认3581磁带库德微码是最新推荐使用的版本：
/tape//pages/opensystems
/tape//pages/codematrix
/systems/support//selectproduct?brandind=50
00034&familyind=0&oldbrand=0&oldfamily=0&oldtype=0&taskind=2&psid=ap
/tape//pages/3581-2u
3. 使用ITDT工具进行诊断和微码升级
4. 隔离是否是由于磁带的故障导致的问题：
参照第一章的有关磁带的故障诊断方法。
5. 隔离是否是磁带机硬件的故障
尝试对同一盘磁带在其他的磁带机上进行读/写操作。
6. 对磁带机做基本的诊断：
使用ITDT工具进行诊断
如果诊断测试是通过的，而故障依然存在，这时不要马上更换磁带机，请向你的上
一级技术支持（CAG或TSG）寻求帮助。同时收集相应得数据。
3583磁带库
1. 3583 picker 故障（SAC 73、7C、81、82．．．．．．）
1) Library, drive, RMU and SDG F/W should be at the latest level.
2) Aug 2008 => Have a PFE version of Library code
- 6.11.0001 for Multipath
- 3.42.0002 for Non-Multipath ==> Picker powers down after 10 minutes
of inactivity , On the first Library motion command, picker powers back up
and continues with the command request
3) Check that all 3583 magazine '6-packs' are revision B -> P/N 19P4529
magazines, Revision A or B is printed on rear magazines. Remove each mag
and check that "Rev-B" should be stamped on rear of each magazine. Please
check to see if ground wire is connected between picker control board and frame.
Please try to manually PUT and GET customer's cartridges from all slots.
4) If you have picker GET failure from LTO-1 drive, please install drive clips 3584
ECA009. (Retain tip H021381, P/N 18P7835 )
5) ASAP Collect library log data. Monitor> SHOWPOS to see if the exact slot/s
having issues can be identified. Also collect >PERR and >PLOG
6) Remove top cover from 3583 to carefully observe picker movements and actions
following a door open/closed operation. Use the 3583 MI Chapter 9. "Service
Procedures" section 'Observing Library Robotics' for reference details.
7) Check Y-axis for any binds by moving it up and down. The binding can be
between picker assembly and Y shaft. If any binds exist, replace appropriate
FRU. Repeat SAC 81 ?? Replace Y-axis motor assembly. Replace
power distribution board. Replace Y-axis drive belt.
8) If SAC 73 or picker finger issues are suspected, then from the SAC 73 section of
the MI .. " Run Grip finger diagnostics (Main Menu —>More —>Service
—>Library —>Diags —>Fingers —>Step —>Open/Close): Only if diagnostic
failed: replace Picker Carriage Assembly P/N 18P7450. If diagnostic passed,
retry it several times. If it fails during successive retries or if intermittent failures
continue to occur during normal operations, replace the Picker Carriage
Assembly P/N 18P7450. Always replace "Picker Carriage Arm Assm" (not
just picker - but the 'Picker Carriage Assembly' this includes picker + board +
carrier bearing .. - part number 18P7450)
9) 3583 S/N prior to 78-16127. SAC 73 00 or 81 00 if a PUT or GET failure
occurs at column 4 and/or 5, please install column magazine spacer kit
10) To reproduce the failure or verify the fix, please remove 3583 top cover & run a
long DEMO test from the 3583 operator panel. Use the 3583 MI Chapter 9.
"Service Procedures" section 'Observing Library Robotics' for reference details
11) Run “>unlearn" and then “>calibrate 300" from library serial port, Follow
command line 'calibrate 300' support procedure ; Error still occurring -
replace Y-axis motor and belt ; Replace Picker Carriage ASSM - part
number 18P7450.
12) If the situation is critical, Install laptop on back of 3583 and run a command line
'library trace' with session capture from 3583 serial. This may need to run for
days/weeks to trace a failure event.
2. 检查并确认3581磁带库德微码是最新推荐使用的版本：
Multipath /tape//pages/3583Mpath
Singlepath /tape//pages/3583Spath
3. 使用ITDT工具进行诊断和微码升级
4. 隔离是否是由于磁带的故障导致的问题：
参照第一章的有关磁带的故障诊断方法。
5. 隔离是否是磁带机硬件的故障
尝试对同一盘磁带在其他的磁带机上进行读/写操作。
6. 对磁带机做基本的诊断：
使用ITDT工具进行诊断
如果诊断测试是通过的，而故障依然存在，这时不要马上更换磁带机，请向你的上
一级技术支持（CAG或TSG）寻求帮助。同时收集相应得数据。
3584磁带库
1. 3584磁带库的Universal Gripper Assembly如果没有物理上的顺坏，不需要更换：
Library Firmware should be updated + potential library re-calibratrion prior to any
non damaged gripper replacement. The library code should get updated along with
any damaged Gripper replacement.
ALMS libraries - a minimum library code level of 8150 should be installed to resolve
gripper reliability & collision detection.
Libraries with ALMS feature disabled - a minimum library code level of 7363
should be installed to resolve gripper reliability & collision detection
2.
3573 LTO磁带库（TS3100、TS3200）
1. 6．70版本的微码能够解决以太网和磁带hung的问题。
2. 2008年4季度的微码将解决和多关于磁带加密的问题。
3. 确保3573的微码是最新的版本：
通过IBM的RMSS weblink查找：
/tape//pages/opensystems
/tape//pages/codematrix
通过Intranet或Internet下载3573的微码：
/systems/support//selectproduct?brandind=5
000034&familyind=0&oldbrand=0&oldfamily=0&oldtype=0&taskind=2&psid=ap
/support/?rs=1154&context=STCZU45&dc=D4
20&uid=ssg1S4000497&loc=en_US&cs=utf-8&lang=en
4. 通过使用ITDT的工具测试诊断和相应的微码升级工作
ITDT工具的下载和使用参照前一章节。
5. 隔离是否是由于磁带的故障导致的问题：
参照第一章的有关磁带的故障诊断方法。
6. 隔离是否是磁带机硬件的故障
尝试对同一盘磁带在其他的磁带机上进行读/写操作。
7. 3573基本数据收集：
LCD: Error Code details
From Eth Web interface :
Service Library -> view logs
Service Library -> view drive logs
Service Library -> save drive dump
On a 3573 there is no WEB / GUI library log collection tool for the client. They
have to telnet into the 3573 and run the FLMON> DPA command and collect CLI
output from the
3576 LTO 磁带库（TS3310）
1. 使用500G和82F0的微码版本，可以解决很多加密和磁带机相关的问题。
2. 确保3576的微码是最新的版本：
通过IBM的RMSS weblink查找：
/tape//pages/opensystems
/tape//pages/codematrix
通过Intranet或Internet下载3580的微码：
/systems/support//selectproduct?brandind=5
000034&familyind=0&oldbrand=0&oldfamily=0&oldtype=0&taskind=2&psid=ap
/support/?rs=1140&context=STCXRHW&dc=D
420&q1=ssg1*&uid=ssg1S4000445&loc=en_US&cs=utf-8&lang=en
3. 3576磁带机清洗所产生的问题：ASC/ASCQ 3BA0
禁止使用有
CLNxxxL1标签的清洗带在LTO4的磁带机中使用。
如果需要清洗，使用没有L1标签的“universal cleaning cartridge”进行
清洗。可以使用CLNxxxL4或CLNxxx的清洗带清洗。
4. 3576磁带库不能在iSeries的主机上被识别：
参照第一章的四、7节
5. 3576 L5B报T020、T007、T083的错误：
3576磁带库在校准I/O station（0，6 location）时，报T007、T083的错误。
原因：The Picker Locking mechanism (slide The Picker Locking mechanism
(slide out metal lever) was left sticking out in the aisle.
3590 磁带驱动器（Bxx、Exx、Hxx）
1. 3590磁带机最新推荐的微码版本：
3590-Hxx and 3590 Exx and Common cardpack F_2FB
3590-Bxx
non
Ultra SCSI cardpack A_593
3590-Bxx Ultra SCSI cardpack B_93C
2. 更换HGA的问题：
在任何更换HGA之前请先更换HGA brush或作extended clean HGA。
更换下来的退旧的备件请将新备件上桔黄色的磁头保护的夹子夹到退旧的备
件上，同时，所有的电缆请保护好。这样更换下来的备件可以被维修后再次被
使用。
3. 如何做extended clean：
在3590的操作面板上将磁带机置于“
CE offline”的模式。
Select 'Config/Install' - Select 'DRV' Options - Select 'Enab
Extended Cln' - "Wrench" to back out to 'Operator' mode. The next
cleaning cartridge - and ONLY the next cleaning cartridge - loaded on the
drive elected to perform an extended cleaning will run for about 50-80
minutes without unloading.
4. 读/写错误，FID F6，FSC 7038报错信息。
产生读/写错误的原因通常是由于HGA brush顺坏、没有按时清洗磁带机和
没有按时PM所导致。最新的3590的微码将磁带机的清洗时间间隔有300GB
减少到150GB。FSC7036是由于磁带机的使用而需要清洗。FSC7038是由于读
/写错误而要求清洗。
1) Upgrade code to F_2FB or B_93C or A_593
2) Review the drive error logs from the 3590 drive Operator panel,
list down all FID/FSC's, clear the error logs.
3) Use lint free gloves when PM-ing 3590 drives - P/N 0461621, do
not touch the tape path with bare hands, even if they are clean.
4) Replace HGA brush assembly P/N 35L1569.
5) Check brush has a firm and level contact with 3590 HGA
6) Whilst the cleaning arm is removed for brush replacement, clean
the tape path with slightly water moistened lint free cloth. I
would recommend leaving the tape guides in place as removing and
replacing them can damage the HGA if your not very careful.
Cleaning of the two HGA 'D' air bearings can still be done with
these guides in place. Also clean the inside of the Machine reel
hub, the tension transducer, decoupler ...
7) Do not touch the surface of actual HGA head with the cleaning
cloth.
8) Run a normal Clean tape mount twice. Use account SSR cleaning
tape or new cleaning tape ! Ensure the usage dots on top of the
SSR Cleaner tape are filled in with each use, we must ensure that
at least the SSRs clean cart is doing a good job. Clean cart P/N
05H7540.
9) Check for visible debris on HGA, do not remove - allow Extended
clean to remove any debris
10) Use the 3590 drive MI procedure for FID D4 and do all of the
documented steps including operator panel FRU replace menu -
'Tape Path Repaired'' to clear the SARS and then the 'End Call'
procedure
11) Use 3590 MI to run Vacuum check/adjustment " Measurement and
Adjustment of Pneumatic System "
12) After completing Pneumatic system use the mounted CE cart (known
good media hopefully) to run drive R/W diagnostics. If the client
used 'K' tape you should use a 'K' tape for the Read/Write
diagnostic
13) Listen for noisy file reel and machine reel motors whilst running
above diagnostic. Replace motors if noisy - do not replace HGA
at this point!
14) If diagnostic fails, run an Extended clean as per MI. - details
also below. Note this will take 50-60 minutes to run
15) Review the drive error logs from the drive Operator panel, list
down all FID/FSC's, action all FID/FSC's listed
16) Clear the error logs once all FID's have been resolved and any
additional diagnostics have been run successfully
17) Run 3590 diagnostic ; Fix Verify - Test Head Using know
good 3590 media See details below
18) If HGA diagnostic still fails check again for visible debris on
HGA, gently manually clean off with another HGA brush using
up/down motion ONLY. If debris is still not moving moisten HGA
brush with clean water and carefully brush with same up/down
motion. Do NOT use isopropyl alcohol or other solvents - these
will dissolve the head materials.
19) Run another extended clean if debris was detected and removed
20) Re-run 3590 diag - Fix Verify - Test Head Using know good
3590 media
21) Whilst unloading the tape used above review the drive error logs
from the drive Operator panel, action all FID/FSC's listed
22) Clear the error logs once all FID's have been resolved and any
additional diagnostics have been run successfully
23) Replace drive covers carefully.
第三章：相关数据的收集
在前面的章节已经提到。当遇到读/写或其它与磁带机相关的问题时，已经做过诸如ITDT等
测试，而且测试是通过的，但问题依然存在。这时不要马上更换磁带机，请向你的上一级技
术支持（CAG或TSG）寻求帮助。
在寻求帮助的时候，因该做好以下的工作：
1． 详细地描述问题的现象。做过哪些诊断测试工作，详细地步骤和结果如何。
2． 主机上的相应的配置和错误信息。如AIX系统得snapshot，Windows的event log．．．．．．
3．
收集详细的磁带机（库）的service
Reference Codes。例如磁带库的SCSI/FSCSI Sense
Key + ASC/ASCQ + HEC/HECQ … 磁带机的FSC, FID, SCSI/FSCSI Sense Key +
ASC/ASCQ…
4． 系统环境的描述。包括所连接的主机类型，磁带机（库）的配置，所使用的备份软件及版
本，SAN配置情况．．．．．．
5． 磁带机（库）的微码版本，主机驱动程序类型和版本。
6． 磁带机（库）的error log、磁带机的DUMP。可以使用ITDT-SE、ITDT0-XD或cetool收
集。
附录A：LTO和3592磁带机微码详细信息。
1． 3592-E06：
1. Support 3592 E06 drives in all configurations
- 3494, 3584, 3577, and Silo libraries
- tabletop or rackmount
- CU, Hydra, or open system attach
2． 3592-E05：
3592 E05 D3I1_DA0
Summary list of major enhancements and fixes:
1. Support recognition and tape reformat from E06 to E05
3592 E05 D3I1_D16
Summary list of major enhancements and fixes:
1. Prevent FSC D12E errors due to CSP update of brick s/n
2. Support the # character when using Internal Label Encryption mode
3592 E05 D3I1_D15
Fixes encryption authentication failures on CSP drives running D3I1_D12 code
3592 E05 D3I1_D12
Summary list of major enhancements and fixes:
1. Additional FIPS Crypto support features
a. Generate GCM IV per NIST 800-38D
b. Indicate FIPS mode to controller and library interfaces
2. Prevent false call homes from incorrect FID on FSC 5066 errors
3. Additional rolling calibration changes
a. Improved ERP handling of write or read temp error bursts
b. Fix more cases of FSC 6017 caused by ERPs during Locate/Space commands
4. Add a slow speed retry during read ERPs
5. Fixes the 'zero key for all records' problem for TSM AME configurations
Detailed list of all changes/fixes:
3088 6017: Extend upif timeout for Space request to 45 minutes
3109 ETH: Disable Link LED on old DCJ cards
3058.1 CRYPTO: Fix infinite EKM failure retry loop
3124 SARS: Support send diag to clear HSARS
3126 NEW: Read redrive FSC4601 (C2 miscorrect EM)
3156 Unexpected POR (op panel interrupt panic)
23218 J2: Create new release for J2 PGA7
23220 J2: Fix Load for deck test
23303 J2: MED: Reduce FSC 5020 temp error
22608 Write filemark failed running Sctape fsc 6000
23355 Add thermal sensor diag on POST
23396 J1,2: change page id for tape directory page on reformat
23401 Add CHN_HW_CALIB_READ_OP command
23416 Raise off-bias to 5mA when tape unloaded
23425 Change FID for 5066 to 86 from 83
23427 J1/J2: Add Drh_Change_Tape_Dir_Format
23406 RABF(80840000-Otr): UNEXP_PERM (1318s)
23426 MED: Try another velocity in read ERP
23452 RW:default- 0933 JBD254JB 9712
23531 Split CALIB_ROLL into CALIB_ROLLW & CALIB_ROLLR cal reasons
23463.5 Connect CALIB_ROLLR, CALIB_ROLLW to rolling calib invocations
23532 J1-FIELD 970D/4601
3224 NEW: Add FIPS flag to library msgs (FCR 3154)
3592 E05 D3I1_C93
Summary list of major enhancements and fixes:
1. Add slow speed read ERP step
2. Fix RABF degraded writing problem
3592 E05 D3I1_C91
EC Contents:
Summary list of major enhancements and fixes:
1. Rolling calibration phase 2 changes
a. Improved ERP handling of write or read temp error bursts
b. Fix some cases of FSC 6017 caused by ERPs during Locate/Space commands
c. Fix some cases of FSC 5066 read perms
d. Add max C2 correction as rolling cal option
2. Fix false Write Protect error caused by load retry
Detailed list of all changes/fixes:
2755.9 CRYPTO: FIPS: support algorithm cert vectors
2968 EVT-J2: FSC D133 ( crypto fail test automatic )
2755.10 CRYPTO: More FIPS cert vector work
2971 WRONG: LDI SCSI_ABORT does not send a response
2967 HANG: Some errors (9711) can cause cmd hangs
2978 CRYPTO: Handle perm during rekey correctly
2979 CAM:tc-3777 0636 J11435 5070
2981 WRONG: CM page table needs to cross-reference actual page
2755.12 CRYPTO: FIPS: Insure initial PRNG Xkey!=Xseed
2755.13 CRYPTO: FIPS: Disable data output on failure
2901 RABF(44010000-Rd2): TIMEOUT (1003s)
2967.1 HANG: Some errors (9711) hang write cmds
3046 PANEL: Fix hole in panel reset debounce
3053 ADI - fix sense data masking after unload error
2954.1 FIBRE: Independent write/read burst sizes
3088 6017: Extend upif timeout for Space request to 45 minutes
22902 J2-EVT: FSC8C00 ( STA_Update_CM() returned 5 )
22914 J1J2:Create new release for J1P12 and J2P6
22940 J2 Field: Slow performance (PMH 20038-660-706)
22944 J2: FSC4600 is returned due to unexpected encryption mod exit
22698 LocShortTypical (346s) WRITE_PERM
22922 RWEodTypical (50646s) READ_PERM
23048 MED: Reduce velo logging in cal trigger log
23050 J2 FIELD FSC 5051 EOT encountered during write
23085 MED: J2: Add new debug command for ERP history
23102 Program INDY voltage based on data rate
23110 MED: Some 7834/5834 ERPs are wrongly triggered
23113 MED: Rolling calib Phase 2
23124 MED: Rolling calib Phase 2
23127 J2: Ingore sticky velocity setting in constant vel mode
22794 WORM:Fail-safe for invalid OPP updating
22982 J1 FIELD 83 5066 0000 2A0F
23168 J2: MED: Fix Build Break
23172 SRV: Disable stepper at POR explicitly
23185 J1/J2: append error is returned by write perm@ABF on WORM
23042 Handle CHN_ErrorInject better in CAL and adaptive settings
23126.1 Rolling Calib Phase 2-existing logic fixes and enhancements
23179 LocLongTypical (7089s) TIMEOUT-10 (old tape, FFP=2368)
23212 RWShortAggressive (1126s) TIMEOUT-08
23126.1 Rolling Calib Phase 2-existing logic fixes and enhancements
23126.2 MED review changes added to base rolling phase 2 work
23126.3 Correct for dsnum corruption during write rolling cali
23227 LocMediumFixed (2399s) READ_PERM
23126.4 Fix loop index problem
23126.6 Rolling calib fix: last-best-option not held at EOW if burst
3592 E05 D3I1_C15
Summary list of major enhancements and fixes:
1. Support LME (library managed encryption) method in 3494 libraries
2. Improve fibre channel transmit signal quality (jitter fix)
3. Drive diagnostic improvements (use correct pattern)
4. Fix write inhibit problem with multi-volume Worm tape application
5. Set Media Life TapeAlert based on lifetime bytes processed
6. ERP enhancements for read interchange problems and long mounts (rolling
calibration changes)
3592 E05 D3I1_B25
Summary list of major enhancements and fixes:
1. FCR 3095 - Support for T10/SSC-3 Encryption method
2. Implementation of required functions for FIPS certification
3. FCR 3118 - Support immediate command termination for Long Erase command
4. Support locate past EOD (convert to linear read)
5. Clear DUC on retry of load error
6. Fix for No Response msgs during clean cycle
7. FCR 3129 - Allow library to clear Flash dump
8. Improvements to Read error recovery procedures aka "slow read/long recall"
Detailed list of all changes/fixes:
21831 FSC 7265 on Write
21858 perm 7282 read error
2738 JAG-1 FIELD DUC not handled by as400
21834 Jag2E: EOD detected is returned instead of FM detected
21762 EVT: FSC6353/7537 on Space EOD
21555 FSC 5475 Cannot get LPOS
21664 BENCH:TDRV 0012 JBC160JB B340 J2E FID 85 B340 029E
21469 Cartridge appears "stuck" due to long CM retries
2659 F016: Double message received caused F016
2662 Bench: FSC 9999 Check_1 w A16
2640 F00B w 942 code
2845 Jag2-Field 9713 28410,442
22257 58B0 Srv over rotation at stop
22263 CAM:tc-10566 3007 JBX076 5475
22291 RVT: FID1 E5 6017 0000 when running host jobs
22352 Jag2: do not write J1 format with speed1 on all of J2 drive
2838 JAG1-Field: Not reporting error (SRR's)
22117 Jag2-Field 6017 1_A27 22337,122
2817 RAS: Make Key Path Config menu options like library options
22176 Jag2: Disable write speed1 on J1 format for specific J2 drives
22099 4353: HS locate to EOT w est LPOS
2800 F027 Check_1 A38 Code
22094 JAG2-FIELD: FSC 4022/970D
22145 JAG: Change cleaning tape speed to 6mps
18484 Speed matching performance
22101 EOD entry of HRTD is cleared before unload
21920 Perm 58B5
21905 J2E: Enhance feature bits for recovered eHKDS
2771 CRYPTO: Simplify zero key transition rules
21989 J2: Disable Speed6 for JB Cartridge
2853 FC Jitter fix: Change Pre-Emphasis Level to 0 (22399)
22438 Revert to previous PLL settings for JA media
2881 Fix F027 Chk_1 w B1D code (break in 2830)
2884 BUILD: Official rj070509a
2876 CRYPTO: PRNG is not connected correctly
2838.2 SARS: temporarily remove SRR FID F5
2883 Fix breakage of Get VPD cmds
3592 E05 D3I1_A38
EC Contents:
Summary list of major enhancements and fixes:
1. Support attachment of the TS3400 (3577 autoloader) for the 3592 tape drive
Detailed list of all changes/fixes:
2639.3 NEW: More ITD changes for 3577 library
2756 CAM:Oracle:Mode Pagex25 Encrypt bits incrctly set to changeable
2759 NEW: Pass all Write buffers to the library
2760 CryRWMediumAggressive (1354s) READ_PERM
2761 BENCH:/gsa/tuc 0909 JJX199JJ 0000 J2N
3592 E05 D3I1_A33
EC Contents:
Summary list of major enhancements and fixes:
1. EEDK writing performance improvement (improve time to 'Ready' for encryption
scenarios)
2. Improved PES acquire method
3. Miscellaneous field problem fixes
Detailed list of changes/fixes:
21664 FID 85 B340 029E
21761 Motor stuck check trace is logged more than expected.
21792 Support new format of Physical Position of
21822 Loosen tape slack detection threshold
21834 Jag2E: EOD detected is returned instead of FM detected
3592 E05 D3I1_A27
EC Contents:
Summary list of major enhancements and fixes:
1. Fix sequence problem with SRR during RES command
3592 E05 D3I1_A21 What’s Fixed
EC Contents:
Summary list of major enhancements and fixes:
1. Support new extended length JB/JX cartridge types
2. Support Encryption Pool ID method
3. HSARS Quick Check
4. Miscellaneous field problem fixes
Detailed list of changes/fixes:
2631 HSARS Quick Check
19712 7A00 loses segment-reusable flag after sns xfr
2591 FSC9712 on write
2541 Fail when library sends message out of order
2513.1 Indicate emulation model on icon
20728 Cartridge initialize fail
20735 J2E: MED: Check EncryptionFlags of EOD, FID and [se]HKDS on rea
20531 Jag2: Add new FSC 4702(WRITE_APPEND_ALL_EHKDS_INVALID)
2662 FSC 9999 Check_1 w A16
21328 5064 is reported on unload in NULL err-inj.
2659 Double message received caused F016
2654 Dump flag clears on reading descriptor data
21430 J2E: MED: Report inconsistency between CM and eHKDS
21441 FSC 4353 on A0B code
21534 FSC 4410 - Buffer Empty
3592 E05 D3I1_942
EC Contents:
Summary list of major enhancements and fixes:
1. Support these tape encryption methods
- SME (system managed encryption)
- LME (library managed encryption)
2. Miscellaneous field problem fixes
3592 E05 D3I1_733
Detailed track list of changes/fixes:
2352 9999-C00C: Fix hang in port switch w/Ayame
2389 F016: Report error w/FID for no BVPD in 3584
2394 Change DLR_MAX_PARM_SIZE to multiple of 4
2425 FCR 3090 - Cross EOD setting
19399 E5 6017 (CM read)
3592 E05 D3I1_72E
EC Contents:
Summary list of major enhancements and fixes:
1. Important field problem fixes
a. Fixes for correctly setting and clearing TapeAlert 18
c. Fix problem where code info header can be corrupted in dumps
d. Fix problem when ATS received before FCP_CONF (could cause hang)
2. FCR's and other functional changes
a. FCR 3026 - LDI Get-Set Behavior (Baud Rate)
b. FCR 3026 - LDI Get-Set Behavior (Emulation Mode)
c. FCR 3062 - LDI SCSI Commands
d. FCR 3065 - LDI Pause Command
e. FCR 3066 - Force ERP (TM Portion)
f. FCR 3068 - LDI Supported Features
g. FCR 3076 - Allow LogSense to be forwarded to LIB when Not Ready
h. Support J1A emulation control from the 3584 library interface
i. Correct problem with Auto(NL) configs to L-Port instead of N-Port
Detailed list of changes/fixes:
2134 NEW: always report E05 to 3584 on E05 drives
2131 9999-A101: String Search integrity check during error
2183 JAG1-FIELD: F008-2707 Chk1
19032 JAG2: FSC4700 after NULL DS failure
19049 E5 970C
19104 JAG1 FIELD E5 6017 and 970C multiple accounts
19207 JAG2: 9702 0003
19243 Split 5060 into 2 fsc's, add flag data
3592 E05 D3I1_6E1
Summary list of major enhancements and fixes:
1. Support J1A Static Emulation
2. Prevent incorrect FRU replacement of Jag1 drive with Jag2
3. Improvements to ERPs when reading Jag1 format
4. Miscellaneous problem fixes
Detailed list of changes/fixes:
Fix problem with default density panel select
Interface for emulation and density controls
always report E05 to 3584 on E05 drives
Reject serial num update if drv model different
Allow selection of FRU Jag2 when emulating Jag1
Fix missing cases of emulated Jag1 FRU cases
FSC 5012 on write,read,rabf
Treat fsc 5800 as non-fatal and cause ERP
3． 3592-J1A：
3592 J1A D3I0_C90
Summary list of major enhancements and fixes:
1. Support recognition and tape reformat from E06 to J1A
2. Rolling Cal Phase 3 changes
a. Additional ERP improvements for write or read temp error bursts
3. More slow speed retries during read ERPs
4. Improved spd1 writing evaluation during diag routines
Detailed list of all changes/fixes:
3171 BUILD: Use unique link space for j1PGA14
3174 FIBRE: hung, transfer permission held by MC
3177 BUILD: Official e080116e
3179 DIAG: rcv diag results Engineering (xE001)
3165.1 Move AF/AE workaround to support debug
3188 HANG: Fix hole in uPIF critical logic
3140 WRONG: need to reset baud rate when go interface down
3195 BUILD: Official e080130e
2927 Support ISOCM/DSOCM (performance)
3236 PANEL: Fix date/time formatting for logs
3300 Hung drive after write perm after turbo SRRs
23592 SRR recovery fails with FSC7070
23608 MED: Change DSS cal log for better FA
22660 FID is not re-write when FMR cartridge is created
23903 CAM:tc-1317 6703 JBA179 5060
23501 LocMediumTypical (1644s) OTHER_PERM (old tape, FFP=665)
23911 6017 error, a buffer image was taken.
23646 Rolling Calib Phase 3 Changes
24001 MED: Repeat slow speed ERP to recover intermittent c2 unco
3346 Modify diag evaluation for new J1 Diag
23614 Dataset transfer cntr on Log Page 38 not updated on temp
24058 New Diag Test for Poor Speed1 Write Drive
24390 CryRWMediumTypical (911s) WRITE_PROT
3592 J1A D3I0_C0D
Summary list of major enhancements and fixes:
1. Fix false FSC 3820 diagnostic errors
2. Prevent false call homes from incorrect FID on FSC 5066 errors
3. Additional rolling calibration changes
a. Improved ERP handling of write or read temp error bursts
b. Fix more cases of FSC 6017 caused by ERPs during Locate/Space commands
4. Add a slow speed retry during read ERPs
5. Fix repeated FSC 8C00 errors following FSC 8E19
Detailed list of all changes/fixes:
3124 SARS: Support send diag to clear HSARS
2818.4 RAS: Fix false FSC 3820 from diag threshold scaling
3126 NEW: Read redrive FSC4601 (C2 miscorrect EM)
3156 Unexpected POR (op panel interrupt panic)
23233 J1: Create the new release for J1 PGA13
23284 MED: minor fix in trace
23126.7 Streaming DSS Capture problems cause DSS failure in rolling cal
23300 MED: RABF cycle clears CQ hist buff unexpectedly
23296 J3: MED: Retention History Page in sHKDS support
22608 Write filemark failed running Sctape fsc 6000
23355 Add thermal sensor diag on POST
23383 MED: Reduce J1 ROM size
23396 J1,2: change page id for tape directory page on reformat
23425 Change FID for 5066 to 86 from 83
23328 J1-Field: Repeated FSC 8C00 following FSC 8E19 error
23426 MED: Try another velocity in read ERP
23472 J1: Read hang without resume when C1 error happens
23531 Split CALIB_ROLL into CALIB_ROLLW & CALIB_ROLLR cal reasons
23463.5 Connect CALIB_ROLLR, CALIB_ROLLW to rolling calib invocations
23532 J1-FIELD 970D/4601
23468.1 J1: SM does not notice tape stop motion in ERP
3197 DUMP: Fix dump tracing for unhandled interrupt (ymt 23675)
2838.3 J1-RAS: Re-enable reporting of too many SRRs FID2 F5 FSC 3826
23794 J1: Fix the check routine for unexpected endmarker detection
23789 Read Position error, buffer image taken..
23671 J1 : drv 5491 : FSC 6017
3592 J1A D3I0_B95
Summary list of major enhancements and fixes:
1. Add FSC 3826 for excessive fibre errors (SRR)
3592 J1A D3I0_B93
Summary list of major enhancements and fixes:
1. Present correct FID code for FSC 5066 (prevent unnecessary Call Home)
2. Fix false FSC 3820 when running drive diagnostics
3. Fix problems with phase 2 rolling cal write/read ERPs
4. Add slow speed read ERP step
5. Fix RABF degraded writing problem
3592 J1A D3I0_B8B
EC Contents:
Summary list of major enhancements and fixes:
1. Rolling calibration phase 2 changes
a. Improved ERP handling of write or read temp error bursts
b. Fix some cases of FSC 6017 caused by ERPs during Locate/Space commands
c. Fix some cases of FSC 5066 read perms
d. Add max C2 correction as rolling cal option
Detailed list of all changes/fixes:
2965 BUILD: Use unique link space for j1PGA12
2967 HANG: Some errors (9711) can cause cmd hangs
2981 WRONG: CM page table needs to cross-reference actual page
2901 RABF(44010000-Rd2): TIMEOUT (1003s)
2967.1 HANG: Some errors (9711) hang write cmds
2996 FIBRE: Read abort [FCRC on read] due to race
3002 SCSI: Sense bit pos valid explicity set (not clr)
3042 BUILD: Fix image size overflow in j1PGA12
3046 PANEL: Fix hole in panel reset debounce
2954 LocRWShort (992s) DATA_MISCOMP (old tape, FFP=1069)
2954.1 FIBRE: Independent write/read burst sizes
3061 WORM: CM update failure is ignored
3088 6017: Extend upif timeout for Space request to 45 minutes
23089 RWLongTypical (1250s) TIMEOUT-0A
23113 MED: Rolling calib Phase 2
23124 MED: Rolling calib Phase 2
23147 WormLabel (1674s) TIMEOUT-2B
22982 J1 FIELD 83 5066 0000 2A0F
23150 J1: Remove codes to check c1c2 and decode error
23185 J1/J2: append error is returned by write perm@ABF on WORM
23212 RWShortAggressive (1126s) TIMEOUT-08
23126.1 Rolling Calib Phase 2-existing logic fixes and enhancements
23126.6 Rolling calib fix: last-best-option not held at EOW if burst
3592 J1A D3I0_B07
EC Contents:
Summary list of major enhancements and fixes:
1. Improve fibre channel transmit signal quality (jitter fix)
2. Drive diagnostic improvements (use correct pattern and threshold scaling)
3. Fix write inhibit problem with multi-volume Worm tape application
4. Set Media Life TapeAlert based on lifetime bytes processed
5. ERP enhancements for read interchange problems and long mounts (rolling
calibration changes)
3592 J1A D3I0_A13
False Diagnostic FSC 3823
3592 J1A D3I0_A0F
Slow read / long recall
3592 J1A D3I0_A0D
EC Contents:
Summary list of major enhancements and fixes:
1. FCR 3118 - Support immediate command termination for Long Erase command
2. Support locate past EOD (convert to linear read)
3. Clear DUC on retry of load error
4. Fix for No Response msgs during clean cycle
5. FCR 3129 - Allow library to clear Flash dump
Detailed list of all changes/fixes:
2738 JAG-1 FIELD DUC not handled by as400
2845 Jag2-Field 9713 28410,442
22291 RVT: FID1 E5 6017 0000 when running host jobs
2838 JAG1-Field: Not reporting error (SRR's)
22117 Jag2-Field 6017 1_A27 22337,122
22181 Jag1-Field 970C 45817,227
2818 RAS: Make diags to wrt/read and inb/outb same amount of data
2822 WRONG: FC settings not correct on 3584 FRU
22145 JAG: Change cleaning tape speed to 6mps
2800 Fix F027 Check_1 A38 Code
22123 Jag1-Field Fix 6017 54888,49R
22101 EOD entry of HRTD is cleared before unload
2684 PERF: Do not rescale/erase if unchanged value
2696 WRONG: Inquiry commands not forwarded to library
2881 Fix F027 Chk_1 w B1D code (break in 2830)
2883 Fix breakage of Get VPD cmds
3592 J1A D3I0_904
EC Contents:
Summary list of major enhancements and fixes:
1. Fix sequence problem with SRR during RES command
3592 J1A D3I0_902
What’s Fixed
EC Contents:
Summary list of major enhancements and fixes:
1. HSARS Quick Check
2. Improved calibration selection during diags
3. Miscellaneous field problem fixes
Detailed list of all changes/fixes:
2630 Drive Reset on Write(ymt21117)
2631 HSARS Quick Check
2640 F00B w 942 code
2659 F016: Double message received caused F016
2625 Drive reset in send diag for reset error injection
2581 F01C-0022: Memory access panic on flash erase
2591 FSC9712 on write
19712 7A00 loses segment-reusable flag after sns xfr
2541 NEW: Fail when library sends message out of order
20995 JAG1-FIELD 970C 000B 283C
3592 J1A D3I0_85A
EC Contents:
Summary list of major enhancements and fixes:
1. Support recognition and tape reformat from E05 encrypted to J1A
2. Miscellaneous field problem fixes
Detailed list of all changes/fixes:
2352 9999-C00C: Fix hang in port switch w/Ayame
2389 F016: Report nicer error w/FID for no BVPD in 3584
2448 F008-47D9: Misrouted unload response (multiple)from the lun
2496 9710: Switch precedence of 9710/9711 on writes only
20430 Add Sticky-Servo ERP
2530 BENCH: Chk-1 F010, Event Queue Full (ymtstor 20725
3592 J1A D3I0_847
EC Contents:
Summary list of major enhancements and fixes:
1. Fix problem with LUN1 read buffer x0A
2. Fix problem with adding fill bytes prior to last fibre frame
3. FCR 3090 - add support for Cross EOD and Cross Perm Mode Select controls
4. Fix 9999-C00C Chk-1 which caused loss of library control path drive
Detailed list of all changes/fixes:
2345 TRACE: Trace full 16 byte CDB
2346 TRACE: Trace queue/abort in summary area
2352 9999-C00C: Fix hang in port switch w/Ayame
2389 F016: Report nicer error w/FID for no BVPD in 3584
2393 DUMP: Do not dump drive on redrivable read perm
2394 Change DLR_MAX_PARM_SIZE to multiple of 4
2425 FCR 3090 - Cross EOD setting
3592 J1A D3I0_83C
EC Contents:
Summary list of major enhancements and fixes:
1. Important field problem fixes
a. Fixes for correctly setting and clearing TapeAlert 18
b. Fix Report LUNs allocation length problem (could cause protocol errors)
c. Fix problem where code info header can be corrupted in dumps
d. Fix problem when ATS received before FCP_CONF (could cause hang)
2. FCR's and other functional changes
a. FCR 3026 - LDI Get-Set Behavior (Baud Rate)
b. FCR 3065 - LDI Pause Command
c. FCR 3066 - Force ERP (TM Portion)
d. FCR 3068 - LDI Supported Features
e. FCR 3076 - Allow LogSense to be forwarded to LIB when Not Ready
f. Correct problem with Auto(NL) configs to L-Port instead of N-Port
Detailed list of all changes/fixes:
2038.1 9999-C00C: Fix hang in turbo counts
2081.3 FIBRE: Fix speed issue by disabling int xcvr on reset
2081.4 FIBRE: Handle path where LIPs can be missed
2139 JAG2-FIELD: Reject serial num update if drv model different
19104 JAG1 FIELD E5 6017 and 970C multiple accounts
2131 9999-A101: String Search check during error
19049 E5 970C
2094.1 F008-4342: Clean TSLLE on unusual error cases
2249 FC cable pull fail:Nport
3592 J1A D3I0_830
19049 E5 970C
19104 JAG1 FIELD E5 6017 and 970C multiple accounts
2183 JAG1-FIELD: F008-2707 Chk1
1871.1 Fix RLUNs allocation length
3592 J1A D3I0_825
Summary list of major enhancements and fixes:
1. Fix problem with incorrect FRU replacement of Jag2 drive with Jag1
2. Prevent false report of TapeAlert 18 to library during load sequence
Detailed list of changes/fixes:
7063 trigger fix
FSC 5012 on write,read,rabf
JAG2-FIELD: Reject serial num update if drv model different
3592 J1A D3I0_81F
Summary list of major enhancements and fixes:
1. Improve drive read ERPs to prevent certain long ERP scenarios
2. Miscellaneous field problem fixes
Detailed list of changes/fixes:
18956 JAG: DSS waveform capture - fix slow read
18972 JAG1: Slow Read Problem - Sticky Temps ERP
2094 F008-4342
2097 Add trace for CM protected and unprotected page tables
2102 FCS 6017
3592 J1A D3I0_81A
1. Miscellaneous field problem fixes, including slow locate. More detailed list not
available at this time.
3592 J1A D3I0_805
Summary list of major enhancements and fixes:
1. 4022 on read
2. 3823: Increase Jag1 Wrt Skip threshold for diags
3. Write failure FSC7888
4. FSC 5012/4401 perms
5. F010 on many repeated perm hidden dumps (inc#21768)
6. FSC 7060 code hole
7. Fix for FSC7520 write perm after rechuck.
8. Misdetect consistency of TapeDir and EOD
9. E5 F010 FFFF 2515
4． LTO4 GEN4：
Drive Code Level: 85V8 (TS2900 Library only)
Fixes:
LUN1: TS2900 library use mode 2 in LUN1 write buffer command
Drive Code Level: 85V6 (TS2240 Standalone Drives only)
Fixes:
Open neg. friction limit for HH due to circuitry offset
Drive Code Level: 85V2 (TS2240 Standalone Drives only)
Fixes:
Tracing and Dump Enhancement
U320 -All FF CDB causes Overlapped command
Enable C1IBC ERP on LTO - ERP enhancement to reduce write/read perms
U320 - Residual count is not reported when EOD detected during tape locate
U320 - Mode Page 19h/Subpage 03h not reporting correctly
ADI - LUN1 queue is hung with RES command.
Write perm ERP enhancements
Auto unthread after 20 minutes of non-activity to drive when media loaded
No indication for temperature error on SCD
Enhancement to Read ERP structure during C2 correction (706x FSCs)
G4HH - Need serial command to disable brush when extruded
SCSI PRIMARY PORT Enable/Disable VIA ADI
Code enhancement physical thread/unthread can be a solution to unthread/thread
failures
eServer: 'J' for invalid cartridge type at any case
Define SCD display for temperature failure in NEC/CAS mode
New POST check for open writer cable to head
SAS - Cable pull caused queue hang
ADI to detect framing and line breaks, hdwre workaround, can cause communication
failure without indication
Log page 0x11, log parm 0x8001, MES value for uninitialized cartridges
Unable to unload tape
U320 - Drive hangs with Bus Reset
Enhancement in Channel code to improve general write and read operational
performance
Improvement to the retention of statistical data stored in VPD/EEPROM
U320 - Multi-initiator Invalid Reselection
Fix for FSC1602 occurrence
U320 - Wrong session may be used when turbo exit
FSC 6000 on SCSI load after FSC 2E05 failure
FCR 3155 - Drive Pass IES Vendor Specific Bits
FCR 3155 - change for all LUN1 commands
Cleaning twice without 2nd load
U320 - Exception on Read FM
U320 - handle sense data for error response on TM
U320 - extra one byte is padded on HP-UX (N138)
Encryption enhancements
Post 7904 even if tape is unloaded after auto unthread
Panic when LDI command read tape with long length
LDI - change method for 3572 inquiry string machine type/number
High-speed refreshes the cartridge to EOT, then to BOT when media debris signature
is detected
Wave motion ERP enhancement - enhancement to greatly reduce stiction
Creep motion improvement for a-unthread (local ERP) - enhancement to greatly
reduce stiction
VFO Detection enhancement - greatly reduce read degradation and perm errors
Accept uninitialized cart which has CM TA page
ADI - Fix mode page 0e 01, display current wwnn
ADI - Fix mode page 19h - data in mode page 0x0e 01
Flashing Activity light on recovery
SAS - Incorrectly aborted command should have sent up a check condition
U320 - Handling delayed scsi response for TM IUs
LDI - Not cleaning up LUN1 cmds properly during login
U320 - Drive hangs with Bus Reset at reselection timing
Auto unthread hang after unthread error - can result in a tape not able to be unloaded
Fix for failure to unload
Fix for a Drive panic during a locate command
Add MAM attribute 80B Application Format Version
Allow return of saved values for modes pages 0x0e 0x
ADI - wrong frame number after login process
ADI - mode page 0x0e 02 (ADI) enable/disable ports separately changed to match
specification
Auto unthread: drive hang with unload request - can result in media unable to be
unloaded
SAS Drive panics on PRO
ADI - Add EPP and ESR bits to VHF data
Support Legato NetWorker (NW) ILEP
FCR 3156 - add correct ITD pages for 3572 (1U) library
Timeout on Locate command
Channel enhancement to ACOMP registers. Resulted in slightly degraded channel
performance
Added check cleaning criteria at boot
Support vendor-specific INIT ELEMENT STATUS(E7h) cmd
MED: med_compare_pos() is called with a wrong argument order
Drive returns 2 5904s
Out-of-range indexing in Error Burst Log, burst detect probs
ADI-FC Race condition creating SIOP, resulted in a no response to RES command
ADI No response after command - framing errors and aborts
Bursting temps for Servo errors can cause excessive backhitching
I/O error on read can cause a Drive Hang
FSC 6000 during data operations
U320 - I/O error causes drive to not respond
Short locate timeout
ADI - No response when using NOP and PAUSE ADI commands
Fix for Mode page 0x1e
Drive Code Level: 82F0 (TS2240 Standalone Drives only)
Fixes:
During a write filemark an FSC 6000 is experienced
When running Diags the drive must clear all reservations when taking the port offline
Fix for an infinite loop retry breakage- When incorrect setup on the EKM causes a
retry, the drive will stop retrying after 3 incorrect keys with correct alias are returned
When media is partially ejected and power is pulled, there is a small possibility for a
hang in the drive on power up
During an SME usage where the EKM is removed from the network, the drive can
post an SCD'3'
On an attempt to mount, the drive fails the mount and incorrectly reported a FSC
2C51
ADI drive communication failure during internal library check. Results in the
appeared hang of the drive/library
In certain environments the FSC 1606 has been seen. This fixes this particular
interface error
Fix planned command
During diagnostics, need to change the help response during the ras diagnostics
Drive did not handle Initiator detected Error msg properly. This results in an interface
error at the host. (U320)
SAS Block length must be a multiple of 4 per the SSC specification
Implement FCR 3146/3147 for High Density 3584 support
After a write error, the drive returns a FSC 605E incorrectly
During write or read operation, the Fibre Channel interface would experience a panic
causing a failure in the customer job
Selection Timed out for TUR during Multiple burst transfer
Added new FSCs with ASC/ASCQs to the drive reporting for IU mode errors (U320)
During a write or read operation, the drive could detect a motor driver failure. When
the motor driver failure occurs (reported as FSC 7875)
The correct ERP needs to be invoked to ensure the integrity of the tape
Change the write attribute command structure to allow the writing of the Cleaner CM
Support the writing of the label to a cleaner CM over LDI interface
If DISCPriv is off the bus, it is disconnected incorrectly by the drive causing a
communication error with the host (U320)
TA16 was being set when the unload button was pushed
When in a non-IU mode, a drive code error was being returned to the host (resulting
in a communication error with the host) U320
Cleaning operation would be executed twice in a row (U320)
FSC 78B5 Beginning of Tape shutdown is experienced as a result of LPOS estimation.
This failure is on LTO4 tapes
Integrate Read and Write channel enhancements
Due to a tray position error, the drive would not load a tape after unload
Added Support for the DTD Port Status Log Page (U320)
The ADC mode page for port status reports the incorrect LVD mode
The Drive Panics on a Write. This results in a communication error with the host, job
failure. This is a result of an incorrect queued command count
Read/Write Channel enhancements for LTO4
Change the point at which the drive reports a failure for the retraction of the head
brush. Experienced as a load failure in the drive
Drive fails as a result of the handling of many commands coming into the drive in a
multi-LUN environment
Assign a unique reporting sense for error relating to tape failure with head interface
Encryption enhancements to FIPS capable code areas
Fix for FSC 7865 permanent error on LTO4 media
Selection Timeout due to Long Bus Reset Assertion (U320)
Sense Key for write protected uninitialized cartridge load should be 07 - it was set at
05
In a SAN environment with link failures, the drive incorrectly fails with FSC 7070 on
the recovery of the link failure
Read after write failed with SK/ASC/ASCQ 04 44 00 and FSC 6410
FSC 1605 reported by the drive as a result of link level errors on the bus in a write
command (U320)
Implement a Tape Alert for FSC 2C3A
ADI reporting of FC status for supported features has an incorrect length
ERP enhancement for high friction media events
Incorrect value in Log Page 0x0C Parameter Code 0x02 (compressed data bytes) at
read operation
Add FSC for safety unthread/rethread and high friction media events
FSC 7133 failure as a result of beginning of wrap Data check ERP
When compression is selected, a faster write speed will be selected
During drive detection, a physical link error may cause the HBA to not respond. This
works around the HBA failure
ADI fix for display message on LUN2 requests
New cleaner tapes can have a CM entry that will cause the Cleaner cartridge to not be
ejected
Under the multi-initiator environment, LTO4 U320 hung up during a write operation
when the other drive issued Reset on the bus. (U320)
In Multi-LUN condition. LUN1 commands that invoke data transfer are issued while
Read/Write in turbo mode
Implement Tape Alert for FSC's 1224 -1227 (RAS failures)
Write timeout on Fibre Channel drives
Unload failure with FSC 2E09 and the Drive posts a SCD '5'. This can be caused by
powering off the drive with tape mounted or at load point
FSC 1606 Fibre Channel DMA FIFO fix
Fix frame number in error recovery for ADI communication - Customer would see a
drive and library failure
ADI disabling of the primary SCSI port prevent selection of the primary port, but
does not correctly prevent bus reset processing
When more than 16 LUNs are connected, the drive did not properly return the correct
LUN
Do not set WP in VPD for mode page 0x03 (ADI)
Library initiation failure over ADI - task management IU should not come during
login process
A Control Path SAS drive can fail for a microcode error as a result of handling abort
requests. This happens mainly on non-TLR supported Host Bus Adapters
SAS change for handling an abort request with iSeries and pSeries SAS adapters
When over temp occurred there was no indication on the SCD in certain cases
Drive Code Level: 8192 (for TS3100/TS3200 at this time)
Fixes:
During reselection in non-IU mode the drive experienced an issue with the reselection.
This resulted in a communication failure between the drive and Host.
After a send diagnostics, drive returns check condition on release (U320)
FSC 78B5 returned to the host with LTO4 media
Drive unable to load a tape manually after it was eject
Cleaning operation twice in a row with U320 drive
Implement Support DTD Port Status Log Page
Drive failure as a result of Queued command count being invalid.
Changed read CRC error sense code (U320)
Sense Key for write protected uninitialized cartridge loaded should be x07 not x05
Fix frame number in error recovery for ADI communication (ADI)
Added iuCRC error FSC to the FSC table in the drive
Read operation stopped due to FSC 7865 error
Need to move brush retract detection from unmount to mount.
Need to invoke GDB when motor driver error happens (Half High drive only)
Drive Code Level: 7BG5
Fixes:
Need to move brush retract failure from unmount to mount
Drive Code Level: 7BG3
Fixes:
Encryption EKM loop fix with EKM
FC only changes to the clock timing on the drive internal bus
Fix calculations of read attributes 0x222 and 0x223
Releveling for FIPS qualification
False excessive read recovery timeout (Read ERPs with slow host)
FSC 2C51 is reported after mount fail
Change FAS Buffer Clock and DMA Clock to avoid FSC1606
FAS timing change previously applied to FC for FSC1605 applied to SAS and U320
Fix TD Sta_Check_Dataset_Number_Consistency()
Return "all pages" for LUN2 for mode sense command
Encryption Loop Fix for EKM interfacing
Incorrect WWNN sent to EKM from Drive in LME mode
Log page length incorrectly reported in the log page header
Need to enable brush extension on rechuck
Improper handling of Proxy(library) termination of the key acquisition
GEN2 tape issue in manufacturing caused by calibration in certain region of tape
Fix reporting of Write protect WORM media sense data from Sense key=03 to Sense
Key=07
Tape breaking scenario at Beginning of tape with unload
T021 error on LUN1 commands causing hang in library in TS3310
MAM attribute 0007 not returned with correct value
Implement head brush on every 5 loads
Implement New MAM attribute 0x224 when G3 cartridge is loaded
Read Attribute needs to support x224 as a first attribute
SCD H on Send Diag fail after FMR fail
Small distance margin for UCC cleaning at 1st cleaning
RW diagnostics with ITDT application fails when using a GEN3 media
Band Change Timeout
Drive Code Level: 7A31 (for TS3310/TS3500 at this time)
Fixes:
LDI Enable Drive_MD messages for LTO
Abort task no status frame received
Update motor limits due to clock frequency change
Fix for long locate due to CQs
Fix for Read Perm
Adjustment for cleaning Algorithm - was too frequent
Invalid SK0 with LTO4 and LME enabled on 3584
Data Path failover failure on rewind with Linux
Expand tolerance on Post motor test
Fix for logical unit reset in ADI mode
Fix for E0 and EF with read and write of encrypted data
Support CALIB_SARS as a valid calibrate reason for LTO drives
Copy comp block to RAM before creating plain block
Speed boundary condition inhibits FSC 7063
Fix for FSC 1012 failure in Library environments
Fix for Mode Page 0x19
Failure with WORM media for OPP
Drive FCE Panic 0xFCFF on Inquiry (Non-IU)
Overlapp command resulting from read buffer on IU mode
U320 Changed default SyncOffset Value
Drive FCE_Panic(0x1111) on Recovered Error
Hang resulting from Exception with Parity Error @ U160
Residual Count is not correctly returned in 160 mode
Multi Initiator does not work correctly in 160
U320 adapter *** Panic on FixedMult w LUN1
Changed Slew Rate Control value (u160 in multipath env)
FSC1017 is returned to TUR and other commands
Fix for one flavor of FSC 1605
AME - IBM proactive key set for read not recognized
U320: need to clear uninitialized variables
ORC check fences drive on illegally written carts
Change timing of checking WP switch- Possible incorrect WP surfaced
FSC2E05->FSC2E19 after Drive Reset -> Overlapped command
Drive FCE Panic FCFF on Write
Data Path Failover Failure on Rewind failover failed
U320 Drive FC Panic 0xFCFF on Read in IU mode with Attn
Fix for MTR sense is reported as recovered when it is not
Data Path Failover fails for Read operation on SAS
Mode page 0e_04 serial number not from VPD on power up
Fix for Read compare error
ModePage 0x19 subpage 0x3
FSC 605E when attempting to read Ultrium2 tapes in LTO GEN4 drive
Residual counter in sense is wrong when Filemark is detected causing EOD detected
incorrectly
Change initial value of INTMSK1 register
Drive FC Panic 0xFCFF on Write in IU mode
Encryption device causes panic in drive (u320)
Reading last block on a pre written GEN2 tape failed FSC 605E
Fix for FSC 2E04 resulting in a unloadable tape
Fix LUN1 Standard Inquiry for U320
Fix for SCSI slow negotiation when in ADI mode
No disconnection during TUR/RSNS/INQ in Non IU mode
If quality of lowest drive speed is bad, the drive selects next speed up only
LDI License Keys for EKM usage
Encryption Regen'd key on EKM creates loop in drive/EKM KEY exch
FMR cartridge cannot be used (SCD 6 FSC 5911)
FMR image is different from original ROM image after ROM recovery will result in
'e' on SCD
Panic on Multi-LUN command (u320)
FCH: Relevel with tapedrv (includes FSC 1605 and FSC 1606 improvements)
Incorrect FSC 1133 during encryption
Exception when running u320 in ADI mode
Servo support of 7 drive speeds
Fix Read FSC 1605 in MultiLUN with u320 drives
Read T/O while the drive detects a FM.
FSC7530 reported as a result of EOT fast locate
Device Not Ready on TURs ( MultiLUN ) (I/U mode)
Fix for Drive panic during write/read operation
SAS Hang in error scenario with expander cable
Media slow recovery enhancement
Servo enhancement for FSC 7834
Bus Reset Problem ( MultiLUN and Daisy Chain )
Calibration Enhancement Phase 2 change
Drive Code Level: 77B1 (for TS3100/TS3200 at this time)
Fixes:
Optimize Speed selection
FSC 6037 Fix during MTR
Enhance LPOS registration
Fibre Channel enhancements
FIPS Certification
SCSI Reset enhancement
Data path failover with Linux
LDI drive status reports wrong value for FMR cart
Sense reporting enhancement
Tracing for LDI/ADI
Encryption enhancement
Dump enhancements
Append mode enhancement
Encryption enhancement with EKM interface
Encryption management failure fix
Unload response failure
Reboot by reading corrupted rom dump
LDI encryption enhancement
U160 incorrect reporting of encryption state
Encryption Auto set to T10
Locate Timeout fix
Encryption enhancement- ADI EKM interfacing
Reservation Check enhancement
FSC 1017 load enhancement
Drive Code Level: 75X2 (for TS3310 at this time)
Fixes:
Image Enhancement
Fix status reporting on FMR
Sense reporting enhancement
ADI/LDI tracing enhancement
Format enhancement when in append mode
Relevel of FCH code
Encryption enhancement
Encryption enhancement - EKM interfacing
Encryption enhancement sense over LDI
Drive Code Level: 7590 (for 3584 at this time)
Fixes:
Fix for EOT shutdown
Dump to Flash enhancement
Remove LUN1 requirement on Poll Queue handling
Library Encryption Enhancement
Tape alert posted on new WORM media
Certain new WORM Cartridges fail with Tempering Check
Drive Code Level: 74H4
Fixes:
No CM Cart failed
Error on Space to EOD
Fix for Servo Write error
MED: Failsafe for a panic which is caused by STICKY_WSRV_TEMP
Fix for encryption Validation
Enhancement for VPD Encryption certificate
Library Interface: LogSns command incorrectly checking for NRD
Fix for Load Failure in certain circumstances
Increment thread count for brand new WORM
Fix 1st encrypted record number in CM status page
Library Interface - Added Clear Flash Dump to supported features in read
SAS Speed Negotiation enhancement
ADI (library fix) for space/no Op
Fix inquiry pages 0x83 and 0x88 for ADT port responses
Library Interface: commands are not forwarded after PAUSE state
Enhancement for Drive Write Fencing on certain perm errors
Enhancement for Link Initialization
Enhancement to persistent reserve
New Function for Encryption with Branded products
Control path drive may not be able to be seen by host
ccSARs enhancement
Deferred SNS reported on recovered ERP
Logical Write Protect should work in all load states
Fix for occasional panic resulting from timed out exchange
SAS Enhancements
Change for protecting sessions w/reservations from implicit logout
Serial number inquiry fix
Fix For invalid field in parameter data on Mode Page x0E
Enhancement of POST error reporting
Fix for FSC that triggers when Clean for usage is required
Match SCSI reference with new log page x3C
Dump dot indicator fix
New PLL settings to improve read/write error rates
Microcode update resets VPD replica
SAS performance compensation for TLR performance on the HBA
Fibre Channel Link enhancement
ILI Sense over written by recovered error
Control and Data path Failover fix for SAS
Initialize element status fix
Properly reject G4 cart in G3 drive when in Library
Fix Frequently requested cleaning
Drivecode Level: 7384
Base Code
5． LTO3 GEN3：
Drivecode Level: 85P1
Release Date: 06/18/08
Fixes:
23932.1 ADI - Fix mode page 0e 01, WWNN
23741 ADI - Detect framing and line breaks, hdwre workaround
23932.2 Fix mode page 19h - data in mode page 0e 01
23977 Handling delayed scsi response for TM IUs
23978 ADI - not cleaning up LUN1 cmds properly during login
24007 ADI - Wrong frame number after login process
24005 add MAM attribute 80B Application Format Version
24016.2 ADI - Mmode page 0e 02 (ADI) enable/disable ports separately
24081 ADI - No response after command - framing errors and aborts
24102 Fix for breakage of config DPF with the new method
24112 ADI - correct scsi id if not in library for ADI 0e_02 mode page
23848 U320 - RAS test failed
24146 ADI: No response when using NOP and Pause ADI commands
24158 Fix for Mode page 0x1e
Drivecode Level: 73P5
Release Date: 05/24/07
Fixes:
21122 Servo Acquire enhancement
21157 Error Reporting enhancement
21232 Data protection mechanism enhancement
21234 Fix for unload error on 5v power interuption
21334 Log page 16 enhancement
21354 Fix For Error Recovery on Fibre Channel
21351 Log Page 16 not saving SK/ASC/ASCQ of 03/53/00
21367 Log page 16 enhancement to compliance
21415 Media Buffer Header data flow fix
21444 Remove iop on reselection timeout
21445 Write Buffer command did not work on ADI
21471 Fix for Cartridge memory corruption recovery
21472 Enhancement for soft error recovery
21480 Fix for WORM corruption on writing the volser
21496 Fix for primary interface not going offline
21507 In certain circumstances TA32 should be turned off
21545 HIB interrupt was kept disabled forever.
21558 Log Page 16 Enhancement
21578 Unexpected media write protect
21617 Drive offline after Fibre Channel wrap test
21831 OEM ADIC - FSC 7265 on Write
21940 VPD life time is updated incorrectly
21972 Fibre Channel link down fix
22000 Log Page 14 enhancement
22011 Enhancement for Append failure due to media degradation
22014 Log Page 38 parms 4-7 not logging
22091 SCSI wrap test fix when over Library interface (LDI)
22141 Write Buffers fix for ADI library interface
22178 Update counters in Log Page x3Ch when unload occurrs
22184 ADI (library fix) for space/no Op
22234 ERP enhancement related to speed selection
22261 Reservation enhancements
22304 Addition of Log Page x3Ch in LTO3
22217 Drive fence enhancement for perm on locate scenario
22399 Fibre Channel Link enhancement
22400 ILI Sense over written by recovered error
6． LTO2 GEN2：
Drivecode Level: 73V1
Release Date: 04/30/07
Fixes:
19363 keep drv OFFLINE until told ONLINE by LDI
19513 TA22 clearing behavior change
19687 Notify lib of aborted LUN1 host command
20128 Set appropreate TA on 2E02 load failure
21090 Fix for incompatible Dataset Identification
21117 Fix for Drive Reset on Write
21221 Fix for Drive Reset for Fibre Channel drives
21617 Fix for Drive offline after FC wrap test
21789 Error Log not cleared by Maint Mode A
21940 VPD life time is updated incorectly
21962 Enhanced reservation implementation
22186 Fix for persistant Reserve
22217 Drive fence enhancement for perm on locate scenario
22219 Persistant reserve enhancement
22244 Power on hours not being updated correctly
22256 End of wrap shut down could cause stuck tape
22261 Protect sessions w/reservations from implicit logout
Drivecode Level: 67U1
Release Date: 11/01/06
Fixes:
17484.1 "FC If the host or switch sends the drive a frame in the wrong class of
service, the drive will correctly send P_RJT, but then the drive will incorrectly
send LIP(F8). LIP(F8) will cause a new loop initialization."
17773 FC Protocol- Drive does not LIP soon enough for missing LIPA
17930 Drive may hang during write at Wrap due to ERP infinite loop
17946 Write permanent error (FSC 7475 or 7115) during attempt toappend at
position other that EOD
18317 When an expired cleaning cartridge is not ejected and seats at themount
position, ready status is reported. Although ready status should not be reported
for a cleaner cartridge.
18772 FC Drive will not recover from a cable pull while data xfer is in progress:
Error recovery does not ever complete and job appends.
18956 Intermittent lower performance on locate/space or read.
19083 FC: drive configures to L-Port instead of N-Port when in Auto(NL)
19120 Read timeout in overrun condition
19138 Enable LDI Supported Features
19141 Enable LDI Get-Set Behavior Baud Rate
19166 Log sense timeout problem during cleaning
19173 FC Drive goes offline due to panic reset in multi-initiator environment
( Panic xFCD0 )
19181 Some drive diagnostics initiated over the host interface hang the drive and
fail the test
19198 Asynchronous Unit Attention was not reported to host.
19225 New tape (not end point tested) used to make a FMR tape the does not
complete successfully.
19053 FC - RR_TOV timeout (SRR fail) / not validating fcp2tag
19062 FC - Detect hardware problem that may cause register mis-writes
19197 FC - No Check Condition for an invalid task attribute
19296 Non zero byte count in RES response
19328 FC Wrap Test Failure on 2GB drives
19339 Null Sense reported after Thermal sensor failure
19350 LDI Pause Command Enabled
19394 Gen2 Drive writing Gen1 cart did not increment Tape Write Pass
19399 ERP’s were improved to recover from a CM read error which would cause
FSC 6017.
19408 Fix for Drive resets when large amounts of data are transferred via LDI
19417 TA18 incorrectly posted when cartridge is loaded – The drive incorrectly
detected a corrupt CM and posted a TA18.
19439 FC Drive, intermittently, does not recover from a cable pull when set to
Nport
19601 Incorrect truncation of cartridge Serial Number in engineering log
19646 Add conditional checking to detect suspected rare off-track condition.
19685 Write FM failed when FC linkdown occurred due to drive panic
19786 Invalid FSC 1042 for invalid field in param list
19835 5 is displayed in the single character display upon receipt of Clear Task Set
message
19858 2nd FM lost in error recovery on Space to BOT.
19953.2 Add Long Erase progress indication
19967 Enable LDI Reset - add Abort Task Set
19979 Added Read Buffer Size Maint_Command to LDI
19993 Inquiry with Invalid field does not set field pointer info
20146 Drive Diagnostic ‘F’ fails on a good drive:
20281 Unexpected Device Driver I/O on mode Select
20330 Added LDI Supported Functions (Read Buffer Size)
20341 In library environment, unload a cartridge without unmounting and load the
cartride. Then next write command is hanged
20398 Bus reset due to bus scan can cause a drive reset
20398 intermittent drive panic in LDI transmit due to bus reset
20419 False detection of Endmarker at DS Boundary
20490 Wrong bit/byte pointers may be reported in sense data, when an invalid
CDB is issued for SCSI Report LUNs command
20509 FC: drive L-port participates while offline
20725 FC drive panics when initiators that rapidly and repeatedly send frames in
the wrong class of over flow a queue
7． LTO1 GEN1:
Drivecode Level: 5AU1
Release Date: 12/20/2005
Fixes
14665 Command time out due to holding of SCSI bus phase unchanged for more
than 2 Seconds
15146 Fix for FSC 4001/2080 due to abundance of write skipped datasets on tape
15511 Implement ERP to detect servo during lateral tape shift is occurring to prevent
degraded performance and FSC 3111
15611 FC Drive panic due to access invalid address while performing force log
capture
15626 Fix for FSC 20C0
15930 Enhance drive diagnostics
15965 Corrupted CM cartridge hangs drive during load
15968 Tape Alert flag 22 is not cleared when cartridge is removed
16104 Abort to CMD causes SCD 4 FSC 219D
16189 Drive Status message to library on Fibre channel drives does not reflect if
drive offline
16204 On Control Path enable drive corrupted Read Element Status data causes
drive to panic
16922 Added ERP for writing block 1 protection flag in Cartridge Memory
16941 On Fibre Channel drives when checking for valid SRR add specific relative
offset
16968 Fibre Channel drive hang when LIP during data transfer
17048 RBL and RDS commands incorrectly return reservation conflict
17516 Internal Locate issue with Read Command on FC Drive
17593 iSeries: Download ITD records not correct
17614 TLWR fails after drive code update by AS/400
17896 Workaround for the CM read timeout during thread operation
17951 FC drive Reboot by exception 0100
18759 Intermittent Read time out on SCSI drives
18034 Report Density data is padded with zero (00h) instead of ASCII space (20h)
Drivecode Level: 53J1
Release Date: 4/13/2005
Fixes
15146 Fix for Perm during read operation
15511 Implement ERP to better detect servo
15611 Fibre Channel drive Panic during force dump processing
15626 Fix for FSC20C0 during write operation
15930 Enhance drive diagnostics
15965 Corrupted CM cartridge hangs drive during load.
15968 Clear TA flag 22 when cartridge is removed from drive
16104 Abort to CMD causes SCD 4 FSC 219D
16189 Fibre Channel Drive Status does not reflect if drive offline over LDI
16204 Control Path Read Element Status data corruption causing panic
16922 Added ERP for writing block 1 protection flag in CM
16941 Improve Latchable SRR redrive on Fibre Channel
16968 Fix Fibre Channel Drive hang when LIP during data transfer
17048 Incorrect reservation behavior for RBL and RDS comm.
17516 Internal Locate issue with Read Command on FC Drive
17593 Fix iSeries Download ITD records
17614 TLWR fails after ucode update by AS/400
17896 Workaround for the CM read timeout during thread
17898 SCSI bus is hold during LUN1 Mode Sense command
附录B：LTO的SCD code详细说明。
Code Cause and Action
SCD 0
No error occurred and no action is required. This code displays:
- When power is cycled (turned off, then on) to the tape drive.
- When diagnostics have finished running and no error occurred.
Note : The single-character display is blank during normal operation of the tape drive.
SCD 1
Cooling problem. The tape drive detected that the recommended operating temperature
was exceeded. Perform the following action:
1. If a fan is present in the enclosure, ensure that it is rotating and is quiet. If not, replace
the fan (for instructions about replacing the fan, see your enclosure’s documentation).
2. Remove any blockage that prevents air from flowing freely through the tape drive.
3. Ensure that the operating temperature and airflow is within the specified range (see
“Specifications” on page 1-19).
4. If the operating temperature is within the specified range and the problem persists,
replace the tape drive.
The error code clears when you power-off the tape drive or place it in maintenance
mode.
SCD 2
Power problem. The tape drive detected that the externally supplied power is either
approaching the specified voltage limits (the drive is still operating) or is outside the
specified voltage limits (the drive is not operating). Perform the following action:
1 . Ensure that the power connector is properly seated.
2 . Ensure that the proper dc voltages are being applied within the tolerances allowed
(see “Specifications” on page 1-19).
3. If the proper voltages are being applied but the problem persists, replace the tape
drive.
The error code clears when you power-off the tape drive or place it in maintenance
mode.
SCD 3
Firmware problem. The tape drive determined that a firmware error occurred. Perform
the following action:
1 . Collect a drive dump from one of the following: Note: Do not force a new
dump; the tape drive has already created one.
- Server’s SCSI or Fibre Channel interface by using a device driver utility or system tool.
To obtain a dump, determine whether your server is installed with a utility that can read
files from the server’s memory. If it is, use that utility to obtain the dump. For information
about using IBM’s utility programs to obtain drive dumps, see the IBM Ultrium Device
Drivers Installation and User’s Guide. To determine where to send a file that contains a
drive dump to be analyzed, contact your Support Center.
- Ultrium Tape Drives (to copy a drive dump, refer to the section about copying a drive
dump in the library’s operator guide).
2. Power the tape drive off and on, then retry the operation that produced the error.
3 . If the problem persists, download new firmware and retry the operation.
4 . If the problem persists, send the drive dump that you collected in step 1 to your
Support
Center.
The error code clears when you power-off the tape drive or place it in maintenance
mode.
Firmware or tape drive problem. The tape drive determined that a firmware or tape drive
hardware
failure occurred. Perform the following action:
SCD 4
1 . Collect a drive dump from one of the following: Note : Do not force a new dump;
one already exists.
-Server’s SCSI or Fibre Channel interface by using a device driver utility or system tool.
To
obtain a dump, determine whether your server is installed with a utility that can read files
from the server’s memory. If it is, use that utility to obtain the dump. For information
about
using IBM’s utility programs to obtain drive dumps, see the IBM Ultrium Device Drivers
Installation and User’s Guide. To determine where to send a file that contains a drive
dump
to be analyzed, contact your Support Center.
- Ultrium Tape Drives (to copy a drive dump, refer to the section about copying a drive
dump
in the library’s operator guide).
2. Power the tape drive off and on, then retry the operation that produced the error. The
error
code clears when you power-off the tape drive or place it in maintenance mode.
3 . If the problem persists, download new firmware and retry the operation; if new
firmware is not
available, replace the tape drive.
SCD 5
Tape drive hardware problem. The drive determined that a tape path or read/write error
occurred.
To prevent damage to the drive or tape, the drive will not allow you to insert a cartridge if
the
current cartridge was successfully ejected. The error code may clear when you cycle
power to the
tape drive or place it in maintenance mode. If the problem persists, replace the tape
drive.
SCD 6
Tape drive or media error. The drive determined that an error occurred, but it cannot
isolate the
error to faulty hardware or to the tape cartridge. Perform the following action:
For Problems with Writing Data:
If the problem occurred while the drive was writing data to the tape, and if you know the
volume
serial number (located on the cartridge label) of the tape cartridge loaded in the drive
when the
problem occurred, retry the operation with a different cartridge:
- If the operation succeeds, the original cartridge was defective. Copy data from the
defective
cartridge and discard it.
- If the operation fails and another drive is available, insert the cartridge into the other
drive and
retry the operation.
------If the operation fails, discard the defective cartridge.
------If the operation succeeds, insert a scratch cartridge into the first drive and run drive
------diagnostics (refer to the appropriate section in the library’s operator guide).
-------------If the diagnostics fail, replace the drive.
------------- If the diagnostics succeed, the error was temporary.
- If the operation fails and another drive is not available, insert a scratch cartridge into
the drive
and run the tape drive diagnostics (refer to the appropriate section in the library’s
operator
guide).
------ If the diagnostics fail, replace the drive.
------ If the diagnostics succeed, discard the cartridge.
If the problem occurs with multiple tape cartridges or if you do not know the tape
cartridge’s
volume serial number, run the tape drive diagnostics (refer to the appropriate section in
the library’s
operator guide):
- If the diagnostics fail, replace the tape drive.
- If the diagnostics succeed, run the Head Read/Write test (refer to the appropriate
section in the
library’s operator guide).
------ If the Test Head diagnostic fails, replace the tape drive.
------ If the Test Head diagnostic succeeds, replace the cartridges that caused the
problem.
The error code clears when you remove the tape cartridge or place the drive in
maintenance mode.
For Problems with Reading Data:
If the problem occurred while the drive was reading data from the tape, and if you know
the volume
serial number of the tape cartridge, perform one of the following procedures:
- If another drive is available, insert the cartridge into the other drive and retry the
operation:
------ If the operation fails, discard the defective cartridge.
------ If the operation succeeds, insert a scratch cartridge into the first drive and run the
tape drive
-------diagnostics (refer to the appropriate section in the library’s operator guide):
------ If the diagnostics fail, replace the drive.
------ If the diagnostics succeed, the error was temporary.
- If another drive is not available, insert a scratch cartridge into the drive and run the
tape drive
diagnostics (refer to the appropriate section in the library’s operator guide):
------If the diagnostics fail, replace the drive.
------If the diagnostics succeed, discard the cartridge.
If the problem occurs with multiple tape cartridges or if you do not know the tape
cartridge’s
volume serial number, run the tape drive diagnostics (refer to the appropriate section in
the library’s
operator guide):
- If the diagnostics fail, replace the tape drive.
- If the diagnostics succeed, run the Head Read/Write test (refer to the appropriate
section in the
--library’s operator guide guide):
------ If the Test Head diagnostic fails, replace the tape drive.
------ If the Test Head diagnostic succeeds, replace the cartridges that caused the
problem.
The error code clears when you remove the tape cartridge or place the drive in
maintenance mode.
SCD 7
A high probability of media error. The tape drive determined that an error occurred
because of a
faulty tape cartridge, and expired cleaning cartridge, or the insertion of an FMR cartridge
as a data
cartridge.
- Try another tape cartridge. If the problem occurs with multiple tape cartridges, see
“Resolving
Media-Related Problems” on page A-14.
- Dispose of the current cleaning cartridge and insert a new cleaning cartridge.
- If the FMR cartridge is no longer needed, go to to the section about erasing an FMR
tape in the
IBM TotalStorage Ultrium Scalable Tape Library 3583 Maintenance Information.
The error code clears when you remove the tape cartridge or place the drive in
maintenance mode.
SCD 8
For SCSI drive:
Tape drive or SCSI bus failure. The tape drive determined that a failure occurred in the
tape drive’s
hardware or in the SCSI bus. See “Fixing SCSI Bus Errors” in the MI. The error code
clears 10
seconds after the drive detected the error or when you place the drive in maintenance
mode.
For Fibre Channel drive:
Tape drive or Fibre Channel failure. The tape drive determined that a failure occurred in
the tape
drive’s hardware or in the Fibre Channel. It detects light through the fiber cable but
cannot perform
data communication properly. The length of the cable between the devices should not
exceed 500
m (1640 ft). See “Fixing Fibre Channel Errors” in the MI. The error code clears when the
drive
detects light and can communicate, or when you place the drive in maintenance mode.
SCD 9
Tape drive or LDI (RS-422) error. The tape drive determined that a failure occurred in
the tape
drive hardware or in the LDI (RS-422) connection.
- Power cycle the drive. If the power-on self test is successful, the problem is resolved.
- If the problem persists, replace the tape drive sled (see “Tape Drive Sled” on page
7-3).
- If the problem persists after replacing the drive, the problem is with the cable between
the drive
sled and the power distribution board, the power distribution board itself, or the main
board.
The error code clears when you place the drive in maintenance mode.
SCD o, c, b, or h
No error or message assigned. There may be a problem with the single-character
display. Turn the
power off, then on and determine whether all segments on the single-character display
are lit. If so,
you may have a down-level version of both your library’s firmware and documentation
(the
documentation may not describe all of the available error codes). Refer to the latest
version of the
firmware or documentation.
SCD A
Tape drive hardware problem. The tape drive determined that a problem occurred which
degraded
the operation of the tape drive, but it did not restrict continued use. If the problem
persists, replace
the tape drive. The drive is usable, though the single-character display continues to
indicate an
error and the status light flashes amber.
The error code may clear when you cycle power to the tape drive or place it in
maintenance mode.
SCD B
No error or message is assigned. See error code 8 in this table.
SCD C
The tape drive needs to be cleaned. Clean the tape drive. See the section about
cleaning drives in
the IBM TotalStorage Ultrium Scalable Tape Library 3583 Setup and Operator Guide.
The error code clears when you clean the tape drive or place it in maintenance mode.
d Fibre Channel AL_PA conflict. More than one device has the same address. Each
device must
have its own unique AL_PA address. See the section about setting Loop IDs in the IBM
TotalStorage Ultrium Scalable Tape Library 3583 Setup and Operator Guide.
SCD D
No error or message assigned. See error code in this table.