FC60 Config problem

meekrob — Fri, 09 Dec 2005 03:57:22 GMT

Hello,

I have a FC60 with three enclosures SC10 in split mode configuration.

1- No fault indicators on any disk array components
2-All disk modules spun up

the problem that when I restart the system (Host) the AM60Srvr daemon doesn't start automatically, when i start this process manually and i I try the see the array ID using amdsp -i command the system reply a message " No array were found by the AM60Srvr"

I restart the system as follow:
1- I powered up each disk enclosure ( total of 3) No error indicator
2- I powered up the controller enclosure, same no error indicator.
3- I boot the host

please see bellow the result of the ioscan -fn

Class I H/W Path Driver S/W State H/W Type Description
=====================================================================================
root 0 root CLAIMED BUS_NEXUS
ioa 0 0 sba CLAIMED BUS_NEXUS System Bus Adapter (803)
ba 0 0/0 lba CLAIMED BUS_NEXUS Local PCI Bus Adapter (782)
lan 0 0/0/0/0 btlan3 CLAIMED INTERFACE HP PCI 10/100Base-TX Core
/dev/diag/lan0 /dev/ether0
ext_bus 0 0/0/1/0 c720 CLAIMED INTERFACE SCSI C896 Ultra Wide Single-Ended
target 0 0/0/1/0.1 tgt CLAIMED DEVICE
disk 0 0/0/1/0.1.0 sdisk CLAIMED DEVICE HP DVD-ROM 305
/dev/dsk/c0t1d0 /dev/rdsk/c0t1d0
target 1 0/0/1/0.7 tgt CLAIMED DEVICE
ctl 0 0/0/1/0.7.0 sctl CLAIMED DEVICE Initiator
/dev/rscsi/c0t7d0
ext_bus 1 0/0/1/1 c720 CLAIMED INTERFACE SCSI C896 Ultra Wide Single-Ended
target 2 0/0/1/1.0 tgt CLAIMED DEVICE
disk 1 0/0/1/1.0.0 sdisk CLAIMED DEVICE FUJITSU MAJ3364MC
/dev/dsk/c1t0d0 /dev/rdsk/c1t0d0
target 3 0/0/1/1.2 tgt CLAIMED DEVICE
disk 2 0/0/1/1.2.0 sdisk CLAIMED DEVICE FUJITSU MAJ3364MC
/dev/dsk/c1t2d0 /dev/rdsk/c1t2d0
target 4 0/0/1/1.7 tgt CLAIMED DEVICE
ctl 1 0/0/1/1.7.0 sctl CLAIMED DEVICE Initiator
/dev/rscsi/c1t7d0
ext_bus 2 0/0/2/0 c720 CLAIMED INTERFACE SCSI C875 Ultra Wide Single-Ended
target 5 0/0/2/0.0 tgt CLAIMED DEVICE
disk 3 0/0/2/0.0.0 sdisk CLAIMED DEVICE COMPAQ BD03685A24
/dev/dsk/c2t0d0 /dev/rdsk/c2t0d0
target 6 0/0/2/0.2 tgt CLAIMED DEVICE
disk 4 0/0/2/0.2.0 sdisk CLAIMED DEVICE FUJITSU MAJ3364MC
/dev/dsk/c2t2d0 /dev/rdsk/c2t2d0
target 7 0/0/2/0.7 tgt CLAIMED DEVICE
ctl 2 0/0/2/0.7.0 sctl CLAIMED DEVICE Initiator
/dev/rscsi/c2t7d0
ext_bus 3 0/0/2/1 c720 CLAIMED INTERFACE SCSI C875 Ultra Wide Single-Ended
target 8 0/0/2/1.7 tgt CLAIMED DEVICE
ctl 3 0/0/2/1.7.0 sctl CLAIMED DEVICE Initiator
/dev/rscsi/c3t7d0
unknown -1 0/0/4/0 UNCLAIMED UNKNOWN PCI BaseSystem (103c10ed)
tty 0 0/0/4/1 asio0 CLAIMED INTERFACE PCI Serial (103c1048)
/dev/GSPdiag1 /dev/tty0p0
/dev/diag/mux0 /dev/tty0p1
/dev/mux0 /dev/tty0p2
ba 1 0/1 lba CLAIMED BUS_NEXUS Local PCI Bus Adapter (782)
ba 2 0/2 lba CLAIMED BUS_NEXUS Local PCI Bus Adapter (782)
ba 3 0/3 lba CLAIMED BUS_NEXUS Local PCI Bus Adapter (782)
ba 4 0/4 lba CLAIMED BUS_NEXUS Local PCI Bus Adapter (782)
ba 5 0/5 lba CLAIMED BUS_NEXUS Local PCI Bus Adapter (782)
ba 6 0/8 lba CLAIMED BUS_NEXUS Local PCI Bus Adapter (782)
fc 0 0/8/0/0 td CLAIMED INTERFACE HP Tachyon TL/TS Fibre Channel Mass Storage Adapter
/dev/td0
fcp 0 0/8/0/0.8 fcp CLAIMED INTERFACE FCP Protocol Adapter
ext_bus 6 0/8/0/0.8.0.255.0 fcpdev CLAIMED INTERFACE FCP Device Interface
target 9 0/8/0/0.8.0.255.0.5 tgt CLAIMED DEVICE
ctl 6 0/8/0/0.8.0.255.0.5.0 sctl CLAIMED DEVICE HP A5277A
/dev/rscsi/c6t5d0
ba 7 0/9 lba CLAIMED BUS_NEXUS Local PCI Bus Adapter (782)
fc 1 0/9/0/0 td CLAIMED INTERFACE HP Tachyon TL/TS Fibre Channel Mass Storage Adapter
/dev/td1
fcp 1 0/9/0/0.8 fcp CLAIMED INTERFACE FCP Protocol Adapter
ext_bus 7 0/9/0/0.8.0.255.0 fcpdev CLAIMED INTERFACE FCP Device Interface
target 10 0/9/0/0.8.0.255.0.4 tgt CLAIMED DEVICE
ctl 7 0/9/0/0.8.0.255.0.4.0 sctl CLAIMED DEVICE HP A5277A
/dev/rscsi/c7t4d0
ba 8 0/10 lba CLAIMED BUS_NEXUS Local PCI Bus Adapter (782)
ext_bus 4 0/10/0/0 c720 CLAIMED INTERFACE SCSI C875 Fast Wide Differential
target 11 0/10/0/0.3 tgt CLAIMED DEVICE
tape 0 0/10/0/0.3.0 stape CLAIMED DEVICE QUANTUM DLT8000
/dev/rmt/0m
/dev/rmt/0mb
/dev/rmt/0mn
/dev/rmt/0mnb
/dev/rmt/c4t3d0BEST
/dev/rmt/c4t3d0BESTb
/dev/rmt/c4t3d0BESTn
/dev/rmt/c4t3d0BESTnb
target 12 0/10/0/0.7 tgt CLAIMED DEVICE
ctl 4 0/10/0/0.7.0 sctl CLAIMED DEVICE Initiator
/dev/rscsi/c4t7d0
ba 9 0/12 lba CLAIMED BUS_NEXUS Local PCI Bus Adapter (782)
lan 1 0/12/0/0 btlan6 CLAIMED INTERFACE HP A3738A PCI 10/100Base-TX Ultimate Combo
/dev/diag/lan1 /dev/lan1
/dev/ether1
pbc 0 32 pbc CLAIMED BUS_NEXUS Bus Converter
processor 0 33 processor CLAIMED PROCESSOR Processor
pbc 1 96 pbc CLAIMED BUS_NEXUS Bus Converter
processor 1 97 processor CLAIMED PROCESSOR Processor
memory 0 192 memory CLAIMED MEMORY Memory

NB: the array's interfaces has been detected by the host, but the host doesn't detect the disks.

Rgds

Re: FC60 Config problem

Andrew Rutter — Fri, 09 Dec 2005 09:44:13 GMT

hi,

from my experience with the fc60's you have powered them up in the correct way, but maybe not for long enough in between.

sc01's first leaving to spin up for baout 5-10 mins
fc60 to power up and leave for 10 mins to look at the arrays.
then power up the system. watching the terminal you should see the armsvr deamon startup.

there has been lots of patches for different systems for the fc60 and armsvr, ensure your upto date.

Also if you have manually started the deamon then you will need to do a full ioscan and then insf -e to create the device files, then check ioscan again before you search for the arrays

Andy

Re: FC60 Config problem

Andrew Rutter — Sat, 10 Dec 2005 12:45:19 GMT

hi,

you may also get more help and responces from other members if you actually showed your appreciation for others by assigning points to the answers/help you are given.

you have a very bad record of this

have assigned points to 2 of 124 responses to my questions

I suggest you review all your other questions and assign accordingly.
You will continue good answers from the very knowledable people here then

Andy

topic FC60 Config problem in Disk Enclosures

FC60 Config problem

Re: FC60 Config problem

Re: FC60 Config problem