Unable to create Filesystem Error when adding a datastore

[sehealth]

Hi,

I have a 800GB LUN from a EMC CX3-20 that is attached to an EXSI 5 server. when I try and make it a datastore i recieve this error:

"Call "HostDatastoreSystem.CreateVmfsDatastore" for object "ha-datastoresystem" on ESXi "172.29.130.200" failed.
Operation failed, diagnostics report:  Unable to create Filesystem, please see VMkernel log for more details: Function not implemented"

I can edit existing VM and add the LUN as RAW storage and it will show up in the VM's  "Disk Manager", but I would like it as a datastore to put new VM on.

I am unclear on EMC's website if my version of Flare and Navisphere (6.26.24) are compatible with ESXi 5, it looks like the error is created when its converting the disk to a datastore.

Any thoughts?

[vmroyale]

Hello and welcome to the communities.

Note: Discussion successfully moved from VMware Knowledge Base to VMware ESXi 5

Is this a newly created LUN?

Good Luck!

[sehealth]

Hi,

Thanks for the reply, yes its a new LUN?

[vmroyale]

FC or iSCSI? If iSCSI, how is it setup and what adapter(s) are you using?

[a_p_]

Maybe there are some "dirty" bytes on the LUN where ESXi expects the partition table. What I would try to do is to add the LUN as a RDM to a VM and run e.g. diskpart to "clear" the disk. Then remove the RDM from the VM selecting "Remove from disk" and try to add create a datastore on the LUN.

André

[sehealth]

Its using Fiber, the drives are new drives in a new RAID, no data has been on the drive. I can attach the drives to an Existing VM and format the LUN.

[sehealth]

I have attached the LUN to the VM and formatted it and then left it unformatted same error. What Filesystem does the datastore format the drive too?

[vmroyale]

VMFS

Do you have other LUNs without this same issue? Are they in the same disk group?

[sehealth]

No this is the only LUN attached, that’s why I was wondering if it’s a compatibility issue with the CX3-20 SAN server.

It will attach to a VM (RAW) but not become a datastore (VMFS). I am thinking its the converting part that is causing the issue.

[sehealth]

Sorry there are local drives attached, but i wanted to have the VM's all on the SAN.

[vmroyale]

I don't know for sure if its a compatibility issue, but I have a CX3-10 with ESXi 5 that does not have this same issue. And that device is definitely not on the HCL for ESXi 5. Have you tried unbinding it and then binding it again? Might be worth a shot.

[HannaL]

What error does the vmkernel report?  Do you have any ESXi 4.x hosts to try it on? looks like it is supported on lower version of ESX.

http://partnerweb.vmware.com/comp_guide2/search.php?deviceCategory=san&productid=5147&deviceCategory...

[sehealth]

No its FC I use.

2012-05-23T19:45:07.946Z cpu1:2907)Vol3: 647: Couldn't read volume header from control: Invalid handle

2012-05-23T19:45:07.946Z cpu1:2907)FSS: 4333: No FS driver claimed device 'control': Not supported

2012-05-23T19:45:08.026Z cpu1:2907)FSS: 4333: No FS driver claimed device 'naa.6006016002111f0034f1514322a4e111:1': Not supported

2012-05-23T19:45:08.053Z cpu1:2907)VC: 1449: Device rescan time 89 msec (total number of devices 7)

2012-05-23T19:45:08.054Z cpu1:2907)VC: 1452: Filesystem probe time 123 msec (devices probed 5 of 7)

[HannaL]

It is saying no file system driver has claimed the device.  Could be satp/psp claimrules issue which could well be due to it not being supported but if you can find someone else who got it working maybe ask what HBA/driver/flare versions they are using. Or reinstall with ESXi 4.1 u2 and wait til EMC completes their testing of this SAN on esxi 5.x and it is listed as supported on the hcl.

[sehealth]

Thanks HannaL, I am downloading 4.1 as i type this...I see that VMRoyale has it working with his CX3-10. VMRoyale did you do anything using the CLI to get it work?

[HannaL]

cool.  That should fix it.

[vmroyale]

I didn't do anything special - it all just worked.

Good point though - just because the storage device is on the HCL doesn't mean it will work. The HBAs need to be listed as well. You might look at the firmware and driver versions there just to make sure.

[ealaqqad]

Hi,

This  sometime can happen if you have some file system that can not be wiped  or understood by your ESXi host on that datastore(Maybe newer version of VMFS than the host). You will need to wipe  the disk clean before being able to use it. I have posted a blog post  on this at:

Call “HostDatastoreSystem.CreateVmfsDatastore” for object “ha-datastoresystem” on ESXi “xxx.xxx.xxx....

Hope this help!

Regards,

Eiad Al-Aqqad

B: http://www.Virtualizationteam.com

B: http://www.TSMGuru.com

[cougar694u]

I know this is an old post, but wanted to provide an answer that fixed it for us.

We have a CX3 as well and had to set failover mode to 4 for this to work properly.  We had been using failover mode 1 and that didn't work, got this same error.

Just fyi.