LTO2 Error

[andrich]

Hello

I am trying to insert new LTO2 tapes in my L180 Robot, but when the Netbackup starts to writing them, an error occurs and the drive goes down:

-bash-3.00# /usr/openv/volmgr/bin/tpconfig -d
Id  DriveName           Type   Residence
      Drive Path                                                       Status
****************************************************************************
0   DRV-1                hcart2 TLD(0)  DRIVE=1
      /dev/rmt/4cbn                                                    UP
1   DRV-2                hcart2 TLD(0)  DRIVE=2
      /dev/rmt/3cbn                                                    DOWN

Jun 10, 2011 2:28:47 PM - mounting S00454
Jun 10, 2011 2:28:49 PM - current media S00454 complete, requesting next media Any
Jun 10, 2011 2:28:52 PM - connecting
Jun 10, 2011 2:29:01 PM - connected; connect time: 0:00:00
Jun 10, 2011 2:29:12 PM - Error bptm (pid=23474) NBJM returned an extended error status: All compatible drive paths are down but media is available (2009)
Jun 10, 2011 2:29:12 PM - Error bptm (pid=23474) INF - All compatible drive paths are down but media is available (2009), cannot continue with copy 1

[Claudio_Veronez]

Andrich

Is there any drive configured as LTO2?

Your L180 have 4 LTO4 drives and 2 LTO2 drives, Look after that configuration.

Best Regards

:wq!

[Marianne]

Please add VERBOSE entry in /usr/openv/volmgr/vm.conf.

Restart NBU.

If drive is DOWN'ed again, please check /var/adm/messages for reason.

Also ensure that you have bptm log dir for further troubleshooting.

[andrich]

Jun 10 13:27:48 svbackup tldcd[17394]: [ID 147745 daemon.error] TLD(0) key = 0x5, asc = 0x30, ascq = 0x0, INCOMPATIBLE MEDIUM INSTALLED
Jun 10 13:27:48 svbackup tldcd[17394]: [ID 719803 daemon.error] TLD(0) Move_medium error
Jun 10 13:28:12 svbackup ltid[1280]: [ID 104275 daemon.error] Operator/EMM server has DOWN'ed drive DRV-1 (device 0)
Jun 10 13:34:09 svbackup ltid[1280]: [ID 250812 daemon.notice] Operator/EMM server has UP'ed drive DRV-1 (device 0)
Jun 10 14:10:12 svbackup sendmail[22478]: [ID 702911 mail.crit] My unqualified host name (svbackup) unknown; sleeping for retry
Jun 10 14:11:12 svbackup sendmail[22478]: [ID 702911 mail.alert] unable to qualify my own domain name (svbackup) -- using short name
Jun 10 14:22:25 svbackup bpjava-msvc[22982]: [ID 427199 user.error] pam_dial_auth: terminal-device not specifiedby login, returning Error in underlying service module.
Jun 10 14:28:48 svbackup tldcd[23488]: [ID 147745 daemon.error] TLD(0) key = 0x5, asc = 0x30, ascq = 0x0, INCOMPATIBLE MEDIUM INSTALLED
Jun 10 14:28:48 svbackup tldcd[23488]: [ID 719803 daemon.error] TLD(0) Move_medium error
Jun 10 14:29:11 svbackup ltid[1280]: [ID 225346 daemon.error] Operator/EMM server has DOWN'ed drive DRV-2 (device 1)
Jun 10 14:35:39 svbackup ltid[1280]: [ID 371883 daemon.notice] Operator/EMM server has UP'ed drive DRV-2 (device 1)

[Marianne]

key = 0x5, asc = 0x30, ascq = 0x0, INCOMPATIBLE MEDIUM INSTALLED

You have inserted media that cannot be loaded in the drive.

***EDIT***

You did not tell us which drive type or which make and model the drives in the L180 are?

Many drive and media types are seen by NBU as hcart2  - e.g LTO2, LTO5, STK9940, etc.. etc..

The NBU density does not make the hardware compatibile - the Library software is intelligent enough to prevent incompatibile media to be loaded in the drive.

[andrich]

My drives are LTO2 (hcart2) and my new medias are LTO2 HP.

0   DRV-1                hcart2 TLD(0)  DRIVE=1
      /dev/rmt/4cbn    

1   DRV-2                hcart2 TLD(0)  DRIVE=2
      /dev/rmt/3cbn                                                   

[Marianne]

Thanks for the clarification. As I've said in my previous post - there are many drive types that NBU will config as hcart2.

tpconfig just shows NBU density, not actual make/model - that can be seen from the inquiry string reported by commands such as 'tpautoconf -t' or 'scan'.

Please check the tape labels carefully - there is SOMETHING about those new tapes that the robot sees as INCOMPATIBLE MEDIUM.

[Anton_Panyushki]

Let's get to the basics.

I suppose your HP LTO2 tapes looks as follows  and their part number is C7972A.

Next, add VERBOSE to vm.conf and

BPTM_VERBOSE = 5

to bp.conf

Create the following directories (if they are not already created)

 mkdir /usr/openv/netbackup/logs/bptm

/usr/openv/volmgr/debug/reqlib

/usr/openv/volmgr/debug/daemon

/usr/openv/volmgr/debug/ltid

Then restart NBU on the server.

Finally, reproduce the issue and examine bptm and VM logs.

It should give you a clue to what happens to the drive.

[Marianne · Accepted solution]

The ROBOT is already telling us that it found INCOMPATIBLE MEDIA:

key = 0x5, asc = 0x30, ascq = 0x0, INCOMPATIBLE MEDIUM INSTALLED

Have a look at this link: http://fixunix.com/veritas-net-backup/481240-seagate-ultrium-drives-netbackup-6-0-a.html   where incorrect labels were put on tapes:

I think I've found the problem, some time ago when ordering new barcodes for
tapes, the barcodes we were ordering started arriving with L2 on them rather
than L1 (I'm assuming this is an identifier to distinguish LTO1 and LTO2
tapes), this is something we did not pick up until now, it seems that version
4.5 of Netbackup did not take note of this identifier, so even though we
were using these barcodes on LTO1 tapes, all has worked fine, so it has never
occurred to us this was going to be a problem in the future. Netbackup 6
however appears to now take note of this identifier and use this to determine
that the tape is incompatible with the drive, for example:

When we try to mount tape 000325 (which is an LTO1 tape but has one of the
new L2 barcodes on it) in an LTO1 drive I get the following using the robtest
utility:

m s2 d1
Initiating MOVE_MEDIUM from address 1001 to 500
move_medium failed
sense key = 0x5, asc = 0x30, ascq = 0x0, INCOMPATIBLE MEDIUM INSTALLED


If I try tape 000007 instead (another LTO1 tape but this has the L1 barcode
on it) the tape mounts fine:

m s34 d1
Initiating MOVE_MEDIUM from address 1033 to 500
MOVE_MEDIUM complete


So as far as netbackup is concerned we are trying to mount an LTO2 tape into
an LTO1 drive so it's rejecting it.