#1473 closed defect (invalid)
Read NVMe Identify Controller failed: IOCTL_SCSI_PASS_THROUGH_DIRECT failed, Error=87
Reported by: | gary20783_smartmon | Owned by: | |
---|---|---|---|
Priority: | minor | Milestone: | |
Component: | all | Version: | 7.2 |
Keywords: | nvme usb windows | Cc: |
Description (last modified by )
Using an ADATA XPG SX8200 Pro 1tB drive gives the above error when issuing any smartctl command. For example, "smartctl -i f:". See output below.
I'm on an HP Envy 15T-EP000 running Windows 10 Pro.
I have used 2 different USB/NVME adapters with the same result.
- https://www.amazon.com/gp/product/B07MBMCX53/ref=ppx_yo_dt_b_asin_title_o01_s00?ie=UTF8&psc=1
- https://www.amazon.com/gp/product/B07N48N5GR/ref=ppx_yo_dt_b_asin_title_o00_s00
I did not find the ADATA drive in the database.
Output from smartctl.
C:\windows\system32>smartctl -i f: smartctl 7.2 2020-12-30 r5155 [x86_64-w64-mingw32-w10-2004] (sf-7.2-1) Copyright (C) 2002-20, Bruce Allen, Christian Franke, www.smartmontools.org Read NVMe Identify Controller failed: IOCTL_SCSI_PASS_THROUGH_DIRECT failed, Error=87
Change History (5)
comment:1 by , 4 years ago
Description: | modified (diff) |
---|---|
Keywords: | windows nvme added |
comment:2 by , 4 years ago
Keywords: | usb added |
---|---|
Milestone: | → undecided |
comment:3 by , 4 years ago
The Plugable enclosure uses the Realtek chip.
Using the smartctl --scan
showed the devices in *nix format. Using /dev/sdc, I was able to successfully query the SMART data.
I did not realize that one could pass the device strings in *nix format.
comment:4 by , 4 years ago
Resolution: | → invalid |
---|---|
Status: | new → closed |
Works if correct device name is specified.
Also works for me with drive letter instead of device name (Win10 Pro 1909, similar Plugable enclosure, Samsung 970 SSD 500G, one NTFS partition). I have no idea why this does not work on your system.
comment:5 by , 4 years ago
Milestone: | undecided |
---|
Mapping of pass-through I/0-controls from partitions behind drive letters to physical drives relies on undocumented windows functionality and does not always work.
Try
smartctl --scan
to see possible valid pseudo device names for the connected physical drives.Is the Plugable enclosure JMicron or Realtek based?
See also "Does the USBC-NVME Support SMART?" at https://plugable.com/products/usbc-nvme#nav-faq