Video Screencast Help
Symantec to Separate Into Two Focused, Industry-Leading Technology Companies. Learn more.

All tape drives are in AVR state.

Created: 19 Nov 2012 • Updated: 20 Nov 2012 | 5 comments
This issue has been solved. See solution.

Initially backups got impacted with 96 status and now backups are not running when we have noticed I see all drives are in AVR Mode

1)Restarted media server----dint work out

2)services refreshed------dint work out

3)Device manager services stopped/restarted--dint work out..

4)when ran robtest received following error message:

Configured robots with local control supporting test utilities:
  TLD(0)     robotic path = /dev/sg/c0tw500507630f4d9c01l1

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

Robot selected: TLD(0)   robotic path = /dev/sg/c0tw500507630f4d9c01l1

Invoking robotic test utility:
/usr/openv/volmgr/bin/tldtest -rn 0 -r /dev/sg/c0tw500507630f4d9c01l1

Opening /dev/sg/c0tw500507630f4d9c01l1
MODE_SENSE complete
Enter tld commands (? returns help information)
s d
read_element_status ioctl() failed: Error 0

5)In the media and device management

under devices

unable to obtain devices.

Error:java.lang.indexoutbounds expectation index :8;size:6

see log file for details

6)tpconfig -d

 

d  DriveName           Type   Residence
      Drive Path                                                       Status
****************************************************************************
0   Hcart3-DR1-0178      hcart3 TLD(0)  DRIVE=1
      /dev/rmt/3cbn                                                    UP
1   Hcart3-DR2-0664      hcart3 TLD(0)  DRIVE=2
      /dev/rmt/2cbn                                                    UP
2   Hcart3-DR3-4743      hcart3 TLD(0)  DRIVE=3
      /dev/rmt/1cbn                                                    UP
3   Hcart3-DR4-1342      hcart3 TLD(0)  DRIVE=4
      /dev/rmt/0cbn                                                    UP

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

7)*********************************************************
*********************** SDT_TAPE    ************************
*********************** SDT_CHANGER ************************
*********************** SDT_OPTICAL ************************
************************************************************
------------------------------------------------------------
Device Name  : "/dev/rmt/1cbn"
Passthru Name: "/dev/sg/c0tw500507630f4d9c03l0"
Volume Header: ""
Port: -1; Bus: -1; Target: -1; LUN: -1
Inquiry    : "IBM     ULT3580-TD3     93G0"
Vendor ID  : "IBM     "
Product ID : "ULT3580-TD3     "
Product Rev: "93G0"
Serial Number: "1210124743"
WWN          : ""
WWN Id Type  : 0
Device Identifier: "IBM     ULT3580-TD3     1210124743"
Device Type    : SDT_TAPE
NetBackup Drive Type: 16
Removable      : Yes
Device Supports: SCSI-3
Flags : 0x0
Reason: 0x0
------------------------------------------------------------
Device Name  : "/dev/rmt/3cbn"
Passthru Name: "/dev/sg/c0tw500507630f4d9c01l0"
Volume Header: ""
Port: -1; Bus: -1; Target: -1; LUN: -1
Inquiry    : "IBM     ULT3580-TD3     93G0"
Vendor ID  : "IBM     "
Product ID : "ULT3580-TD3     "
Product Rev: "93G0"
Serial Number: "0007820178"
WWN          : ""
WWN Id Type  : 0
Device Identifier: "IBM     ULT3580-TD3     0007820178"
Device Type    : SDT_TAPE
NetBackup Drive Type: 16
Removable      : Yes
Device Supports: SCSI-3
Flags : 0x0
Reason: 0x0
------------------------------------------------------------
Device Name  : "/dev/sg/c0tw500507630f4d9c01l1"
Passthru Name: "/dev/sg/c0tw500507630f4d9c01l1"
Volume Header: ""
Port: -1; Bus: -1; Target: -1; LUN: -1
Inquiry    : "IBM     03584L32        7420"
Vendor ID  : "IBM     "
Product ID : "03584L32        "
Product Rev: "7420"
Serial Number: "0000078210390000"
WWN          : ""
WWN Id Type  : 0
Device Identifier: "IBM     03584L32        0000078210390000"
Device Type    : SDT_CHANGER
NetBackup Robot Type: 8
Removable      : Yes
Device Supports: SCSI-3
Number of Drives : 0
Number of Slots  : 0
Number of Media Access Ports: 0
Flags : 0x0
Reason: 0x0
------------------------------------------------------------
Device Name  : "/dev/rmt/2cbn"
Passthru Name: "/dev/sg/c0tw500507630f4d9c02l0"
Volume Header: ""
Port: -1; Bus: -1; Target: -1; LUN: -1
Inquiry    : "IBM     ULT3580-TD3     93G0"
Vendor ID  : "IBM     "
Product ID : "ULT3580-TD3     "
Product Rev: "93G0"
Serial Number: "0007820664"
WWN          : ""
WWN Id Type  : 0
Device Identifier: "IBM     ULT3580-TD3     0007820664"
Device Type    : SDT_TAPE
NetBackup Drive Type: 16
Removable      : Yes
Device Supports: SCSI-3
Flags : 0x0
Reason: 0x0
------------------------------------------------------------
Device Name  : "/dev/rmt/0cbn"
Passthru Name: "/dev/sg/c0tw500507630f4d9c04l0"
Volume Header: ""
Port: -1; Bus: -1; Target: -1; LUN: -1
Inquiry    : "IBM     ULT3580-TD3     93G0"
Vendor ID  : "IBM     "
Product ID : "ULT3580-TD3     "
Product Rev: "93G0"
Serial Number: "0007821342"
WWN          : ""
WWN Id Type  : 0
Device Identifier: "IBM     ULT3580-TD3     0007821342"
Device Type    : SDT_TAPE
NetBackup Drive Type: 16
Removable      : Yes
Device Supports: SCSI-3
Flags : 0x0
Reason: 0x0
 

 

Discussion Filed Under:

Comments 5 CommentsJump to latest comment

mph999's picture

It looks like you connect ok to the robot - mode_sense completes, so comms is there.

This ..

read_element_status ioctl() failed: Error 0

Looks is a hardware error.

Time to call hardware support people. ...

+

scan shows changer, but changer is not showing any drives

Device Name  : "/dev/sg/c0tw500507630f4d9c01l1"
Passthru Name: "/dev/sg/c0tw500507630f4d9c01l1"
Volume Header: ""
Port: -1; Bus: -1; Target: -1; LUN: -1
Inquiry    : "IBM     03584L32        7420"
Vendor ID  : "IBM     "
Product ID : "03584L32        "
Product Rev: "7420"
Serial Number: "0000078210390000"
WWN          : ""
WWN Id Type  : 0
Device Identifier: "IBM     03584L32        0000078210390000"
Device Type    : SDT_CHANGER
NetBackup Robot Type: 8
Removable      : Yes
Device Supports: SCSI-3
Number of Drives : 0
Number of Slots  : 0
Number of Media Access Ports: 0
Flags : 0x0
Reason: 0x0

 

Look at this example from my server

 

Device Name  : "/dev/sg/c0tw2103000d77640cc8l0"

Passthru Name: "/dev/sg/c0tw2103000d77640cc8l0"
Volume Header: ""
Port: -1; Bus: -1; Target: -1; LUN: -1
Inquiry    : "ATL     P1000           2.01"
Vendor ID  : "ATL     "
Product ID : "P1000           "
Product Rev: "2.01"
Serial Number: "0XHZ30022R"
WWN          : ""
WWN Id Type  : 0
Device Identifier: "ATL     P1000           0XHZ30022R  "
Device Type    : SDT_CHANGER
NetBackup Robot Type: 8
Removable      : Yes
Device Supports: SCSI-3
Number of Drives : 4
Number of Slots  : 30
Number of Media Access Ports: 2
Drive 1 Serial Number      : "0XHZ30022S"
Drive 2 Serial Number      : "0XHZ30022T"
Drive 3 Serial Number      : "0XHZ30022Z"
Drive 4 Serial Number      : "0XHZ300230"
Flags : 0x0
Reason: 0x0
 
 
... See how it shows the drives, compare this to yours, no drives ...
 
So yep, def looks like issue on robot.
 
Nothing can be done within NBU to fix this.
 
Martin

 

Regards,  Martin
 
Setting Logs in NetBackup:
http://www.symantec.com/docs/TECH75805
 
SOLUTION
RamNagalla's picture

 

hi Sri vani

yes, its hardware issue, check if you are able to mount tapes from the library console.

if you are not able to mount tapes into any of the drive, engaged your hardware vendor, power cycle of the library also would help some times.. 

sri vani's picture

Thank you Martin/Nagalla.

Martin Thank you so much  for detailed explanation.I have raised a hardware support call ,Hope CE will reach on site and verify the things soon.

Please check the below message:is this because of hardware error?

5)In the media and device management

under devices

unable to obtain devices.

Error:java.lang.indexoutbounds expectation index :8;size:6

see log file for details

mph999's picture

Not sure to be honest what is causing that - fix the robot first, then see how things are.

Martin

 

Regards,  Martin
 
Setting Logs in NetBackup:
http://www.symantec.com/docs/TECH75805
 
sri vani's picture

Hi Martin ,

Issue is fixed now.

SEC Card and Gripper got corrupted in the library.

we see no errors after replacement of SEC Card and Gripper.

The media device manager error also automatically fixed after this.

Thanks a bunch!!!!