SMART Disk error

Hi

I am using CentOS 6.7 and one of my machines showing a few SMART disk errors.

ATA Error Count: 10 (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]

Open in new window



My question is if it is something to worry about? Can they be fixed without replacing the drive?

Following is the complete output:

smartctl 5.43 2012-06-30 r3573 [x86_64-linux-2.6.32-573.el6.x86_64] (local build)
Copyright (C) 2002-12 by Bruce Allen, http://smartmontools.sourceforge.net

=== START OF INFORMATION SECTION ===
Model Family:     Hitachi Deskstar E7K1000
Device Model:     Hitachi HDE721010SLA330
Serial Number:    MS0XJUEK
LU WWN Device Id: 5 000cca 35eccf988
Firmware Version: ST6OA3BF
User Capacity:    1,000,204,886,016 bytes [1.00 TB]
Sector Size:      512 bytes logical/physical
Device is:        In smartctl database [for details use: -P show]
ATA Version is:   8
ATA Standard is:  ATA-8-ACS revision 4
Local Time is:    Thu Oct 15 11:32:59 2015 PKT
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:  (0x85)	Offline data collection activity
					was aborted by an interrupting command from host.
					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: 		(14090) 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: 	 (   1) minutes.
Extended self-test routine
recommended polling time: 	 ( 235) 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       -       1
  2 Throughput_Performance  0x0005   121   121   054    Pre-fail  Offline      -       156
  3 Spin_Up_Time            0x0007   100   100   024    Pre-fail  Always       -       443
  4 Start_Stop_Count        0x0012   100   100   000    Old_age   Always       -       5
  5 Reallocated_Sector_Ct   0x0033   100   100   005    Pre-fail  Always       -       1
  7 Seek_Error_Rate         0x000b   100   100   067    Pre-fail  Always       -       0
  8 Seek_Time_Performance   0x0005   123   123   020    Pre-fail  Offline      -       34
  9 Power_On_Hours          0x0012   100   100   000    Old_age   Always       -       2597
 10 Spin_Retry_Count        0x0013   100   100   060    Pre-fail  Always       -       0
 12 Power_Cycle_Count       0x0032   100   100   000    Old_age   Always       -       5
192 Power-Off_Retract_Count 0x0032   100   100   000    Old_age   Always       -       53
193 Load_Cycle_Count        0x0012   100   100   000    Old_age   Always       -       53
194 Temperature_Celsius     0x0002   146   146   000    Old_age   Always       -       41 (Min/Max 25/46)
196 Reallocated_Event_Count 0x0032   100   100   000    Old_age   Always       -       1
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       -       0

SMART Error Log Version: 1
ATA Error Count: 10 (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 10 occurred at disk power-on lifetime: 26959 hours (1123 days + 7 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
  -- -- -- -- -- -- --
  40 51 01 90 5f 32 4b  Error: UNC at LBA = 0x0b325f90 = 187850640

  Commands leading to the command that caused the error were:
  CR FR SC SN CL CH DH DC   Powered_Up_Time  Command/Feature_Name
  -- -- -- -- -- -- -- --  ----------------  --------------------
  42 00 01 90 5f 32 40 0a  28d+06:57:34.204  READ VERIFY SECTOR(S) EXT
  27 00 00 00 00 00 e0 0a  28d+06:57:34.204  READ NATIVE MAX ADDRESS EXT
  ec 00 00 00 00 00 a0 0a  28d+06:57:34.204  IDENTIFY DEVICE
  ef 03 46 00 00 00 a0 0a  28d+06:57:34.204  SET FEATURES [Set transfer mode]
  27 00 00 00 00 00 e0 0a  28d+06:57:34.204  READ NATIVE MAX ADDRESS EXT

Error 9 occurred at disk power-on lifetime: 26959 hours (1123 days + 7 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
  -- -- -- -- -- -- --
  40 51 01 8f 5f 32 4b  Error: UNC at LBA = 0x0b325f8f = 187850639

  Commands leading to the command that caused the error were:
  CR FR SC SN CL CH DH DC   Powered_Up_Time  Command/Feature_Name
  -- -- -- -- -- -- -- --  ----------------  --------------------
  42 00 01 8f 5f 32 40 0a  28d+06:57:29.804  READ VERIFY SECTOR(S) EXT
  42 00 01 8e 5f 32 40 0a  28d+06:57:29.804  READ VERIFY SECTOR(S) EXT
  42 00 01 8d 5f 32 40 0a  28d+06:57:29.804  READ VERIFY SECTOR(S) EXT
  42 00 01 8c 5f 32 40 0a  28d+06:57:29.804  READ VERIFY SECTOR(S) EXT
  42 00 01 8b 5f 32 40 0a  28d+06:57:29.804  READ VERIFY SECTOR(S) EXT

Error 8 occurred at disk power-on lifetime: 26959 hours (1123 days + 7 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
  -- -- -- -- -- -- --
  40 51 b0 8f 5f 32 4b  Error: UNC at LBA = 0x0b325f8f = 187850639

  Commands leading to the command that caused the error were:
  CR FR SC SN CL CH DH DC   Powered_Up_Time  Command/Feature_Name
  -- -- -- -- -- -- -- --  ----------------  --------------------
  42 00 10 2f 57 32 40 0a  28d+06:57:24.704  READ VERIFY SECTOR(S) EXT
  ec 00 01 00 00 00 00 0a  28d+06:57:24.704  IDENTIFY DEVICE
  ec 00 01 00 00 00 00 0a  28d+06:57:24.704  IDENTIFY DEVICE
  42 00 c2 cf 4e 36 40 0a  28d+06:57:24.604  READ VERIFY SECTOR(S) EXT
  42 00 20 af 00 36 40 0a  28d+06:57:24.504  READ VERIFY SECTOR(S) EXT

Error 7 occurred at disk power-on lifetime: 26959 hours (1123 days + 7 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
  -- -- -- -- -- -- --
  40 51 c0 8f 5f 32 4b  Error: UNC at LBA = 0x0b325f8f = 187850639

  Commands leading to the command that caused the error were:
  CR FR SC SN CL CH DH DC   Powered_Up_Time  Command/Feature_Name
  -- -- -- -- -- -- -- --  ----------------  --------------------
  42 00 20 2f 57 32 40 0a  28d+06:57:18.404  READ VERIFY SECTOR(S) EXT
  42 00 20 0f 09 32 40 0a  28d+06:57:18.304  READ VERIFY SECTOR(S) EXT
  42 00 20 ef ba 31 40 0a  28d+06:57:18.204  READ VERIFY SECTOR(S) EXT
  42 00 20 cf 6c 31 40 0a  28d+06:57:18.004  READ VERIFY SECTOR(S) EXT
  42 00 20 af 1e 31 40 0a  28d+06:57:17.904  READ VERIFY SECTOR(S) EXT

Error 6 occurred at disk power-on lifetime: 26197 hours (1091 days + 13 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
  -- -- -- -- -- -- --
  40 51 a8 8f 5f 32 eb  Error: UNC 168 sectors at LBA = 0x0b325f8f = 187850639

  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 c0 77 5c 32 e0 00  46d+06:01:40.000  READ DMA EXT
  27 00 00 00 00 00 e0 0a  46d+06:01:40.000  READ NATIVE MAX ADDRESS EXT
  ec 00 00 00 00 00 a0 0a  46d+06:01:40.000  IDENTIFY DEVICE
  ef 03 46 00 00 00 a0 0a  46d+06:01:40.000  SET FEATURES [Set transfer mode]
  27 00 00 00 00 00 e0 0a  46d+06:01:40.000  READ NATIVE MAX ADDRESS EXT

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%      2196         -
# 2  Short offline       Completed without error       00%     33349         -
# 3  Short offline       Completed without error       00%     26959         -
# 4  Short offline       Completed without error       00%     11805         -
# 5  Short offline       Completed without error       00%     10258         -

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.

Open in new window

sysautomationAsked:
Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

Dave BaldwinFixer of ProblemsCommented:
The only way to see if you can fix those errors without replacing the drive is to do a low level manufacturers format.  Which may not work and will of course remove all of your data.  I'd suggest you clone it and replace it.
0
Mal OsborneAlpha GeekCommented:
My experience with SMART has been that it is very questionable; I have seen several drives with obvious mechanical errors report nothing, and others with errors keep running for several years.

If this drive is in a "mission critical" server, I would still be replacing it. Repairing HDDs is only practical for data recovery.
0
nobusCommented:
monitor these errors - if they increase - you'll pass the threshold level, and get errors at each boot up
if they don't increase - just use it

i also agree with malmensa's comments
0
Introducing the "443 Security Simplified" Podcast

This new podcast puts you inside the minds of leading white-hat hackers and security researchers. Hosts Marc Laliberte and Corey Nachreiner turn complex security concepts into easily understood and actionable insights on the latest cyber security headlines and trends.

akbCommented:
Download HardDiskSentinel and run it. It gives will analyse the SMART data and give you a readable report.

http://www.hdsentinel.com/
0
andreasSystem AdminCommented:
Your harddisk hace faulty sector. You should have known good and current backups at hand.

For further testing you might run the manufacturers diagnostic tool.

I would not recommend even thinking about fixing hdd problems,  if they are hardware related. If smart shows errors its time for a new drive, except the machine and its data is not important, e.g. testing purpose a toy or a gimmick only.
0
Gerwin Jansen, EE MVETopic Advisor Commented:
This drive has a 5 year warranty, I suggest you RMA it and have it replaced.
0

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Linux

From novice to tech pro — start learning today.

Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.