Custom Query (1560 matches)

Filters
 
Or
 
  
 
Columns

Show under each result:


Results (418 - 420 of 1560)

Ticket Resolution Summary Owner Reporter
#1473 invalid Read NVMe Identify Controller failed: IOCTL_SCSI_PASS_THROUGH_DIRECT failed, Error=87 gary20783_smartmon
Description

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.

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
#1474 fixed Drive submission - WDC WD40NDZM-59A8KS1 xpdite
#1476 invalid WD80EFAX-68LHPN0 drive permanently shows ATA Error TuxoHolic
Description

This disk suddenly got a permanent error entry: 199 UDMA_CRC_Error_Count 0x000a 200 200 000 Old_age Always - 1

SMART Error Log Version: 1 ATA Error Count: 1 Error 1 occurred at disk power-on lifetime: 1051 hours (43 days + 19 hours)

When the command that caused the error occurred, the device was active or idle. After command completion occurred, registers were: ER ST SC SN CL CH DH -- -- -- -- -- -- -- 84 41 00 00 00 00 00 Error: ICRC, ABRT at LBA = 0x00000000 = 0

Commands leading to the command that caused the error were: CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name -- -- -- -- -- -- -- -- ---------------- -------------------- 60 00 00 d0 b6 27 40 80 00:17:24.781 READ FPDMA QUEUED 60 00 00 d0 b5 27 40 80 00:16:42.916 READ FPDMA QUEUED 60 00 00 d0 b4 27 40 80 00:16:42.915 READ FPDMA QUEUED 60 00 00 d0 b3 27 40 80 00:16:42.914 READ FPDMA QUEUED 60 00 00 d0 b2 27 40 80 00:16:42.912 READ FPDMA QUEUED

It looks like a single data transmission (CRC) error bewtween disk and SATA controller.

Is it correct to assume that this does not really influence the probability of future errors?

Unfortunately running smartctl -ad sat /dev/sdb returns error status 0x4000 wich I could not find in the documentation. Could you please give a hint to documentation of high valued exist status. Many thanks!

Batch Modify
Note: See TracBatchModify for help on using batch modify.
Note: See TracQuery for help on using queries.