Skip to content
View in the app

A better way to browse. Learn more.

Unraid

A full-screen app on your home screen with push notifications, badges and more.

To install this app on iOS and iPadOS
  1. Tap the Share icon in Safari
  2. Scroll the menu and tap Add to Home Screen.
  3. Tap Add in the top-right corner.
To install this app on Android
  1. Tap the 3-dot menu (⋮) in the top-right corner of the browser.
  2. Tap Add to Home screen or Install app.
  3. Confirm by tapping Install.

SMART Test Passes, But ATA Error Count Exists - Safe To Use?

Featured Replies

UnRaid marked one of my hard drives as red recently.  I did a SMART test and while the SMART tests all come back clean (I also put the hard drive into another computer and did other hdd scan tests which revealed no problems).  However, on the SMART Status Page, the hard drive also reveals "ATA Error Count: 1" and has some information that my other hard drives do not have.  I do not understand this error, especially since the SMART tests keep coming back clean.  Should I proceed to insert this disk back into the array, or do I need to proceed to replace it? 

 

I should note that I have had to hard reboot this server a few times since I've been having some problems with UnRaid freezing during a robocopy operation.  So, I'm not sure if this error may be related to that.

 

Here is the SMART Status Report:

 

Statistics for /dev/sdj SAMSUNG_HD103UJ_S13PJ1CS301478

smartctl -a -d ata /dev/sdj
smartctl 5.40 2010-10-16 r3189 [i486-slackware-linux-gnu] (local build)
Copyright (C) 2002-10 by Bruce Allen, http://smartmontools.sourceforge.net

=== START OF INFORMATION SECTION ===
Model Family:     SAMSUNG SpinPoint F1 DT series
Device Model:     SAMSUNG HD103UJ
Serial Number:    S13PJ1CS301478
Firmware Version: 1AA01113
User Capacity:    1,000,204,886,016 bytes
Device is:        In smartctl database [for details use: -P show]
ATA Version is:   8
ATA Standard is:  ATA-8-ACS revision 3b
Local Time is:    Sun Mar 24 20:03:53 2013 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:  (0x00)	Offline data collection activity
				was never started.
				Auto Offline Data Collection: Disabled.
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: 		 (11601) seconds.
Offline data collection
capabilities: 			 (0x7b) SMART execute Offline immediate.
				Auto Offline data collection on/off support.
				Suspend Offline collection upon new
				command.
				Offline surface scan supported.
				Self-test supported.
				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: 	 ( 194) minutes.
Conveyance self-test routine
recommended polling time: 	 (  21) minutes.
SCT capabilities: 	       (0x003f)	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     0x000f   100   100   051    Pre-fail  Always       -       0
  3 Spin_Up_Time            0x0007   068   068   011    Pre-fail  Always       -       10310
  4 Start_Stop_Count        0x0032   099   099   000    Old_age   Always       -       903
  5 Reallocated_Sector_Ct   0x0033   100   100   010    Pre-fail  Always       -       0
  7 Seek_Error_Rate         0x000f   100   100   051    Pre-fail  Always       -       0
  8 Seek_Time_Performance   0x0025   100   100   015    Pre-fail  Offline      -       9853
  9 Power_On_Hours          0x0032   098   098   000    Old_age   Always       -       11730
10 Spin_Retry_Count        0x0033   100   100   051    Pre-fail  Always       -       0
11 Calibration_Retry_Count 0x0012   100   100   000    Old_age   Always       -       0
12 Power_Cycle_Count       0x0032   100   100   000    Old_age   Always       -       334
13 Read_Soft_Error_Rate    0x000e   100   100   000    Old_age   Always       -       0
183 Runtime_Bad_Block       0x0032   100   100   000    Old_age   Always       -       26
184 End-to-End_Error        0x0033   100   100   000    Pre-fail  Always       -       0
187 Reported_Uncorrect      0x0032   100   100   000    Old_age   Always       -       0
188 Command_Timeout         0x0032   100   100   000    Old_age   Always       -       0
190 Airflow_Temperature_Cel 0x0022   067   062   000    Old_age   Always       -       33 (Min/Max 30/33)
194 Temperature_Celsius     0x0022   068   061   000    Old_age   Always       -       32 (Min/Max 29/35)
195 Hardware_ECC_Recovered  0x001a   100   100   000    Old_age   Always       -       494
196 Reallocated_Event_Count 0x0032   100   100   000    Old_age   Always       -       0
197 Current_Pending_Sector  0x0012   100   100   000    Old_age   Always       -       0
198 Offline_Uncorrectable   0x0030   100   100   000    Old_age   Offline      -       0
199 UDMA_CRC_Error_Count    0x003e   100   100   000    Old_age   Always       -       199
200 Multi_Zone_Error_Rate   0x000a   100   100   000    Old_age   Always       -       0
201 Soft_Read_Error_Rate    0x000a   100   100   000    Old_age   Always       -       0

SMART Error Log Version: 1
ATA Error Count: 1
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 1 occurred at disk power-on lifetime: 0 hours (0 days + 0 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
  -- -- -- -- -- -- --
  00 d0 00 a7 4e 29 e0   at LBA = 0x00294ea7 = 2707111

  Commands leading to the command that caused the error were:
  CR FR SC SN CL CH DH DC   Powered_Up_Time  Command/Feature_Name
  -- -- -- -- -- -- -- --  ----------------  --------------------
  c8 00 10 97 4e 29 e0 08      05:10:22.830  READ DMA
  c8 00 e0 b7 45 29 e0 08      05:10:22.810  READ DMA
  c8 00 08 97 42 29 e0 08      05:10:22.810  READ DMA
  c8 00 90 07 3e 29 e0 08      05:10:22.800  READ DMA
  c8 00 98 87 3b 29 e0 08      05:10:22.790  READ DMA

SMART Self-test log structure revision number 1
Num  Test_Description    Status                  Remaining  LifeTime(hours)  LBA_of_first_error
# 1  Extended offline    Completed without error       00%     11729         -
# 2  Short offline       Completed without error       00%     11725         -
# 3  Short offline       Completed without error       00%     11725         -
# 4  Short offline       Completed without error       00%     11707         -
# 5  Short offline       Completed without error       00%     11707         -
# 6  Short offline       Completed without error       00%        31         -
# 7  Short offline       Interrupted (host reset)      90%        31         -

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.

 

Any help you can provide would be appreciated.  Thanks!

199 UDMA_CRC_Error_Count    0x003e  100  100  000    Old_age  Always      -      199

indicates a problem with the cabling to this drive and checksum errors across it.  If you've been anal and tie-wrapped your SATA cables into neat bundles, you've caused the problem, as the cables are not shielded and pick up noise from each other.  Cut the tie-wraps and get some space between the cables.  (messy = better)

It is especially bad if they are bundled with the power cables.

 

In any case,the drive is probably fine, but the cable/cabling to it needs attention.

 

Joe  L.

  • Author

Thanks for the prompt information Joe!  I had bought this server from LimeTech, but I did have to replace the power supply early last year, and I don't recall whether I tried to "clean things up".  I've uploaded some photos of how it currently looks below:

https://skydrive.live.com/redir?resid=57B825B47436CA07!107&authkey=!APAW42tism9WA3o

In case that link breaks since it's too long, here is a shortened link:

http://sdrv.ms/11AFkOx

 

The drive in question is in the middle bay.  Does this look too tight?  And if I remove the tie, can I ignore this error unless I see the error again?

 

Thanks!

The ATA Error Count is just a history of certain errors and it stays with the drive, but only the last 5 are displayed.  Each one shows the operational hour in which it occurred, and you can see in your SMART report that the only error says "Error 1 occurred at disk power-on lifetime: 0 hours", when the drive was brand new!  You now have operated this drive for over 11,700 hours, so that's a long time ago.

 

Keep your SMART reports for each drive, so you can compare them.  If you check another SMART report in a week or month, and the CRC error count is still 199, then you know that you probably fixed the problem, because there are no additional CRC errors.

  • Author

Rob:  Thanks for pointing out that this error occurred at day and hour 0!  In that case, I'll leave things as-is and I'll attempt to re-add it to the array using Joe's instructions at http://lime-technology.com/forum/index.php?topic=2569.msg20649#msg20649.

 

Thanks again Joe L and RobJ for your very prompt and insightful answers!

The drive in question is in the middle bay.  Does this look too tight?  And if I remove the tie, can I ignore this error unless I see the error again?

 

Thanks!

The cables to that middle bay are closely adjacent for most of their length, cut the tie-wrap, try to separate the cables so they are not all closely adjacent and not parallel for most of their length.
  • Author

Will do.  Thanks for checking Joe!

Archived

This topic is now archived and is closed to further replies.

Account

Navigation

Search

Search

Configure browser push notifications

Chrome (Android)
  1. Tap the lock icon next to the address bar.
  2. Tap Permissions → Notifications.
  3. Adjust your preference.
Chrome (Desktop)
  1. Click the padlock icon in the address bar.
  2. Select Site settings.
  3. Find Notifications and adjust your preference.