robot issue with OS system

Hi, after reboot th erobot cannot initialized and I see on the OS system

bash host# cfgadm -c configure c4
cfgadm: Library error: failed to create device node: 500104f0006e46a8: I/O error
Operation partially successful. Some failures seen

bash host# cfgadm -c unconfigure c4::500104f0006e46a8
cfgadm: Library error: remove operation failed: /devices/pci@8,700000/SUNW,qlc@5/fp@0,0/sg@w500104f0006e46a8,0: Inappropriate ioctl for device

6 Replies

Re: robot issue with OS system

Can you run

 

#luxadm probe

 

command and send the o/p

 

Re: robot issue with OS system

Let me explain before:

 

when I go and reset the robot and bott the server then all drives are ok and robot initialized

 

when I then start backups the first 3 run fine, further more will cause that thesystemmessage"cannot initialize robot"

g1bs01 console login: Jan 21 13:06:46 g1bs01 ltid[848]: Request for media ID 000316 is being rejected because it cannot be found in designated slot

 

Jan 21 13:07:23 g1bs01 tldcd[1853]: TLD(0) key = 0x4, asc = 0x40, ascq = 0x1, HARDWARE ERROR, GENERAL
Jan 21 13:07:23 g1bs01 tldcd[1853]: TLD(0) Move_medium error: CHECK CONDITION
Jan 21 13:07:23 g1bs01 tldcd[1853]: TLD(0) could not move unknown media from drive 5 to media access port
Jan 21 13:07:23 g1bs01 tldd[899]: TLD(0) drive 5 (device 4) is being DOWNED, status: Robotic dismount failure
Jan 21 13:07:23 g1bs01 tldd[899]: Check integrity of the drive, drive path, and media
Jan 21 13:07:23 g1bs01 tldd[899]: TLD(0) going to DOWN state, status: Unable to initialize robot
Jan 21 13:07:25 g1bs01 tldd[899]: Cannot find request in DecodeResponse, pid = 1965
Jan 21 13:09:28 g1bs01 tldd[899]: TLD(0) unavailable: initialization failed: Unable to initialize robot
Jan 21 13:11:30 g1bs01 last message repeated 1 time
Jan 21 13:13:32 g1bs01 tldd[899]: TLD(0) unavailable: initialization failed: Unable to initialize robot
Jan 21 13:19:39 g1bs01 last message repeated 3 times
Jan 21 13:21:41 g1bs01 tldd[899]: TLD(0) unavailable: initialization failed: Unable to initialize robot

 

 

i checked and see again drive 4 are downed by the system

I come more and more to the result that maybe drive 4 is defect and needs to be replaced

 

and here is the luxadm probe

 bash g1bs01# luxadm probe
Found Enclosure:
SUNWGS INT FCBPL   Name:FCloop   Node WWN:50800200001ced38   Logical Path:/dev/es/ses1

Found Fibre Channel device(s):
  Node WWN:5005076312013dd9  Device Type:Tape device
    Logical Path:/dev/rmt/0n
  Node WWN:5005076312006e14  Device Type:Tape device
    Logical Path:/dev/rmt/1n
  Node WWN:50050763002150e5  Device Type:Tape device
    Logical Path:/dev/rmt/2n
  Node WWN:5005076300217b29  Device Type:Tape device
    Logical Path:/dev/rmt/3n
  Node WWN:500507631201d49c  Device Type:Tape device
    Logical Path:/dev/rmt/4n
  Node WWN:5005076300214c76  Device Type:Tape device
    Logical Path:/dev/rmt/5n
  Node WWN:5005076300214fe9  Device Type:Tape device
    Logical Path:/dev/rmt/6n
  Node WWN:500507631201d589  Device Type:Tape device
    Logical Path:/dev/rmt/7n
  Node WWN:500507631201d2ec  Device Type:Tape device
    Logical Path:/dev/rmt/8n
  Node WWN:5005076300214ef3  Device Type:Tape device
    Logical Path:/dev/rmt/9n
  Node WWN:500507631201cbe8  Device Type:Tape device
    Logical Path:/dev/rmt/10n
  Node WWN:500507631320b05e  Device Type:Tape device
    Logical Path:/dev/rmt/11n
bash g1bs01#

 

 

 

Re: robot issue with OS system

Manfred - you certainly seem to be having a few issues, what with all your other posts etc!!

 

If you can communicate with your robot, can you try & inventory it &  update volume configuration?

 

The reason I say this is from your last post:

"...

g1bs01 console login: Jan 21 13:06:46 g1bs01 ltid[848]: Request for media ID 000316 is being rejected because it cannot be found in designated slot

..."

This would indicate to me that the library contents or NetBackups idea of its contents have become somewhat mixed up. This can lead to drives going down if NB tries to mount a tape which it believes is in a certain slot but ends up loading A.N.Other tape.

Re: robot issue with OS system

This is the biggest clue ...

 

Jan 21 13:07:23 g1bs01 tldcd[1853]: TLD(0) key = 0x4, asc = 0x40, ascq = 0x1, HARDWARE ERROR, GENERAL

 

Sense key messages come back from the robot - I think it's hardware engineer time ...

 

Martin

Re: robot issue with OS system

Andy, you may right, we had a lot of error messages which confused me.

I now found out that whenever I down drive # (which is the one with the error message)

the system was ok and robot could be initialized.

 

So we had a hardware engineer on side which did the job first time.

He should just exchange the drive but therefore he powered off the complete L700

The result was after he powered it onagain the L700 display get lost of the 6th drive in the config.

 

Even power off and on juts this drive didnt help,all cables are ok bezel are mounted as well.

 

Anybody who know how to add a drive to the L700 config ?

Re: robot issue with OS system

Is this issue Solved ?? Smiley Happy

 

For Addition of Drive; Just mount the Drive in Library, and run COnfigure Storage Device Wizard, it will bring you the list of Drives and Robots connected to your server; if you are ok with that devices then goahead and apply that configurations !

 

that's it Smiley Happy