Failed to open device naa.xxxxx:1 : not supported

[aduitsis]

I have a Dell R610 running esxi5.5 trying to access a 250Gb LUN in an EMC CX3-40f Clariion array. The LUN is indeed visible, as I can myself see by issuing

~ # esxcli storage core device list
....
naa.600601601f712100669db307a087e011
   Display Name: DGC Fibre Channel Disk (naa.600601601f712100669db307a087e011)
   Has Settable Display Name: true
   Size: 256000
   Device Type: Direct-Access 
   Multipath Plugin: NMP
   Devfs Path: /vmfs/devices/disks/naa.600601601f712100669db307a087e011
   Vendor: DGC     
   Model: VRAID           
   Revision: 0326
   SCSI Level: 4
   Is Pseudo: false
   Status: on
   Is RDM Capable: true
   Is Local: false
   Is Removable: false
   Is SSD: false
   Is Offline: false
   Is Perennially Reserved: false
   Queue Full Sample Size: 0
   Queue Full Threshold: 0
   Thin Provisioning Status: unknown
   Attached Filters: 
   VAAI Status: unknown
   Other UIDs: vml.0200000000600601601f712100669db307a087e011565241494420
   Is Local SAS Device: false
   Is USB: false
   Is Boot USB Device: false
   No of outstanding IOs with competing worlds: 32
...

However, when trying to mount the LUN via the esxi console, I get an error. The vmkernel.log says:

2015-03-23T14:20:28.006Z cpu9:33519)NMP: nmp_ThrottleLogForDevice:2321: Cmd 0x16 (0x412e803c0300, 0) to dev "naa.600601601f712100669db307a087e011" on path "vmhba2:C0:T0:L0" Failed: H:0x0 D:0x2 P:0x0 Valid sense data: 0x5 0x20 0x0. Act:NONE
2015-03-23T14:20:28.006Z cpu9:33519)ScsiDeviceIO: 2338: Cmd(0x412e803c0300) 0x16, CmdSN 0xc44 from world 0 to dev "naa.600601601f712100669db307a087e011" failed H:0x0 D:0x2 P:0x0 Valid sense data: 0x5 0x20 0x0.
2015-03-23T14:20:28.006Z cpu4:34247 opID=50ddd7ac)World: 14299: VC opID D6D55F59-0000010A maps to vmkernel opID 50ddd7ac
2015-03-23T14:20:28.006Z cpu4:34247 opID=50ddd7ac)LVM: 11786: Failed to open device naa.600601601f712100669db307a087e011:1 : Not supported

Anybody knows what is the culprit?

The LUN is formatted, as I've been able to format it and mount it correctly to other esxi machines (Dell R620). Everything goes smoothly. So as far as I can tell, the only difference is that this server is an R610.

Thanks,

Athanasios

[TDilling]

I am having the exact same issue. RAID6 (VRAID) everything is the same except my lun is 600G, and I am on a CX3-20f

Have you resolve this yet?

It seems as though once you have presented a LUN on a specific LUN # you cannot change that LUN.  This problem started when I backed everything up and recreated a fresh LUN that was larger.  I am no longer able to access it.  I can access the Partition Table with partedUtil, I can even mount the raw disk to a windows box that is on a VM.  But I cannot get VMWare to access the LUN and create the VMFS partition.

Any ideas at all?

Bad news is if I cannot get this fixed we will be moving away from VMWare to Hyper-V, because I cannot defend this behavior!!! ergh...

[aduitsis]

Hello,

Yes it is resolved, here's how: Re: Failed to open device naa.xxxxx:1 : not supported (xpost from vsphere hypervisor forum)

You can actually change the LUN# from the Clariion by finding the tab saying "Host LUNs" or something to that effect, but you don't really need to change the LUN#. The problem is that you probably had some other OS using the same FC card and the Clariion remembers it. The simple solution is to de-register the client. At least that's what worked for us.

Good luck,

Athanasios