only one drive is visible of MSL4048 tape library

[symsonu]

Hello friends,

I need help in troubleshotting the issue of MSL4048 on solaris 10

only one chnager and drive is visible and second drive is not detecting.

Kindly help

bash-3.2# sgscan
/dev/sg/c0t0l0: Disk (/dev/rdsk/c0t0d0): "HP      LOGICAL VOLUME"
/dev/sg/c0t1l0: Disk (/dev/rdsk/c0t1d0): "HP      LOGICAL VOLUME"
/dev/sg/c0tw5001438016025bfal0: Tape (/dev/rmt/0): "HP      Ultrium 4-SCSI"
/dev/sg/c0tw5001438016025bfal1: Changer: "HP      MSL G3 Series"

bash-3.2# ./tpconfig -d
Id  DriveName           Type   Residence
      Drive Path                                                       Status
****************************************************************************
0   HP.ULTRIUM4-SCSI.000 hcart  TLD(0)  DRIVE=1
      /dev/rmt/0cbn                                                    UP

Currently defined robotics are:
  TLD(0)     robotic path = /dev/sg/c0tw5001438016025bfal1

EMM Server = khombs1bl

bash-3.2# vmoprcmd

                           HOST STATUS
Host Name                                  Version   Host Status
=========================================  =======   ===========
khombs1bl                                  750400    ACTIVE

                                PENDING REQUESTS

                                    <NONE>

                                  DRIVE STATUS

Drive Name               Label   Ready  RecMID  ExtMID  Wr.Enbl.  Type
    Host                       DrivePath                            Status
=============================================================================
HP.ULTRIUM4-SCSI.000     No      No                     No        hcart
    khombs1bl                  /dev/rmt/0cbn                        TLD

only one drive as shown above. How to detect second drive

At solaris level :-->

bash-3.2# iostat -En | grep -i rmt
rmt/0            Soft Errors: 0 Hard Errors: 0 Transport Errors: 0
bash-3.2#

bash-3.2# cfgadm -al | grep -i tape
c1::5001438016025bfa           tape         connected    configured   unknown
bash-3.2#

It looks loke second drive is not getting detetcted at OS level...

How to move forward ?

Regards

S.

[Marianne]

It looks like second drive is not getting detetcted at OS level...

How to move forward ?

Check physical connection.
If connected via a switch, check zoning. 

Use hardware installation documentation to ensure connections are done correctly.

[Michael_G_Ander · Accepted solution]

Have experienced a similar issue, where the cause of the the problem was the order of the SCSI/LUN number between the control path tape drive and robot, in our case the robot should have a higher number than the control path tape drive.

On another robot the problem was the SCSI terminators hadn't implemented on the relevant tape drives

Hope this help

[symsonu]

Hello Michael,

can you please elaborate .I could not understand

as how to check these? and correct it please

[Marianne]

All of the info in Michael's post should also be contained in hardware installation documentation.
These docs normally have diagrams with detailed description.

Your other option is to contact your hardware support team.

[Michael_G_Ander]

In the first case the robot should be LUN 1 and the tape it was controlled through LUN 0 else we couldn't see the that tape drive. As Mariane said it should be documented in the manual for the robot

In the second case the SCSI terminators was not installed from the supplier, in our case they hang in a small bag on the back of the tape drives. The solution was to shutdown down the robot, install the terminators, start up the robot. It should be documented in the manual for the robot, if terminators is needed on the tape drives

[jim_dalton]

along similar lines...check the serial of the drive you can see. IIRC and as mentioned by MGA and others this robot puts the robotics and the drive through one of the drive paths and you can choose which. As you can see the robot then it'll then tell u which drive it cant see. Check the admin gui for the robot to see how its defined there: http://robot.ip.or.name. Login as administrator.Jim 

[Yasuhisa_Ishika · Accepted solution]

Check hardware connectivity and SAN zoning. Each tape drives in MSL4048 has its own FC or SAS port. In your command outputs, only one drive(drive 1 in MSL) is visible from Solaris. Correct connectivity issue and run devfsadm to let Solaris recognize tape drives.

After tape drives become vidible from Solaris, you need to reconfigure sg driver configuration sg.build and sg.install. Check Device Configuration Guide for more detail.