Drives are in AVR mode

Question

Master (Linux, 7.0.1)

Media (Linux, 7.0.1)

Drives are in AVR mode for one media server. Server rebooted, drive reconfigured, but still issue is there.

Able to scan the drives on media server, tpconfig -l, scan -tape are working. Ran tpautoconf -a, but no luck.

Please assist.

&nbsp;

[root@mediaserver bin]# ./scan -tape | more
	************************************************************
	*********************** SDT_TAPE &nbsp; &nbsp;************************
	************************************************************
	------------------------------------------------------------
	Device Name &nbsp;: "/dev/nst3"
	Passthru Name: "/dev/sg5"
	Volume Header: ""
	Port: -1; Bus: -1; Target: -1; LUN: -1
	Inquiry &nbsp; &nbsp;: "IBM &nbsp; &nbsp; ULTRIUM-TD3 &nbsp; &nbsp; 93GM"
	Vendor ID &nbsp;: "IBM &nbsp; &nbsp; "
	Product ID : "ULTRIUM-TD3 &nbsp; &nbsp; "
	Product Rev: "93GM"
	Serial Number: "F001509031"
	WWN &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;: ""
	WWN Id Type &nbsp;: 0
	Device Identifier: "IBM &nbsp; &nbsp; ULTRIUM-TD3 &nbsp; &nbsp; F001509034"
	Device Type &nbsp; &nbsp;: SDT_TAPE
	NetBackup Drive Type: 16
	Removable &nbsp; &nbsp; &nbsp;: Yes
	Device Supports: SCSI-3
	Flags : 0x0
	Reason: 0x0
	------------------------------------------------------------
	Device Name &nbsp;: "/dev/nst4"
	Passthru Name: "/dev/sg6"
	Volume Header: ""
	Port: -1; Bus: -1; Target: -1; LUN: -1
	Inquiry &nbsp; &nbsp;: "IBM &nbsp; &nbsp; ULTRIUM-TD3 &nbsp; &nbsp; 93GM"
	Vendor ID &nbsp;: "IBM &nbsp; &nbsp; "
	Product ID : "ULTRIUM-TD3 &nbsp; &nbsp; "
	Product Rev: "93GM"
	Serial Number: "F001509037"
	WWN &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;: ""
	WWN Id Type &nbsp;: 0
	Device Identifier: "IBM &nbsp; &nbsp; ULTRIUM-TD3 &nbsp; &nbsp; F001509027"
	Device Type &nbsp; &nbsp;: SDT_TAPE
	NetBackup Drive Type: 16
	Removable &nbsp; &nbsp; &nbsp;: Yes
	Device Supports: SCSI-3
	Flags : 0x0
	Reason: 0x0
	------------------------------------------------------------
	Device Name &nbsp;: "/dev/nst2"
	Passthru Name: "/dev/sg3"
	Volume Header: ""
	Port: -1; Bus: -1; Target: -1; LUN: -1
	Inquiry &nbsp; &nbsp;: "IBM &nbsp; &nbsp; ULTRIUM-TD2 &nbsp; &nbsp; A4N0"
	Vendor ID &nbsp;: "IBM &nbsp; &nbsp; "
	Product ID : "ULTRIUM-TD2 &nbsp; &nbsp; "
	Product Rev: "A4N0"
	Serial Number: "F00150900D"
	WWN &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;: ""
	WWN Id Type &nbsp;: 0
	Device Identifier: "IBM &nbsp; &nbsp; ULTRIUM-TD2 &nbsp; &nbsp; F00150902D"
	Device Type &nbsp; &nbsp;: SDT_TAPE
	NetBackup Drive Type: 10
	Removable &nbsp; &nbsp; &nbsp;: Yes
	Device Supports: SCSI-3
	Flags : 0x0
	Reason: 0x0
	------------------------------------------------------------
	Device Name &nbsp;: "/dev/nst1"
	Passthru Name: "/dev/sg2"
	Volume Header: ""
	Port: -1; Bus: -1; Target: -1; LUN: -1
	Inquiry &nbsp; &nbsp;: "IBM &nbsp; &nbsp; ULTRIUM-TD2 &nbsp; &nbsp; A4N0"
	Vendor ID &nbsp;: "IBM &nbsp; &nbsp; "
	Product ID : "ULTRIUM-TD2 &nbsp; &nbsp; "
	Product Rev: "A4N0"
	Serial Number: "F001509007"
	WWN &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;: ""
	WWN Id Type &nbsp;: 0
	Device Identifier: "IBM &nbsp; &nbsp; ULTRIUM-TD2 &nbsp; &nbsp; F001509009"
	Device Type &nbsp; &nbsp;: SDT_TAPE
	NetBackup Drive Type: 10
	Removable &nbsp; &nbsp; &nbsp;: Yes
	Device Supports: SCSI-3
	Flags : 0x0
	Reason: 0x0
	------------------------------------------------------------
	Device Name &nbsp;: "/dev/nst0"
	Passthru Name: "/dev/sg1"
	Volume Header: ""
	Port: -1; Bus: -1; Target: -1; LUN: -1
	Inquiry &nbsp; &nbsp;: "IBM &nbsp; &nbsp; ULTRIUM-TD2 &nbsp; &nbsp; A4N0"
	Vendor ID &nbsp;: "IBM &nbsp; &nbsp; "
	Product ID : "ULTRIUM-TD2 &nbsp; &nbsp; "
	Product Rev: "A4N0"
	Serial Number: "F001509001"
	WWN &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;: ""
	WWN Id Type &nbsp;: 0
	Device Identifier: "IBM &nbsp; &nbsp; ULTRIUM-TD2 &nbsp; &nbsp; F001509006"
	Device Type &nbsp; &nbsp;: SDT_TAPE
	NetBackup Drive Type: 10
	Removable &nbsp; &nbsp; &nbsp;: Yes
	Device Supports: SCSI-3
	Flags : 0x0
	Reason: 0x0

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

[root@mediaserver bin]# ./tpconfig -l
	Device Robot Drive &nbsp; &nbsp; &nbsp; Robot &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;Drive &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;Device &nbsp; &nbsp; Second
	Type &nbsp; &nbsp; Num Index &nbsp;Type DrNum Status &nbsp;Comment &nbsp; &nbsp;Name &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; Path &nbsp; &nbsp; &nbsp; Device Path
	robot &nbsp; &nbsp; &nbsp;4 &nbsp; &nbsp;- &nbsp; &nbsp;TLD &nbsp; &nbsp;- &nbsp; &nbsp; &nbsp; - &nbsp;- &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;- &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;robotichost
	&nbsp; drive &nbsp; &nbsp;- &nbsp; &nbsp;3 hcart3 &nbsp; &nbsp;6 &nbsp; &nbsp; &nbsp;UP &nbsp;- &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;drive-hcart3-004-10 &nbsp;/dev/nst4
	&nbsp; drive &nbsp; &nbsp;- &nbsp; &nbsp;7 hcart2 &nbsp; &nbsp;5 &nbsp; &nbsp; &nbsp;UP &nbsp;- &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;drive-hcart2-004-04 &nbsp;/dev/nst3
	&nbsp; drive &nbsp; &nbsp;- &nbsp; &nbsp;8 hcart2 &nbsp; &nbsp;3 &nbsp; &nbsp; &nbsp;UP &nbsp;- &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;drive-hcart2-004-03 &nbsp;/dev/nst2
	&nbsp; drive &nbsp; &nbsp;- &nbsp; &nbsp;9 hcart2 &nbsp; &nbsp;2 &nbsp; &nbsp; &nbsp;UP &nbsp;- &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;drive-hcart2-004-02 &nbsp;/dev/nst1
	&nbsp; drive &nbsp; &nbsp;- &nbsp; 10 hcart2 &nbsp; &nbsp;1 &nbsp; &nbsp;DOWN &nbsp;- &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;drive-hcart2-004-01 &nbsp;/dev/nst0

marianne · Accepted Answer

The robot axis problem is why drives are in AVR state - robot control process in NBU will go down when there is a hardware issue with the robot.
	No robot daemon/process will leave drives in AVR.

I am just surprised that fixing the robot is taking so long.&nbsp;
	More than 3 weeks now?
	How are backups done in the meantime?

marianne · Answer

Your tpconfig output shows robot on a different host, right?

AVR in this instance means that media server has lost network/port connectivity to&nbsp;robotichost.&nbsp;

Check that PBX ia running on media server, verify that PBX (port 1556) is open in both directions between media server and&nbsp;robotichost, double-check forward and reverse name lookup between media server and&nbsp;robotichost, that SERVER entries exist on media server and&nbsp;robotichost for one another.

If you feel that all of the above is fine, stop NBU on media server.
	Add VERBOSE entry to vm.conf on media server, then start NBU.
	Check /var/log/messages for errors if drives still come up in AVR status.

yasuhisa_ishika · Answer

Please post output of "scan", "tpconfig -d"and "vmoprcmd" on both this media server and robotic control host.

mph999 · Answer

Marianne is correct, if the media server with the drives in AVR is NOT the RCH, then there is  comms issue between the media server and the RCH, more accurately tldd on the media sever with drives in AVR is not able to communicate with tldcd on the RCH.

When you reconfigured the drives, at the beginning where you select the servers to scan you must select both the media serer with the drives AND the RCH at the same time, else the drives woud have been configure as standalone and will lalways show AVR.

marianne · Answer

A week later and no response? Seems this cannot be too much of an issue...

vickie · Answer

There is an issue with the library, working with the vendor on it.

Forum Discussion

Drives are in AVR mode

11 Replies

Related Content

Tape drive - restart mode

Re: Drive is in SCAN-TLD

Drives Are in AVR mode.

Drives are in restart mode

tape drives in restart mode

Recent Discussions

"failed, status 6" error after increasing datastore (LUN) capacity

command: bperror

MS-SharePoint policy restore error (2804) .

How to restore a backup

How to configure RBAC