Video Screencast Help
Search Video Help Close Back
to help
New in the Rewards Catalog: Vouchers for "Symantec Technical Specialist" and "Symantec Certified Specialist" exams.

dont' see the robotic arm in the output of scan command

Updated: 21 May 2010 | 2 comments
xsanch's picture
0 0 Votes
Login to vote

Hi,

have an issue which is probably HW related on Linux (RHEL). I am not able to see the robotic arm in the output of scan command:

The scan shows me only the tape driver:
mphgt30# /usr/openv/volmgr/bin/scan
************************************************************
*********************** SDT_TAPE    ************************
*********************** SDT_CHANGER ************************
*********************** SDT_OPTICAL ************************
************************************************************
------------------------------------------------------------
Device Name  : "/dev/st/nh0c0t4l0"
Passthru Name: "/dev/sg/h0c0t4l0"
Volume Header: ""
Port: -1; Bus: -1; Target: -1; LUN: -1
Inquiry    : "QUANTUM SDLT600         2B2B"
Vendor ID  : "QUANTUM "
Product ID : "SDLT600         "
Product Rev: "2B2B"
Serial Number: "QP0720AMC00185"
WWN          : "QUANTUM SDLT600         QP0720AMC001"
WWN Id Type  : 1
Device Identifier: "QUANTUM SDLT600         QP0720AMC00185  "
Device Type    : SDT_TAPE
NetBackup Drive Type: 9
Removable      : Yes
Device Supports: SCSI-4
Flags : 0x4
Reason: 0x0

Output of the tpconfig :
mphgt30# /usr/openv/volmgr/bin/tpconfig -d
Index DriveName              DrivePath                Type    Shared   Status
***** *********              **********               ****    ******   ******
  0   Drive0                 /dev/st/nh0c0t4l0        8mm      No       UP
    TL8(0) Definition    DRIVE=1

Currently defined robotics are:
  TL8(0)     robotic path = /dev/sg/h2c0t2l0,
             volume database host = mphgt30-br

If I probe the robotic arm I got errors:
mphgt30# /usr/openv/volmgr/bin/robtest
Configured robots with local control supporting test utilities:
  TL8(0)     robotic path = /dev/sg/h2c0t2l0

Robot Selection
---------------
  1)  TL8 0
  2)  none/quit
Enter choice: 1

Robot selected: TL8(0)   robotic path = /dev/sg/h2c0t2l0

Invoking robotic test utility:
/usr/openv/volmgr/bin/tl8test -r /dev/sg/h2c0t2l0 -d1 /dev/st/nh0c0t4l0

Opening /dev/sg/h2c0t2l0
user_scsi_sense failed 1h
sense key = 0x5, asc = 0x24, ascq = 0x0, INVALID FIELD IN CDB
Enter tl8 commands (? returns help information)
init
Initiating INITIALIZE_ELEMENT_STATUS
user_scsi_sense failed 1h
sense key = 0x5, asc = 0x20, ascq = 0x0, INVALID COMMAND OPERATION CODE

This is the output of dmesg | grep scsi:
scsi : aborting command due to timeout : pid 4, scsi0, channel 0, id 4, lun 0 Inquiry 00 00 00 ff 00
mptscsih: ioc0: id=4 OldAbort: unknown target (sc=f7501000)
mptscsih: ioc0: id=4 OldReset: scheduling BUS_RESET SCSI IO (sc=f7501000)
mptscsih: ioc0: id=4 OldReset: scheduling BUS_RESET SCSI IO (sc=f7501000)

This is the output of cat /proc/scsi/scsi : 

# cat /proc/scsi/scsi
Attached devices:
Host: scsi0 Channel: 00 Id: 04 Lun: 00
  Vendor: QUANTUM  Model: SDLT600          Rev: 2B2B
  Type:   Sequential-Access                ANSI SCSI revision: 04
Host: scsi2 Channel: 00 Id: 02 Lun: 00
  Vendor: LSILOGIC Model: Logical Volume   Rev: 3000
  Type:   Direct-Access                    ANSI SCSI revision: 02
Host: scsi3 Channel: 00 Id: 00 Lun: 00
  Vendor: TEAC     Model: DW-224SL-R       Rev: 1.0B
  Type:   CD-ROM                           ANSI SCSI revision: 02
Host: scsi3 Channel: 00 Id: 00 Lun: 01
  Vendor: TEAC     Model: DW-224SL-R       Rev: 1.0B
  Type:   CD-ROM                           ANSI SCSI revision: 02
Host: scsi3 Channel: 00 Id: 00 Lun: 02
  Vendor: TEAC     Model: DW-224SL-R       Rev: 1.0B
  Type:   CD-ROM                           ANSI SCSI revision: 02
Host: scsi3 Channel: 00 Id: 00 Lun: 03
  Vendor: TEAC     Model: DW-224SL-R       Rev: 1.0B
  Type:   CD-ROM                           ANSI SCSI revision: 02
Host: scsi3 Channel: 00 Id: 00 Lun: 04
  Vendor: TEAC     Model: DW-224SL-R       Rev: 1.0B
  Type:   CD-ROM                           ANSI SCSI revision: 02
Host: scsi3 Channel: 00 Id: 00 Lun: 05
  Vendor: TEAC     Model: DW-224SL-R       Rev: 1.0B
  Type:   CD-ROM                           ANSI SCSI revision: 02
Host: scsi3 Channel: 00 Id: 00 Lun: 06
  Vendor: TEAC     Model: DW-224SL-R       Rev: 1.0B
  Type:   CD-ROM                           ANSI SCSI revision: 02
Host: scsi3 Channel: 00 Id: 00 Lun: 07
  Vendor: TEAC     Model: DW-224SL-R       Rev: 1.0B
  Type:   CD-ROM                           ANSI SCSI revision: 02

The st and sg modules are loaded:
mphgt30# lsmod | egrep 'st|sg'
sg                     37292   0  (autoclean)
st                     31556   0  (unused)
scsi_mod              116140   5  [sg ide-scsi st mptscsih sd_mod]

The modules.conf have:

options scsi_mod max_scsi_luns=255

What do you suggest ? Check cables or termination ?

Thanks,

Jorge

discussion Filed Under:

Comments

John Stockard's picture
21
Aug
2009
1 Vote +1
Login to vote

Cables, termination, power-cycle library

I would start by double-checking the SCSI cabling between your media server and the library, as well as the SCSI terminators.  You might also need to go into the BIOS for your LSILogic SCSI card and see if the SCSI card itself is automatically terminating it's end of the SCSI bus.

If the cabling looks sound, try power-cycling the library.

If it still doesn't work, you may need to call your hardware vendor to get the library serviced.

John Stockard's picture
21
Aug
2009
0 Votes 0
Login to vote

RAID controller?

Is that LSI Logic SCSI card just a regular SCSI card or is it actually a RAID controller?  I've seen issues when trying to attach tape drives and tape libraries to a RAID controller.  If you have a standalone traditional SCSI card available, try installing it into the media server and then use it to connect to the tape library.