Identifying correct disk in 3320 array

Greetings,

I had an interesting "failure" of four disks at one time in a 3320 JBOD 
expansion chassis attached to a 3320 raid controller.

Six disks on channel 2  are configured as NRAID and presented to the 
host as stand alone disks.  We used these six to build a raidz pool with 
one hot-spare.  we were able to recover all but one disk, the zpool 
re-silvered the spare and is using it now and telling me one of the 
original disks is faulted with "too many errors"

What I am unable to wrap my head around is figuring out which of the 
five possible disks (I know which one the spare is/was originally) is 
the one that the system claims has failed.  The RAID controller has not 
notified me of any errors beyond yesterdays notification of I/O timeouts 
on four of the five in-use drives.

c4t3d4 - marked as failed /dev/dsk/c4t3d4s2 -> 
../../devices/pci@1d,700000/scsi@1,1/sd@3,4:c

Does the device name in some way map back to how the 3320 present the 
disk to the host, which is to say is disk c4t3d4 actually logical drive 
4 which I can map back to a physical drive using sccli show drive as

Ch     Id      Size   Speed  LD     Status     IDs 
Rev
----------------------------------------------------------------------------
2      8  279.40GB   320MB  ld4    ONLINE     FUJITSU MAW3300NCSUN300G 1703
                                                    S/N 000726D02VPV

Sorry for what appears to me to be a very basic question, but it is 
something I am having trouble with this morning.  I'd rather ask a 
possibly obvious question than yank the wrong drive out of the array. 
Perhaps there just hasn't been enough coffee yet today.

Thank you
Bob

-- 
***********************************************************************
Robert M. Martel                 I met someone who looks a lot like you
System Administrator             She does the things you do
Levin College of Urban Affairs   But she is an IBM
Cleveland State University                           -Jeff Lynne
(216) 687-2214
[email protected]
***********************************************************************