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

MSL2024 not responding to mc commands

SOLVED
Go to solution
Norman Dignard
Regular Advisor

MSL2024 not responding to mc commands

I'm trying to script some backup routines to move tapes from/to the mail slot and tape drive. The drive is attched to a U320 scsi card using an mpt driver. The autochanger is also claimed. I ran ltt tools on the libray as well as the /usr/contrib/src/scsi_io test and all tested fine.

The mc command just gives me errors:
mc -p /dev/rac/c9t4d1 -q
ERROR: 0x0 No Sense : 0x16 Unknown Additional Sense Code

#mc -q /dev/rac/c9t4d1
ERROR: No such file or directory
mc /dev/rac/c9t4d1 -q
ERROR: No such file or directory

In any event mpt, sctl and schgr are in the kernel
#lsdev -d sctl
Character Block Driver Class
203 -1 sctl ctl
#lsdev -d schgr
Character Block Driver Class
231 29 schgr autoch

#lsdev -d mpt
Character Block Driver Class
96 -1 mpt ext_bus

spt & spt0 are not in the kernel.

I’ve looked over tech notes KBAN00000190 and OV-EN010365 and it’s reference in the Data Protector 5.0 Installation and Licensing Guide, page B25, according to the doc “The type of the SCSI Robotic Driver in use depends on the hardware. Systems, equipped with the GSC/HSC or PCI bus have the SCSI Autochanger Driver named schgr, and systems, equipped with the EISA bus have the SCSI Pass-Through Driver named sctl, which is already built in the kernel. However, the SCSI Pass-Through Driver used on HP Servers with NIO Bus is named spt. It is installed on the system without being built into the kernel by default.”

Note that we do not have Omniback or Data Proctector installed on the system.

In both KBAN00000190 and OV-EN010365 it states if the ext_bus is scsi1, scsi2, scsi3 use spt for the picker. If it’s C700 or c720, the picker uses sctl.

Looking at my system the ext_bus is mpt.

#ioscan
Class I H/W Path Driver S/W State H/W Type Description

============================================================================

ba 8 0/9 lba CLAIMED BUS_NEXUS Local PCI Bus Adapter (782)

ext_bus 9 0/9/0/0 mpt CLAIMED INTERFACE SCSI Ultra320 A6961-60011
/dev/mpt9

target 16 0/9/0/0.4 tgt CLAIMED DEVICE

tape 3 0/9/0/0.4.0 stape CLAIMED DEVICE HP Ultrium 3-SCSI
/dev/rmt/3m /dev/rmt/3mnb /dev/rmt/c9t4d0BESTn
/dev/rmt/3mb /dev/rmt/c9t4d0BEST
/dev/rmt/c9t4d0BESTnb
/dev/rmt/3mn /dev/rmt/c9t4d0BESTb

autoch 1 0/9/0/0.4.1 schgr CLAIMED DEVICE HP MSL G3 Series
/dev/rac/c9t4d1

target 17 0/9/0/0.7 tgt CLAIMED DEVICE

ctl 9 0/9/0/0.7.0 sctl CLAIMED DEVICE Initiator
/dev/rscsi/c9t7d0

ext_bus 10 0/9/0/1 mpt CLAIMED INTERFACE SCSI Ultra320 A6961-60011
/dev/mpt10

target 18 0/9/0/1.7 tgt CLAIMED DEVICE

ctl 10 0/9/0/1.7.0 sctl CLAIMED DEVICE Initiator
/dev/rscsi/c10t7d0


Any ideas ?
6 REPLIES
Robin T. Slotten
Trusted Contributor

Re: MSL2024 not responding to mc commands

mc -p -q is the correct syntax

# mc -p /dev/rac/c4t0d0 -q
Vendor ID : HP
Product ID : MSL6000 Series
Product Rev : 0507

# mc -q /dev/rac/c4t0d0
ERROR: No such file or directory

# mc /dev/rac/c4t0d0 -q
ERROR: No such file or directory

This is what mine looks like ( connected via a fibre switch )
# ioscan -fnkH 0/5
Class I H/W Path Driver S/W State H/W Type Description
===========================================================================
ba 6 0/5 lba CLAIMED BUS_NEXUS Local PCI-X Bus Adapter (122e)
ba 7 0/5/1/0 PCItoPCI CLAIMED BUS_NEXUS PCItoPCI Bridge
fc 2 0/5/1/0/4/0 fcd CLAIMED INTERFACE HP 2Gb PCI/PCI-X Fibre Channel FC/GigE Dual Port Combo Adapter
/dev/fcd2
fcp 1 0/5/1/0/4/0.10 fcd_fcp CLAIMED INTERFACE FCP Domain
ext_bus 4 0/5/1/0/4/0.10.10.255.0 fcd_vbus CLAIMED INTERFACE FCP Device Interface
target 41 0/5/1/0/4/0.10.10.255.0.0 tgt CLAIMED DEVICE
autoch 0 0/5/1/0/4/0.10.10.255.0.0.0 schgr CLAIMED DEVICE HP MSL6000 Series
/dev/rac/c4t0d0
tape 0 0/5/1/0/4/0.10.10.255.0.0.1 stape CLAIMED DEVICE HP Ultrium 3-SCSI
/dev/rmt/0m /dev/rmt/0mn /dev/rmt/c4t0d1BEST /dev/rmt/c4t0d1BESTn
/dev/rmt/0mb /dev/rmt/0mnb /dev/rmt/c4t0d1BESTb /dev/rmt/c4t0d1BESTnb
tape 1 0/5/1/0/4/0.10.10.255.0.0.2 stape CLAIMED DEVICE HP Ultrium 3-SCSI
/dev/rmt/1m /dev/rmt/1mn /dev/rmt/c4t0d2BEST /dev/rmt/c4t0d2BESTn
/dev/rmt/1mb /dev/rmt/1mnb /dev/rmt/c4t0d2BESTb /dev/rmt/c4t0d2BESTnb
lan 3 0/5/1/0/6/0 igelan CLAIMED INTERFACE HP A9782-60001 PCI/PCI-X 1000Base-SX FC/GigE Combo Adapter

# lsdev -d sctl
Character Block Driver Class
203 -1 sctl ctl
# lsdev -d schgr
Character Block Driver Class
231 29 schgr autoch
# lsdev -d mpt
Character Block Driver Class
57 -1 mpt ext_bus
#

Your configuration loks OK. Did you reboot your tape library?
IF you do it more than twice, write a script.
Curtis Ballard
Honored Contributor

Re: MSL2024 not responding to mc commands

Very complete posting thank you.

There is a drive firmware defect in a one revision of each Ultrium drive that was available for a short time that causes this error. There is also a defect in mc where it doesn't handle the error response correctly. The drive firmware is fixed and posted. The mc fix in in progress.

You need G54W firmware in your parallel SCSI Ultrium 3 drive.

The drive firmware revisions with the fix are:
Ultrium 1 HH - P54W
Ultrium 2 HH - S54W
Ultrium 2 FH - F68W
Ultrium 2 Fibre Channel - K46W or K620
Ultrium 3 SCSI - G54W
Ultrium 3 Fibre Channel 2GB - L57W or L58S
Ultrium 3 Fibre Channel 4GB - M22W

It was a timing issue that so far only mc exposes. When a "Read Element Status" command was issued to the library it would complete and return data and the drive would put the command complete condition on an internal queue which took a fraction of a second to process. There are a few commands that the drive can't pass on to the library unless the previous command has completed and mc will turn around and fire off one of those immediately following the RES command. Often the next command gets there before the drive has processed the command complete condition and the drive returns a SCSI Check Condition with an ASC/ASCQ of 0x00/0x16 which is Command in Progress. The mc utility should understand that UA and retry the command but it doesn't.
Norman Dignard
Regular Advisor

Re: MSL2024 not responding to mc commands

I did reboot both the library and the hos but I still get the same results. I even recreated the device file but that did not work.

#mc -p /dev/rac/c9t4d1 -q
ERROR: 0x2 Not Ready : 0x401 Logical unit in process of becoming ready

The above was when the library was being excerised via the Web console (moving a tape). Below is the results after all library operations had completed.

root@cmssf3/dev #mc -p /dev/rac/c9t4d1 -q
ERROR: 0x0 No Sense : 0x16 Unknown Additional Sense Code

I did check the firwware on the MSL.
The library is 2.40/1.66e with bootcode fw
0.50. The drive is at G53W. I don't know why the drive firware is affecting the library mc responses but I'll take your work for it. I'll try to get the drive firmware updated.

Curtis Ballard
Honored Contributor
Solution

Re: MSL2024 not responding to mc commands

The drive firmware effects the library responses to mc because in this library the drive proxies the SCSI port for the library and every command goes to the drive first which then passes it on to the library.
Luk Vandenbussche
Honored Contributor

Re: MSL2024 not responding to mc commands

Try this

mc -p /dev/rac/c9t4d1 -r ISDM
Norman Dignard
Regular Advisor

Re: MSL2024 not responding to mc commands

Upgrading the firmware on both the library and drive resolved the mc cmd errors.