Help with Intel D4502 on ESXi 6.7U3

[ipreferpie]

Hi everyone,

I recently purchased 2 used Intel D4502 U.2 7.68TB NVMe drives and am having problems having ESXi 6.7U3 detecting the drives. Here's what I did:

ESXi server --
-attached to Supermicro AOC-SLG3-4E4T HBA to Supermicro BPN-SAS3-846-8N backplane. (Have an Intel Optane 905p 960GB U.2 attached with no problems)
-installed Intel SSD DC Tools 3.0.26 for ESXi 6.7
-installed intel-nvme-vmd-1.8.0.1001-1OEM.670.0.0.8169922.x86_64.vib driver
-cannot see in Storage devices under ESXi and isdct tool doesn't detect anything

Testing on Windows 10 box --
-attached to Intel M.2 to U.2 adapter
-installed Intel SSD DC Tools 3.0.26 for Windows
-installed Intel NVMe Miniport and Filter Device Management
-only AFTER the NVMe Miniport and Filter Device Management was installed can isdct.exe detect the D4502 drive (say it's in good health and firmware is updated to QDV1ED0E)
-under Device Manager, I can see that Intel(R) SSD DC P4500/4600/4501/4601/4608/4510/4610/4511 Series is installed as a Storage controller
-however, under Disk Management the D4502 doesn't show up
-using the Intel Management and Storage Tool, the D4502 shows up but cannot scan or erase

Am I missing some type of driver in ESXi to get it to work? Although my goal isn't to get the D4502 drives working in Windows, I am experiencing problems. Wondering if anyone with experience can chime in, it'll be greatly appreciated!

 

[ipreferpie]

Here's my output from isdct.exe show -a -intelssd

- Intel SSD DC D4502 BTLD74630DJD8P0F -

AggregationThreshold : 0
AggregationTime : 0
ArbitrationBurst : 4
Bootloader : 0114
CoalescingDisable : Invalid Field in Command
ControllerCompatibleIDs : PCI\\VEN_8086&DEV_0A54&REV_00PCI\\VEN_8086&DEV_0A54PCI\\VEN_8086&CC_010802PCI\\VEN_8086&CC_0108PCI\\VEN_8086PCI\\CC_010802PCI\\CC_0108
ControllerDescription : @oem71.inf,%pci\\ven_8086&dev_0a54.devicedesc%;Intel(R) SSD DC P4500/4600/4501/4601/4608/4510/4610/4511 Series
ControllerID : PCI\\VEN_8086&DEV_0A54&SUBSYS_01001120&REV_00\\4&712265C&0&0009
ControllerIDEMode : False
ControllerManufacturer : @oem71.inf,%intel%;Intel
ControllerService : IaNVMe
DevicePath : \\\\.\\SCSI4:
DeviceStatus : Healthy
DirectivesSupported : False
DisableThermalThrottle : Invalid Field in Command
DriverDescription : Intel(R) SSD DC P4500/4600/4501/4601/4608/4510/4610/4511 Series
DriverMajorVersion : 4
DriverManufacturer : Intel
DriverMinorVersion : 4
DriverVersion : 4.4.0.1003
DynamicMMIOEnabled : The selected drive does not support this feature.
EnduranceAnalyzer : Media Workload Indicators have reset values. Run 60+ minute workload prior to running the endurance analyzer.
ErrorString : Value not found
Firmware : QDV1ED0E
FirmwareActivationNoticesConfiguration : False
FirmwareUpdateAvailable : No known update for SSD. If an update is expected, please contact your SSD Vendor representative about firmware update for this drive.
FormatNVMCryptoEraseSupported : True
FormatNVMSupported : True
HighPriorityWeightArbitration : 15
IOCompletionQueuesRequested : 127
IOSubmissionQueuesRequested : 127
Index : 0
Intel : True
IntelGen3SATA : False
IntelNVMe : True
InterruptVector : Invalid Field in Command
IsDualPort : True
LatencyTrackingEnabled : False
LowPriorityWeightArbitration : 15
MediumPriorityWeightArbitration : 15
ModelNumber : INTEL SSDPD2KS076T7M
NVMe1Point2OrGreater : True
NVMeControllerID : 0
NVMeMajorVersion : 1
NVMeMinorVersion : 2
NVMePowerState : 0
NVMeTertiaryVersion : 0
NamespaceAttributeNoticesConfiguration : False
NamespaceId : 4294967295
NamespaceManagementSupported : True
NativeMaxLBA : Failed to retrieve data from selected device.
NumErrorLogPageEntries : 63
NumberOfNamespacesSupported : 16
OEM : EMC
OpalState : Unsupported
PCILinkGenSpeed : 3
PCILinkGenSpeedBackground : 3
PCILinkGenSpeedOther : 0
PCILinkGenSpeedThis : 3
PCILinkWidth : 4
PCILinkWidthBackground : 4
PCILinkWidthOther : 0
PCILinkWidthThis : 2
PLITestTimeInterval : The selected drive does not support this feature.
PNPString : PCI\\VEN_8086&DEV_0A54&SUBSYS_01001120&REV_00\\4&712265C&0&0009
PhyConfig : The selected drive does not support this feature.
PhySpeed : The selected drive does not support this feature.
PhysicalSectorSize : The selected drive does not support this feature.
PowerGovernorAveragePower : Feature is not supported.
PowerGovernorBurstPower : Feature is not supported.
PowerGovernorMode : 0
Product : Cliffdale DP
ProductFamily : Intel SSD DC D4502
ProductProtocol : NVME
ReadErrorRecoveryTimer : Device does not support this command set.
SCSIPortNumber : 4
SMARTEnabled : True
SMARTHealthCriticalWarningsConfiguration : 0
SMBusAddress : 255
SMI : False
SanitizeBlockEraseSupported : True
SanitizeCryptoScrambleSupported : True
SanitizeOverwriteSupported : False
SectorSize : 512
SelfTestSupported : True
SerialNumber : BTLDxxxxxxxxxxxxxxxxxx
TCGSupported : True
TelemetryLogSupported : True
TempThreshold : 70
TemperatureLoggingInterval : The selected drive does not support this feature.
TimeLimitedErrorRecovery : Invalid Field in Command
TrimSupported : True
VolatileWriteCacheEnabled : Drive does not support Write Cache.
WriteAtomicityDisableNormal : 0
WriteCacheReorderingStateEnabled : The selected drive does not support this feature.
WriteCacheState : The selected drive does not support this feature.
WriteErrorRecoveryTimer : Device does not support this command set.

 

[ipreferpie]

another quick positive update:

In ESXi, I get to see that " NVMe Datacenter SSD [3DNAND, Beta Rock Controller] " is listed in the hardware section and can be passed through. The drive can be seen also as a device under "Storage". Strange thing is that it keeps in dropping in and out randomly during reboots. Takes around 5-7 reboots to see both. It's getting closer to working but super frustrating.

Also, the drops likely aren't temperature related. They're hovering between 35C to 45C.

Going to take a break. After a successful passthrough, I'll try to see if the drives can be read in a Windows and an OpenSolaris ZFS VM later.

 

[ipreferpie]

Solved the issue. Had to use isdct to detach, delete, create then attach a new namespace in that order. Now Windows and Linux can read it.

 

[mirrormax]

how was the speed of these drives? hard to find any benchmarks