Device ATA error

o0o

Dabbler
Joined
Feb 10, 2021
Messages
20
Hi,

from time to time during heavy data movement I get this error message:
CRITICAL
Device: /dev/ada3, ATA error count increased from 118 to 119.

What does this mean exactly?

I can see no data loss.
The disc is connected to a 2-port SATA controller. The other disc on the same controller never showed this alert (so far).
The disc is a very new Toshiba 8TB HDD.
Shall I take care of this, or since no data loss accept this error?

Otherwise I would like to check, if it is the controller or the disc. Can I simply switch SATA ports with an other disc? Or will this destroy my multi disc pool?

Thanks for your help!
 

o0o

Dabbler
Joined
Feb 10, 2021
Messages
20
I forgot: I already used the search and couldn't find a solution. I read the thread about power. I have a 550W PSU for 8 drives, this shall be enough. When the error appeared for the first time, I replaced the SATA cable.

And I got this:

Code:
root@truenas[~]# smartctl -a /dev/ada3
smartctl 7.1 2019-12-30 r5022 [FreeBSD 12.2-RELEASE-p3 amd64] (local build)
Copyright (C) 2002-19, Bruce Allen, Christian Franke, www.smartmontools.org

=== START OF INFORMATION SECTION ===
Model Family:     Toshiba MG06ACA... Enterprise Capacity HDD
Device Model:     TOSHIBA MG06ACA800E
Serial Number:    80N0A2HWFKRE
LU WWN Device Id: 5 000039 a58d29981
Firmware Version: 0108
User Capacity:    8,001,563,222,016 bytes [8.00 TB]
Sector Sizes:     512 bytes logical, 4096 bytes physical
Rotation Rate:    7200 rpm
Form Factor:      3.5 inches
Device is:        In smartctl database [for details use: -P show]
ATA Version is:   ACS-3 T13/2161-D revision 5
SATA Version is:  SATA 3.3, 6.0 Gb/s (current: 1.5 Gb/s)
Local Time is:    Thu Feb 25 00:50:34 2021 CET
SMART support is: Available - device has SMART capability.
SMART support is: Enabled

=== START OF READ SMART DATA SECTION ===
SMART overall-health self-assessment test result: PASSED

General SMART Values:
Offline data collection status:  (0x82) Offline data collection activity
                                        was completed without error.
                                        Auto Offline Data Collection: Enabled.
Self-test execution status:      (   0) The previous self-test routine completed
                                        without error or no self-test has ever
                                        been run.
Total time to complete Offline
data collection:                (  120) seconds.
Offline data collection
capabilities:                    (0x5b) SMART execute Offline immediate.
                                        Auto Offline data collection on/off support.
                                        Suspend Offline collection upon new
                                        command.
                                        Offline surface scan supported.
                                        Self-test supported.
                                        No Conveyance Self-test supported.
                                        Selective Self-test supported.
SMART capabilities:            (0x0003) Saves SMART data before entering
                                        power-saving mode.
                                        Supports SMART auto save timer.
Error logging capability:        (0x01) Error logging supported.
                                        General Purpose Logging supported.
Short self-test routine
recommended polling time:        (   2) minutes.
Extended self-test routine
recommended polling time:        ( 843) minutes.
SCT capabilities:              (0x003d) SCT Status supported.
                                        SCT Error Recovery Control supported.
                                        SCT Feature Control supported.
                                        SCT Data Table supported.

SMART Attributes Data Structure revision number: 16
Vendor Specific SMART Attributes with Thresholds:
ID# ATTRIBUTE_NAME          FLAG     VALUE WORST THRESH TYPE      UPDATED  WHEN_FAILED RAW_VALUE
  1 Raw_Read_Error_Rate     0x000b   100   100   050    Pre-fail  Always       -       0
  2 Throughput_Performance  0x0005   100   100   050    Pre-fail  Offline      -       0
  3 Spin_Up_Time            0x0027   100   100   001    Pre-fail  Always       -       8144
  4 Start_Stop_Count        0x0032   100   100   000    Old_age   Always       -       3
  5 Reallocated_Sector_Ct   0x0033   100   100   010    Pre-fail  Always       -       0
  7 Seek_Error_Rate         0x000b   100   100   050    Pre-fail  Always       -       0
  8 Seek_Time_Performance   0x0005   100   100   050    Pre-fail  Offline      -       0
  9 Power_On_Hours          0x0032   100   100   000    Old_age   Always       -       333
 10 Spin_Retry_Count        0x0033   100   100   030    Pre-fail  Always       -       0
 12 Power_Cycle_Count       0x0032   100   100   000    Old_age   Always       -       3
191 G-Sense_Error_Rate      0x0032   100   100   000    Old_age   Always       -       1
192 Power-Off_Retract_Count 0x0032   100   100   000    Old_age   Always       -       1
193 Load_Cycle_Count        0x0032   100   100   000    Old_age   Always       -       3
194 Temperature_Celsius     0x0022   100   100   000    Old_age   Always       -       43 (Min/Max 17/44)
196 Reallocated_Event_Count 0x0032   100   100   000    Old_age   Always       -       0
197 Current_Pending_Sector  0x0032   100   100   000    Old_age   Always       -       0
198 Offline_Uncorrectable   0x0030   100   100   000    Old_age   Offline      -       0
199 UDMA_CRC_Error_Count    0x0032   200   200   000    Old_age   Always       -       119
220 Disk_Shift              0x0002   100   100   000    Old_age   Always       -       84148229
222 Loaded_Hours            0x0032   100   100   000    Old_age   Always       -       333
223 Load_Retry_Count        0x0032   100   100   000    Old_age   Always       -       0
224 Load_Friction           0x0022   100   100   000    Old_age   Always       -       0
226 Load-in_Time            0x0026   100   100   000    Old_age   Always       -       530
240 Head_Flying_Hours       0x0001   100   100   001    Pre-fail  Offline      -       0

SMART Error Log Version: 1
ATA Error Count: 119 (device log contains only the most recent five errors)
        CR = Command Register [HEX]
        FR = Features Register [HEX]
        SC = Sector Count Register [HEX]
        SN = Sector Number Register [HEX]
        CL = Cylinder Low Register [HEX]
        CH = Cylinder High Register [HEX]
        DH = Device/Head Register [HEX]
        DC = Device Command Register [HEX]
        ER = Error register [HEX]
        ST = Status register [HEX]
Powered_Up_Time is measured from power on, and printed as
DDd+hh:mm:SS.sss where DD=days, hh=hours, mm=minutes,
SS=sec, and sss=millisec. It "wraps" after 49.710 days.

Error 119 occurred at disk power-on lifetime: 332 hours (13 days + 20 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 51 28 67 60 33 40  Error: ICRC, ABRT 40 sectors at LBA = 0x00336067 = 3367015

  Commands leading to the command that caused the error were:
  CR FR SC SN CL CH DH DC   Powered_Up_Time  Command/Feature_Name
  -- -- -- -- -- -- -- --  ----------------  --------------------
  25 00 f8 70 58 33 40 00  11d+20:26:48.204  READ DMA EXT
  25 00 08 68 58 33 40 00  11d+20:26:48.204  READ DMA EXT
  25 00 f8 70 50 33 40 00  11d+20:26:48.193  READ DMA EXT
  25 00 08 68 50 33 40 00  11d+20:26:48.192  READ DMA EXT
  25 00 f8 70 48 33 40 00  11d+20:26:48.182  READ DMA EXT

Error 118 occurred at disk power-on lifetime: 313 hours (13 days + 1 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 51 88 3f c6 63 40  Error: ICRC, ABRT 136 sectors at LBA = 0x0063c63f = 6538815

  Commands leading to the command that caused the error were:
  CR FR SC SN CL CH DH DC   Powered_Up_Time  Command/Feature_Name
  -- -- -- -- -- -- -- --  ----------------  --------------------
  25 00 f8 48 be 63 40 00  11d+01:42:20.667  READ DMA EXT
  25 00 08 40 be 63 40 00  11d+01:42:20.667  READ DMA EXT
  25 00 f8 48 b6 63 40 00  11d+01:42:20.656  READ DMA EXT
  25 00 08 40 b6 63 40 00  11d+01:42:20.656  READ DMA EXT
  25 00 f8 48 ae 63 40 00  11d+01:42:20.645  READ DMA EXT

Error 117 occurred at disk power-on lifetime: 311 hours (12 days + 23 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 51 18 ef e6 ce 40  Error: ICRC, ABRT 24 sectors at LBA = 0x00cee6ef = 13559535

  Commands leading to the command that caused the error were:
  CR FR SC SN CL CH DH DC   Powered_Up_Time  Command/Feature_Name
  -- -- -- -- -- -- -- --  ----------------  --------------------
  25 00 f8 f8 de ce 40 00  10d+23:53:03.978  READ DMA EXT
  25 00 08 f0 de ce 40 00  10d+23:53:03.977  READ DMA EXT
  25 00 f8 f8 d6 ce 40 00  10d+23:53:03.966  READ DMA EXT
  25 00 08 f0 d6 ce 40 00  10d+23:53:03.966  READ DMA EXT
  25 00 f8 f8 ce ce 40 00  10d+23:53:03.955  READ DMA EXT

Error 116 occurred at disk power-on lifetime: 310 hours (12 days + 22 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 51 e8 d7 2f 31 40  Error: ICRC, ABRT 232 sectors at LBA = 0x00312fd7 = 3223511

  Commands leading to the command that caused the error were:
  CR FR SC SN CL CH DH DC   Powered_Up_Time  Command/Feature_Name
  -- -- -- -- -- -- -- --  ----------------  --------------------
  25 00 f8 e0 27 31 40 00  10d+22:54:21.889  READ DMA EXT
  25 00 08 d8 27 31 40 00  10d+22:54:21.888  READ DMA EXT
  25 00 f8 e0 1f 31 40 00  10d+22:54:21.874  READ DMA EXT
  25 00 08 d8 1f 31 40 00  10d+22:54:21.873  READ DMA EXT
  25 00 f8 e0 17 31 40 00  10d+22:54:21.853  READ DMA EXT

Error 115 occurred at disk power-on lifetime: 309 hours (12 days + 21 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 51 18 0f c4 97 40  Error: ICRC, ABRT 24 sectors at LBA = 0x0097c40f = 9946127

  Commands leading to the command that caused the error were:
  CR FR SC SN CL CH DH DC   Powered_Up_Time  Command/Feature_Name
  -- -- -- -- -- -- -- --  ----------------  --------------------
  25 00 f8 18 bc 97 40 00  10d+21:28:43.755  READ DMA EXT
  25 00 08 10 bc 97 40 00  10d+21:28:43.754  READ DMA EXT
  25 00 f8 18 b4 97 40 00  10d+21:28:43.736  READ DMA EXT
  25 00 08 10 b4 97 40 00  10d+21:28:43.735  READ DMA EXT
  25 00 f8 18 ac 97 40 00  10d+21:28:43.720  READ DMA EXT

SMART Self-test log structure revision number 1
Num  Test_Description    Status                  Remaining  LifeTime(hours)  LBA_of_first_error
# 1  Short offline       Completed without error       00%       256         -
# 2  Short offline       Completed without error       00%        19         -

SMART Selective self-test log data structure revision number 1
 SPAN  MIN_LBA  MAX_LBA  CURRENT_TEST_STATUS
    1        0        0  Not_testing
    2        0        0  Not_testing
    3        0        0  Not_testing
    4        0        0  Not_testing
    5        0        0  Not_testing
Selective self-test flags (0x0):
  After scanning selected spans, do NOT read-scan remainder of disk.
If Selective self-test is pending on power-up, resume after 0 minute delay.
 

sretalla

Powered by Neutrality
Moderator
Joined
Jan 1, 2016
Messages
9,702
199 UDMA_CRC_Error_Count 0x0032 200 200 000 Old_age Always - 119
This is the line that caused the alert.

If it continues increasing, you may have a disk with a bad onboard controller, if it stops increasing, your cabling/port change has worked.

The fact that all of the blocks referenced in the errors are different and you don't find read or write errors implies that it isn't actually the blocks that are bad.
 
  • Like
Reactions: o0o

o0o

Dabbler
Joined
Feb 10, 2021
Messages
20
Thanks. The errors started counting at 0. So it increased. It mostly happens, when heavy writing and reading occurs at the same time.

Is it possible to switch ports without destroying the pools?
 

sretalla

Powered by Neutrality
Moderator
Joined
Jan 1, 2016
Messages
9,702
s it possible to switch ports without destroying the pools?
Yes. ZFS doesn't care which connection path it needs to take.
 

ChrisRJ

Wizard
Joined
Oct 23, 2020
Messages
1,906
I would also not rule out that the serious limitations of the system (single core CPU and 3 GB RAM) might play a role here.
 

joeschmuck

Old Man
Moderator
Joined
May 28, 2011
Messages
10,970
@sretalla is correct, the error UDMA_CRC_ERROR is a communications error between the drive and the SATA controller, meaning the SATA cable is the general cause. Please note that once this value has been stored on the hard drive, it remains persistent and cannot be reset to zero.

My advice is: (NOTE: Always secure power before moving any cables!!!!!)
1) Swap the SATA cable between drive Serial Number: 80N0A2HWFKRE (use the serial number to identify the drive) and an adjacent hard drive.
2) If ID 199 continues to increment for this hard drive then odds are the drive has faulty electronics, but swap the power and check again for the heck of it.
3) If ID 199 stops incrementing, check the other drive you swapped the cable with, if it is incrementing then the SATA cable or SATA Controller is bad, got to step 4. If ID 199 in not incrementing at all then it was a loose connector (hopefully).
4) If the problem moved to the second drive now you need to replace the SATA cable with a new one and this will generally fix this kind of problem, but if the problem continues then the SATA Controller is likely bad and you are going to not be a happy person.
 

sretalla

Powered by Neutrality
Moderator
Joined
Jan 1, 2016
Messages
9,702
(single core CPU and 3 GB RAM)
Indeed this isn't ideal (and even a setup for problems which will certainly arrive).

You need a minimum of 8GB of RAM to maintain ZFS stability
 
Top