Hello. Been working on Marianne's suggestion to resolve 'condition' failed status - rebooted the server and power cycled the tape drive. No longer says 'condition failed':
Ap_Id Type Receptacle Occupant Condition
c8 fc connected unconfigured unknown
c9 fc-private connected configured unknown
c9::500110a0008c72fa,0 tape connected configured unknown
c9::500110a0008c72fa,1 med-changer connected configured unknown
c10 fc connected unconfigured unknown
c11 fc-private connected configured unknown
c11::500110a0008c7300,0 tape connected configured unknown
However, in /var/adm/messages, I am getting this now:
Jan 9 15:03:12 nbolmasterback vmd[717]: [ID 617826 daemon.notice] ready for connections
Jan 9 15:03:22 nbolmasterback avrd[741]: [ID 748556 daemon.notice] st.conf configuration for HP.ULTRIUM4-SCSI.000 (device 0), name [HP Ultrium LTO 4], vid [HP Ultrium 4*], type 0x3b, block size 0, options 0x18619 (see st(7D) man page)Jan 9 15:03:45 nbolmasterback mac: [ID 736570 kern.info] NOTICE: e1000g1 unregistered
Jan 9 15:03:45 nbolmasterback mac: [ID 736570 kern.info] NOTICE: e1000g2 unregistered
Jan 9 15:03:45 nbolmasterback mac: [ID 736570 kern.info] NOTICE: e1000g3 unregistered
Jan 9 15:03:58 nbolmasterback pseudo: [ID 129642 kern.info] pseudo-device: devinfo0
Jan 9 15:03:58 nbolmasterback genunix: [ID 936769 kern.info] devinfo0 is /pseudo/devinfo@0
Jan 9 15:04:41 nbolmasterback pseudo: [ID 129642 kern.info] pseudo-device: fcsm0
Jan 9 15:04:41 nbolmasterback genunix: [ID 936769 kern.info] fcsm0 is /pseudo/fcsm@0
Jan 9 15:04:50 nbolmasterback scsi: [ID 799468 kern.info] st1 at fp5: name w500110a0008c7300,0, bus address 2
Jan 9 15:04:50 nbolmasterback genunix: [ID 936769 kern.info] st1 is /pci@3,0/pci1022,7458@a/pci10df,fc12@1,1/fp@0,0/tape@w500110a0008c7300,0
Jan 9 15:04:50 nbolmasterback scsi: [ID 365881 kern.info] /pci@3,0/pci1022,7458@a/pci10df,fc12@1,1/fp@0,0/tape@w500110a0008c7300,0 (st1):
Jan 9 15:04:50 nbolmasterback <HP Ultrium LTO 4>
Jan 9 15:04:50 nbolmasterback avrd[741]: [ID 990698 daemon.notice] st.conf configuration for HP.ULTRIUM4-SCSI.001 (device 1), name [HP Ultrium LTO 4], vid [HP Ultrium 4*], type 0x3b, block size 0, options 0x18619 (see st(7D) man page)Jan 9 15:04:54 nbolmasterback tldcd[748]: [ID 295976 daemon.error] TLD(0) [748] robotic path /dev/sg/c0tw500110a0008c72fal1 does not exist
Jan 9 15:04:54 nbolmasterback last message repeated 1 time
Jan 9 15:04:54 nbolmasterback tldd[727]: [ID 795118 daemon.error] TLD(0) unavailable: initialization failed: Unable to open robotic path
Jan 9 15:06:56 nbolmasterback tldcd[748]: [ID 295976 daemon.error] TLD(0) [748] robotic path /dev/sg/c0tw500110a0008c72fal1 does not exist
Jan 9 15:06:56 nbolmasterback last message repeated 1 time
Jan 9 15:06:56 nbolmasterback tldd[727]: [ID 795118 daemon.error] TLD(0) unavailable: initialization failed: Unable to open robotic path
Jan 9 15:08:58 nbolmasterback tldcd[748]: [ID 295976 daemon.error] TLD(0) [748] robotic path /dev/sg/c0tw500110a0008c72fal1 does not exist
Jan 9 15:27:19 nbolmasterback sg: [ID 266374 kern.notice] Symantec SCSA Generic Revision: 3.7
____________
I see the drive listed here, however, saying the robotic path doesn't exist is interesting. Again, I only started looking at the tape drive after a week of 2009 errors. After a software reboot, I am having these issues. How to reconfigure the path? Even though nothing changed, is this simply refreshing / reseting this?