本章提供了可帮助您排除 LTFS-LE 系统故障的信息。其中包含以下主题:
在搜索磁带库期间,LTFS-LE 会处理每个卷。在此过程中,LTFS-LE 将执行文件系统检查。
在某些情况下,可能会由于文件系统检查超时而无法处理某个卷。这将在 LTFS-LE BUI "Dashboard" 页面中显示的 "Recent Events" 窗格中指出,如下图所示:
如图 11-1所示,对卷 F52268 的文件系统检查由于某个自动处理事件持续时间超过两个小时而失败。
这由靠近显示屏顶部的以下事件条目指出:
Volume F52268 auto processing complete. Dismount File System for Volume F52268 failed. Check the system for volume F52268 failed. Dismount File System for Volume F52268 failed.
当发生此情况时,请执行以下步骤来重新处理卷:
登录到 LTFS-LE 服务器并发出以下命令来检查文件系统检查 (ltfsck) 命令是否仍在运行:
[root@ltfssrv LTFS_LE_TUTILS]# ps -elf | grep ltfsck
输出示例:
0 S root 30029 29971 0 78 0 - 16485 wait 13:12 pts/12 00:00:00 sh -c /usr/local/bin/ltfsck -e orcltape /dev/st0 2>&1 4 S root 30030 30029 0 75 0 - 12804 sg_ioc 13:12 pts/12 00:00:00 /usr/local/bin/ltfsck -e orcltape /dev/st0 0 S root 30032 28601 0 78 0 - 15293 pipe_w 13:13 pts/18 00:00:00 grep ltfsck
确认没有 ltfsck 进程正在运行后,使用 ACSLS 卸载卷。
成功从 ACSLS 卸载卷后,使用 LTFS-LE BUI 弹出卷。请参见弹出卷。
在成功弹出卷后,将卷转移到安装了 LTFS Open Edition (LTFS-OE) 的独立服务器上。
发出以下文件系统检查 (ltfsck) 命令之一,针对挂载了该卷的磁带机执行手动文件系统检查:
/usr/local/bin/ltfsck –e orcltape /dev/st? /usr/local/bin/ltfsck –e ibmtape /dev/IBMTape? /usr/local/bin/ltfsck –e ltotape /dev/st?
用实际的磁带机标识符替换 st? 或 IBMTape?。
有关可用命令选项的列表,请参阅《LTFS Open Edition Readme》。
在 ltfsck 命令成功后,您可以将卷重新引入磁带库中。请参见使用 ACSLS 装入卷。
等待 LTFS-LE 自动处理完成,然后开始使用卷。
与任何正常运行的软件系统一样,LTFS-LE 将生成持久保留在内部磁带机中的日志记录信息。
LTFS-LE 使用标准 Linux 日志轮转功能将磁盘使用量保持在可管理的大小,同时提供最新的信息来帮助服务代表对问题进行调试。当日志达到特定大小后,将对日志进行轮转并清除旧的日志。
要进一步管理磁盘空间,服务代表可以选择更改在系统中保留的日志数目。这可能会导致旧的孤立日志被保留下来,而不相应轮转。在这种情况下,建议服务代表手动删除孤立日志。这些日志的时间戳指出其已过时,并且其轮转值大于新日志的轮转值。
如果 LTFS-LE BUI "Manage Volumes" 页面上的卷显示为“灰色”,则指示该卷不可用。
下图显示了 LTFS-LE BUI "Manage Volumes" 页面,其中突出显示的卷 (ISR932) 灰显。
出现这种情况的原因可能是:
用户打开磁带库,并以物理方式移除卷介质。手动或自动重新搜索磁带库时,LTFS-LE 与 ACSLS 不同步。LTFS-LE 将移除的卷标记为在其数据库中不可用,因此该卷在 LTFS-LE BUI 中灰显。
LTFS-LE 软件无法解决磁带或磁带机上的错误。该卷留在了磁带机中,但是 LTFS-LE 将该卷标记为在其数据库中不可用,因此该卷在 LTFS-LE BUI 中灰显。
在这两种情况下,LTFS-LE "Dashboard" 中将显示错误消息,指出需要手动干预才能更正此问题。
如果发生这种情况,请执行以下步骤以从 LTFSLE 数据库中移除该卷:
在 LTFSLE BUI 的 "Manage Volumes" 页面中,记录灰显的不可用卷的序列号。
以 root 用户身份登录到 LTFSLE 服务器。
发出以下命令以导航到 LTFS-LE bin 目录:
# cd /var/opt/Oracle/LTFS_LE/bin
发出以下命令以运行 LTFS-LE CLI 工具:
# java -jar LTFSLE_FixTool.jar
Command List.
.
1. chgdrvpendingsta command.
.
Usage: chgdrvpendingsta <Drive serial number>
Example 1: chgdrvpendingsta 576001000419
Example 2: chgdrvpendingsta 576001000421
2. delunavailablevol command.
.
Usage: delunavailablevol <Volume serial number>
Example 1: delunavailablevol ISR401
Example 2: delunavailablevol ISR402
.
3. quit.
.
ltfs>
.
对灰显的卷运行 delunavailablevol 命令,提供您在步骤 1 中记录的卷序列号。
例如:
ltfs> delunavailablevol ISR213 . Unavailable volume <ISR213> is deleted successfully! .
发出以下命令以退出 LTFS-LE CLI 工具:
ltfs> quit
发出以下命令以停止 LTFS-LE 服务:
# /var/opt/Oracle/LTFS_LE/bin/manageLtfsleServices -t
发出以下系列命令以检查后端 LTFS 文件系统是否仍处于挂载状态,然后卸载所有文件系统。在 LTFS 进程完成之前,请等待。
# mount | grep -i LTFS_LE
# dismount -f <LTFS mount point>
# ps -elf | grep "/usr/local/bin/ltfs"
发出以下系列命令以标识具有已挂载卷的磁带机,然后重绕卷并取消卷锁定:
# sg_inq /dev/st?
# mt -f /dev/st? rewind
# mt -f /dev/st? unlock
使用文件系统检查 (ltfsck) 命令修复卷文件系统。有关可用命令选项的列表,请参阅《LTFS Open Edition Readme》。
如果此操作失败,请从安装有 LTFS Open Edition 软件的独立系统发出 ltfsck 命令。
使用 ACSLS,从磁带机中手动移除卷,并使其从磁带库中弹出。使用 "Force" 选项。
发出以下命令以重新启动 LTFS-LE 服务:
# /var/opt/Oracle/LTFS_LE/bin/manageLtfsleServices -s
发出以下命令以确保所有 LTFS-LE 服务都在运行:
# /var/opt/Oracle/LTFS_LE/bin/manageLtfsleServices -i
将文件系统修复后的卷重新装入磁带库中。
如果要将特定类型的所有磁带机(例如所有 T10000C 磁带机)置于脱机状态,一定要首先将该类型的所有介质置于脱机状态。否则,在 LTFS-LE BUI 的 "Manage Drives" 页面中,与该磁带机类型匹配的最后一个磁带机的 "Availability" 可能仍保持 "Pending" 状态,如下图所示:
如图 11-3所示,突出显示的磁带机 (579001000425) 的 "Availability" 显示为 "Pending" 状态,无法使用。
如果发生这种情况,请执行以下步骤以使磁带机摆脱 "Pending" 状态:
在 LTFSLE BUI 的 "Manage Drives" 页面中,记录处于 "Pending" 状态的磁带机的序列号。
以 root 用户身份登录到 LTFSLE 服务器。
发出以下命令以导航到 LTFS-LE bin 目录:
# cd /var/opt/Oracle/LTFS_LE/bin
发出以下命令以运行 LTFS-LE CLI 工具:
# java -jar LTFSLE_FixTool.jar
Command List.
.
1. chgdrvpendingsta command.
.
Usage: chgdrvpendingsta <Drive serial number>
Example 1: chgdrvpendingsta 576001000419
Example 2: chgdrvpendingsta 576001000421
2. delunavailablevol command.
.
Usage: delunavailablevol <Volume serial number>
Example 1: delunavailablevol ISR401
Example 2: delunavailablevol ISR402
.
3. quit.
.
ltfs>
.
对处于 "Pending" 状态的磁带机运行 chgdrvpendingsta 命令,提供您在步骤 1 中记录的序列号。
例如:
ltfs> chgdrvpendingsta HU1104ETMM . Drive Status was set to Offline state if previous state is Pending.(Current @ Status is Offline.) . ltfs> .
发出以下命令以退出 LTFS-LE CLI 工具:
ltfs> quit
发出以下命令以停止 LTFS-LE 服务:
# /var/opt/Oracle/LTFS_LE/bin/manageLtfsleServices -t
发出以下命令以重新启动 LTFS-LE 服务:
# /var/opt/Oracle/LTFS_LE/bin/manageLtfsleServices -s
在排除 LTFS-LE 服务器问题时,以下 Linux 命令和实用程序可能比较有用。
可发出以下命令来启动、停止或禁用 LTFS-LE 服务,或显示关于 LTFS-LE 服务的信息:
/var/opt/Oracle/LTFS_LE/bin/manageLtfsleServices [-h] [-s] [-t] [-i] [-r] [-a] [-d] [-l]
-h 显示此(帮助)消息
-s 启动 LTFS-LE 服务
-t 终止/停止/关闭 LTFS-LE 服务
-i 显示 LTFS-LE 服务的信息/状态
-r 保留供将来的服务使用
-a 添加 LTFS-LE 服务
-d 删除/禁用 LTFS-LE 服务
-l 按启动顺序列出服务名称
下面是指定了 -i 选项时此命令的输出样例:
Wed Jul 17 17:18:56 MDT 2013 - INFO: Beginning Management of LTFS-LE Services... Wed Jul 17 17:18:56 MDT 2013 - INFO: Statusing LTFS-LE MySQL Replication Master: LTFS-LE MySQL Replication Master instance is up and running, pid=6225... Wed Jul 17 17:18:56 MDT 2013 - INFO: Statusing LTFS-LE MySQL Replication Slave: LTFS-LE MySQL Replication Slave instance is up and running, pid=6282... Wed Jul 17 17:18:56 MDT 2013 - INFO: Statusing LTFS-LE Global Namespace Service: INFO: LTFS-LE Global Namespace Service filesystem is mounted and available, filesystem(s)=/mnt/LTFS_LE/metadata on /LTFSLE type LTFS_LE (rw,dir=/mnt/LTFS_LE/metadata/,debug=1)... Wed Jul 17 17:18:56 MDT 2013 - INFO: Statusing LTFS-LE Weblogic Application Server: INFO: LTFS-LE Weblogic Server process is up and running, pid(s)=6496... Wed Jul 17 17:18:56 MDT 2013 - INFO: Statusing LTFS-LE Backup Service: LTFS-LE Backup Service instance is up and running, pid=6763... Wed Jul 17 17:18:56 MDT 2013 - INFO: Statusing LTFS-LE Tape Automation Service: INFO: LTFS-LE Tape Automation Main Service process is up and running, pid(s)=6977... Wed Jul 17 17:18:56 MDT 2013 - INFO: Statusing LTFS-LE Tape Monitor Service: LTFS-LE Tape Automation Monitor Service process is up and running, pid(s)=7014... Wed Jul 17 17:18:56 MDT 2013 - INFO: Statusing LTFS-LE JMS Utils Service: INFO: LTFS-LE JMS Tape Utils Service process is up and running, pid(s)=7114... Wed Jul 17 17:18:56 MDT 2013 - INFO: Statusing LTFS-LE Comm Service: INFO: LTFS-LE Comm Service process is up and running, pid(s)=7249... Wed Jul 17 17:18:56 MDT 2013 - INFO: Finishing Management of LTFS-LE Services...
下面是指定了 -l 选项时此命令的输出样例:
Wed Jul 17 17:19:25 MDT 2013 - INFO: Beginning Management of LTFS-LE Services... Wed Jul 17 17:19:25 MDT 2013 - INFO: LTFS-LE Linux service name: ltfs-mysql-master Wed Jul 17 17:19:25 MDT 2013 - INFO: LTFS-LE Linux service name: ltfs-mysql-slave-local Wed Jul 17 17:19:25 MDT 2013 - INFO: LTFS-LE Linux service name: ltfsle-global-namespace Wed Jul 17 17:19:25 MDT 2013 - INFO: LTFS-LE Linux service name: ltfsle-weblogic-server Wed Jul 17 17:19:25 MDT 2013 - INFO: LTFS-LE Linux service name: ltfs-backup-service Wed Jul 17 17:19:25 MDT 2013 - INFO: LTFS-LE Linux service name: ltfsle-tape-automation Wed Jul 17 17:19:25 MDT 2013 - INFO: LTFS-LE Linux service name: ltfsle-tape-monitor Wed Jul 17 17:19:25 MDT 2013 - INFO: LTFS-LE Linux service name: ltfsle-jmsutils Wed Jul 17 17:19:25 MDT 2013 - INFO: LTFS-LE Linux service name: ltfsle-comm Wed Jul 17 17:19:25 MDT 2013 - INFO: Finishing Management of LTFS-LE Services.
可发出以下命令来获取磁带机信息,包括供应商、型号、设备路径和固件版本:
# lsscsi -g | grep tape
[7:0:0:0] tape STK T10000C 1.57 /dev/st0 /dev/sg2 [7:0:1:0] tape STK T10000C 1.57 /dev/st1 /dev/sg3 [7:0:2:0] tape HP Ultrium 5-SCSI I3CS /dev/st2 /dev/sg4 [7:0:3:0] tape HP Ultrium 5-SCSI I59S /dev/st3 /dev/sg5 [7:0:4:0] tape IBM ULTRIUM-TD5 B173 - /dev/sg6 [7:0:5:0] tape IBM ULTRIUM-TD5 BBN2 - /dev/sg7 [7:0:6:0] tape HP Ultrium 5-SCSI I59S /dev/st4 /dev/sg8 [7:0:7:0] tape IBM ULTRIUM-TD5 BBN2 - /dev/sg9 [7:0:8:0] tape STK T10000D 406. /dev/st5 /dev/sg10 [7:0:9:0] tape STK T10000D 406. /dev/st6 /dev/sg11 #
# cat /proc/scsi/scsi
Attached devices: Host: scsi0 Channel: 00 Id: 00 Lun: 00 Vendor: SEAGATE Model: ST973402SSUN72G Rev: 0603 Type: Direct-Access ANSI SCSI revision: 05 Host: scsi0 Channel: 00 Id: 01 Lun: 00 Vendor: SEAGATE Model: ST973402SSUN72G Rev: 0603 Type: Direct-Access ANSI SCSI revision: 05 Host: scsi7 Channel: 00 Id: 00 Lun: 00 Vendor: STK Model: T10000C Rev: 1.57 Type: Sequential-Access ANSI SCSI revision: 05 Host: scsi7 Channel: 00 Id: 01 Lun: 00 Vendor: STK Model: T10000C Rev: 1.57 Type: Sequential-Access ANSI SCSI revision: 05 Host: scsi7 Channel: 00 Id: 02 Lun: 00 Vendor: HP Model: Ultrium 5-SCSI Rev: I3CS Type: Sequential-Access ANSI SCSI revision: 06 Host: scsi7 Channel: 00 Id: 03 Lun: 00 Vendor: HP Model: Ultrium 5-SCSI Rev: I59S Type: Sequential-Access ANSI SCSI revision: 06 Host: scsi7 Channel: 00 Id: 04 Lun: 00 Vendor: IBM Model: ULTRIUM-TD5 Rev: B173 Type: Sequential-Access ANSI SCSI revision: 06 Host: scsi7 Channel: 00 Id: 05 Lun: 00 Vendor: IBM Model: ULTRIUM-TD5 Rev: BBN2 Type: Sequential-Access ANSI SCSI revision: 06 Host: scsi7 Channel: 00 Id: 06 Lun: 00 Vendor: HP Model: Ultrium 5-SCSI Rev: I59S Type: Sequential-Access ANSI SCSI revision: 06 Host: scsi7 Channel: 00 Id: 07 Lun: 00 Vendor: IBM Model: ULTRIUM-TD5 Rev: BBN2 Type: Sequential-Access ANSI SCSI revision: 06 Host: scsi7 Channel: 00 Id: 08 Lun: 00 Vendor: STK Model: T10000D Rev: 406. Type: Sequential-Access ANSI SCSI revision: 05 Host: scsi7 Channel: 00 Id: 09 Lun: 00 Vendor: STK Model: T10000D Rev: 406. Type: Sequential-Access ANSI SCSI revision: 05 #
可发出以下命令来列出 IBM 磁带设备编号和驱动程序版本:
# cat /proc/scsi/IBMtape
lin_tape version: 1.76.0 lin_tape major number: 252 Attached Tape Devices: Number model SN HBA SCSI FO Path 0 ULTRIUM-TD5 1068008446 lpfc 7:0:4:0 NA 1 ULTRIUM-TD5 9068800738 lpfc 7:0:5:0 NA 2 ULTRIUM-TD5 9068800775 lpfc 7:0:7:0 NA #
可发出以下命令来确定磁带机是否正在通信。还将返回磁带机序列号。
# sg_inq /dev/sg3
standard INQUIRY:
PQual=0 Device_type=1 RMB=1 version=0x05 [SPC-3]
[AERC=0] [TrmTsk=0] NormACA=0 HiSUP=0 Resp_data_format=2
SCCS=0 ACC=0 TPGS=1 3PC=0 Protect=1 BQue=0
EncServ=0 MultiP=1 (VS=0) [MChngr=0] [ACKREQQ=0] Addr16=0
[RelAdr=0] WBus16=0 Sync=0 Linked=0 [TranDis=0] CmdQue=0
[SPI: Clocking=0x0 QAS=0 IUS=0]
length=74 (0x4a) Peripheral device type: tape
Vendor identification: STK
Product identification: T10000C
Product revision level: 1.57
Unit serial number: 576001000504
#
可发出以下命令来获取当前磁带机状态详细信息。
# mt -f /dev/st2 status
SCSI 2 tape drive: File number=0, block number=0, partition=0. Tape block size 0 bytes. Density code 0x4c (no translation). Soft error count since last status=0 General status bits on (41010000): BOT ONLINE IM_REP_EN #
LTFS-LE 磁带机转储位于 /var/log 中。
# ls /var/log/ltfs*
# ls /var/log/ltfs* /var/log/ltfs_20130522_063813_HU1246T79Y.ltd /var/log/ltfs_20130610_094800_HU1246T79Y.ltd /var/log/ltfs_20130522_083536_HU1246T79Y.ltd /var/log/ltfs_20130610_094828_HU1246T7B4.ltd /var/log/ltfs_20130522_093815_HU1246T79Y.ltd /var/log/ltfs_20130610_144131_HU19477N8F.ltd /var/log/ltfs_20130523_114650_HU1246T7B4.ltd /var/log/ltfs_2013_0610_144600.dmp /var/log/ltfs_20130523_114917_HU1246T7B4.ltd /var/log/ltfs_2013_0610_144600_f.dmp #
可发出以下系列命令来获取 SCSI 跟踪。
显示当前级别:
# sysctl dev.scsi.logging_level dev.scsi.logging_level = 0
如果不是级别 128,请启用级别 128:
# sysctl -w dev.scsi.logging_level=128 dev.scsi.logging_level = 128
要获取短时间内的非常详细的 scsi 日志记录,请启用级别 -1:
# sysctl -w dev.scsi.logging_level=-1 dev.scsi.logging_level = -1
日志输出将位于 /var/log/messages 中。
可发出以下命令来显示关于当前正在运行的 OEL 版本的信息。
# uname -a && cat /etc/*release
Linux busch.central.sun.com 2.6.18-194.el5 #1 SMP Tue Mar 16 21:52:39 EDT 2010 x86_64 x86_64 x86_64 GNU/Linux Red Hat Enterprise Linux Server release 6.5 (Santiago)
可发出以下命令来显示详细的磁带机和介质状态详细信息。
# tapeinfo -f /dev/sg2
Product Type: Tape Drive
Vendor ID: 'HP '
Product ID: 'Ultrium 5-SCSI '
Revision: 'I59S'
Attached Changer: No
SerialNumber: 'HU19477N8F'
MinBlock:1
MaxBlock:16777215
SCSI ID: 0
SCSI LUN: 0
Ready: yes
BufferedMode: yes
Medium Type: Not Loaded
Density Code: 0x58
BlockSize: 0
DataCompEnabled: yes
DataCompCapable: yes
DataDeCompEnabled: yes
CompType: 0x1
DeCompType: 0x1
BOP: yes
Block Position: 0
#
可发出以下命令来显示文件系统信息,以及已使用的空间和可用空间。
# df
Filesystem 1K-blocks Used Available Use% Mounted on
/dev/mapper/VolGroup00-LogVol00
525579536 18681380 479769532 4% /
/dev/sda1 988088 29736 907348 4% /boot
tmpfs 12265656 0 12265656 0% /dev/shm
/mnt/LTFS_LE/metadata
525579536 18681380 479769532 4% /LTFSLE
ltfs 4383036416 0 4383036416 0% /mnt/LTFS_LE/objects/loss_576004000641
#
注:
标签为 ltfs 的文件系统挂载在序列号为 576004000641 的磁带机上。# mount /dev/mapper/VolGroup00-LogVol00 on / type ext3 (rw) proc on /proc type proc (rw) sysfs on /sys type sysfs (rw) devpts on /dev/pts type devpts (rw,gid=5,mode=620) /dev/sda1 on /boot type ext3 (rw) tmpfs on /dev/shm type tmpfs (rw) none on /proc/sys/fs/binfmt_misc type binfmt_misc (rw) sunrpc on /var/lib/nfs/rpc_pipefs type rpc_pipefs (rw) /mnt/LTFS_LE/metadata on /LTFSLE type LTFS_LE (rw,dir=/mnt/LTFS_LE/metadata/,debug=1) ltfs on /mnt/LTFS_LE/objects/loss_HU19477NE4 type fuse (rw,nosuid,nodev,default_permissions,allow_other) ltfs on /mnt/LTFS_LE/objects/loss_576004000641 type fuse (rw,nosuid,nodev,default_permissions,allow_other) #
可发出以下命令来确定哪些进程当前在文件系统上打开了文件。
# lsof /mnt/LTFS_LE/objects/loss_576004000641
COMMAND PID USER FD TYPE DEVICE SIZE/OFF NODE NAME vi 21155 root 3u REG 0,23 12288 7 /mnt/LTFS_LE/objects/loss_576004000641/.mjg.swp #
可发出以下命令来显示当前正在运行的 LTFS-OE 版本。
# ltfs -V
LTFS version 2.0.0 (20130108_orcl) LTFS Format Specification version 2.0.0 # # rpm -q ltfs ltfs-1.2.5_lto6-20130501_orcl_oels_5_5_t10kd #
当磁带机上发生单元警示时可发出以下命令。
# sg_turs -v /dev/sg5
test unit ready cdb: 00 00 00 00 00 00
test unit ready: Fixed format, current; Sense key: Unit Attention
Additional sense: Import or export element accessed
Completed 1 Test Unit Ready commands with 1 errors
# sg_logs --verbose /dev/sg5
inquiry cdb: 12 00 00 00 24 00
STK SL150 0182
log sense cdb: 4d 00 40 00 00 00 00 00 04 00
log sense cdb: 4d 00 40 00 00 00 00 00 08 00
log sense: requested 8 bytes but got 7 bytes
Supported log pages:
0x00 Supported log pages
0x07 Last n error events
0x2e TapeAlert (smc-3)
#
要获取所有字节,请将 -H 添加到 sg_logs 命令。
# sg_logs --all /dev/sg5
STK T10000C 1.57
Supported log pages:
0x00 Supported log pages
0x02 Error counters (write)
0x03 Error counters (read)
0x06 Non-medium errors
0x0c Sequential access device (ssc-2)
0x17 ??
0x2e TapeAlert (ssc-2)
0x31 [unknown vendor specific page code]
0x3b [unknown vendor specific page code]
0x3c [unknown vendor specific page code]
Write error counter page
Errors corrected without substantial delay = 0
Errors corrected with possible delays = 0
Total rewrites or rereads = 0
Total errors corrected = 0
Total times correction algorithm processed = 0
Total bytes processed = 2929
Total uncorrected errors = 0
Read error counter page
Errors corrected without substantial delay = 0
Errors corrected with possible delays = 0
Total rewrites or rereads = 0
Total errors corrected = 0
Total times correction algorithm processed = 0
Total bytes processed = 3875
Total uncorrected errors = 0
Non-medium error page
Non-medium error count = 0
Sequential access device page (ssc-3)
Data bytes received with WRITE commands: 0 GB
Data bytes written to media by WRITE commands: 0 GB
Data bytes read from media by READ commands: 0 GB
Data bytes transferred by READ commands: 0 GB
Cleaning action not required (or completed)
Vendor specific parameter [0x8000] value: 2257920
No ascii information for page = 0x17, here is hex:
00 17 00 00 14 02 03 43 10 07 00 00 00 00 00 00 7a
10 07 00 00 01 00 00 00 01
Tape alert page (ssc-3) [0x2e]
Read warning: 0
Write warning: 0
Hard error: 0
Media: 0
Read failure: 0
Write failure: 0
Media life: 0
Not data grade: 0
Write protect: 0
No removal: 0
Cleaning media: 0
Unsupported format: 0
Recoverable mechanical cartridge failure: 0
Unrecoverable mechanical cartridge failure: 0
Memory chip in cartridge failure: 0
Forced eject: 0
Read only format: 0
Tape directory corrupted on load: 0
Nearing media life: 0
Cleaning required: 0
Cleaning requested: 0
Expired cleaning media: 0
Invalid cleaning tape: 0
Retension requested: 0
Dual port interface error: 0
Cooling fan failing: 0
Power supply failure: 0
Power consumption: 0
Drive maintenance: 0
Hardware A: 0
Hardware B: 0
Interface: 0
Eject media: 0
Microcode update fail: 0
Drive humidity: 0
Drive temperature: 0
Drive voltage: 0
Predictive failure: 0
Diagnostics required: 0
Obsolete (28h): 0
Obsolete (29h): 0
Obsolete (2Ah): 0
Obsolete (2Bh): 0
Obsolete (2Ch): 0
Obsolete (2Dh): 0
Obsolete (2Eh): 0
Reserved (2Fh): 0
Reserved (30h): 0
Reserved (31h): 0
Lost statistics: 0
Tape directory invalid at unload: 0
Tape system area write failure: 0
Tape system area read failure: 0
No start of data: 0
Loading failure: 0
Unrecoverable unload failure: 0
Automation interface failure: 0
Firmware failure: 0
WORM medium - integrity check failed: 0
WORM medium - overwrite attempted: 0
Reserved parameter code 0x3d, flag: 0
Reserved parameter code 0x3e, flag: 0
Reserved parameter code 0x3f, flag: 0
Reserved parameter code 0x40, flag: 0
No ascii information for page = 0x31, here is hex:
00 31 00 00 20 00 01 c0 04 00 00 22 74 00 02 c0 04
10 00 41 4f f5 00 03 c0 04 00 00 22 e7 00 04 c0 04
20 00 41 4f f5
No ascii information for page = 0x3b, here is hex:
00 3b 00 02 c8 01 00 74 04 00 00 00 00 01 01 74 04
10 00 00 00 00 01 02 74 04 00 00 00 00 01 03 74 04
20 00 00 00 00 01 04 74 04 00 00 00 00 01 05 74 04
30 00 00 00 00 01 10 74 04 00 00 00 00 01 11 74 04
..... [truncated after 64 of 716 bytes (use '-H' to see the rest)]
No ascii information for page = 0x3c, here is hex:
00 3c 00 0b e4 01 00 74 04 00 00 00 00 01 01 74 04
10 00 00 00 00 01 02 74 04 00 00 00 00 01 03 74 04
20 00 00 00 00 01 04 74 04 00 00 00 00 01 05 74 04
30 00 00 00 00 01 06 74 04 00 00 00 00 01 07 74 04
..... [truncated after 64 of 3048 bytes (use '-H' to see the rest)]
#