Hello !
I'm building my vmware home lab and I'm having an issue when it comes to create datastores:
The host is a Dell Optiplex 7010 running unmodified ESXi 6.7.0 on a USB stick.
The san storage server is a HP Proliant ML110 G6 running the latest version of ESOS, disks are standard SATA spinners.
Both are connected with fibre channel via a switch, QLE2462 on the host and QLE2460 on the san storage server.
The zoning has been done and seems to work, I can see the 'ATA Fibre Channel Disk (naa...)' on the host.
Now when I try to create a datastore with the disk, I get the following error message:
Failed to create VMFS datastore test - Operation failed, diagnostics report: Unable to create Filesystem, please see VMkernel log for more details: Failed to create VMFS on device naa.5000c50051394f65:1
I looked at the VMkernel log, and this is what I found:
(showing all events between first mention of naa and last mention)
2018-05-10T12:33:49.592Z cpu2:2097564)ScsiDeviceIO: 9297: Get VPD 86 Inquiry for device "naa.5000c50051394f65" from Plugin "NMP" failed. Not supported
2018-05-10T12:33:49.592Z cpu0:2097564)ScsiDeviceIO: 7998: QErr is correctly set to 0x0 for device naa.5000c50051394f65.
2018-05-10T12:33:49.592Z cpu1:2097564)ScsiDeviceIO: 8495: Could not detect setting of sitpua for device naa.5000c50051394f65. Error Not supported.
2018-05-10T12:33:49.595Z cpu1:2097564)WARNING: NFS: 1227: Invalid volume UUID naa.5000c50051394f65:1
2018-05-10T12:33:49.601Z cpu3:2097564)FSS: 6092: No FS driver claimed device 'naa.5000c50051394f65:1': No filesystem on the device
2018-05-10T12:33:49.601Z cpu3:2097564)ScsiEvents: 300: EventSubsystem: Device Events, Event Mask: 40, Parameter: 0x4302c7adbac0, Registered!
2018-05-10T12:33:49.601Z cpu3:2097564)ScsiEvents: 300: EventSubsystem: Device Events, Event Mask: 200, Parameter: 0x4302c7adbac0, Registered!
2018-05-10T12:33:49.601Z cpu3:2097564)ScsiEvents: 300: EventSubsystem: Device Events, Event Mask: 800, Parameter: 0x4302c7adbac0, Registered!
2018-05-10T12:33:49.601Z cpu3:2097564)ScsiEvents: 300: EventSubsystem: Device Events, Event Mask: 400, Parameter: 0x4302c7adbac0, Registered!
2018-05-10T12:33:49.601Z cpu3:2097564)ScsiEvents: 300: EventSubsystem: Device Events, Event Mask: 8, Parameter: 0x4302c7adbac0, Registered!
2018-05-10T12:33:49.601Z cpu3:2097564)ScsiDevice: 4936: Successfully registered device "naa.5000c50051394f65" from plugin "NMP" of type 0
2018-05-10T12:33:49.601Z cpu0:2097564)NMP: nmp_DeviceUpdateProtectionInfo:747: Set protection info for device 'naa.5000c50051394f65', Enabled: 0 ProtType: 0x0 Guard: 0x0 ProtMask: 0x0
2018-05-10T12:33:49.601Z cpu0:2097564)ScsiEvents: 300: EventSubsystem: Device Events, Event Mask: 180, Parameter: 0x430661162010, Registered!
2018-05-10T12:35:07.531Z cpu0:2097547)INFO (ne1000): false RX hang detected on vmnic0
2018-05-10T12:35:28.531Z cpu0:2097547)INFO (ne1000): false RX hang detected on vmnic0
2018-05-10T12:35:31.950Z cpu1:2098532 opID=5e847b04)World: 11942: VC opID 0f90c609 maps to vmkernel opID 5e847b04
2018-05-10T12:35:31.950Z cpu1:2098532 opID=5e847b04)NVDManagement: 1478: No nvdimms found on the system
2018-05-10T12:35:38.182Z cpu1:2099660)WARNING: NFS: 1227: Invalid volume UUID naa.5000c50051394f65:1
2018-05-10T12:35:38.189Z cpu0:2099660)FSS: 6092: No FS driver claimed device 'naa.5000c50051394f65:1': No filesystem on the device
2018-05-10T12:35:38.197Z cpu3:2097178)ScsiDeviceIO: 3015: Cmd(0x459a40b53a40) 0x1a, CmdSN 0x352 from world 0 to dev "t10.SanDisk00Ultra00000000000000000000004C530001311229109510" failed H:0x0 D:0x2 P:0x0 Valid sense data: 0x5 0x24 0x0.
2018-05-10T12:35:38.225Z cpu0:2098648 opID=c86f69bb)World: 11942: VC opID 0f90c616 maps to vmkernel opID c86f69bb
2018-05-10T12:35:38.225Z cpu0:2098648 opID=c86f69bb)VC: 4616: Device rescan time 38 msec (total number of devices 4)
2018-05-10T12:35:38.225Z cpu0:2098648 opID=c86f69bb)VC: 4619: Filesystem probe time 50 msec (devices probed 4 of 4)
2018-05-10T12:35:38.225Z cpu0:2098648 opID=c86f69bb)VC: 4621: Refresh open volume time 0 msec
2018-05-10T12:36:01.982Z cpu0:2099252 opID=b22879f6)World: 11942: VC opID 0f90c64e maps to vmkernel opID b22879f6
2018-05-10T12:36:01.982Z cpu0:2099252 opID=b22879f6)NVDManagement: 1478: No nvdimms found on the system
2018-05-10T12:36:14.372Z cpu0:2099251 opID=8b2af442)World: 11942: VC opID 0f90c65c maps to vmkernel opID 8b2af442
2018-05-10T12:36:14.372Z cpu0:2099251 opID=8b2af442)LVM: 12674: LVMProbeDevice failed with status "Device does not contain a logical volume".
2018-05-10T12:36:14.374Z cpu0:2097701)ScsiDeviceIO: 3029: Cmd(0x459a40b72580) 0x16, CmdSN 0x484 from world 0 to dev "naa.5000c50051394f65" failed H:0x0 D:0x2 P:0x0 Valid sense data: 0x5 0x20 0x0.
2018-05-10T12:36:14.375Z cpu0:2099251 opID=8b2af442)LVM: 10419: LVMProbeDevice failed on (3444132192, naa.5000c50051394f65:1): Device does not contain a logical volume
2018-05-10T12:36:14.375Z cpu0:2099251 opID=8b2af442)FSS: 2350: Failed to create FS on dev [naa.5000c50051394f65:1] fs [test] type [vmfs6] fbSize 1048576 => Not supported
It looks like a VMFS partition has been created when I look again at the disk properties, but there's isn't any datastore:
I found lots of articles about clearing existing partitions on the disk which I did multiple times but it's not helping.
Can someone help?
Accepted Solutions
Solution found:
It was a ESOS config mistake I made so not so much related to ESXi:
I actually found the solution last night. I was messing around with all the options in ESOS and at some point I realize that I was always using the same type of device when going through the config: dev_disk
I'm really not familiar with ESOS, still learning, and for days I was stuck because I thought the ESOS config I had was correct since I could see the disk in ESXi...
So last night I changed the device type to vdisk_blockio and I was able to create a datastore 
I think it was very irritating at the end but I now know this important difference when creating devices which I suppose also exists when working with other san storage system...
Solution found:
It was a ESOS config mistake I made so not so much related to ESXi:
I actually found the solution last night. I was messing around with all the options in ESOS and at some point I realize that I was always using the same type of device when going through the config: dev_disk
I'm really not familiar with ESOS, still learning, and for days I was stuck because I thought the ESOS config I had was correct since I could see the disk in ESXi...
So last night I changed the device type to vdisk_blockio and I was able to create a datastore
I think it was very irritating at the end but I now know this important difference when creating devices which I suppose also exists when working with other san storage system...