Opened 3 years ago

Closed 3 years ago

#1476 closed task (invalid)

WD80EFAX-68LHPN0 drive permanently shows ATA Error

Reported by: TuxoHolic Owned by:
Priority: minor Milestone:
Component: smartctl Version:
Keywords: ata Cc:


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:
-- -- -- -- -- -- --
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!

Attachments (1)

smart-x.log (16.4 KB ) - added by TuxoHolic 3 years ago.
smartctl -d sat -a -x

Download all attachments as: .zip

Change History (3)

comment:1 by Christian Franke, 3 years ago

Component: allsmartctl
Keywords: ata added
Milestone: undecided

Please provide the output of smartctl -d sat -a -x /dev/sdb as an attachment(!) to this ticket. Add -q noserial if desired. Do not discard the very first output line as it contains important information about smartctl version and platform.

Such a single CRC error is usually harmless. But this error log may be incomplete because it is the legacy error log (-l error) which only supports 28-bit LBA. Also check the extended error log (-l xerror, included in -x but not in -a) instead.

Smartctl exits with 0x40 if the legacy error log is non-empty. This is usually returned as 0x4000 by POSIX functions like pclose() and waitpid() and should be converted back with WEXITSTATUS().

by TuxoHolic, 3 years ago

Attachment: smart-x.log added

smartctl -d sat -a -x

comment:2 by Christian Franke, 3 years ago

Milestone: undecided
Resolution: invalid
Status: newclosed

Drive reports single CRC error in both error logs. Smartctl behaves as expected.

Note: See TracTickets for help on using tickets.