Community
cancel
Showing results for 
Search instead for 
Did you mean: 
Ndf
Beginner
2,652 Views

SSD Data Center tools in ESXi do not see SSD DS S3520

Hellow.

"SSD Data Center tools" do not see the SSD drive. (tried 3.0.4 and 3.0.7)

SSD DS S3520 firmware N2010112.

Tried ESXi 5.5 U1 and 6.5.

I have two servers based on motherboards ASUS P9D-M with chipset C224 with LSI® MegaRAID on board (no RAID in AHCI mode) and "server" ASUS on H67-V (in AHCI mode).

I did everything in accordance with the documentation.

- SSDs are connected to the SATA port directly. AHCI mode. (no RAID)

- VIB installed

Try:

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

And all the time i see the same thing: - "No results"

What did I miss?

~ # esxcli storage core device list

t10.ATA_____INTEL_SSDSC2BB480G7_____________________PHDV73710800480BGN__

Display Name: Local ATA Disk (t10.ATA_____INTEL_SSDSC2BB480G7_____________________PHDV73710800480BGN__)

Has Settable Display Name: true

Size: 457862

Device Type: Direct-Access

Multipath Plugin: NMP

Devfs Path: /vmfs/devices/disks/t10.ATA_____INTEL_SSDSC2BB480G7_____________________PHDV73710800480BGN__

Vendor: ATA

Model: INTEL SSDSC2BB48

Revision: N201

SCSI Level: 5

Is Pseudo: false

Status: on

Is RDM Capable: false

Is Local: true

Is Removable: false

Is SSD: true

Is Offline: false

Is Perennially Reserved: false

Queue Full Sample Size: 0

Queue Full Threshold: 0

Thin Provisioning Status: yes

Attached Filters:

VAAI Status: unknown

Other UIDs: vml.010000000050484456373337313038303034383042474e2020494e54454c20

Is Local SAS Device: false

Is Boot USB Device: false

No of outstanding IOs with competing worlds: 32

~ #

~ # esxcli storage core path list

sata.vmhba0-sata.0:0-t10.ATA_____INTEL_SSDSC2BB480G7_____________________PHDV73710800480BGN__

UID: sata.vmhba0-sata.0:0-t10.ATA_____INTEL_SSDSC2BB480G7_____________________PHDV73710800480BGN__

Runtime Name: vmhba0:C0:T0:L0

Device: t10.ATA_____INTEL_SSDSC2BB480G7_____________________PHDV73710800480BGN__

Device Display Name: Local ATA Disk (t10.ATA_____INTEL_SSDSC2BB480G7_____________________PHDV73710800480BGN__)

Adapter: vmhba0

Channel: 0

Target: 0

LUN: 0

Plugin: NMP

State: active

Transport: sata

Adapter Identifier: sata.vmhba0

Target Identifier: sata.0:0

Adapter Transport Details: Unavailable or path is unclaimed

Target Transport Details: Unavailable or path is unclaimed

Maximum IO Size: 33553920

~ #

0 Kudos
26 Replies
idata
Community Manager
152 Views

Hi Sptta,

 

 

We understand the situation regarding the Intel® SSD Data Center Tool.

 

 

Could you please confirm if the SSD is connected directly to the motherboard? If not, we suggest you connect the SSD directly to the motherboard because the Intel® SSD Data Center Tool is not able to see the SSD's when it is not connected directly to it.

 

 

 

We look forward to hearing back from you.

 

 

Regards,

 

Junior M.

 

Ndf
Beginner
152 Views

Hellow/

Yes, SSD directly connected. SATA ports in AHCI mode.

idata
Community Manager
152 Views

Hi Sptta,

 

 

We would further investigate on this with our additional resources, we will keep you posted with any updates.

 

 

Regards,

 

Junior M.
Ndf
Beginner
152 Views

Hi Junior M.

I see we are in different time zones. This is a problem. I do not want to spend the next 5 years on the issue.

The equipment still stands on my table. So if you need any configuration information, I'm ready to provide it.

Server 1:

MB: ASUS P9D-M rev 1.03

Server 2:

MB: ASUS P8H67-V rev 3.0

I repeat, I checked on ESHI 5.5 U1 and 6.5.

If you need anything to check or you need any information about the configuration, I'm ready to provide it.

idata
Community Manager
152 Views

Hi Sptta,

 

 

We would like to inform you that the https://downloadcenter.intel.com/download/27248?v=t latest version of the Intel® SSD Data Center Tool does not support VMware*. However, it seems that a https://downloadcenter.intel.com/download/27144/Intel-SSD-Data-Center-Tool previous version of the Tool(3.0.7) supports the following versions of ESXI* 5.5 or 6.0 as per our https://www.intel.com/content/dam/support/us/en/documents/memory-and-storage/Intel_SSD_DCT_3_0_x_Use... documents.

 

 

There's a note in the User Guide, page 7, that states that the user must set their ESXi* host acceptance level to "Community Supported" in order to install the tool.

 

 

Regards,

 

Junior M.

 

Ndf
Beginner
152 Views

Hi.

I patched the SSD with the latest firmware. I tried to change the ports on the board. Tried to use EsXi 5.5, 6.0, 6.5. The result is the same.

In "Intel_SSD_Data_Center_Tool_3_0_7_User_Guide_331961-012.pdf" # 1.3 "Supported SSDs" i see my "DS S3520". It`s SATA. It`s directly connected to MB.

And it does not work. This is strange.

Do I have the wrong motherboard? Can I ask you to recommend me a desktop motherboard (or a chipset) on which it will definitely work? Or LSI Adapter...

Why ISDCT trying to search for NVMe?:

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

Set EnableLog successful.

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

No results

TDKI.log

15:24:07:300533 [debug] tdk_interface_dll.cpp(259) SendXMLMessage: Entering

15:24:07:302121 [debug] TDKInterface.cpp(522) scan: Entering

15:24:07:302135 [debug] DeviceFinder_NVME.cpp(63) scan: Entering

15:24:07:302143 [debug] DeviceFinder_NVME.cpp(100) scanPhysicalDevices: Entering

15:24:07:302211 [error] Connection_Path.cpp(91) open: vmk_MgmtUserInit error: 19

15:24:07:302229 [error] DeviceFinder_NVME.cpp(134) scanPhysicalDevices: Failed to connect to device. Ignoring intel-nvme0

15:24:07:302265 [error] Connection_Path.cpp(91) open: vmk_MgmtUserInit error: 19

15:24:07:302274 [error] DeviceFinder_NVME.cpp(134) scanPhysicalDevices: Failed to connect to device. Ignoring intel-nvme1

15:24:07:302299 [error] Connection_Path.cpp(91) open: vmk_MgmtUserInit error: 19

* * * * * *

15:24:07:305290 [error] Connection_Path.cpp(91) open: vmk_MgmtUserInit error: 19

15:24:07:305298 [error] DeviceFinder_NVME.cpp(134) scanPhysicalDevices: Failed to connect to device. Ignoring intel-nvme97

15:24:07:305321 [error] Connection_Path.cpp(91) open: vmk_MgmtUserInit error: 19

15:24:07:305329 [error] DeviceFinder_NVME.cpp(134) scanPhysicalDevices: Failed to connect to device. Ignoring intel-nvme98

15:24:07:305336 [debug] DeviceFinder_NVME.cpp scanPhysicalDevices: Exiting

15:24:07:305343 [debug] DeviceFinder_NVME.cpp scan: Exiting

15:24:07:305350 [debug] TDKInterface.cpp scan: Exiting

15:24:07:305447 [debug] tdk_interface_dll.cpp SendXMLMessage: Exiting

15:24:07:305455 [debug] tdk_interface_dll.cpp(303) ReceiveXMLMessage: Entering

15:24:07:305515 [debug] tdk_interface_dll.cpp ReceiveXMLMessage: Exiting

15:24:07:305523 [debug] tdk_interface_dll.cpp(303) ReceiveXMLMessage: Entering

15:24:07:305548 [debug] tdk_interface_dll.cpp ReceiveXMLMessage: Exiting

idata
Community Manager
152 Views

Hi Sptta,

 

 

We recommend you to try with other previous versions of the Intel® SSD Data Center Tool:

 

 

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

 

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

 

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

 

 

Please keep in mind that those versions only work with ESXI* 5.5 or 6.0. Make sure you uninstall the previous version before proceeding.

 

 

The tool should not ask you for NVMe* drivers because this SSD is SATA, do you have other SSDs connected to the motherboard?

 

 

Could you please let us know where you found those logs?

 

 

Regards,

 

Junior M.
Ndf
Beginner
152 Views

This log file was created in /var/log/ when i make ./isdct set -system EnableLog = 'true'.

In "Intel_SSD_Data_Center_Tool_3_0_7_User_Guide_331961-012.pdf" # .2.4.1 "Show tool configuration"

/opt/intel/isdct # ./isdct show -system

- ISDCT Config -

EnableLog: true

LogFile: /var/log/TDKI.log

idata
Community Manager
152 Views

Hi Sptta,

 

 

Thanks for the information provided.

 

 

Please let us know if you have the same output with the previous versions of the tool.

 

 

Regards,

 

Junior M.
Ndf
Beginner
152 Views

I checked. Same.

I see that the new version 3.0.9 has been released. Interestingly, there will be a result. There is not yet for Vmware.

idata
Community Manager
152 Views

Hi Sptta,

 

 

Thanks for the information, it seems that the Firmware of the SSD is not the latest one. The latest version of the Firmware is N2010121.

 

 

We recommend you to follow the next steps in order to update it:

 

 

1- Go to https://downloadcenter.intel.com/download/26491/Intel-SSD-Firmware-Update-Tool https://downloadcenter.intel.com/download/26491/Intel-SSD-Firmware-Update-Tool

 

 

2- Download the issdfut_2.2.3.iso

 

 

3- Go to https://www.google.com/url%3Fq%3Dhttps%253A%252F%252Frufus.akeo.ie%252F%26sa%3DD%26sntz%3D1%26usg%3D... https://rufus.akeo.ie/and download Rufus.

 

 

4- Connect an empty USB flash drive to the PC.

 

 

5- Open Rufus and change only the options "Device" and select your USB. Then go to ISO image, click on search and select the issdfut_2.2.3.iso you previously downloaded.

 

 

6- Go to your BIOS -> Boot -> Boot priority -> select the "USB" as primary.

 

 

7- Re-boot your PC. It should enter the firmware update tool for your SSD.

 

 

8- Update the firmware and then boot windows.

 

 

9- If it does not boot the "USB" or it gives you an error, please go to BIOS and change the boot mode to "legacy only". Then try again.

 

 

NOTE: Any links provided for third party tools or sites are offered for your convenience and should not be viewed as an endorsement by Intel® of the content, products, or services offered there. We do not offer support for any third party tool mentioned here.

 

 

 

Please try it and let us know the results.

 

 

Regards,

 

Junior M.

 

Ndf
Beginner
152 Views

I already did it. As soon as I saw the problem... SSD firmware updated.

May I ask you, could you clarify whether this is possible on 'my' chipsets at all? For me to buy another hardware is not a problem.

The problem - is not to get the job done...

idata
Community Manager
152 Views

Hi Sptta,

 

 

Thanks for the reply.

 

 

Based on the release notes for the Intel® SSD Data Center Tool there is no specific requirement related to the chipset.

 

 

We would investigate this with our additional resources. We would keep you posted with any updates.

 

 

Regards,

 

Junior M.
idata
Community Manager
152 Views

Hi Sptta,

 

 

Could you please provide us with the Intel® SSD Data Center Tool logs.

 

 

Please run the following commands:

 

 

isdct set –system EnableLog=True • isdct set –system LogFile=myDCTlogfile.txt

 

 

We look forward to hearing back from you.

 

 

Regards,

 

Junior M.

 

 

Ndf
Beginner
152 Views

ESXi 6.5

Intel SSD Data Center Tool 3.0.7 (latest for VmWare)

[root@localhost:~] cd /opt/intel/isdct/

[root@localhost:/opt/intel/isdct] ./isdct set -system LogFile = 'myDCTlogfile.txt'

Set LogFile successful.

[root@localhost:/opt/intel/isdct] ./isdct set -system EnableLog = 'true'

Set EnableLog successful.

[root@localhost:/opt/intel/isdct] ./isdct show -intelssd

No results

LogFile (/opt/intel/isdct/myDCTlogfile.txt):

19:06:21:250961 [debug] tdk_interface_dll.cpp(259) SendXMLMessage: Entering

19:06:21:253026 [debug] TDKInterface.cpp(522) scan: Entering

19:06:21:253049 [debug] DeviceFinder_NVME.cpp(63) scan: Entering

19:06:21:253061 [debug] DeviceFinder_NVME.cpp(100) scanPhysicalDevices: Entering

19:06:21:253161 [error] Connection_Path.cpp(91) open: vmk_MgmtUserInit error: 19

19:06:21:253191 [error] DeviceFinder_NVME.cpp(134) scanPhysicalDevices: Failed to connect to device. Ignoring intel-nvme0

19:06:21:253241 [error] Connection_Path.cpp(91) open: vmk_MgmtUserInit error: 19

19:06:21:253256 [error] DeviceFinder_NVME.cpp(134) scanPhysicalDevices: Failed to connect to device. Ignoring intel-nvme1

19:06:21:253292 [error] Connection_Path.cpp(91) open: vmk_MgmtUserInit error: 19

19:06:21:253306 [error] DeviceFinder_NVME.cpp(134) scanPhysicalDevices: Failed to connect to device. Ignoring intel-nvme2

19:06:21:253341 [error] Connection_Path.cpp(91) open: vmk_MgmtUserInit error: 19

19:06:21:253354 [error] DeviceFinder_NVME.cpp(134) scanPhysicalDevices: Failed to connect to device. Ignoring intel-nvme3

19:06:21:253389 [error] Connection_Path.cpp(91) open: vmk_MgmtUserInit error: 19

19:06:21:253402 [error] DeviceFinder_NVME.cpp(134) scanPhysicalDevices: Failed to connect to device. Ignoring intel-nvme4

19:06:21:253436 [error] Connection_Path.cpp(91) open: vmk_MgmtUserInit error: 19

19:06:21:253449 [error] DeviceFinder_NVME.cpp(134) scanPhysicalDevices: Failed to connect to device. Ignoring intel-nvme5

19:06:21:253483 [error] Connection_Path.cpp(91) open: vmk_MgmtUserInit error: 19

19:06:21:253497 [error] DeviceFinder_NVME.cpp(134) scanPhysicalDevices: Failed to connect to device. Ignoring intel-nvme6

19:06:21:253531 [error] Connection_Path.cpp(91) open: vmk_MgmtUserInit error: 19

19:06:21:253544 [error] DeviceFinder_NVME.cpp(134) scanPhysicalDevices: Failed to connect to device. Ignoring intel-nvme7

19:06:21:253578 [error] Connection_Path.cpp(91) open: vmk_MgmtUserInit error: 19

19:06:21:253591 [error] DeviceFinder_NVME.cpp(134) scanPhysicalDevices: Failed to connect to device. Ignoring intel-nvme8

19:06:21:253625 [error] Connection_Path.cpp(91) open: vmk_MgmtUserInit error: 19

19:06:21:253638 [error] DeviceFinder_NVME.cpp(134) scanPhysicalDevices: Failed to connect to device. Ignoring intel-nvme9

19:06:21:253672 [error] Connection_Path.cpp(91) open: vmk_MgmtUserInit error: 19

19:06:21:253686 [error] DeviceFinder_NVME.cpp(134) scanPhysicalDevices: Failed to connect to device. Ignoring intel-nvme10

19:06:21:253720 [error] Connection_Path.cpp(91) open: vmk_MgmtUserInit error: 19

19:06:21:253733 [error] DeviceFinder_NVME.cpp(134) scanPhysicalDevices: Failed to connect to device. Ignoring intel-nvme11

19:06:21:253767 [error] Connection_Path.cpp(91) open: vmk_MgmtUserInit error: 19

19:06:21:253780 [error] DeviceFinder_NVME.cpp(134) scanPhysicalDevices: Failed to connect to device. Ignoring intel-nvme12

19:06:21:253814 [error] Connection_Path.cpp(91) open: vmk_MgmtUserInit error: 19

19:06:21:253827 [error] DeviceFinder_NVME.cpp(134) scanPhysicalDevices: Failed to connect to device. Ignoring intel-nvme13

19:06:21:253861 [error] Connection_Path.cpp(91) open: vmk_MgmtUserInit error: 19

19:06:21:253874 [error] DeviceFinder_NVME.cpp(134) scanPhysicalDevices: Failed to connect to device. Ignoring intel-nvme14

19:06:21:253908 [error] Connection_Path.cpp(91) open: vmk_MgmtUserInit error: 19

19:06:21:253922 [error] DeviceFinder_NVME.cpp(134) scanPhysicalDevices: Failed to connect to device. Ignoring intel-nvme15

19:06:21:253956 [error] Connection_Path.cpp(91) open: vmk_MgmtUserInit error: 19

19:06:21:253969 [error] DeviceFinder_NVME.cpp(134) scanPhysicalDevices: Failed to connect to device. Ignoring intel-nvme16

19:06:21:254003 [error] Connection_Path.cpp(91) open: vmk_MgmtUserInit error: 19

19:06:21:254016 [error] DeviceFinder_NVME.cpp(134) scanPhysicalDevices: Failed to connect to device. Ignoring intel-nvme17

19:06:21:254050 [error] Connection_Path.cpp(91) open: vmk_MgmtUserInit error: 19

19:06:21:254063 [error] DeviceFinder_NVME.cpp(134) scanPhysicalDevices: Failed to connect to device. Ignoring intel-nvme18

19:06:21:254097 [error] Connection_Path.cpp(91) open: vmk_MgmtUserInit error: 19

19:06:21:254110 [error] DeviceFinder_NVME.cpp(134) scanPhysicalDevices: Failed to connect to device. Ignoring intel-nvme19

19:06:21:254144 [error] Connection_Path.cpp(91) open: vmk_MgmtUserInit error: 19

19:06:21:254157 [error] DeviceFinder_NVME.cpp(134) scanPhysicalDevices: Failed to connect to device. Ignoring intel-nvme20

19:06:21:254195 [error] Connection_Path.cpp(91) open: vmk_MgmtUserInit error: 19

19:06:21:254209 [error] DeviceFinder_NVME.cpp(134) scanPhysicalDevices: Failed to connect to device. Ignoring intel-nvme21

19:06:21:254244 [error] Connection_Path.cpp(91) open: vmk_MgmtUserInit error: 19

19:06:21:254257 [error] DeviceFinder_NVME.cpp(134) scanPhysicalDevices: Failed to connect to device. Ignoring intel-nvme22

19:06:21:254291 [error] Connection_Path.cpp(91) open: vmk_MgmtUserInit error: 19

19:06:21:254304 [error] DeviceFinder_NVME.cpp(134) scanPhysicalDevices: Failed to connect to device. Ignoring intel-nvme23

19:06:21:254338 [error] Connection_Path.cpp(91) open: vmk_MgmtUserInit error: 19

19:06:21:254351 [error] DeviceFinder_NVME.cpp(134) scanPhysicalDevices: Failed to connect to device. Ignoring intel-nvme24

19:06:21:254386 [error] Connection_Path.cpp(91) open: vmk_MgmtUserInit error: 19

19:06:21:254399 [error] DeviceFinder_NVME.cpp(134) scanPhysicalDevices: Failed to connect to device. Ignoring intel-nvme25

19:06:21:254432 [error] Connection_Path.cpp(91) open: vmk_MgmtUserInit error: 19

19:06:21:254446 [error] DeviceFinder_NVME.cpp(134) scanPhysicalDevices: Failed to connect to device. Ignoring intel-nvme26

19:06:21:254480 [error] Connection_Path.cpp(91) open: vmk_MgmtUserInit error: 19

19:06:21:254493 [error] DeviceFinder_NVME.cpp(134) scanPhysicalDevices: Failed to connect to device. Ignoring intel-nvme27

19:06:21:254526 [error] Connection_Path.cpp(91) open: vmk_MgmtUserInit error: 19

19:06:21:254539 [error] DeviceFinder_NVME.cpp(134) scanPhysicalDevices: Failed to connect to device. Ignoring intel-nvme28

19:06:21:254573 [error] Connection_Path.cpp(91) open: vmk_MgmtUserInit error: 19

19:06:21:254586 [error] DeviceFinder_NVME.cpp(134) scanPhysicalDevices: Failed to connect to device. Ignoring intel-nvme29

19:06:21:254620 [error] Connection_Path.cpp(91) open: vmk_MgmtUserInit error: 19

19:06:21:254633 [error] DeviceFinder_NVME.cpp(134) scanPhysicalDevices: Failed to connect to device. Ignoring intel-nvme30

19:06:21:254667 [error] Connection_Path.cpp(91) open: vmk_MgmtUserInit error: 19

19:06:21:254680 [error] DeviceFinder_NVME.cpp(134) scanPhysicalDevices: Failed to connect to device. Ignoring intel-nvme31

19:06:21:254714 [error] Connection_Path.cpp(91) open: vmk_MgmtUserInit error: 19

19:06:21:254727 [error] DeviceFinder_NVME.cpp(...

idata
Community Manager
152 Views

Hi Sptta,

 

 

Thanks for the pictures and the information provided.

 

 

We would further investigate on this, we will keep you posted with any updates.

 

 

Regards,

 

Junior M.
DStor
Beginner
152 Views

SO I don't want to coopt this thread but I think i have the same issue.. so hopefully it can shes some light.

 

 

I have Vmware esxi 6.0 and 6.5 running p3700 NVMe drives in dell r730xd servers and non of them report back and the log looks just like Sptta's logfile.... ( tool version 3.0.4.400 )

as a side note a p3700 bougth in the same lot( so same firmeware in theory) in a different dell server ( r720) reports just fine with the same tool version on esx 6.0

Thanks

Derek

idata
Community Manager
152 Views

Hi Sptta,

 

 

We would like to inform you that the latest version of the https://downloadcenter.intel.com/download/27248/Intel-SSD-Data-Center-Tool?product=87278 Intel® SSD Data Center Tool(3.0.9)

 

has been released.

 

 

We recommend you to perform a fresh installation of the VMware* ESXi 6.5 and try with the latest version of the Intel® SSD Data Center Tool.

 

 

Please let us know if you have the same results.

 

 

Regards,

 

Junior M.

 

DStor
Beginner
152 Views

Intel,

I tried the newest version 3.09 on my esxi 6.5 install on a Dell R730xd and the logs looks the same and it reports "no results" exact same behavior as all the older versions....

Thanks

Derek