ATA error count keeps increasing

Status
Not open for further replies.
R

redzero36

Cadet
Joined
Mar 24, 2017
Messages
5
One of my hdds ata error count keeps increasing. Its a new harddrive so I'm hoping its nothing serious. It started at like 200 before now its like 417. Should I be worried? Maybe try to return it?

I did the smartctl -a thing but I don't really understand it.
Code:

  smartctl 6.5 2016-05-07 r4318 [FreeBSD 10.3-STABLE amd64] (local build)
Copyright (C) 2002-16, Bruce Allen, Christian Franke, www.smartmontools.org
=== START OF INFORMATION SECTION ===
Model Family:  Hitachi Ultrastar 7K3000
Device Model:  Hitachi HUA723030ALA640
Serial Number:  MK0371YVH0N0XA
LU WWN Device Id: 5 000cca 234ce62b1
Firmware Version: MKAOAA10
User Capacity:  3,000,592,982,016 bytes [3.00 TB]
Sector Size:  512 bytes logical/physical
Rotation Rate:  7200 rpm
Form Factor:  3.5 inches
Device is:  In smartctl database [for details use: -P show]
ATA Version is:  ATA8-ACS T13/1699-D revision 4
SATA Version is:  SATA 2.6, 6.0 Gb/s (current: 1.5 Gb/s)
Local Time is:  Tue Mar 28 15:25:45 2017 PDT
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:  (  24) seconds.
Offline data collection
capabilities:  (0x5b) SMART execute Offline immediate.
  Auto Offline data collection on/off supp  ort.
  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:  (  1) minutes.
Extended self-test routine
recommended polling time:  ( 468) 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  016  Pre-fail  Always  -  0
  2 Throughput_Performance  0x0005  135  135  054  Pre-fail  Offline  -  84
  3 Spin_Up_Time  0x0007  135  135  024  Pre-fail  Always  -  519 (Average 622)
  4 Start_Stop_Count  0x0012  100  100  000  Old_age  Always  -  29
  5 Reallocated_Sector_Ct  0x0033  100  100  005  Pre-fail  Always  -  0
  7 Seek_Error_Rate  0x000b  100  100  067  Pre-fail  Always  -  0
  8 Seek_Time_Performance  0x0005  123  123  020  Pre-fail  Offline  -  31
  9 Power_On_Hours  0x0012  100  100  000  Old_age  Always  -  55
 10 Spin_Retry_Count  0x0013  100  100  060  Pre-fail  Always  -  0
 12 Power_Cycle_Count  0x0032  100  100  000  Old_age  Always  -  29
192 Power-Off_Retract_Count 0x0032  100  100  000  Old_age  Always  -  30
193 Load_Cycle_Count  0x0012  100  100  000  Old_age  Always  -  30
194 Temperature_Celsius  0x0002  117  117  000  Old_age  Always  -  51 (Min/Max 19/53)
196 Reallocated_Event_Count 0x0032  100  100  000  Old_age  Always  -  0
197 Current_Pending_Sector  0x0022  100  100  000  Old_age  Always  -  0
198 Offline_Uncorrectable  0x0008  100  100  000  Old_age  Offline  -  0
199 UDMA_CRC_Error_Count  0x000a  200  200  000  Old_age  Always  -  479
SMART Error Log Version: 1
ATA Error Count: 479 (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 479 occurred at disk power-on lifetime: 42 hours (1 days + 18 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 01 2f f9 57 00  Error: ICRC, ABRT at LBA = 0x0057f92f = 5765423
  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 08 00 2f f9 57 40 ff  08:44:34.817  READ FPDMA QUEUED
  60 08 40 28 f9 57 40 00  08:44:34.817  READ FPDMA QUEUED
  60 08 38 60 f9 57 40 00  08:44:34.809  READ FPDMA QUEUED
  60 08 30 b0 f9 57 40 00  08:44:34.804  READ FPDMA QUEUED
  60 08 28 58 f9 57 40 00  08:44:34.791  READ FPDMA QUEUED
Error 478 occurred at disk power-on lifetime: 42 hours (1 days + 18 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 01 1f c1 42 04  Error: ICRC, ABRT at LBA = 0x0442c11f = 71483679
  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 08 00 1f c1 42 44 ff  08:41:31.652  READ FPDMA QUEUED
  60 08 10 10 c1 42 40 00  08:41:31.652  READ FPDMA QUEUED
  60 08 08 38 c1 42 40 00  08:41:31.652  READ FPDMA QUEUED
  60 08 00 c8 c1 42 40 00  08:41:31.652  READ FPDMA QUEUED
  60 08 f8 40 c1 42 40 00  08:41:31.652  READ FPDMA QUEUED
Error 477 occurred at disk power-on lifetime: 42 hours (1 days + 18 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 01 1f 9a 5a 00  Error: ICRC, ABRT at LBA = 0x005a9a1f = 5937695
  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 08 00 1f 9a 5a 40 ff  08:41:31.062  READ FPDMA QUEUED
  60 08 e0 18 9a 5a 40 00  08:41:31.062  READ FPDMA QUEUED
  60 08 d8 f8 9a 5a 40 00  08:41:31.061  READ FPDMA QUEUED
  60 08 d0 c0 99 5a 40 00  08:41:31.061  READ FPDMA QUEUED
  60 08 c8 d8 9a 5a 40 00  08:41:31.060  READ FPDMA QUEUED
Error 476 occurred at disk power-on lifetime: 42 hours (1 days + 18 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 01 0f 65 5a 00  Error: ICRC, ABRT at LBA = 0x005a650f = 5924111
  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 08 00 0f 65 5a 40 ff  08:41:30.095  READ FPDMA QUEUED
  60 08 b0 08 65 5a 40 00  08:41:30.095  READ FPDMA QUEUED
  60 08 a8 68 64 5a 40 00  08:41:30.091  READ FPDMA QUEUED
  60 08 a0 a8 68 5a 40 00  08:41:30.089  READ FPDMA QUEUED
  60 08 98 e8 63 5a 40 00  08:41:30.086  READ FPDMA QUEUED
Error 475 occurred at disk power-on lifetime: 42 hours (1 days + 18 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 01 ef 66 5a 00  Error: ICRC, ABRT at LBA = 0x005a66ef = 5924591
  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 08 00 ef 66 5a 40 ff  08:41:29.878  READ FPDMA QUEUED
  60 08 f0 e8 66 5a 40 00  08:41:29.878  READ FPDMA QUEUED
  60 08 e8 68 65 5a 40 00  08:41:29.876  READ FPDMA QUEUED
  60 08 e0 80 68 5a 40 00  08:41:29.875  READ FPDMA QUEUED
  60 08 d8 70 68 5a 40 00  08:41:29.873  READ FPDMA QUEUED
SMART Self-test log structure revision number 1
Num  Test_Description  Status  Remaining  LifeTime(hours)  LBA  _of_first_error
# 1  Short captive  Completed without error  00%  1  -
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.
 
R

Robert Trevellyan

Pony Wrangler
Joined
May 16, 2014
Messages
3,778
R

redzero36

Cadet
Joined
Mar 24, 2017
Messages
5
Robert Trevellyan said:
Check out the hard drive troubleshooting guide.
https://forums.freenas.org/index.php?resources/hard-drive-troubleshooting-guide.17/

Sometimes that's a cable problem.

Too hot!
Click to expand...
Finally have time to do the tests, been very busy. So I started the long test and it says it gonna take like 8 hours. So I'll be following the guide. It seems straight forward enough. Also about it being too hot, I plan on buying a new computer case when I have the funds for it so hopefully soon I can buy a new case with more fans available. Also what is the temperature range I should be aiming for?

edit: Also when doing the long smart test, is it safe to be using the server? Like writing to the hdd? I'm still trying to setup my jails.
Also on 3.b "b. If any of the IDs are greater than zero (0) then the drive has failed for RMA purposes." the IDs the guide is talking about is just 5,197,198 right? And how do I know if the cable swap fixed it?

edit 2:
Okay so the results of the long test for IDs 5,197,198 are still 0. I swapped the data cables so I guess I just wait a while till something happens.
 
Last edited:
Mr_N

Mr_N

Patron
Joined
Aug 31, 2013
Messages
289
you dont really wanna be running drives too far over 30 degC for an extended period, over 40 is bad... theres a script around somewhere that you could run as a scheduled task to give you some idea of your drive temps across the day

long drive tests will go quicker if the nas isnt being used same as for a scrub, but you can still use them if you have to, usually these things would be scheduled for overnight ;)
 
R

Robert Trevellyan

Pony Wrangler
Joined
May 16, 2014
Messages
3,778
redzero36 said:
what is the temperature range I should be aiming for?
Click to expand...
I wouldn't be concerned about running them in the mid-30s if the temperatures are steady. Scrubs tend to push them hardest, so you need some headroom from the idle temps. Wide fluctuations are undesirable.
 
Mr_N

Mr_N

Patron
Joined
Aug 31, 2013
Messages
289
yeah brain fart, 30-35 is ok :)
 
Status
Not open for further replies.

Similar threads

E
SOLVED New WD Gold 12TBs in Lenovo SA120: ATA error count increased
Replies
18
Views
4K
eroji
E
JKman
smartctl results interpreter please
Replies
13
Views
2K
JKman
JKman
angelus249
  • Locked
Not sure how to interpret SMART, please confirm
Replies
9
Views
3K
angelus249
angelus249
Q
Keep getting ATA errors, SMART seems fine
Replies
0
Views
726
quik
Q
A
Is the disk dying (ATA error count increased from 0 to 1)?
Replies
6
Views
4K
AgentMC
A
Top