Problems with A5000, E3500, Sol10 & luxadm

Hi,

I am setting up an E3500 with Solaris 10 u2 attached to an A5000 with 14x 18.2Gb HDD through an FC100/S. The drives are all part number 390-0011. The drive that you will see below is being problematic has been swapped out three times with different drives that are known to work on other A5000s. The two ports of the FC100/S are currently connected to port 0 of IB A & B on the A5000. In a week or two when I am in the same building as the system, IB B will be disconnected from the current FC100/S and connected to a second FC100/S that is going to be put in the sytem. On the touch panel of the A5000, all disks are spun up and attached to both ports with no errors. Upon bootup of the E3500, I am seeing the following:

WARNING: /sbus@2,0/SUNW,socal@1,0/sf@0,0 (sf1):

target 0x7d, AL-PA 0x1 and hard address 0x0 don't match

WARNING: /sbus@2,0/SUNW,socal@1,0/sf@0,0 (sf1):

target 0x0, duplicateswitch settings

WARNING: /sbus@2,0/SUNW,socal@1,0/sf@1,0 (sf2):

target 0x0, duplicateswitch settings

Additionally, although there are 14 disks in the array, only 13 are shown under /devices. For example:

bash-3.00# ls -lha /devices/sbus\@2\,0/SUNW\,socal\@1\,0/sf\@1\,0/ | grep"0$"

drwxr-xr-x2 rootsys 512 Jan 18 12:20 ses@w50800200000123d3,0

crw-rw-rw-1 binbin153, 2 Jan 29 05:53 ses@w50800200000123d3,0:0

drwxr-xr-x2 rootsys 512 Jan 18 12:20 ses@w50800200000123d4,0

crw-rw-rw-1 binbin153, 3 Jan 29 05:53 ses@w50800200000123d4,0:0

drwxr-xr-x2 rootsys 512 Jan 18 12:20 ssd@w22000004cfe13d03,0

drwxr-xr-x2 rootsys 512 Jan 18 12:20 ssd@w22000004cfe1f023,0

drwxr-xr-x2 rootsys 512 Jan 18 12:20 ssd@w220000203773f98a,0

drwxr-xr-x2 rootsys 512 Jan 18 12:20 ssd@w22000020378f121e,0

drwxr-xr-x2 rootsys 512 Jan 18 12:20 ssd@w22000020378f90e0,0

drwxr-xr-x2 rootsys 512 Jan 18 12:20 ssd@w22000020378f9512,0

drwxr-xr-x2 rootsys 512 Jan 18 12:20 ssd@w22000020378fc1d1,0

drwxr-xr-x2 rootsys 512 Jan 18 12:20 ssd@w22000020378fc237,0

drwxr-xr-x2 rootsys 512 Jan 18 12:20 ssd@w22000020378fc2c3,0

drwxr-xr-x2 rootsys 512 Jan 18 12:20 ssd@w22000020378fccc6,0

drwxr-xr-x2 rootsys 512 Jan 18 12:20 ssd@w220000203796f392,0

drwxr-xr-x2 rootsys 512 Jan 18 12:20 ssd@w2200002037a8167c,0

drwxr-xr-x2 rootsys 512 Jan 18 12:20 ssd@w2200002037a87600,0

Before posting anywhere with a question, I wanted to check patch levels and firmware revisions against the compatibility matrix(Doc ID 43212). However, I am running into a problem with luxadm. When I probe the system, I get the following:

bash-3.00# luxadm probe

Found Enclosure(s):

SENAName:cab4aNode WWN:50800200000123d0

Logical Path:/dev/es/ses0

Logical Path:/dev/es/ses1

Logical Path:/dev/es/ses2

Logical Path:/dev/es/ses3

Found Fibre Channel device(s):

Node WWN:2000002037222d2f Device Type:Disk device

Logical Path:/dev/rdsk/c0t0d0s2

Node WWN:2000002037227e74 Device Type:Disk device

Logical Path:/dev/rdsk/c0t1d0s2

Node WWN:200000203719b378 Device Type:Disk device

Logical Path:/dev/rdsk/c0t2d0s2

Node WWN:2000002037332050 Device Type:Disk device

Logical Path:/dev/rdsk/c0t3d0s2

Node WWN:200000203726a482 Device Type:Disk device

Logical Path:/dev/rdsk/c1t4d0s2

Node WWN:20000020372285a1 Device Type:Disk device

Logical Path:/dev/rdsk/c1t5d0s2

Node WWN:20000020372289ab Device Type:Disk device

Logical Path:/dev/rdsk/c1t6d0s2

Node WWN:2000002037331f3f Device Type:Disk device

Logical Path:/dev/rdsk/c1t7d0s2

However, trying to display information about the array gives an error:

bash-3.00# luxadm display cab4a

SENA

Error: Invalid pathname - /devices/sbus@2,0/SUNW,socal@1,0/sf@0,0/ses@w50800200000123d1,0:0.

That's where the problem is. What do you guys think is causing that error message? I'm really not sure where to begin looking. Some additional output in case it's handy:

bash-3.00# ls -lha /dev/es

total 18

drwxr-xr-x2 rootroot 512 Jan 18 00:38 .

drwxr-xr-x 17 rootsys 3.5K Jan 30 14:50 ..

lrwxrwxrwx1 rootroot 70 Jan 18 00:38 ses0 -> ../../devices/sbus@2,0/SUNW,socal@1,0/sf@0,0/ses@w50800200000123d1,0:0

lrwxrwxrwx1 rootroot 70 Jan 18 00:38 ses1 -> ../../devices/sbus@2,0/SUNW,socal@1,0/sf@0,0/ses@w50800200000123d2,0:0

lrwxrwxrwx1 rootroot 70 Jan 18 00:38 ses2 -> ../../devices/sbus@2,0/SUNW,socal@1,0/sf@1,0/ses@w50800200000123d3,0:0

lrwxrwxrwx1 rootroot 70 Jan 18 00:38 ses3 -> ../../devices/sbus@2,0/SUNW,socal@1,0/sf@1,0/ses@w50800200000123d4,0:0

bash-3.00# luxadm -e port

/devices/sbus@2,0/SUNW,socal@d,10000:0CONNECTED

/devices/sbus@2,0/SUNW,socal@d,10000:1CONNECTED

/devices/sbus@2,0/SUNW,socal@1,0:0 CONNECTED

/devices/sbus@2,0/SUNW,socal@1,0:1 CONNECTED

bash-3.00# luxadm -e dump_map /devices/sbus@2,0/SUNW,socal@1,0:0

Host Adapter AL_PA: 2

Pos AL_PA

02

11

2d2

3ef

4e8

5e4

6e2

7e1

8e0

9dc

10b5

11cd

12cc

13cb

14ca

15c9

16c7

17c6

bash-3.00# prtconf -vp | grep FCode

version:'@(#) FCode 1.12 99/07/30'

version:'@(#) FCode 1.13 2000/02/02'

bash-3.00# ls -lha /dev/dsk/c[2,3]*d0

lrwxrwxrwx1 rootroot 71 Jan 18 00:38 /dev/dsk/c2t16d0 -> ../../devices/sbus@2,0/SUNW,socal@1,0/sf@0,0/ssd@w210000203773f98a,0:wd

lrwxrwxrwx1 rootroot 71 Jan 18 00:38 /dev/dsk/c2t17d0 -> ../../devices/sbus@2,0/SUNW,socal@1,0/sf@0,0/ssd@w21000020378fccc6,0:wd

lrwxrwxrwx1 rootroot 71 Jan 18 00:38 /dev/dsk/c2t18d0 -> ../../devices/sbus@2,0/SUNW,socal@1,0/sf@0,0/ssd@w21000020378fc1d1,0:wd

lrwxrwxrwx1 rootroot 71 Jan 18 00:38 /dev/dsk/c2t19d0 -> ../../devices/sbus@2,0/SUNW,socal@1,0/sf@0,0/ssd@w21000020378f90e0,0:wd

lrwxrwxrwx1 rootroot 71 Jan 18 00:38 /dev/dsk/c2t1d0 -> ../../devices/sbus@2,0/SUNW,socal@1,0/sf@0,0/ssd@w21000004cfe13d03,0:wd

lrwxrwxrwx1 rootroot 71 Jan 18 00:38 /dev/dsk/c2t20d0 -> ../../devices/sbus@2,0/SUNW,socal@1,0/sf@0,0/ssd@w21000020378fc2c3,0:wd

lrwxrwxrwx1 rootroot 71 Jan 18 00:38 /dev/dsk/c2t21d0 -> ../../devices/sbus@2,0/SUNW,socal@1,0/sf@0,0/ssd@w21000020378f9512,0:wd

lrwxrwxrwx1 rootroot 71 Jan 18 00:38 /dev/dsk/c2t22d0 -> ../../devices/sbus@2,0/SUNW,socal@1,0/sf@0,0/ssd@w21000020378fc237,0:wd

lrwxrwxrwx1 rootroot 71 Jan 18 00:38 /dev/dsk/c2t2d0 -> ../../devices/sbus@2,0/SUNW,socal@1,0/sf@0,0/ssd@w210000203796f392,0:wd

lrwxrwxrwx1 rootroot 71 Jan 18 00:38 /dev/dsk/c2t3d0 -> ../../devices/sbus@2,0/SUNW,socal@1,0/sf@0,0/ssd@w21000020378f121e,0:wd

lrwxrwxrwx1 rootroot 71 Jan 18 00:38 /dev/dsk/c2t4d0 -> ../../devices/sbus@2,0/SUNW,socal@1,0/sf@0,0/ssd@w21000004cfe1f023,0:wd

lrwxrwxrwx1 rootroot 71 Jan 18 00:38 /dev/dsk/c2t5d0 -> ../../devices/sbus@2,0/SUNW,socal@1,0/sf@0,0/ssd@w2100002037a8167c,0:wd

lrwxrwxrwx1 rootroot 71 Jan 18 00:38 /dev/dsk/c2t6d0 -> ../../devices/sbus@2,0/SUNW,socal@1,0/sf@0,0/ssd@w2100002037a87600,0:wd

lrwxrwxrwx1 rootroot 71 Jan 18 00:38 /dev/dsk/c3t16d0 -> ../../devices/sbus@2,0/SUNW,socal@1,0/sf@1,0/ssd@w220000203773f98a,0:wd

lrwxrwxrwx1 rootroot 71 Jan 18 00:38 /dev/dsk/c3t17d0 -> ../../devices/sbus@2,0/SUNW,socal@1,0/sf@1,0/ssd@w22000020378fccc6,0:wd

lrwxrwxrwx1 rootroot 71 Jan 18 00:38 /dev/dsk/c3t18d0 -> ../../devices/sbus@2,0/SUNW,socal@1,0/sf@1,0/ssd@w22000020378fc1d1,0:wd

lrwxrwxrwx1 rootroot 71 Jan 18 00:38 /dev/dsk/c3t19d0 -> ../../devices/sbus@2,0/SUNW,socal@1,0/sf@1,0/ssd@w22000020378f90e0,0:wd

lrwxrwxrwx1 rootroot 71 Jan 18 00:38 /dev/dsk/c3t1d0 -> ../../devices/sbus@2,0/SUNW,socal@1,0/sf@1,0/ssd@w22000004cfe13d03,0:wd

lrwxrwxrwx1 rootroot 71 Jan 18 00:38 /dev/dsk/c3t20d0 -> ../../devices/sbus@2,0/SUNW,socal@1,0/sf@1,0/ssd@w22000020378fc2c3,0:wd

lrwxrwxrwx1 rootroot 71 Jan 18 00:38 /dev/dsk/c3t21d0 -> ../../devices/sbus@2,0/SUNW,socal@1,0/sf@1,0/ssd@w22000020378f9512,0:wd

lrwxrwxrwx1 rootroot 71 Jan 18 00:38 /dev/dsk/c3t22d0 -> ../../devices/sbus@2,0/SUNW,socal@1,0/sf@1,0/ssd@w22000020378fc237,0:wd

lrwxrwxrwx1 rootroot 71 Jan 18 00:38 /dev/dsk/c3t2d0 -> ../../devices/sbus@2,0/SUNW,socal@1,0/sf@1,0/ssd@w220000203796f392,0:wd

lrwxrwxrwx1 rootroot 71 Jan 18 00:38 /dev/dsk/c3t3d0 -> ../../devices/sbus@2,0/SUNW,socal@1,0/sf@1,0/ssd@w22000020378f121e,0:wd

lrwxrwxrwx1 rootroot 71 Jan 18 00:38 /dev/dsk/c3t4d0 -> ../../devices/sbus@2,0/SUNW,socal@1,0/sf@1,0/ssd@w22000004cfe1f023,0:wd

lrwxrwxrwx1 rootroot 71 Jan 18 00:38 /dev/dsk/c3t5d0 -> ../../devices/sbus@2,0/SUNW,socal@1,0/sf@1,0/ssd@w2200002037a8167c,0:wd

lrwxrwxrwx1 rootroot 71 Jan 18 00:38 /dev/dsk/c3t6d0 -> ../../devices/sbus@2,0/SUNW,socal@1,0/sf@1,0/ssd@w2200002037a87600,0:wd

Thanks,

-Aaron Taylor

[9216 byte] By [subgeniuskittya] at [2007-11-26 16:45:47]
# 1
Probably no much help here but are all the drives seen from the OBP?This might help with the problem being hardware or maybe corrupt devices within solaris?!?Does the luxadm command if the suspect drive is removed? if that's possible. Cheers garyg
northgate-isa at 2007-7-8 23:13:07 > top of Java-index,Storage Forums,Storage General Discussion...
# 2
That's a good idea. This weekend I'll take the machine offline long enough to drop to the OBP and post what I find.Thanks,-Aaron Taylor
subgeniuskittya at 2007-7-8 23:13:07 > top of Java-index,Storage Forums,Storage General Discussion...
# 3
After you make sure everything is cabled correctly and you're at the latest patch revs run "devfsadm -C" to clean up any device links that may have been created but no longer correct.
torreysuna at 2007-7-8 23:13:07 > top of Java-index,Storage Forums,Storage General Discussion...