Seems like it Duke. After bang my head and running probe-scsi-all from OK prompt somehow that error isnt showing up now but ran into different issue on same server
Look at the below output of cfgadm , I understand pcisch0:hpc1_slot0 stuff if related to tape drives.
bash-2.03# cfgadm -al
Ap_Id Type Receptacle Occupant Condition
SBa cpu/mem connected configured ok
SBa::cpu0 cpu connected configured ok
SBa::cpu1 cpu connected configured ok
SBa::memory memory connected configured ok
SBb cpu/mem connected unconfigured ok
SBc cpu/mem connected unconfigured ok
SBd cpu/mem connected unconfigured ok
c0 scsi-bus connected configured unknown
c0::dsk/c0t6d0 CD-ROM connected configured unknown
c2 scsi-bus connected unconfigured unknown
c3 scsi-bus connected unconfigured unknown
pcisch0:hpc1_slot0 unknown empty unconfigured unknown
pcisch0:hpc1_slot1 unknown empty unconfigured unknown
pcisch0:hpc1_slot2 unknown empty unconfigured unknown
pcisch0:hpc1_slot3 unknown empty unconfigured unknown
pcisch2:hpc2_slot4 unknown empty unconfigured unknown
pcisch2:hpc2_slot5 mult/hp connected configured ok
pcisch2:hpc2_slot6 unknown empty unconfigured unknown
pcisch3:hpc0_slot7 unknown empty unconfigured unknown
pcisch3:hpc0_slot8 unknown empty unconfigured unknown
I cant see c1 controller in above stuff, where as all the disk are using c1 controller.
It could be a poor contact on an add-in card. I would power down, pull out each add-in card, and plug it back in again just to make sure the edge contacts are making. Perhaps this machine has been around a while and card(s) need reseating.
I tried doing it but see see the same output of cfgadm -al as sent before and still no C1 controller in the list
Whenever i reboot the server glm issue pops up then none of the commands work but after couple of hours glm issue disappears and commands starts tot work
Under normal circumstances no system will change its behaviour i.e., commands which don't work just start working after a couple of hours of running. There are only so many things that can cause it.
The system is running something at boot time which is time-based and toggling off something for a couple of hours.
A peripheral system is toggling something for a couple of hours e.g. a SAN is making volumes unavailable at certain times.
Or most likely it is a hardware problem e.g. as the system heats up things start working, see my post#8.