I have 2 new SAN disks attached to a host. One looks normal and Veritas can see it and initialize it. The other, shows an "ERROR" in vxdisk list.
vxdisk list
DEVICE TYPE DISK GROUP STATUS
c0t0d0s2 auto:none - - online invalid
c2t0d0s2 auto:none - - online invalid
c2t6d0s2 auto:none - - online invalid
fabric_50 auto:cdsdisk fabric_11 ocsrawdg online shared
. . .
fabric_78 auto:cdsdisk fabric_28 ocsrawdg online shared
fabric_79 auto - - error
fabric_80 auto:cdsdisk - - online
I left out a bunch of other disks between fabric_50 and fabric_78 as they are not relevant. Note fabric_79 and fabric_80 are the 2 new disks. They both appear normal in Solaris format, and the NetApp host tools show them as both good.
#format
Searching for disks...done
#sanlun lun show
controller: lun-pathname device filename adapter protocol lun size lun state
filer2: /vol/acqbiz_vis_prod_nona_nox_cluster_ebsfsdg/lun1 /dev/rdsk/c8t60A98000486E5A71675A5A447168634Bd0s2 qlc1 FCP 102g (109521666048) GOOD
filer1: /vol/acqbiz_vis_prod_nona_nox_cluster_ocsrawdg/lun1 /dev/rdsk/c8t60A98000486E5A7153345A4471373748d0s2 qlc1 FCP 1.1t (1204738326528) GOOD
I've left out a lot of excess output, but the interesting stuff should be here. Finally, issuing a vxdisk init give an error.
#vxdisk init fabric_79
VxVM vxdisk ERROR V-5-1-5433 Device fabric_79: init failed:
Device path not valid
I even tried dd'ing /dev/zero onto the first 4 blocks of the device and relabeling the disk with format. Still no joy. Does anyone have any idea what the problem might be? I'm going to have hard time convincing the SAN folks it's a problem since it looks fine with format and the NetApp tool, but there must be something I've missed. One thing I probably should mention is the LUN is 1.1T in size.
