I know this thread is old but I've also recently run into a similar problem. My ESXi 6.7 host gives me an error when I try to create a datastore on a volume on my HP P2000 StorageWorks array. The error that ESXi gives me in the web browser is "Failed to create VMFS datastore: Cannot change the host configuration"
Already Tried:
-Deleting the RAID array and making a new one
-Deleting the volume and making a new one
-Manually creating partitions using fdisk
-Manually creating partition tables using partedUtil
Below are the VMkernel logs.
2019-02-11T22:18:26.424Z cpu14:2097435)WARNING: ScsiDevice: 7641: GetDeviceAttributes during periodic probe'naa.600c0ff00011cebd0000000000000000': failed with Not found
2019-02-11T22:23:26.418Z cpu14:2097435)WARNING: VMW_SATP_ALUA: satp_alua_issueCommandOnPath:792: Path "vmhba64:C1:T0:L4" determined to be in unexpected NOT READY state when probed (0x2/0x4/0x3).
2019-02-11T22:23:26.420Z cpu12:2097435)WARNING: VMW_SATP_ALUA: satp_alua_issueCommandOnPath:792: Path "vmhba64:C2:T0:L4" determined to be in unexpected NOT READY state when probed (0x2/0x4/0x3).
2019-02-11T22:23:26.420Z cpu12:2097435)WARNING: VMW_SATP_ALUA: satp_alua_issueCommandOnPath:792: Path "vmhba64:C0:T0:L4" determined to be in unexpected NOT READY state when probed (0x2/0x4/0x3).
2019-02-11T22:23:26.421Z cpu12:2097435)WARNING: VMW_SATP_ALUA: satp_alua_issueCommandOnPath:792: Path "vmhba64:C1:T0:L5" determined to be in unexpected NOT READY state when probed (0x2/0x4/0x3).
2019-02-11T22:23:26.422Z cpu12:2097435)WARNING: VMW_SATP_ALUA: satp_alua_issueCommandOnPath:792: Path "vmhba64:C2:T0:L5" determined to be in unexpected NOT READY state when probed (0x2/0x4/0x3).
2019-02-11T22:23:26.423Z cpu12:2097435)WARNING: VMW_SATP_ALUA: satp_alua_issueCommandOnPath:792: Path "vmhba64:C0:T0:L5" determined to be in unexpected NOT READY state when probed (0x2/0x4/0x3).
2019-02-11T22:23:26.423Z cpu12:2097435)WARNING: ScsiDevice: 7641: GetDeviceAttributes during periodic probe'naa.600c0ff00011dc040000000000000000': failed with Not found
2019-02-11T22:23:26.424Z cpu12:2097435)WARNING: ScsiDevice: 7641: GetDeviceAttributes during periodic probe'naa.600c0ff00011cebd0000000000000000': failed with Not found
2019-02-11T22:28:26.419Z cpu12:2097435)WARNING: VMW_SATP_ALUA: satp_alua_issueCommandOnPath:792: Path "vmhba64:C1:T0:L4" determined to be in unexpected NOT READY state when probed (0x2/0x4/0x3).
2019-02-11T22:28:26.420Z cpu12:2097435)WARNING: VMW_SATP_ALUA: satp_alua_issueCommandOnPath:792: Path "vmhba64:C2:T0:L4" determined to be in unexpected NOT READY state when probed (0x2/0x4/0x3).
2019-02-11T22:28:26.420Z cpu12:2097435)WARNING: VMW_SATP_ALUA: satp_alua_issueCommandOnPath:792: Path "vmhba64:C0:T0:L4" determined to be in unexpected NOT READY state when probed (0x2/0x4/0x3).
2019-02-11T22:28:26.422Z cpu12:2097435)WARNING: VMW_SATP_ALUA: satp_alua_issueCommandOnPath:792: Path "vmhba64:C1:T0:L5" determined to be in unexpected NOT READY state when probed (0x2/0x4/0x3).
2019-02-11T22:28:26.423Z cpu12:2097435)WARNING: VMW_SATP_ALUA: satp_alua_issueCommandOnPath:792: Path "vmhba64:C2:T0:L5" determined to be in unexpected NOT READY state when probed (0x2/0x4/0x3).
2019-02-11T22:28:26.423Z cpu12:2097435)WARNING: VMW_SATP_ALUA: satp_alua_issueCommandOnPath:792: Path "vmhba64:C0:T0:L5" determined to be in unexpected NOT READY state when probed (0x2/0x4/0x3).
2019-02-11T22:28:26.423Z cpu12:2097435)WARNING: ScsiDevice: 7641: GetDeviceAttributes during periodic probe'naa.600c0ff00011dc040000000000000000': failed with Not found
2019-02-11T22:28:26.424Z cpu12:2097435)WARNING: ScsiDevice: 7641: GetDeviceAttributes during periodic probe'naa.600c0ff00011cebd0000000000000000': failed with Not found
2019-02-11T22:33:26.435Z cpu12:2097435)WARNING: VMW_SATP_ALUA: satp_alua_issueCommandOnPath:792: Path "vmhba64:C1:T0:L4" determined to be in unexpected NOT READY state when probed (0x2/0x4/0x3).
2019-02-11T22:33:26.437Z cpu12:2097435)WARNING: VMW_SATP_ALUA: satp_alua_issueCommandOnPath:792: Path "vmhba64:C2:T0:L4" determined to be in unexpected NOT READY state when probed (0x2/0x4/0x3).
2019-02-11T22:33:26.438Z cpu12:2097435)WARNING: VMW_SATP_ALUA: satp_alua_issueCommandOnPath:792: Path "vmhba64:C0:T0:L4" determined to be in unexpected NOT READY state when probed (0x2/0x4/0x3).
2019-02-11T22:33:26.438Z cpu12:2097435)WARNING: VMW_SATP_ALUA: satp_alua_issueCommandOnPath:792: Path "vmhba64:C1:T0:L5" determined to be in unexpected NOT READY state when probed (0x2/0x4/0x3).
2019-02-11T22:33:26.438Z cpu12:2097435)WARNING: VMW_SATP_ALUA: satp_alua_issueCommandOnPath:792: Path "vmhba64:C2:T0:L5" determined to be in unexpected NOT READY state when probed (0x2/0x4/0x3).
2019-02-11T22:33:26.439Z cpu12:2097435)WARNING: VMW_SATP_ALUA: satp_alua_issueCommandOnPath:792: Path "vmhba64:C0:T0:L5" determined to be in unexpected NOT READY state when probed (0x2/0x4/0x3).
2019-02-11T22:33:26.439Z cpu12:2097435)WARNING: ScsiDevice: 7641: GetDeviceAttributes during periodic probe'naa.600c0ff00011dc040000000000000000': failed with Not found
2019-02-11T22:33:26.440Z cpu12:2097435)WARNING: ScsiDevice: 7641: GetDeviceAttributes during periodic probe'naa.600c0ff00011cebd0000000000000000': failed with Not found
2019-02-11T22:33:26.449Z cpu3:2097429)StorageApdHandler: 977: APD Handle Created with lock[StorageApd-0x4303bde69e90]
2019-02-11T22:33:26.449Z cpu3:2097429)ScsiEvents: 501: Event Subsystem: Device Events, Created!
2019-02-11T22:33:26.449Z cpu3:2097429)VMWARE SCSI Id: Id for vmhba64:C1:T0:L6
0x60 0x0c 0x0f 0xf0 0x00 0x11 0xce 0xbd 0x0f 0x92 0x61 0x5c 0x01 0x00 0x00 0x00 0x50 0x32 0x30 0x30 0x30 0x47
2019-02-11T22:33:26.449Z cpu3:2097429)VMWARE SCSI Id: Id for vmhba64:C2:T0:L6
0x60 0x0c 0x0f 0xf0 0x00 0x11 0xce 0xbd 0x0f 0x92 0x61 0x5c 0x01 0x00 0x00 0x00 0x50 0x32 0x30 0x30 0x30 0x47
2019-02-11T22:33:26.450Z cpu3:2097429)VMWARE SCSI Id: Id for vmhba64:C0:T0:L6
0x60 0x0c 0x0f 0xf0 0x00 0x11 0xce 0xbd 0x0f 0x92 0x61 0x5c 0x01 0x00 0x00 0x00 0x50 0x32 0x30 0x30 0x30 0x47
2019-02-11T22:33:26.450Z cpu3:2097429)ScsiDeviceIO: 9297: Get VPD 86 Inquiry for device "naa.600c0ff00011cebd0f92615c01000000" from Plugin "NMP" failed. Not supported
2019-02-11T22:33:26.450Z cpu3:2097429)ScsiDeviceIO: 7998: QErr is correctly set to 0x0 for device naa.600c0ff00011cebd0f92615c01000000.
2019-02-11T22:33:26.451Z cpu3:2097429)ScsiDeviceIO: 8495: Could not detect setting of sitpua for device naa.600c0ff00011cebd0f92615c01000000. Error Not supported.
2019-02-11T22:33:26.467Z cpu3:2097429)ScsiEvents: 300: EventSubsystem: Device Events, Event Mask: 40, Parameter: 0x4303bde743c0, Registered!
2019-02-11T22:33:26.467Z cpu3:2097429)ScsiEvents: 300: EventSubsystem: Device Events, Event Mask: 200, Parameter: 0x4303bde743c0, Registered!
2019-02-11T22:33:26.467Z cpu3:2097429)ScsiEvents: 300: EventSubsystem: Device Events, Event Mask: 800, Parameter: 0x4303bde743c0, Registered!
2019-02-11T22:33:26.467Z cpu3:2097429)ScsiEvents: 300: EventSubsystem: Device Events, Event Mask: 400, Parameter: 0x4303bde743c0, Registered!
2019-02-11T22:33:26.467Z cpu3:2097429)ScsiEvents: 300: EventSubsystem: Device Events, Event Mask: 8, Parameter: 0x4303bde743c0, Registered!
2019-02-11T22:33:26.467Z cpu3:2097429)ScsiDevice: 4936: Successfully registered device "naa.600c0ff00011cebd0f92615c01000000" from plugin "NMP" of type 0
2019-02-11T22:33:26.467Z cpu3:2097429)NMP: nmp_DeviceUpdateProtectionInfo:747: Set protection info for device 'naa.600c0ff00011cebd0f92615c01000000', Enabled: 0 ProtType: 0x0 Guard: 0x0 ProtMask: 0x0
2019-02-11T22:33:26.467Z cpu3:2097429)ScsiEvents: 300: EventSubsystem: Device Events, Event Mask: 180, Parameter: 0x4309de76e2a0, Registered!
2019-02-11T22:33:34.797Z cpu5:2098772 opID=2a26ee8a)World: 11942: VC opID 0d3b2165 maps to vmkernel opID 2a26ee8a
2019-02-11T22:33:34.797Z cpu5:2098772 opID=2a26ee8a)NVDManagement: 1478: No nvdimms found on the system
2019-02-11T22:34:14.375Z cpu5:2099337 opID=7e6bf57)World: 11942: VC opID 0d3b2170 maps to vmkernel opID 7e6bf57
2019-02-11T22:34:14.375Z cpu5:2099337 opID=7e6bf57)VC: 4616: Device rescan time 699 msec (total number of devices 3)
2019-02-11T22:34:14.375Z cpu5:2099337 opID=7e6bf57)VC: 4619: Filesystem probe time 2770 msec (devices probed 3 of 3)
2019-02-11T22:34:14.375Z cpu5:2099337 opID=7e6bf57)VC: 4621: Refresh open volume time 0 msec
2019-02-11T22:34:23.498Z cpu6:2097446)ScsiPath: 8458: DeletePath : adapter=vmhba64, channel=0, target=0, lun=4
2019-02-11T22:34:23.498Z cpu0:2097448)ScsiPath: 8458: DeletePath : adapter=vmhba64, channel=0, target=0, lun=5
2019-02-11T22:34:23.498Z cpu6:2097446)WARNING: VMW_SATP_ALUA: satp_alua_issueCommandOnPath:792: Path "vmhba64:C1:T0:L4" determined to be in unexpected NOT READY state when probed (0x2/0x4/0x3).
2019-02-11T22:34:23.499Z cpu6:2097446)WARNING: VMW_SATP_ALUA: satp_alua_issueCommandOnPath:792: Path "vmhba64:C2:T0:L4" determined to be in unexpected NOT READY state when probed (0x2/0x4/0x3).
2019-02-11T22:34:23.499Z cpu6:2097446)WARNING: ScsiPath: 8537: Remove path: vmhba64:C0:T0:L4
2019-02-11T22:34:23.499Z cpu6:2097446)ScsiPath: 8458: DeletePath : adapter=vmhba64, channel=2, target=0, lun=4
2019-02-11T22:34:23.499Z cpu0:2097448)WARNING: VMW_SATP_ALUA: satp_alua_issueCommandOnPath:792: Path "vmhba64:C1:T0:L5" determined to be in unexpected NOT READY state when probed (0x2/0x4/0x3).
[root@localhost:~] partedUtil getptbl
Usage:
Get Partitions : get <diskName>
Set Partitions : set <diskName> ["partNum startSector endSector type attr"]*
Delete Partition : delete <diskName> <partNum>
Resize Partition : resize <diskName> <partNum> <start> <end>
Get Partitions : getptbl <diskName>
Set Partitions : setptbl <diskName> <label> ["partNum startSector endSector type/guid attr"]*
Fix Partition Table : fix <diskName>
Create New Label (all existing data will be lost): mklabel <diskName> <label>
Show commonly used partition type guids : showGuids
Get usable first and last sectors : getUsableSectors <diskName>
Fix GPT Table interactively : fixGpt <diskName>
Show Partition Information : partinfo <diskName> <partNum>
Add Partition Information : add <diskName> <label> ["partNum startSector endSector type/guid attr"]
[root@localhost:~] partedUtil -l
Usage:
Get Partitions : get <diskName>
Set Partitions : set <diskName> ["partNum startSector endSector type attr"]*
Delete Partition : delete <diskName> <partNum>
Resize Partition : resize <diskName> <partNum> <start> <end>
Get Partitions : getptbl <diskName>
Set Partitions : setptbl <diskName> <label> ["partNum startSector endSector type/guid attr"]*
Fix Partition Table : fix <diskName>
Create New Label (all existing data will be lost): mklabel <diskName> <label>
Show commonly used partition type guids : showGuids
Get usable first and last sectors : getUsableSectors <diskName>
Fix GPT Table interactively : fixGpt <diskName>
Show Partition Information : partinfo <diskName> <partNum>
Add Partition Information : add <diskName> <label> ["partNum startSector endSector type/guid attr"]
[root@localhost:~] fdisk -l
***
*** The fdisk command is deprecated: fdisk does not handle GPT partitions. Please use partedUtil
***
Disk /dev/disks/naa.600c0ff00011cebd0f92615c01000000: 499.5 GB, 499590955008 bytes
255 heads, 63 sectors/track, 60738 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Disk /dev/disks/naa.600c0ff00011cebd0f92615c01000000 doesn't contain a valid partition table
Found valid GPT with protective MBR; using GPT
Disk /dev/disks/mpx.vmhba32:C0:T0:L0: 15278080 sectors, 3364M
Logical sector size: 512
Disk identifier (GUID): e75aaf72-26be-4f51-9ad1-b8d85ca2ddb2
Partition table holds up to 128 entries
First usable sector is 34, last usable sector is 15278046
Number Start (sector) End (sector) Size Code Name
1 64 8191 4064K 0700
5 8224 520191 249M 0700
6 520224 1032191 249M 0700
7 1032224 1257471 109M 0700
8 1257504 1843199 285M 0700
9 1843200 7086079 2560M 0700