robot inventory failed : Unable to sense robotic device (202)

[ady2k]

I had tried to connect Netbackup 6.0 on RH Enterprise 4.0 to
Tandberg DLT IV. I already patched a new mapping device patch.
Any idea to solve the "Unable to sense robotic device (202)"?
I attached the error messages below here :

Device Name : "/dev/nst0"
Passthru Name: "/dev/sg1"
Volume Header: ""
Port: -1; Bus: -1; Target: -1; LUN: -1
Inquiry : "QUANTUM DLT8000 0232"
Vendor ID : "QUANTUM "
Product ID : "DLT8000 "
Product Rev: "0232"
Serial Number: "TNB35P0079"
WWN : ""
WWN Id Type : 0
Device Identifier: ""
Device Type : SDT_TAPE
NetBackup Drive Type: 11
Removable : Yes
Device Supports: SCSI-2
Flags : 0x0
Reason: 0x0
------------------------------------------------------------
Device Name : "/dev/sg0"
Passthru Name: "/dev/sg0"
Volume Header: ""
Port: -1; Bus: -1; Target: -1; LUN: -1
Inquiry : "NEC DL0101H-0E 0002"
Vendor ID : "NEC "
Product ID : "DL0101H-0E "
Product Rev: "0002"
Serial Number: ""
WWN : ""
WWN Id Type : 0
Device Identifier: ""
Device Type : SDT_CHANGER
NetBackup Robot Type: 8
Removable : Yes
Device Supports: SCSI-2
Number of Drives : 1
Number of Slots : 9
Number of Media Access Ports: 0
Flags : 0x0
Reason: 0x0

#robtest
mode
Library not found in device mapping table - using default settings
First transport addr = 86, Number transport elements = 1
First storage addr = 0, Number storage elements = 9
First media access port addr = 0, Number media access port elements = 0
First drive addr = 82, Number drive elements = 1
Library does have a barcode reader
MODE_SENSE complete

s d
read_element_status failed
sense key = 0x2, asc = 0x4, ascq = 0x85, UNKNOWN ERROR, KEY: 0x02, ASC: 0x04, ASCQ: 0x85

init
Initiating INITIALIZE_ELEMENT_STATUS
initialize_element_status failed
sense key = 0x2, asc = 0x4, ascq = 0x85, UNKNOWN ERROR, KEY: 0x02, ASC: 0x04, ASCQ: 0x85


Thank you for advance....

 

[MrPudding]

Do you have any media in it? Remove and tapes and try again.

If it works check the media you have removed and make sure they all have bar codes and that none of the bar codes are unreadable.

It might sound strange but if you have media with no or unreadable barcodes in a library that has a bar code reader you get robotic sense errors.

MrP

 

[ady2k]

I got 6 pcs of tapes inside there.
But I don't have a barcode on every tape at this time.
Maybe I just labeled it the media after I did inventory robot succesfully.
Should I have a barcode on every tape ? If I did Inventory Robot from netbackup 6 and came out "robot inventory failed : Unable to sense robotic device (202)".
Thanks for advance....

 

[MrPudding]

That is you problem then. Netbackup can deal with tapes with no barcode if they are in a blind library. If the library has a reader then it expects every piece of media to have a barcode.

Remove the media without barcodes and try again.

MrP

 

[ady2k]

I should have a barcode for every tapes.
Can I skip the barcade?
If I can label it the tape from netbackup. For what function the bplabel provideed by Veritas ?

 

[MrPudding]

If your library is equiped with a barcode reader then you will need a barcode on every tape.

MrP

 

[ady2k]

You meant the robotic would not work without any barcode on the tape ?
Does it make sense ?
I don't think this is a good solution to solve my problem.
If I can do inventory robot and without barcode on the tape.
Maybe the netbackup would not show me a media ID.Because I don't use barcode on the tape.
But the inventory robot should work well. That would not show a error messages "Unable to sense robotic device (202)

 

[MrPudding]

OK. I have seen this error before several times on different sites. Have you actually tried what I suggested? Remove the tapes that do not have barcodes on them and try to run an inventory. This will confirm if the problem is what I think it is.

MrP

 

[ady2k]

Ok, I will try it later.
Thanks.

 

[ady2k]

I should lock the Autoloader door. And I can do inventory Robot successfully. That's got it from google search.
Actually the error messages happenned on Veritas Netbackup 5.1 for windows.So I used that solution...
Thanks