Tape Drive - HPE StoreEver LTO-6 Ultrium 6250

Issues related to hardware problems
Post Reply
kavd85
Posts: 1
Joined: 2016/09/23 16:55:39

Tape Drive - HPE StoreEver LTO-6 Ultrium 6250

Post by kavd85 » 2016/09/23 18:46:32

HI, some weeks ago, I Installed a Tape Drive on VMWare, and create a Virtual Machine with CentOS 6.7.

cat /etc/redhat-release
CentOS release 6.7 (Final)

Linux xxxx 2.6.32-573.el6.x86_64


Initially could see information about tape.
tapeinfo -f /dev/st0
Product Type: Tape Drive
Vendor ID: 'HP '
Product ID: 'Ultrium 6-SCSI '
Revision: '353D'
Attached Changer API: No
SerialNumber: 'HUJ5314CPA'
MinBlock: 1
MaxBlock: 16777215
SCSI ID: 0
SCSI LUN: 0
Ready: yes
BufferedMode: yes
Medium Type: Not Loaded
Density Code: 0x5a
BlockSize: 0
DataCompEnabled: yes
DataCompCapable: yes
DataDeCompEnabled: yes
CompType: 0x1
DeCompType: 0x1
BOP: yes
Block Position: 0
ActivePartition: 0
EarlyWarningSize: 0
NumPartitions: 0
MaxPartitions: 3

in this moment I can execute the next comand
mt -f /dev/nst0 status
SCSI 2 tape drive:
File number=0, block number=0, partition=0.
Tape block size 0 bytes. Density code 0x5a (no translation).
Soft error count since last status=0
General status bits on (41010000):
BOT ONLINE IM_REP_EN

|cpio -ovH -O /dev/nst0

after I execute

cpio -itv -I /dev/nst0 and show thw next message

Found end of tape. Load next tape and press RETURN.

Now I load the tape, but don't discover nothing and execute the comand

mt -f /dev/nst0 status

but say

/dev/nst0: Device or resource busy

sometimes when I execute th same comand in the log appear

kernel: INFO: task mt:1560 blocked for more than 120 seconds.
kernel: Not tainted 2.6.32-573.el6.x86_64 #1
kernel: "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
kernel: mt D 0000000000000001 0 1560 1509 0x00000084
kernel: ffff8801bb4aba38 0000000000000082 0000000000000000 ffff8801b5912ac0
kernel: ffff8801b61f9000 ffff8801b591d480 000000571226fbf8 ffff8801b61f9000
kernel: ffff8801bb4aba58 0000000100011f1a ffff8801b768e5f8 ffff8801bb4abfd8
kernel: Call Trace:
kernel: [<ffffffff81539085>] schedule_timeout+0x215/0x2e0
kernel: [<ffffffff81291d87>] ? kobject_put+0x27/0x60
kernel: [<ffffffff81538d03>] wait_for_common+0x123/0x180
kernel: [<ffffffff810672b0>] ? default_wake_function+0x0/0x20
kernel: [<ffffffff81538e1d>] wait_for_completion+0x1d/0x20
kernel: [<ffffffffa01372ba>] st_do_scsi.clone.0+0x21a/0x390 [st]
kernel: [<ffffffffa0138e62>] check_tape+0x112/0x860 [st]
kernel: [<ffffffffa013974e>] st_open+0x19e/0x2d0 [st]
kernel: [<ffffffff81195e25>] chrdev_open+0x125/0x230
kernel: [<ffffffff81195d00>] ? chrdev_open+0x0/0x230
kernel: [<ffffffff8118eac2>] __dentry_open+0x122/0x380
kernel: [<ffffffff8123ab72>] ? selinux_inode_permission+0x72/0xb0
kernel: [<ffffffff8123261f>] ? security_inode_permission+0x1f/0x30
kernel: [<ffffffff8118ee34>] nameidata_to_filp+0x54/0x70
kernel: [<ffffffff811a4cc0>] do_filp_open+0x6d0/0xd20
kernel: [<ffffffff8129d79a>] ? strncpy_from_user+0x4a/0x90
kernel: [<ffffffff811b1ba2>] ? alloc_fd+0x92/0x160
kernel: [<ffffffff8118e867>] do_sys_open+0x67/0x130
kernel: [<ffffffff8118e970>] sys_open+0x20/0x30
kernel: [<ffffffff8100b0d2>] system_call_fastpath+0x16/0x1b

Has anyone had a similar problem?

Post Reply