Community
cancel
Showing results for 
Search instead for 
Did you mean: 
Highlighted
Community Manager
2,226 Views

Intel DC P4510 U.2 are not recognized in ESXI

Hello,

we use a backplane from Supermicro with 4x DC P4510 1GB with a Broadcom 9400-16i controller. The hard disks are recognized in the BIOS and displayed correctly. In the ESXI the drives do not appear after booting.

We use:

Fresh Installation - VMWare 6.7 U1

Supermicro X11DPi-NT

Intel Data Center Tool 3.0.14-400

Latest Intel NVMe VMD 1.4.0.1016 (we also try 1.3.2.8 and 1.2.1.15)

Broadcom 9400-16i (also try 9405W-16i) with latest Firmware P8 in IT Mode

Broadcom LSI msgpt35-08 Latest Driver

When we use the Broadcom Controller in Passthrough the Drives are visibel under Freenas. But they are not recognized as NVMe drives and are very slow. So I think it's a driver problem

What can we do....

Best regards

André

0 Kudos
8 Replies
Highlighted
Community Manager
135 Views

Hello andy_web,

 

 

Thank you for contacting Intel® Technical Support.

 

 

As we understand, you need assistance with your Intel® SSD DC P4510 Series (1.0TB, 2.5in PCIe 3.1 x4, 3D2, TLC)If we infer correctly, please review the information below:

 

  • We advise you to contact your OEM and VMware* in order to get further information and support regarding the available driver support and compatibility for your current configuration performance issue.

 

From our side, since your drive is detected by the BIOS and the OS it seems to be more a matter of configuration that from the drive itself.

 

 

In order to confirm this we will appreciate if you can provide us with the Smart logs from your Intel® SSD DC P4510 Series (1.0TB, 2.5in PCIe 3.1 x4, 3D2, TLC):

 

 

The Intel's Data Center Tool (DCT) can be used to read out the SMART attributes to download this tool please follow this link:

 

https://downloadcenter.intel.com/download/27863/Intel-SSD-Data-Center-Tool https://downloadcenter.intel.com/download/27863/Intel-SSD-Data-Center-Tool

 

We hope you find this information useful.

 

 

We will be looking forward to your reply including the smart logs.

 

 

Best regards,

 

 

Josh B.

 

Intel® Customer Support Technician

 

Under Contract to Intel Corporation

 

0 Kudos
Highlighted
Community Manager
135 Views

Hello Josh,

Thanks for the reply!

The Supermicro website lists only SATA drives. Why does the board have then 2 PCI-E 3.0 NVMe x4 Internal Port (s)?

The latest driver on the VMWare website is used. This is 1.4.0.1016 Even the older drivers have already been tested, as this has indeed to other users here in the forum to success. Look here:

 

Here is the Logfile:

/opt/intel/isdct$ ./isdct show -intelssd

No results

/opt/intel/isdct$ ./isdct set -system LogFile = 'log.txt'

Set LogFile successful.

/opt/intel/isdct$ ./isdct set -system EnableLog = 'true'

Set EnableLog successful.

/opt/intel/isdct$ ./isdct show -intelssd

No results

/opt/intel/isdct$ more log.txt

05:51:51:286353 [debug] tdk_interface_dll.cpp(289) SendXMLMessage: Entering

05:51:51:288268 [debug] TDKInterface.cpp(345) scan: Entering

05:51:51:288284 [debug] DeviceFinder_NVME.cpp(66) scan: Entering

05:51:51:288291 [debug] DeviceFinder_NVME.cpp(110) scanPhysicalDevices: Entering

05:51:51:288304 [debug] DeviceFinder_NVME.cpp(310) getNVMeAdapters: Entering

05:51:51:288413 [debug] DeviceFinder_NVME.cpp(343) getNVMeAdapters: Failed to initialize VMK handle to retrieve NVMe adapter list.

05:51:51:288429 [debug] DeviceFinder_NVME.cpp getNVMeAdapters: Exiting

05:51:51:288451 [debug] DeviceFinder_NVME.cpp(151) discoverPhysicalDevice: Entering

05:51:51:288492 [error] Connection_Path.cpp(95) open: vmk_MgmtUserInit error: 19

05:51:51:288502 [error] DeviceFinder_NVME.cpp(182) discoverPhysicalDevice: Failed to connect to device. Ignoring intel-nvme0

05:51:51:288510 [debug] DeviceFinder_NVME.cpp discoverPhysicalDevice: Exiting

05:51:51:288518 [debug] DeviceFinder_NVME.cpp(151) discoverPhysicalDevice: Entering

05:51:51:288544 [error] Connection_Path.cpp(95) open: vmk_MgmtUserInit error: 19

05:51:51:288552 [error] DeviceFinder_NVME.cpp(182) discoverPhysicalDevice: Failed to connect to device. Ignoring intel-nvme1

05:51:51:288558 [debug] DeviceFinder_NVME.cpp discoverPhysicalDevice: Exiting

05:51:51:288565 [debug] DeviceFinder_NVME.cpp(151) discoverPhysicalDevice: Entering

05:51:51:288590 [error] Connection_Path.cpp(95) open: vmk_MgmtUserInit error: 19

05:51:51:288598 [error] DeviceFinder_NVME.cpp(182) discoverPhysicalDevice: Failed to connect to device. Ignoring intel-nvme2

05:51:51:288604 [debug] DeviceFinder_NVME.cpp discoverPhysicalDevice: Exiting

05:51:51:288611 [debug] DeviceFinder_NVME.cpp(151) discoverPhysicalDevice: Entering

05:51:51:288635 [error] Connection_Path.cpp(95) open: vmk_MgmtUserInit error: 19

05:51:51:288642 [error] DeviceFinder_NVME.cpp(182) discoverPhysicalDevice: Failed to connect to device. Ignoring intel-nvme3

05:51:51:288649 [debug] DeviceFinder_NVME.cpp discoverPhysicalDevice: Exiting

05:51:51:288655 [debug] DeviceFinder_NVME.cpp(151) discoverPhysicalDevice: Entering

05:51:51:288679 [error] Connection_Path.cpp(95) open: vmk_MgmtUserInit error: 19

05:51:51:288687 [error] DeviceFinder_NVME.cpp(182) discoverPhysicalDevice: Failed to connect to device. Ignoring intel-nvme4

05:51:51:288693 [debug] DeviceFinder_NVME.cpp discoverPhysicalDevice: Exiting

05:51:51:288700 [debug] DeviceFinder_NVME.cpp(151) discoverPhysicalDevice: Entering

05:51:51:288723 [error] Connection_Path.cpp(95) open: vmk_MgmtUserInit error: 19

05:51:51:288731 [error] DeviceFinder_NVME.cpp(182) discoverPhysicalDevice: Failed to connect to device. Ignoring intel-nvme5

05:51:51:288737 [debug] DeviceFinder_NVME.cpp discoverPhysicalDevice: Exiting

05:51:51:288743 [debug] DeviceFinder_NVME.cpp(151) discoverPhysicalDevice: Entering

05:51:51:288767 [error] Connection_Path.cpp(95) open: vmk_MgmtUserInit error: 19

05:51:51:288774 [error] DeviceFinder_NVME.cpp(182) discoverPhysicalDevice: Failed to connect to device. Ignoring intel-nvme6

05:51:51:288780 [debug] DeviceFinder_NVME.cpp discoverPhysicalDevice: Exiting

05:51:51:288787 [debug] DeviceFinder_NVME.cpp(151) discoverPhysicalDevice: Entering

05:51:51:288810 [error] Connection_Path.cpp(95) open: vmk_MgmtUserInit error: 19

05:51:51:288818 [error] DeviceFinder_NVME.cpp(182) discoverPhysicalDevice: Failed to connect to device. Ignoring intel-nvme7

05:51:51:288824 [debug] DeviceFinder_NVME.cpp discoverPhysicalDevice: Exiting

05:51:51:288830 [debug] DeviceFinder_NVME.cpp(151) discoverPhysicalDevice: Entering

05:51:51:288854 [error] Connection_Path.cpp(95) open: vmk_MgmtUserInit error: 19

05:51:51:288861 [error] DeviceFinder_NVME.cpp(182) discoverPhysicalDevice: Failed to connect to device. Ignoring intel-nvme8

05:51:51:288867 [debug] DeviceFinder_NVME.cpp discoverPhysicalDevice: Exiting

05:51:51:288874 [debug] DeviceFinder_NVME.cpp(151) discoverPhysicalDevice: Entering

05:51:51:288897 [error] Connection_Path.cpp(95) open: vmk_MgmtUserInit error: 19

05:51:51:288905 [error] DeviceFinder_NVME.cpp(182) discoverPhysicalDevice: Failed to connect to device. Ignoring intel-nvme9

05:51:51:288915 [debug] DeviceFinder_NVME.cpp discoverPhysicalDevice: Exiting

05:51:51:288922 [debug] DeviceFinder_NVME.cpp(151) discoverPhysicalDevice: Entering

05:51:51:288946 [error] Connection_Path.cpp(95) open: vmk_MgmtUserInit error: 19

05:51:51:288953 [error] DeviceFinder_NVME.cpp(182) discoverPhysicalDevice: Failed to connect to device. Ignoring intel-nvme10

05:51:51:288959 [debug] DeviceFinder_NVME.cpp discoverPhysicalDevice: Exiting

05:51:51:288966 [debug] DeviceFinder_NVME.cpp(151) discoverPhysicalDevice: Entering

05:51:51:288990 [error] Connection_Path.cpp(95) open: vmk_MgmtUserInit error: 19

05:51:51:288998 [error] DeviceFinder_NVME.cpp(182) discoverPhysicalDevice: Failed to connect to device. Ignoring intel-nvme11

05:51:51:289004 [debug] DeviceFinder_NVME.cpp discoverPhysicalDevice: Exiting

05:51:51:289010 [debug] DeviceFinder_NVME.cpp(151) discoverPhysicalDevice: Entering

05:51:51:289034 [error] Connection_Path.cpp(95) open: vmk_MgmtUserInit error: 19

05:51:51:289041 [error] DeviceFinder_NVME.cpp(182) discoverPhysicalDevice: Failed to connect to device. Ignoring intel-nvme12

05:51:51:289047 [debug] DeviceFinder_NVME.cpp discoverPhysicalDevice: Exiting

05:51:51:289054 [debug] DeviceFinder_NVME.cpp(151) discoverPhysicalDevice: Entering

05:51:51:289077 [error] Connection_Path.cpp(95) open: vmk_MgmtUserInit error: 19

05:51:51:289085 [error] DeviceFinder_NVME.cpp(182) discoverPhysicalDevice: Failed to connect to device. Ignoring intel-nvme13

05:51:51:289091 [debug] DeviceFinder_NVME.cpp discoverPhysicalDevice: Exiting

05:51:51:289097 [debug] DeviceFinder_NVME.cpp(151) discoverPhysicalDevice: Entering

05:51:51:289121 [error] Connection_Path.cpp(95) open: vmk_MgmtUserInit error: 19

05:51:51:289128 [error] DeviceFinder_NVME.cpp(182) discoverPhysicalDevice: Failed to connect to device. Ignoring intel-nvme14

05:51:51:289134 [debug] DeviceFinder_NVME.cpp discoverPhysicalDevice: Exiting

05:51:51:289141 [debug] DeviceFinder_NVME.cpp(151) discoverPhysicalDevice: Entering

05:51:51:289164 [error] Connection_Path.cpp(95) open: ...

0 Kudos
Highlighted
Community Manager
135 Views

Hello Josh,

I tested a little bit further. I connected the Intel NVMe boards from the backplane to the motherboard with an Occulink cable. All three possible drivers (1.4.0.1016, 1.3.2.8, and 1.2.1.15) do not display disks in VMware. The plates are found by ISDCT.

/opt/intel/isdct$ ./isdct show -intelssd

- Intel SSD DC P4510 Series BTLJ82XXXXXXXXXXXXXX

Bootloader : 0203

DevicePath : intel-nvme0

DeviceStatus : Healthy

Firmware : VDV10131

FirmwareUpdateAvailable : The selected Intel SSD contains current firmware as of this tool release.

Index : 0

ModelNumber : INTEL SSDPE2KX010T8

ProductFamily : Intel SSD DC P4510 Series

SerialNumber : BTLJ82XXXXXXXXXXXXXX

- Intel SSD DC P4510 Series BTLJ82XXXXXXXXXXXXXX

Bootloader : 0203

DevicePath : intel-nvme1

DeviceStatus : Healthy

Firmware : VDV10131

FirmwareUpdateAvailable : The selected Intel SSD contains current firmware as of this tool release.

Index : 1

ModelNumber : INTEL SSDPE2KX010T8

ProductFamily : Intel SSD DC P4510 Series

SerialNumber : BTLJ82XXXXXXXXXXXXXX

With the driver 1.2.1.15 the memory adapter is detected as DC P3520. See the screenshot.

Unfortunately, no drive is detected for all drivers in ESXI.

Best regards

André

0 Kudos
Highlighted
Community Manager
135 Views

Hello andy_web,

 

 

Thank you for your reply.

 

 

We are going to be working in reviewing the information, picture and the logs you provided, we will be contacting you back as soon as we have an update or in case that further information is required.

 

 

Thank you for your patience and understanding.

 

 

Best regards,

 

 

Josh B.

 

Intel® Customer Support Technician

 

Under Contract to Intel Corporation
0 Kudos
Highlighted
Community Manager
135 Views

Hello andy_web,

 

 

Thank you for your patience,

 

 

Based on the information you shared with us you are running the firmware VDV10131 this is a supported firmware and was validated by VMware to work on his OS and they should provide you with further support for the issue. We advise you to create a ticket in parallel with VMware to work along with and let us know if they provide you with an update or if further assistance is required from our side.

 

 

Best regards,

 

 

Josh B.

 

Intel® Customer Support Technician

 

Under Contract to Intel Corporation

 

0 Kudos
Highlighted
Community Manager
135 Views

Hello andy_web,

 

 

Thank you for having contacted Intel Technical Support.

 

 

We have not heard from you since our last communication and we would like to know if you need further assistance or if we can close this case?

 

 

Important note: Should further assistance or clarification be required, we will greatly appreciate if you reply to this post instead of writing a new one unless your inquiry is completely unrelated. This way we will prevent generating a duplicate post and we will not lose the train of thought.

 

 

We will be looking forward to your reply.

 

 

Best regards,

 

 

Josh B.

 

Intel® Customer Support Technician

 

Under Contract to Intel Corporation
0 Kudos
Highlighted
Community Manager
135 Views

Hello,

the threat can be closed. My problem was not solved, but unfortunately we have no time to test further. The server is needed productively. The NVMe SSD are still not recognized in ESXI.

Best regards

André

0 Kudos
Highlighted
Community Manager
135 Views

Hello andy_web,

 

 

Thank you for your reply.

 

 

We understand that you needed to have your server up and running as soon as possible but if you need further assistance please do not hesitate to contact us back at any time.

 

 

Best regards.

 

 

Josh B.

 

Intel Customer Support Technician

 

Under Contract to Intel Corporation

 

0 Kudos