Windows 10 To Go: IOCTL_STORAGE_QUERY_PROPERTY(NVMe) failed, Error=1117

[Greg Bohn]

Hi;

Running smartmontools 6.6 r4594 under Windows 10, I receive the following error when I try to access my Samsung 960 Pro 512 GB NVMe drive:

smartctl -a /dev/sdf

smartctl 6.6 2017-11-05 r4594 [x86_64-w64-mingw32-w10-1709] (sf-6.6-1)
Copyright (C) 2002-17, Bruce Allen, Christian Franke, www.smartmontools.org

Read NVMe Identify Controller failed: IOCTL_STORAGE_QUERY_PROPERTY(NVMe) failed, Error=1117

I was under the impression from the 6.6 release notes that the built-in Windows NVMe 10 driver (stornvme.sys) would work.

Am I missing something? Do I need to add an additional driver or use a different command line option?

Getting SMART from the other (SATA attached) drives seems to work o.k.

Thanks.

[Christian Franke]

Are you sure that stornvme.sys is actually used?
Which Chipset or NVMe Controller is used?

Please provide output of smartctl -d nvme -r ioctl,2 --scan.

[Greg Bohn]

Device Mananger listing

[Greg Bohn]

'smartctl -d nvme -r ioctl,2 --scan' result

[Greg Bohn]

Are you sure that stornvme.sys is actually used?

I'm not sure. I was going by the fact that the Device Manager 'Storage Controllers' shows a 'Standard NVM Express controller', and the driver details show stornvme.sys I believe.

Please provide output of smartctl -d nvme -r ioctl,2

I have added this to the attachments.

This is with Windows 10 1709.

Which Chipset or NVMe Controller is used?

This is in a PCI Express slot in an Asus X99-E WS/USB3.1 motherboard. It is an X99 chipset system.

I don't believe I installed the Samsung nvme driver (and I would have thought it would show up under 'storage controllers' if I had).

Let me know if I should check anythings else.

Thanks.

[Christian Franke]

Device scan output and driver version look sane. NVMe access works for me with same driver on Win 10 Pro 1709 with VirtualBox 5.2.0 NVMe emulation (no access to a similar real machine right now).

Which driver is installed for SATA access (Intel, Microsoft) ?

Please provide output of smartctl -r ioctl,2 -i /dev/sdf.

[Greg Bohn]

Device manager list for IDE/ATA controllers

[Greg Bohn]

I attached a .jpg of the device manager list for 'IDE ATA/ATAPI controllers'. I think this is saying that it is using the microsoft drivers.

Output of 'smartctl -r ioctl,2 -i /dev/sdf' is

smartctl 6.6 2017-11-05 r4594 [x86_64-w64-mingw32-w10-1709] (sf-6.6-1)
Copyright (C) 2002-17, Bruce Allen, Christian Franke, www.smartmontools.org

.\PhysicalDrive5: successfully opened

IOCTL_STORAGE_QUERY_PROPERTY returns:

Vendor: "(null)"
Product: "Samsung SSD 960 PRO 512GB"
Revision: "2B6QCXP7"
Removable: No
BusType: 0x11

.\PhysicalDrive5: successfully opened

[NVMe call: opcode=0x06, size=0x1000, nsid=0x00000000, cdw10=0x00000001]

[STORAGE_QUERY_PROPERTY: Id=49, Type=1, Value=0x00000001, SubVal=0x00000000]
[STORAGE_QUERY_PROPERTY: ReturnData=0x00000000, Reserved[3]={0x0, 0x0, 0x0}]

[NVMe call failed: IOCTL_STORAGE_QUERY_PROPERTY(NVMe) failed, Error=1117]

Read NVMe Identify Controller failed: IOCTL_STORAGE_QUERY_PROPERTY(NVMe) failed, Error=1117

I don't know if it makes a difference, but this is a 'Windows-to-go' type Windows 10 1709 booted from USB (in BIOS mode).

This system is normally booted as a Windows 7 system, but I created a Windows-to-go system to be able to boot and see information about the 960 Pro drive (I hoped) from smartctl.

Under Windows 7 I use the Samsung nmve 2.3 driver, which as I understand it, is not compatible with the smartctl nvme support in that environment. (I get the impression I would at least need to disable some type of driver checking and install a different or additional unsigned driver of some sort).

Under windows 7, I get:

...

.\PhysicalDrive5: successfully opened

[NVMe call: opcode=0x06, size=0x1000, nsid=0x00000000, cdw10=0x00000001]

[STORAGE_QUERY_PROPERTY: Id=49, Type=1, Value=0x00000001, SubVal=0x00000000]
[STORAGE_QUERY_PROPERTY: ReturnData=0x00000000, Reserved[3]={0x0, 0x0, 0x0}]
[Duration: 0.016s]

[NVMe call failed: IOCTL_STORAGE_QUERY_PROPERTY(NVMe) failed, Error=1]

Read NVMe Identify Controller failed: IOCTL_STORAGE_QUERY_PROPERTY(NVMe) failed,

Error=1

[Christian Franke]

I have no idea whether Windows-to-go should make any difference. If possible, please test whether ​CrystalDiskInfo could access the NVMe drive. Its use of NMVe IOCTL_STORAGE_QUERY_PROPERTY differs slightly (access rights, buffer size).

Samsung (and Intel and OCZ/Toshiba) NVMe drivers reportedly support the ​NVME_PASS_THROUGH I/O-control from OpenFabrics driver, see NVMe wiki page. Requires a different pseudo device name, e.g. /dev/nvme0. Try smartctl -d nvme --scan on this system.

[Greg Bohn]

Results from W10 CrystalDiskInfo 7.5.0

[Greg Bohn]

I ran CrystalDiskInfo 7.5.0 in the Windows 10 environment, and it appears to have collected info for the 960 Pro. I attached W10-Crystal-DiskInfo-960.jpg with the results.

As far as the Windows 7 environment goes, I have good news. I ran

C:\Program Files\smartmontools\bin>smartctl -d nvme --scan
/dev/sdf -d nvme # /dev/sdf, NVMe device
/dev/nvme0 -d nvme # /dev/nvme0, NVMe device

I then ran smartctl -x /dev/nvme0. and much to my surprise it worked! I will attach the text output.

I must have misunderstood the smartmontools nvme page at https://www.smartmontools.org/wiki/NVMe_Support. I thought it was telling me that I needed to install an additional 'OpenFabrics' driver, which I then thought involved disabling driver signing.

Apparently this was working as is under Windows 7 64-bit and I incorrectly thought I would use /dev/sdf.

Thanks!

As far as Windows 10 goes, it would still be nice to eventually get that working for the day when I may be forced to go that route.

Does it sound like Switching to use the Samsung 2.3 driver should work as is (in Windows 10)?

[Greg Bohn]

Smartctl -x /dev/nvme results from Window 7 64-bit with Samsung 2.3 driver

[Christian Franke]

Info on NVMe page is modified.

If CrystalDiskInfo works, it should be possible to track down the issue. First please repeat the test with the 32-bit version of smartctl from same package (no need to install, select "Extract Files only" or unpack the installer with 7-Zip). The 64-bit version is build with high-entropy ASLR which may have an influence.

[Alex Samorukov]

btw, could be helpful also to get debug log from the diskinfo - ​https://crystalmark.info/software/CrystalDiskInfo/manual-en/Contact.html . Not sure if all nvme details are written to it, but subject to check

[Greg Bohn]

CrystalDiskInfo32 log file run under Windows 10

[Greg Bohn]

CrystalDiskInfo64 log file run under Windows 10

[Greg Bohn]

I ran a test with both the 32 and 64-bit versions of CrystalDiskInfo with the .ini file set to DebugMode=1. They both seemed to work o.k. (and were able to show info. from the Samsung 960 Pro nvme drive).

I attached the 32 and 64-bit log files. These look pretty much the same to me except for the numbers at the start of each line.

[Christian Franke]

Please run a test with 32-bit version of smartctl, see above.

[Greg Bohn]

smartctl under W10: 32-bit version

[Greg Bohn]

W10: 32-bit version smartctl -d nvme -r ioctl,2 --scan

[Greg Bohn]

I ran using the 32-bit version of smartctl (I think) under Windows 10 and it appears to fail in the same way.

[Greg Bohn]

Also, I don't know if it's relevant or not, but the 'E:" drive is a spanned/dynamic disk composed of two of the physical drives.

[Christian Franke]

Should have no influence if Windows builtin dynamic functionality is used.

I still could not reproduce the problem with the systems I have access to. Are you willing to test some smartctl.exe experimental builds? If yes, we can handle this via private mail.

[Greg Bohn]

Are you willing to test some smartctl.exe experimental builds?

Sure.

[ANail]

Hello.
I have a similar case. Could you please let me know if any progress?

[Christian Franke]

Sorry, no. Problem could not be reproduced.
Please be more specific (Windows version, SSD, NVMe driver version, do other tools work?, ...)

[Christian Franke]

Replying to Greg Bohn:

I ran CrystalDiskInfo 7.5.0 in the Windows 10 environment, and it appears to have collected info for the 960 Pro.

These lines from the attached file W10-DiskInfo64.log​ show that IOCTL_STORAGE_QUERY_PROPERTY also does not work for CrystalDiskInfo:

00000984 DoIdentifyDeviceNVMeStorageQuery
00000984 DoIdentifyDeviceNVMeSamsung
00001000 AddDiskNVMe - CMD_TYPE_NVME_SAMSUNG

CrystalDiskInfo then uses Samsung specific subcommands of the NVMe SECURITY SEND/RECEIVE commands (accessible via SCSI SECURITY PROTOCOL OUT/IN) instead. These commands provide an alternative NVMe pass-through access path.

This is not implemented in smartmontools. Feel free to create a related ticket. Note that this would not solve the issue for NVMe drives from other vendors.

[ANail]

Not sure that it is for this ticket. But problem with Samsung NVMe
smartctl -d nvme --scan
does not report anything.

CrystalDisk and NVMeTools.exe did not find as well.

Disk: Samsung NVMe PM971

[ANail]

Hello guys, any update for "Samsung NVMe PM971"?

[Christian Franke]

Replying to ANail:

smartctl -d nvme --scan
does not report anything.

CrystalDisk and NVMeTools.exe did not find as well.

Then it is unlikely that we could implement this for smartmontools. Either there is no NVMe pass-through support or the related documentation is only available under NDA.

Disk: Samsung NVMe PM971

As above: Please be more specific (Windows version, NVMe driver version, ...)

[ANail]

Hello!

OS: Windows 10 Prof
Driver name: iaStorA.sys
Driver comnpany: Intel Corporation
Driver file version: 15.7.5.1025

Could you please advise if Intel has PSDK driver (​http://www.spdk.io/) for Windows and what is "NDA" in comment above?
Thanks.

[Christian Franke]

Driver name: iaStorA.sys
Driver comnpany: Intel Corporation

This is the Intel RST driver and therefore unrelated to this ticket (Microsoft NVMe driver stornvme.sys). The RST driver neither supports NVME_PASS_THROUGH nor IOCTL_STORAGE_QUERY_PROPERTY. The Samsung NVMe driver may work or not. See also the NMVe wiki page.

Could you please advise if Intel has PSDK driver (​http://www.spdk.io/) for Windows

Unknown.

and what is "NDA" in comment above?

For example: Intel requires a ​NDA to get info about proprietary functionality (like possible NVMe pass-through support) of the RST driver.

PS: This is a bug tracker, not a support forum. Don't use this ticket for further questions, use the ​smartmontools support mailing list instead.

[Christian Franke]

Replying to Greg Bohn:

I don't know if it makes a difference, but this is a 'Windows-to-go' type Windows 10 1709 booted from USB (in BIOS mode).

The ​Windows To Go overview says "Internal disks are offline". Does this possibly also mean that certain pass-through I/O-controls are also disabled in this mode?

[Christian Franke]

The problem could not be reproduced on regular Windows 10. It is possibly an intentional limitation of ​Windows To Go and which cannot be fixed.

See ticket #1067 for the Samsung specific alternative NVMe pass-through support which is used by ​CrystalDiskInfo.