Intel® Optane™ Solid State Drives
Support for Issues Related to Solid State Drives based on Intel® Optane™ technology, Intel® MAS and Firmware Update Tool
Announcements
The Intel sign-in experience has changed to support enhanced security controls. If you sign in, click here for more information.
414 Discussions

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

Ndf
Beginner
‎11-17-2017 09:02 AM
3,474 Views

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

Link Copied

26 Replies
DStor
Beginner
‎12-06-2017 09:34 AM
144 Views
In response to Ndf

Here you go

16:22:55:582462 [debug] tdk_interface_dll.cpp(262) SendXMLMessage: Entering

16:22:55:584462 [debug] TDKInterface.cpp(522) scan: Entering

16:22:55:584480 [debug] DeviceFinder_NVME.cpp(63) scan: Entering

16:22:55:584490 [debug] DeviceFinder_NVME.cpp(100) scanPhysicalDevices: Entering

16:22:55:584597 [error] Connection_Path.cpp(91) open: vmk_MgmtUserInit error: 19

16:22:55:584621 [error] DeviceFinder_NVME.cpp(134) scanPhysicalDevices: Failed to connect to device. Ignoring intel-nvme0

16:22:55:584674 [error] Connection_Path.cpp(91) open: vmk_MgmtUserInit error: 19

16:22:55:584688 [error] DeviceFinder_NVME.cpp(134) scanPhysicalDevices: Failed to connect to device. Ignoring intel-nvme1

16:22:55:584724 [error] Connection_Path.cpp(91) open: vmk_MgmtUserInit error: 19

16:22:55:584736 [error] DeviceFinder_NVME.cpp(134) scanPhysicalDevices: Failed to connect to device. Ignoring intel-nvme2

16:22:55:584770 [error] Connection_Path.cpp(91) open: vmk_MgmtUserInit error: 19

16:22:55:584782 [error] DeviceFinder_NVME.cpp(134) scanPhysicalDevices: Failed to connect to device. Ignoring intel-nvme3

16:22:55:584815 [error] Connection_Path.cpp(91) open: vmk_MgmtUserInit error: 19

16:22:55:584827 [error] DeviceFinder_NVME.cpp(134) scanPhysicalDevices: Failed to connect to device. Ignoring intel-nvme4

16:22:55:584859 [error] Connection_Path.cpp(91) open: vmk_MgmtUserInit error: 19

16:22:55:584871 [error] DeviceFinder_NVME.cpp(134) scanPhysicalDevices: Failed to connect to device. Ignoring intel-nvme5

16:22:55:584903 [error] Connection_Path.cpp(91) open: vmk_MgmtUserInit error: 19

16:22:55:584915 [error] DeviceFinder_NVME.cpp(134) scanPhysicalDevices: Failed to connect to device. Ignoring intel-nvme6

16:22:55:584947 [error] Connection_Path.cpp(91) open: vmk_MgmtUserInit error: 19

16:22:55:584959 [error] DeviceFinder_NVME.cpp(134) scanPhysicalDevices: Failed to connect to device. Ignoring intel-nvme7

16:22:55:584991 [error] Connection_Path.cpp(91) open: vmk_MgmtUserInit error: 19

16:22:55:585003 [error] DeviceFinder_NVME.cpp(134) scanPhysicalDevices: Failed to connect to device. Ignoring intel-nvme8

16:22:55:585035 [error] Connection_Path.cpp(91) open: vmk_MgmtUserInit error: 19

16:22:55:585047 [error] DeviceFinder_NVME.cpp(134) scanPhysicalDevices: Failed to connect to device. Ignoring intel-nvme9

16:22:55:585079 [error] Connection_Path.cpp(91) open: vmk_MgmtUserInit error: 19

16:22:55:585091 [error] DeviceFinder_NVME.cpp(134) scanPhysicalDevices: Failed to connect to device. Ignoring intel-nvme10

16:22:55:585124 [error] Connection_Path.cpp(91) open: vmk_MgmtUserInit error: 19

16:22:55:585135 [error] DeviceFinder_NVME.cpp(134) scanPhysicalDevices: Failed to connect to device. Ignoring intel-nvme11

16:22:55:585168 [error] Connection_Path.cpp(91) open: vmk_MgmtUserInit error: 19

16:22:55:585180 [error] DeviceFinder_NVME.cpp(134) scanPhysicalDevices: Failed to connect to device. Ignoring intel-nvme12

16:22:55:585212 [error] Connection_Path.cpp(91) open: vmk_MgmtUserInit error: 19

16:22:55:585224 [error] DeviceFinder_NVME.cpp(134) scanPhysicalDevices: Failed to connect to device. Ignoring intel-nvme13

16:22:55:585256 [error] Connection_Path.cpp(91) open: vmk_MgmtUserInit error: 19

16:22:55:585268 [error] DeviceFinder_NVME.cpp(134) scanPhysicalDevices: Failed to connect to device. Ignoring intel-nvme14

16:22:55:585300 [error] Connection_Path.cpp(91) open: vmk_MgmtUserInit error: 19

16:22:55:585312 [error] DeviceFinder_NVME.cpp(134) scanPhysicalDevices: Failed to connect to device. Ignoring intel-nvme15

16:22:55:585344 [error] Connection_Path.cpp(91) open: vmk_MgmtUserInit error: 19

16:22:55:585356 [error] DeviceFinder_NVME.cpp(134) scanPhysicalDevices: Failed to connect to device. Ignoring intel-nvme16

16:22:55:585388 [error] Connection_Path.cpp(91) open: vmk_MgmtUserInit error: 19

16:22:55:585400 [error] DeviceFinder_NVME.cpp(134) scanPhysicalDevices: Failed to connect to device. Ignoring intel-nvme17

16:22:55:585432 [error] Connection_Path.cpp(91) open: vmk_MgmtUserInit error: 19

16:22:55:585444 [error] DeviceFinder_NVME.cpp(134) scanPhysicalDevices: Failed to connect to device. Ignoring intel-nvme18

16:22:55:585476 [error] Connection_Path.cpp(91) open: vmk_MgmtUserInit error: 19

16:22:55:585487 [error] DeviceFinder_NVME.cpp(134) scanPhysicalDevices: Failed to connect to device. Ignoring intel-nvme19

16:22:55:585520 [error] Connection_Path.cpp(91) open: vmk_MgmtUserInit error: 19

16:22:55:585532 [error] DeviceFinder_NVME.cpp(134) scanPhysicalDevices: Failed to connect to device. Ignoring intel-nvme20

16:22:55:585564 [error] Connection_Path.cpp(91) open: vmk_MgmtUserInit error: 19

16:22:55:585575 [error] DeviceFinder_NVME.cpp(134) scanPhysicalDevices: Failed to connect to device. Ignoring intel-nvme21

16:22:55:585607 [error] Connection_Path.cpp(91) open: vmk_MgmtUserInit error: 19

16:22:55:585619 [error] DeviceFinder_NVME.cpp(134) scanPhysicalDevices: Failed to connect to device. Ignoring intel-nvme22

16:22:55:585651 [error] Connection_Path.cpp(91) open: vmk_MgmtUserInit error: 19

16:22:55:585662 [error] DeviceFinder_NVME.cpp(134) scanPhysicalDevices: Failed to connect to device. Ignoring intel-nvme23

16:22:55:585695 [error] Connection_Path.cpp(91) open: vmk_MgmtUserInit error: 19

16:22:55:585706 [error] DeviceFinder_NVME.cpp(134) scanPhysicalDevices: Failed to connect to device. Ignoring intel-nvme24

16:22:55:585738 [error] Connection_Path.cpp(91) open: vmk_MgmtUserInit error: 19

16:22:55:585750 [error] DeviceFinder_NVME.cpp(134) scanPhysicalDevices: Failed to connect to device. Ignoring intel-nvme25

16:22:55:585782 [error] Connection_Path.cpp(91) open: vmk_MgmtUserInit error: 19

16:22:55:585794 [error] DeviceFinder_NVME.cpp(134) scanPhysicalDevices: Failed to connect to device. Ignoring intel-nvme26

16:22:55:585826 [error] Connection_Path.cpp(91) open: vmk_MgmtUserInit error: 19

16:22:55:585838 [error] DeviceFinder_NVME.cpp(134) scanPhysicalDevices: Failed to connect to device. Ignoring intel-nvme27

16:22:55:585870 [error] Connection_Path.cpp(91) open: vmk_MgmtUserInit error: 19

16:22:55:585882 [error] DeviceFinder_NVME.cpp(134) scanPhysicalDevices: Failed to connect to device. Ignoring intel-nvme28

16:22:55:585914 [error] Connection_Path.cpp(91) open: vmk_MgmtUserInit error: 19

16:22:55:585925 [error] DeviceFinder_NVME.cpp(134) scanPhysicalDevices: Failed to connect to device. Ignoring intel-nvme29

16:22:55:585958 [error] Connection_Path.cpp(91) open: vmk_MgmtUserInit error: 19

16:22:55:585969 [error] DeviceFinder_NVME.cpp(134) scanPhysicalDevices: Failed to connect to device. Ignoring intel-nvme30

16:22:55:586001 [error] Connection_Path.cpp(91) open: vmk_MgmtUserInit error: 19

16:22:55:586013 [error] DeviceFinder_NVME.cpp(134) scanPhysicalDevices: Failed to connect to device. Ignoring intel-nvme31

16:22:55:586045 [error] Connection_Path.cpp(91) open: vmk_MgmtUserInit error: 19

16:22:55:586056 [error] DeviceFinder_NVME.cpp(134) scanPhysicalDevices: Failed to connect to device. Ignoring intel-nvme32

16:22:55:586089 [error] Connection_Path.cpp(91) open: vmk_MgmtUserInit error: 19

16:22:55:586101 [error] DeviceFinder_NVME.cpp(134) scanPhysicalDevices: Failed to connect to device. Ignoring intel-nvme33

16:22:55:586133 [error] Connection_Path.cpp(91) open: vmk_MgmtUserInit error: 19

16:22:55:586145 [error] DeviceFinder_NVME.cpp(134) scanPhysicalDevices: Failed to connect to device. Ignoring intel-nvme34

16:22:55:586177 [error] Connection_Path.cpp(91) open: vmk_MgmtUserInit error: 19

16:22:55:586189 [error] DeviceFinder_NVME.cpp(134) scanPhysicalDevices: Failed to connect to device. Ignoring intel-nvme35

16:22:55:586221 [error] Connection_Path.cpp(91) open: vmk_MgmtUserInit error: 19

16:22:55:586233 [error] DeviceFinder_NVME.cpp(134) scanPhysicalDevices: Failed to connect to device. Ignoring intel-nvme36

16:22:55:586265 [error] Connection_Path.cpp(91) open: vmk_MgmtUserInit error: 19

16:22:55:586277 [error] DeviceFinder_NVME.cpp(134) scanPhysicalDevices: Failed to conne...

In response to Ndf
0 Kudos
Copy link
idata
Employee
‎12-06-2017 09:54 AM
144 Views
In response to Ndf

Hi Derek1234,

 

 

Thanks for the logs provided.

 

 

Could you please confirm if you installed the latest Intel® SSD Data Center Tool in a fresh installation of the VMware* ESXi?

 

 

Regards,

 

Junior M.

 

In response to Ndf
0 Kudos
Copy link
DStor
Beginner
‎12-06-2017 10:48 AM
144 Views
In response to Ndf

Intel,

no it is not a fresh install of 6.5. This is a production server running live VM's I can't reinstall Vmware from scratch. But I do get the same behavior on 6.0 and 6.5 on R730XD servers. ( I do have a R720 that is running ESXi 6.0 and it recognizes just fine).

Thanks

Derek

In response to Ndf
0 Kudos
Copy link
idata
Employee
‎12-06-2017 04:00 PM
144 Views
In response to Ndf

Hi Derek1234,

 

 

Thanks for the information.

 

 

We would investigate the situation with the logs provided. We will keep you posted with any updates.

 

 

Regards,

 

Junior M.
In response to Ndf
0 Kudos
Copy link
idata
Employee
‎12-14-2017 04:05 PM
144 Views
In response to Ndf

Hi Sptta,

Could you please let us know if you were able to try with the fresh installation of the ESXI*?

Derek1234

We still investigating the logs you provided. We will keep you posted with any updates.

Regards,

 

Junior M.
In response to Ndf
0 Kudos
Copy link
idata
Employee
‎12-21-2017 01:56 PM
144 Views
In response to Ndf

Hi Derek1234 Sptta,

We would like to let you know that as per Intel® SSD Data Center Tool https://www.intel.com/content/dam/support/us/en/documents/memory-and-storage/Intel_SSD_DCT_3_0_x_User_Guide.pdf user guide, section 1.2(system requirements). On ESXi* systems, the tool only works on Intel(R) PCIe NVMe* drives using the Intel(R) ESXi* NVMe* driver. That is why you are not able to see the SSDs with the commands.

Please let us know if there is something else we can assist you with.

Regards,

 

Junior M.
In response to Ndf
0 Kudos
Copy link
Reply

For more complete information about compiler optimizations, see our Optimization Notice.