I had the same issue. Support sent me this KB which basically states VMFS6 is not yet supported but provides a workaround. Be mindful of using VMFS6 though. For us we saw lots of SCSI sense codes on the ESXi host when using VMFS6 so we switch back to VMFS5.

https://emcservice.force.com/CustomersPartners/kA2f1000000G7DACA0

Hi folks.

Have a look at this KB: https://support.emc.com/kb/516823

The new Dell EMC Unity OE is just around the corner though.

Andre @ Dell EMC

Would you mind sharing in more detail what you experienced with VMFS6?  You mentioned seeing lots of SCSI sense codes and switched back to VMFS5.

We recently had a system panic shortly after allocating Unity LUNs to an ESXi cluster on VMFS6 and I wonder if it might be directly related to the Unity not yet support VMFS6 datastores.

Correct, it can be done, just not automatically.

Once the LUN/Datastore is presented to ESXi 6.5 it can be formatted with VMFS 6

The KB does NOT mean that using VMFS6 is not support with Unity - it is

I just means that if you create your LUNs through the VMware datastore option on Unity we will create it with vmfs5

You are welcome to just create LUNs and manually assign them to your ESX servers - then you can use vmfs6

These are the ESXi vmkernal log scsi sense codes we saw when performing storage v-motions to a destination datastore lun that was VMFS6...

"naa.6006016030f04500521b715ad6def1c7" failed H:0x0 D:0x2 P:0x5 Invalid sense data: 0x80 0x41 0x0."

When using VMFS5 instead, we did not see these scsi sense codes present. Unity code was 4.2.1.9535982, and VMware is 6.5 update1. Compression enabled on Unity lun for all tests.