05-09-2018 10:43 AM
Hey guys, I have two NVMe (P4600 4.0TB) connect on a Dell 720, OS ESXI 6.5U2 (Iso provided by Dell).
I am running a fresh ESXI installation. Here are the steps per instructions:
esxcli software acceptance set --level=CommunitySupported
esxcli software acceptance get
CommunitySupported
esxcli software vib install -d "/tmp/intel_ssd_data_center_tool_3.0.11-400_OfflineBundle.zip" --no-sig-check
Installation Result
Message: Operation finished successfully.
Reboot Required: false
VIBs Installed: Intel_bootbank_intel_ssd_data_center_tool_3.0.11-400
VIBs Removed:
VIBs Skipped:
[root@XXXX:/opt/intel/isdct] ./isdct show -intelssd
No results
So I upgraded the firmware to version QDV10710 Bootloader=QB1B0122 for both NVMe, but the problem persists.
Enable logging:
./isdct set -system LogFile = 'log.txt'
./isdct set -system EnableLog = 'true'
[root@xxxx:/opt/intel/isdct] vi log.txt
17:37:35:191645 [debug] tdk_interface_dll.cpp(287) SendXMLMessage: Entering
17:37:35:193646 [debug] TDKInterface.cpp(345) scan: Entering
17:37:35:193666 [debug] DeviceFinder_NVME.cpp(63) scan: Entering
17:37:35:193678 [debug] DeviceFinder_NVME.cpp(100) scanPhysicalDevices: Entering
17:37:35:193784 [error] Connection_Path.cpp(91) open: vmk_MgmtUserInit error: 19
17:37:35:193811 [error] DeviceFinder_NVME.cpp(134) scanPhysicalDevices: Failed to connect to device. Ignoring intel-nvme0
17:37:35:193864 [error] Connection_Path.cpp(91) open: vmk_MgmtUserInit error: 19
17:37:35:193880 [error] DeviceFinder_NVME.cpp(134) scanPhysicalDevices: Failed to connect to device. Ignoring intel-nvme1
17:37:35:193917 [error] Connection_Path.cpp(91) open: vmk_MgmtUserInit error: 19
17:37:35:193931 [error] DeviceFinder_NVME.cpp(134) scanPhysicalDevices: Failed to connect to device. Ignoring intel-nvme2
17:37:35:193967 [error] Connection_Path.cpp(91) open: vmk_MgmtUserInit error: 19
17:37:35:193981 [error] DeviceFinder_NVME.cpp(134) scanPhysicalDevices: Failed to connect to device. Ignoring intel-nvme3
17:37:35:194017 [error] Connection_Path.cpp(91) open: vmk_MgmtUserInit error: 19
(...counting by 98)
17:37:35:198600 [error] DeviceFinder_NVME.cpp(134) scanPhysicalDevices: Failed to connect to device. Ignoring intel-nvme98
17:37:35:198609 [debug] DeviceFinder_NVME.cpp scanPhysicalDevices: Exiting
17:37:35:198620 [debug] DeviceFinder_NVME.cpp scan: Exiting
17:37:35:198633 [debug] TDKInterface.cpp scan: Exiting
17:37:35:198762 [debug] tdk_interface_dll.cpp SendXMLMessage: Exiting
17:37:35:198775 [debug] tdk_interface_dll.cpp(331) ReceiveXMLMessage: Entering
17:37:35:198850 [debug] tdk_interface_dll.cpp ReceiveXMLMessage: Exiting
17:37:35:198864 [debug] tdk_interface_dll.cpp(331) ReceiveXMLMessage: Entering
17:37:35:198897 [debug] tdk_interface_dll.cpp ReceiveXMLMessage: Exiting
Any ideas how I can fix it?
Thank you!
Regards,
Lucas
05-10-2018 09:07 AM
Hello Lucas,
Thanks for your reply. It is good to know ISDCT is now recognizing the SSDs after downgrading the NVMe driver.Please let us know if there's anything else we can do for you.Best regards,Eugenio F.05-10-2018 09:07 AM
Hello Lucas,
Thanks for your reply. It is good to know ISDCT is now recognizing the SSDs after downgrading the driver.Please let us know if there's anything else we can do for you.Best regards,Eugenio F.05-10-2018 09:12 AM
Thanks so much for all assistance provided Eugenio.
One last question.
Is it possible to do a self-test for NVME? I would like to make sure those NVME are 100% health for production.
Regards,
Lucas
05-10-2018 11:01 AM
Hello Lucas,
You can monitor the drive health by checking its S.M.A.R.T. details using either ISDCT Heath Sensor and Show SMART commands, or https://kb.vmware.com/s/article/2040405 ESXi* own SMART commands.Please refer to the ISDCT User manual to get more details for each command syntax:- https://www.intel.com/content/www/us/en/support/articles/000020016/memory-and-storage.html User and Install Guides for Intel® SSD Data Center ToolBest regards,Eugenio F.