Hi Team, Tape library on my server showing all drives as AVR mode. Pls help Thanks

@Venki009 - please help us to help you and reply to the questions we have been asking. Not sure why you have started a new discussion: Library in AVR mode without giving us any information about your environment. Have a look at this TN and previous discussions for troubleshooting tips and type of information needed: http://www.symantec.com/docs/TECH38829 https://www-secure.symantec.com/connect/forums/all-drives-are-avr-state https://www-secure.symantec.com/connect/forums/all-tape-drives-are-avr-state

All drives showing AVR

Marianne
Level 6
11 years ago
Thanks for telling us that it is Linux.
You have selected Solaris as OS.

Was everything working fine previously? If so, what has changed?

It seems that the OS has lost connectivity to the robot and the drives.
Have you checked the robot console and/or GUI interface for errors?
If SAN connected - have you checked switch logs?
Physical connectivity - cables, etc?

Please check what the OS sees:

cat /proc/scsi/scsi
Venki009
Level 4
11 years ago
Hi,

cat /proc/scsi/scsi
Attached devices:
Host: scsi0 Channel: 00 Id: 00 Lun: 00
Vendor: IBM-ESXS Model: ST9600205SS      Rev: B552
Type:   Direct-Access                    ANSI SCSI revision: 06
Host: scsi0 Channel: 00 Id: 01 Lun: 00
Vendor: IBM-ESXS Model: ST9600205SS      Rev: B552
Type:   Direct-Access                    ANSI SCSI revision: 06
Host: scsi0 Channel: 01 Id: 03 Lun: 00
Vendor: LSILOGIC Model: Logical Volume   Rev: 3000
Type:   Direct-Access                    ANSI SCSI revision: 02
Host: scsi2 Channel: 00 Id: 00 Lun: 00
Vendor: IBM      Model: 1746      FAStT Rev: 1070
Type:   Direct-Access                    ANSI SCSI revision: 05
Host: scsi2 Channel: 00 Id: 00 Lun: 31
Vendor: IBM      Model: Universal Xport Rev: 1070
Type:   Direct-Access                    ANSI SCSI revision: 05
Host: scsi2 Channel: 00 Id: 01 Lun: 00
Vendor: IBM      Model: 1746      FAStT Rev: 1070
Type:   Direct-Access                    ANSI SCSI revision: 05
Host: scsi2 Channel: 00 Id: 01 Lun: 31
Vendor: IBM      Model: Universal Xport Rev: 1070
Type:   Direct-Access                    ANSI SCSI revision: 05
Host: scsi2 Channel: 00 Id: 02 Lun: 00
Vendor: IBM      Model: 1746      FAStT Rev: 1070
Type:   Direct-Access                    ANSI SCSI revision: 05
Host: scsi2 Channel: 00 Id: 02 Lun: 01
Vendor: IBM      Model: 1746      FAStT Rev: 1070
Type:   Direct-Access                    ANSI SCSI revision: 05
Host: scsi2 Channel: 00 Id: 02 Lun: 02
Vendor: IBM      Model: 1746      FAStT Rev: 1070
Type:   Direct-Access                    ANSI SCSI revision: 05
Host: scsi2 Channel: 00 Id: 02 Lun: 03
Vendor: IBM      Model: 1746      FAStT Rev: 1070
Type:   Direct-Access                    ANSI SCSI revision: 05
Host: scsi2 Channel: 00 Id: 02 Lun: 04
Vendor: IBM      Model: 1746      FAStT Rev: 1070
Type:   Direct-Access                    ANSI SCSI revision: 05
Host: scsi2 Channel: 00 Id: 02 Lun: 05
Vendor: IBM      Model: 1746      FAStT Rev: 1070
Type:   Direct-Access                    ANSI SCSI revision: 05
Host: scsi2 Channel: 00 Id: 02 Lun: 31
Vendor: IBM      Model: Universal Xport Rev: 1070
Type:   Direct-Access                    ANSI SCSI revision: 05
Host: scsi2 Channel: 00 Id: 03 Lun: 00
Vendor: IBM      Model: 1746      FAStT Rev: 1070
Type:   Direct-Access                    ANSI SCSI revision: 05
Host: scsi2 Channel: 00 Id: 03 Lun: 01
Vendor: IBM      Model: 1746      FAStT Rev: 1070
Type:   Direct-Access                    ANSI SCSI revision: 05
Host: scsi2 Channel: 00 Id: 03 Lun: 02
Vendor: IBM      Model: 1746      FAStT Rev: 1070
Type:   Direct-Access                    ANSI SCSI revision: 05
Host: scsi2 Channel: 00 Id: 03 Lun: 03
Vendor: IBM      Model: 1746      FAStT Rev: 1070
Type:   Direct-Access                    ANSI SCSI revision: 05
Host: scsi2 Channel: 00 Id: 03 Lun: 04
Vendor: IBM      Model: 1746      FAStT Rev: 1070
Type:   Direct-Access                    ANSI SCSI revision: 05
Host: scsi2 Channel: 00 Id: 03 Lun: 05
Vendor: IBM      Model: 1746      FAStT Rev: 1070
Type:   Direct-Access                    ANSI SCSI revision: 05
Host: scsi2 Channel: 00 Id: 03 Lun: 31
Vendor: IBM      Model: Universal Xport Rev: 1070
Type:   Direct-Access                    ANSI SCSI revision: 05
Host: scsi2 Channel: 00 Id: 04 Lun: 00
Vendor: IBM      Model: ULT3580-HH5      Rev: D8D5
Type:   Sequential-Access                ANSI SCSI revision: 06
Host: scsi3 Channel: 00 Id: 01 Lun: 00
Vendor: IBM      Model: VirtualDisk      Rev: 1070
Type:   Direct-Access                    ANSI SCSI revision: 05
Host: scsi3 Channel: 00 Id: 01 Lun: 01
Vendor: IBM      Model: VirtualDisk      Rev: 1070
Type:   Direct-Access                    ANSI SCSI revision: 05
Host: scsi3 Channel: 00 Id: 01 Lun: 02
Vendor: IBM      Model: VirtualDisk      Rev: 1070
Type:   Direct-Access                    ANSI SCSI revision: 05
Host: scsi3 Channel: 00 Id: 01 Lun: 03
Vendor: IBM      Model: VirtualDisk      Rev: 1070
Type:   Direct-Access                    ANSI SCSI revision: 05
Host: scsi3 Channel: 00 Id: 01 Lun: 04
Vendor: IBM      Model: VirtualDisk      Rev: 1070
Type:   Direct-Access                    ANSI SCSI revision: 05
Host: scsi3 Channel: 00 Id: 01 Lun: 05
Vendor: IBM      Model: VirtualDisk      Rev: 1070
Type:   Direct-Access                    ANSI SCSI revision: 05
Host: scsi1 Channel: 00 Id: 00 Lun: 00
Vendor: IBM      Model: 1746      FAStT Rev: 1070
Type:   Direct-Access                    ANSI SCSI revision: 05
Host: scsi1 Channel: 00 Id: 00 Lun: 01
Vendor: IBM      Model: 1746      FAStT Rev: 1070
Type:   Direct-Access                    ANSI SCSI revision: 05
Host: scsi1 Channel: 00 Id: 00 Lun: 02
Vendor: IBM      Model: 1746      FAStT Rev: 1070
Type:   Direct-Access                    ANSI SCSI revision: 05
Host: scsi1 Channel: 00 Id: 00 Lun: 03
Vendor: IBM      Model: 1746      FAStT Rev: 1070
Type:   Direct-Access                    ANSI SCSI revision: 05
Host: scsi1 Channel: 00 Id: 00 Lun: 04
Vendor: IBM      Model: 1746      FAStT Rev: 1070
Type:   Direct-Access                    ANSI SCSI revision: 05
Host: scsi1 Channel: 00 Id: 00 Lun: 05
Vendor: IBM      Model: 1746      FAStT Rev: 1070
Type:   Direct-Access                    ANSI SCSI revision: 05
Host: scsi1 Channel: 00 Id: 00 Lun: 31
Vendor: IBM      Model: Universal Xport Rev: 1070
Type:   Direct-Access                    ANSI SCSI revision: 05
Host: scsi1 Channel: 00 Id: 01 Lun: 00
Vendor: IBM      Model: ULT3580-HH5      Rev: D8D5
Type:   Sequential-Access                ANSI SCSI revision: 06
Host: scsi1 Channel: 00 Id: 01 Lun: 01
Vendor: IBM      Model: 3573-TL          Rev: C.20
Type:   Medium Changer                   ANSI SCSI revision: 05
Host: scsi1 Channel: 00 Id: 02 Lun: 00
Vendor: IBM      Model: 1746      FAStT Rev: 1070
Type:   Direct-Access                    ANSI SCSI revision: 05
Host: scsi1 Channel: 00 Id: 02 Lun: 01
Vendor: IBM      Model: 1746      FAStT Rev: 1070
Type:   Direct-Access                    ANSI SCSI revision: 05
Host: scsi1 Channel: 00 Id: 02 Lun: 02
Vendor: IBM      Model: 1746      FAStT Rev: 1070
Type:   Direct-Access                    ANSI SCSI revision: 05
Host: scsi1 Channel: 00 Id: 02 Lun: 03
Vendor: IBM      Model: 1746      FAStT Rev: 1070
Type:   Direct-Access                    ANSI SCSI revision: 05
Host: scsi1 Channel: 00 Id: 02 Lun: 04
Vendor: IBM      Model: 1746      FAStT Rev: 1070
Type:   Direct-Access                    ANSI SCSI revision: 05
Host: scsi1 Channel: 00 Id: 02 Lun: 05
Vendor: IBM      Model: 1746      FAStT Rev: 1070
Type:   Direct-Access                    ANSI SCSI revision: 05
Host: scsi1 Channel: 00 Id: 02 Lun: 31
Vendor: IBM      Model: Universal Xport Rev: 1070
Type:   Direct-Access                    ANSI SCSI revision: 05
Host: scsi2 Channel: 00 Id: 05 Lun: 00
Vendor: IBM      Model: ULT3580-HH5      Rev: D8D5
Type:   Sequential-Access                ANSI SCSI revision: 06
Host: scsi1 Channel: 00 Id: 03 Lun: 00
Vendor: IBM      Model: ULT3580-HH5      Rev: D8D5
Type:   Sequential-Access                ANSI SCSI revision: 06
Host: scsi2 Channel: 00 Id: 05 Lun: 01
Vendor: IBM      Model: 3573-TL          Rev: C.20
Type:   Medium Changer                   ANSI SCSI revision: 05
Host: scsi2 Channel: 00 Id: 04 Lun: 01
Vendor: IBM      Model: 3573-TL          Rev: C.20
Type:   Medium Changer                   ANSI SCSI revision: 05
Host: scsi1 Channel: 00 Id: 03 Lun: 01
Vendor: IBM      Model: 3573-TL          Rev: C.20
Type:   Medium Changer                   ANSI SCSI revision: 05
Venki009
Level 4
11 years ago
Hi,

My TL again reconfigure the entire drives.Now its working fine.

What is basic cause of drives going AVR mode can u please elobrate.

Thanx
Will_Restore
Level 6
11 years ago
As noted above, communication loss is the likely problem. It could be cable disconnect, bad switch or HBA. You have to trace the path from library to host, verifying each part along the way.
Marianne
Level 6
11 years ago
NBU needs the OS for device access.

All device-related troubleshooting should start at OS level.

Check /var/log/messages for errors when drives go in AVR state.

Please look at all the URLs that I posted on 4 Sept:
https://www-secure.symantec.com/connect/forums/all-drives-showing-avr#comment-10456631
Venki009
Level 4
11 years ago
Thanks all.
Venki009
Level 4
11 years ago
Hi marianne,

Again AVR mode,why this happen frequently,is any problem with drives or os.

pls help

output of /var/log/messages

Sep 6 10:41:17 SRILANKA SQLAnywhere(nb_SRILANKA): Starting checkpoint of "NBAZDB" (NBAZDB.db) at Sat Sep 06 2014 10:41

Sep 6 10:41:17 SRILANKA SQLAnywhere(nb_SRILANKA): Finished checkpoint of "NBAZDB" (NBAZDB.db) at Sat Sep 06 2014 10:41

Sep 6 10:41:17 SRILANKA SQLAnywhere(nb_SRILANKA): Finished checkpoint of "NBAZDB" (NBAZDB.db) at Sat Sep 06 2014 10:41

Sep 6 10:42:35 SRILANKA tldcd[25107]: TLD(0) opening robotic path /dev/sg16

Sep 6 10:42:35 SRILANKA tldcd[25107]: TLD(0) opening robotic path /dev/sg16

Sep 6 10:43:35 SRILANKA kernel: qla2xxx 0000:29:00.0: scsi(1:1:1): Abort command issued -- 1 10704a6d 2002.

Sep 6 10:43:35 SRILANKA kernel: qla2xxx 0000:29:00.0: scsi(1:1:1): Abort command issued -- 1 10704a6d 2002.

Sep 6 10:43:35 SRILANKA kernel: scsi 1:0:1:1: timing out command, waited 60s

Sep 6 10:43:35 SRILANKA kernel: scsi 1:0:1:1: timing out command, waited 60s

Sep 6 10:43:35 SRILANKA tldcd[25107]: TLD(0) mode_sense ioctl() failed: Success

Sep 6 10:43:35 SRILANKA tldcd[25107]: TLD(0) mode_sense ioctl() failed: Success

Sep 6 10:43:37 SRILANKA tldcd[25107]: tldcd.c.3021, process_request(), received command=9, from peername=172.27.195.56, version 50

Sep 6 10:43:37 SRILANKA tldcd[25107]: tldcd.c.3021, process_request(), received command=9, from peername=172.27.195.56, version 50

Sep 6 10:43:37 SRILANKA tldcd[25107]: TLD(0) opening robotic path /dev/sg16

Sep 6 10:43:37 SRILANKA tldcd[25107]: TLD(0) opening robotic path /dev/sg16

Sep 6 10:44:37 SRILANKA kernel: qla2xxx 0000:29:00.0: scsi(1:1:1): Abort command issued -- 1 10704a8d 2002.

Sep 6 10:44:37 SRILANKA kernel: qla2xxx 0000:29:00.0: scsi(1:1:1): Abort command issued -- 1 10704a8d 2002.

Sep 6 10:44:37 SRILANKA kernel: scsi 1:0:1:1: timing out command, waited 60s

Sep 6 10:44:37 SRILANKA kernel: scsi 1:0:1:1: timing out command, waited 60s

Sep 6 10:44:37 SRILANKA tldcd[25107]: TLD(0) mode_sense ioctl() failed: Success

Sep 6 10:44:37 SRILANKA tldcd[25107]: TLD(0) mode_sense ioctl() failed: Success

Sep 6 10:44:37 SRILANKA tldd[25098]: DecodeQuery() Actual status: Unable to sense robotic device

Sep 6 10:44:37 SRILANKA tldd[25098]: DecodeQuery() Actual status: Unable to sense robotic device

Sep 6 10:44:37 SRILANKA tldd[25098]: TLD(0) unavailable: initialization failed: Unable to sense robotic device

Sep 6 10:44:37 SRILANKA tldd[25098]: TLD(0) unavailable: initialization failed: Unable to sense robotic device

Sep 6 10:46:39 SRILANKA tldcd[25107]: TLD(0) opening robotic path /dev/sg16

Sep 6 10:46:39 SRILANKA tldcd[25107]: TLD(0) opening robotic path /dev/sg16

Sep 6 10:47:39 SRILANKA kernel: qla2xxx 0000:29:00.0: scsi(1:1:1): Abort command issued -- 1 10704aea 2002.

Sep 6 10:47:39 SRILANKA kernel: qla2xxx 0000:29:00.0: scsi(1:1:1): Abort command issued -- 1 10704aea 2002.

Sep 6 10:47:39 SRILANKA kernel: scsi 1:0:1:1: timing out command, waited 60s

Sep 6 10:47:39 SRILANKA kernel: scsi 1:0:1:1: timing out command, waited 60s

Sep 6 10:47:39 SRILANKA tldcd[25107]: TLD(0) mode_sense ioctl() failed: Success

Sep 6 10:47:39 SRILANKA tldcd[25107]: TLD(0) mode_sense ioctl() failed: Success

Sep 6 10:47:41 SRILANKA tldcd[25107]: tldcd.c.3021, process_request(), received command=9, from peername=172.27.195.56, version 50

Sep 6 10:47:41 SRILANKA tldcd[25107]: tldcd.c.3021, process_request(), received command=9, from peername=172.27.195.56, version 50

Sep 6 10:47:41 SRILANKA tldcd[25107]: TLD(0) opening robotic path /dev/sg16

Sep 6 10:47:41 SRILANKA tldcd[25107]: TLD(0) opening robotic path /dev/sg16

Sep 6 10:48:41 SRILANKA kernel: qla2xxx 0000:29:00.0: scsi(1:1:1): Abort command issued -- 1 10704b12 2002.

Sep 6 10:48:41 SRILANKA kernel: qla2xxx 0000:29:00.0: scsi(1:1:1): Abort command issued -- 1 10704b12 2002.

Sep 6 10:48:41 SRILANKA kernel: scsi 1:0:1:1: timing out command, waited 60s

Sep 6 10:48:41 SRILANKA kernel: scsi 1:0:1:1: timing out command, waited 60s

Sep 6 10:48:41 SRILANKA tldcd[25107]: TLD(0) mode_sense ioctl() failed: Success

Sep 6 10:48:41 SRILANKA tldcd[25107]: TLD(0) mode_sense ioctl() failed: Success

Sep 6 10:48:41 SRILANKA tldd[25098]: DecodeQuery() Actual status: Unable to sense robotic device

Sep 6 10:48:41 SRILANKA tldd[25098]: DecodeQuery() Actual status: Unable to sense robotic device

Sep 6 10:48:41 SRILANKA tldd[25098]: TLD(0) unavailable: initialization failed: Unable to sense robotic device

Sep 6 10:48:41 SRILANKA tldd[25098]: TLD(0) unavailable: initialization failed: Unable to sense robotic device
Venki009
Level 4
11 years ago
Hi,

./scan
************************************************************
*********************** SDT_TAPE    ************************
*********************** SDT_CHANGER ************************
************************************************************

./robtest
Configured robots with local control supporting test utilities:
TLD(0)     robotic path = /dev/sg16

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

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

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

Opening /dev/sg16
mph999
Level 6
11 years ago
AVR is either : Drives not configured as robotic controlled Drives correctly configured, but comms failure to the robot If drives on avr on a media server that is not the robot control host, but drives on the robot control host are fine, then comms issue between tldd on the media server and tldcd on the robot control host. I don't think I have ever seen a AVR issue not caused by one of the above.
Marianne
Level 6
11 years ago
You need to log a call with your hardware vendor. Either an issue with the HBA or the robot:

Sep 6 10:44:37 SRILANKA kernel: scsi 1:0:1:1: timing out command, waited 60s

Sep 6 10:44:37 SRILANKA tldd[25098]: DecodeQuery() Actual status: Unable to sense robotic device

Sep 6 10:44:37 SRILANKA tldd[25098]: TLD(0) unavailable: initialization failed: Unable to sense robotic device

There is nothing that can be done from NBU to fix it.

Forum Discussion

All drives showing AVR

Related Content

Drive status shows AVR should be TLD

Drives Showing Missing Paths

tape drive shows active , but the ready column shows NO

Re: Drives in robot showing as Standalone

Tape drive shows no media. Inventory doesn't work.

Recent Discussions

NetBackup Virtual Appliance

Control number of VM backups running concurrently

restoring file from linux source to windows target; is possible?

MSDP 2 MSDP duplication

DR file package to NAS Share