VMware 6.7U3 NVMe Storage Issue

Notice: Page may contain affiliate links for which we may earn a small commission through services like Amazon Affiliates or Skimlinks.
S

schujj07

New Member
May 10, 2018
29
16
3
41
I am having problems with VMware seeing my new WD Gold NVMe SSDs on my HP DL385 Gen 10 hosts. I am getting this for logs for the 4 drives:

Code: 
2020-10-07T17:58:18.494Z cpu42:2098140)ScsiEvents: 501: Event Subsystem: Device Events, Created!
2020-10-07T17:58:18.494Z cpu42:2098140)VMWARE SCSI Id: Id for vmhba4:C0:T0:L0
0x30 0x30 0x42 0x37 0x5f 0x41 0x38 0x30 0x30 0x5f 0x38 0x33 0x45 0x45 0x5f 0x31 0x34 0x30 0x30 0x00 0x57 0x44 0x43 0x2d 0x57 0x44
2020-10-07T17:58:18.494Z cpu42:2098140)ScsiDeviceIO: 8515: QErr is correctly set to 0x0 for device t10.NVMe____WDC2DWDS768T1D0D2D01AJB0__________________00B7A80083EE1400.
2020-10-07T17:58:18.494Z cpu106:2097405)ScsiDeviceIO: 3469: Cmd(0x45a16f266f40) 0x1a, CmdSN 0x8888 from world 0 to dev "t10.NVMe____WDC2DWDS768T1D0D2D01AJB0__________________00B7A80083EE1400" failed H:0x0 D:0x2 P:0x0 Valid sense data: 0x
2020-10-07T17:58:18.494Z cpu42:2098140)ScsiDeviceIO: 9012: Could not detect setting of sitpua for device t10.NVMe____WDC2DWDS768T1D0D2D01AJB0__________________00B7A80083EE1400. Error Not supported.
2020-10-07T17:58:18.494Z cpu42:2098140)ScsiDevice: 3664: Failing registration of device 't10.NVMe____WDC2DWDS768T1D0D2D01AJB0__________________00B7A80083EE1400':  Unsupported device attributes isLocal:1, isSSD:1, isNmpPlugin:1
2020-10-07T17:58:18.494Z cpu42:2098140)ScsiDevice: 5486: Failed to Unregister 'REPORTED LUNS DATA CHANGED' unit attention for device:t10.NVMe____WDC2DWDS768T1D0D2D01AJB0__________________00B7A80083EE1400. Reason: Not found
2020-10-07T17:58:18.494Z cpu42:2098140)ScsiDevice: 5496: Failed to Unregister 'MODE PARAMETERS CHANGED' unit attention for device:t10.NVMe____WDC2DWDS768T1D0D2D01AJB0__________________00B7A80083EE1400. Reason: Not found
2020-10-07T17:58:18.494Z cpu42:2098140)ScsiDevice: 5506: Failed to Unregister 'CAPACITY DATA HAS CHANGED' unit attention for device:t10.NVMe____WDC2DWDS768T1D0D2D01AJB0__________________00B7A80083EE1400. Reason: Not found
2020-10-07T17:58:18.494Z cpu42:2098140)ScsiDevice: 5516: Failed to Unregister 'ASYMMETRIC ACCESS STATE CHANGED' unit attention for device:t10.NVMe____WDC2DWDS768T1D0D2D01AJB0__________________00B7A80083EE1400. Reason: Not found
2020-10-07T17:58:18.494Z cpu42:2098140)ScsiDevice: 5526: Failed to Unregister 'INQUIRY PARAMETERS CHANGED' unit attention for device:t10.NVMe____WDC2DWDS768T1D0D2D01AJB0__________________00B7A80083EE1400. Reason: Not found
2020-10-07T17:58:18.494Z cpu42:2098140)ScsiDevice: 5592: Unregistered device 't10.NVMe____WDC2DWDS768T1D0D2D01AJB0__________________00B7A80083EE1400' [0x430e00889200]
2020-10-07T17:58:18.494Z cpu42:2098140)ScsiEvents: 545: Event Subsystem: Device Events, Destroyed!
2020-10-07T17:58:18.494Z cpu42:2098140)WARNING: NMP: nmp_RegisterDevice:873: Registration of NMP device with primary uid 't10.NVMe____WDC2DWDS768T1D0D2D01AJB0__________________00B7A80083EE1400' failed. Not supported
2020-10-07T17:58:18.494Z cpu42:2098140)StorageApdHandler: 1063: Freeing APD handle 0x430e0085da60 []
2020-10-07T17:58:18.494Z cpu42:2098140)StorageApdHandler: 1147: APD Handle freed!
2020-10-07T17:58:18.497Z cpu78:2098142)StorageApdHandler: 977: APD Handle  Created with lock[StorageApd-0x430e00818ce0]
Running the command "esxcli storage core path list" gives information like this for those drives:

Code: 
pscsi.vmhba1-pscsi.0:0-
   UID: pscsi.vmhba1-pscsi.0:0-
   Runtime Name: vmhba1:C0:T0:L0
   Device: No associated device
   Device Display Name: No associated device
   Adapter: vmhba1
   Channel: 0
   Target: 0
   LUN: 0
   Plugin: NMP
   State: active
   Transport: parallel
   Adapter Identifier: pscsi.vmhba1
   Target Identifier: pscsi.0:0
   Adapter Transport Details: Unavailable or path is unclaimed
   Target Transport Details: Unavailable or path is unclaimed
   Maximum IO Size: 2097152
Sadly these SSD are not on the VMware HCL, however, they are basically rebadged Ultrastar SN640s that are on the HCL.

Troubleshooting already done:
Installed newest HP branded ESXi image
Installed newest HP Firmware Firmware (this allowed the drives to be seen in iLO.
Moved drives to different ports on the host
 
  • Like
Reactions: Derwood
D

Derwood

Member
May 22, 2019
52
1
8
Interesting topic and solution finding, reminds me of the NetApp 520B > 512B sector change. Just never seen anyone having to do such with ESXi.

Thanks very much for posting as I'm sure this will become something I come across soon.
 
R

Rand__

Well-Known Member
Mar 6, 2014
6,655
1,781
113
schujj07 said:
Ended up being that the drives are formatted for 4Kn and VMware doesn't support NVMe SSD with 4Kn formatting. Once they were reformatted to 512e I was able to access them.
Click to expand...
Thanks for this, spent the evening trying to find out why ESXi didnt want that stupid nvme drive while it was working fine when passed through to windows....
Must have played with sectors one time and reformated to 4kn...
 
You must log in or register to reply here.
Top Bottom