Issue creating VMFS Datastore on an iSCSI storage device

[TomasKettlewell]

I am setting up a new storage array which will attach to the VM hosts via iSCSI, I have created the config, presented the disks and scanned the new devices in OK.

I am getting an error, when i try to create a VMFS datastore:

Operation failed, diagnostics report:  Unable to create Filesystem, please see VMkernel log for more details: Function not implemented

Logs from VMKernel show:

2018-11-07T12:27:00.414Z cpu14:33983 opID=b1a924d1)World: 14369: VC opID AddVmfsDatastoreFlow-add-1624371-ngc:70061446-2c-90 maps to vmkernel opID b1a924d1

2018-11-07T12:27:00.414Z cpu14:33983 opID=b1a924d1)Vol3: 731: Couldn't read volume header from control: Not supported

2018-11-07T12:27:00.414Z cpu14:33983 opID=b1a924d1)Vol3: 731: Couldn't read volume header from control: Not supported

2018-11-07T12:27:00.414Z cpu14:33983 opID=b1a924d1)FSS: 5099: No FS driver claimed device 'control': Not supported

2018-11-07T12:27:00.437Z cpu14:33983 opID=b1a924d1)FSS: 5099: No FS driver claimed device 'eui.0180007:1': Not supported

2018-11-07T12:27:00.439Z cpu14:33983 opID=b1a924d1)VC: 2052: Device rescan time 22 msec (total number of devices 6)

2018-11-07T12:27:00.439Z cpu14:33983 opID=b1a924d1)VC: 2055: Filesystem probe time 30 msec (devices probed 5 of 6)

2018-11-07T12:27:00.439Z cpu14:33983 opID=b1a924d1)VC: 2057: Refresh open volume time 1 msec

2018-11-07T12:27:00.486Z cpu14:33983 opID=b1a924d1)FSS: 5099: No FS driver claimed device 'eui.0180007:1': Not supported

2018-11-07T12:27:00.492Z cpu14:33983 opID=b1a924d1)Vol3: 731: Couldn't read volume header from control: Not supported

2018-11-07T12:27:00.492Z cpu14:33983 opID=b1a924d1)Vol3: 731: Couldn't read volume header from control: Not supported

2018-11-07T12:27:00.492Z cpu14:33983 opID=b1a924d1)FSS: 5099: No FS driver claimed device 'control': Not supported

2018-11-07T12:27:00.504Z cpu14:33983 opID=b1a924d1)VC: 2052: Device rescan time 19 msec (total number of devices 6)

2018-11-07T12:27:00.504Z cpu14:33983 opID=b1a924d1)VC: 2055: Filesystem probe time 36 msec (devices probed 6 of 6)

2018-11-07T12:27:00.504Z cpu14:33983 opID=b1a924d1)VC: 2057: Refresh open volume time 0 msec

2018-11-07T12:27:00.644Z cpu14:33983 opID=b1a924d1)Vol3: 731: Couldn't read volume header from control: Not supported

2018-11-07T12:27:00.644Z cpu14:33983 opID=b1a924d1)Vol3: 731: Couldn't read volume header from control: Not supported

2018-11-07T12:27:00.644Z cpu14:33983 opID=b1a924d1)FSS: 5099: No FS driver claimed device 'control': Not supported

2018-11-07T12:27:00.659Z cpu14:33983 opID=b1a924d1)FSS: 5099: No FS driver claimed device 'eui.0180007:1': Not supported

2018-11-07T12:27:00.669Z cpu14:33983 opID=b1a924d1)FSS: 5099: No FS driver claimed device 'eui.0180008:1': Not supported

2018-11-07T12:27:00.677Z cpu14:33983 opID=b1a924d1)VC: 2052: Device rescan time 23 msec (total number of devices 7)

2018-11-07T12:27:00.677Z cpu14:33983 opID=b1a924d1)VC: 2055: Filesystem probe time 36 msec (devices probed 6 of 7)

2018-11-07T12:27:00.677Z cpu14:33983 opID=b1a924d1)VC: 2057: Refresh open volume time 7 msec

2018-11-07T12:27:00.691Z cpu28:33154)NMP: nmp_ThrottleLogForDevice:2458: Cmd 0x16 (0x412ec3f4a740, 0) to dev "eui.0180008" on path "vmhba32:C1:T0:L3" Failed: H:0x0 D:0x2 P:0x0 Valid sense data: 0x5 0x26 0x0. Act:NONE

2018-11-07T12:27:00.691Z cpu28:33154)ScsiDeviceIO: 2369: Cmd(0x412ec3f4a740) 0x16, CmdSN 0x996 from world 0 to dev "eui.0180008" failed H:0x0 D:0x2 P:0x0 Valid sense data: 0x5 0x26 0x0.

2018-11-07T12:27:00.693Z cpu14:33983 opID=b1a924d1)LVM: 7611: LVMProbeDevice failed on (3707944608, eui.0180008:1): Device does not contain a logical volume

This is a clean disk (no previous formatting and nothing is attaching and formatting it).

[continuum]

> 2018-11-07T12:27:00.659Z cpu14:33983 opID=b1a924d1)FSS: 5099: No FS driver claimed device 'eui.0180007:1': Not supported

> 2018-11-07T12:27:00.669Z cpu14:33983 opID=b1a924d1)FSS: 5099: No FS driver claimed device 'eui.0180008:1': Not supported

Both disks listed here seem to have at least one existing partition.
Check with partedUtil and eventually delete any partitions that already exist.
> This is a clean disk (no previous formatting and nothing is attaching and formatting it).
Sure ? - the log snippets dont confirm that theory.

[TomasKettlewell]

Sure ? - the log snippets dont confirm that theory.

Yes, these are new volumes created in the storage array, the array itself is new with these volumes being the first ones created, i've deleted a couple and re-created new volumes and checked they have been created with new UUID's.

The only potential partition that could have been created was when I set a name on the disk in VMWare (which worked successfully), but I have tried creating a datastore on a new disk that had not been renamed with the same result.

[continuum]

Sometimes it helps to wipe the first 2gb on the device using
dd if=/dev/zero of=/dev/disks/DEVICE bs=1M count=2048
but in some cases that is not permitted.