LinuxQuestions.org
Visit Jeremy's Blog.
Go Back   LinuxQuestions.org > Forums > Linux Forums > Linux - Hardware
User Name
Password
Linux - Hardware This forum is for Hardware issues.
Having trouble installing a piece of hardware? Want to know if that peripheral is compatible with Linux?

Notices


Reply
  Search this Thread
Old 07-04-2012, 05:32 PM   #1
sk545
Member
 
Registered: Aug 2002
Posts: 312

Rep: Reputation: 30
Question Smartctl giving errors, is hard drive going bad?


I as using a avg rescue cd, and for some reason it informed of errors from smartctrl in the very beginning before the scan. So, I decided to run the Seatools utility and also Drive Fitness Test from hitachi. Ran both the short and the long tests which the drive passed. Also used Part Image and ran gsmartcontrol with the long and short tests. The log is the following from that:

Code:
smartctl 5.41 2011-06-09 r3365 [i686-linux-3.0.0-pmagic] (local build)
Copyright (C) 2002-11 by Bruce Allen, http://smartmontools.sourceforge.net

=== START OF INFORMATION SECTION ===
Model Family:    Seagate 
Device Model:     
Serial Number:    
Firmware Version: 
User Capacity:    
Sector Size:      
Device is:        In smartctl database [for details use: -P show]
ATA Version is:   6
ATA Standard is:  ATA/ATAPI-6 T13 1410D revision 2
Local Time is:    Tue Jul  3 21:43:37 2012 UTC
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: 		(  430) 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: 	 ( 111) minutes.

SMART Attributes Data Structure revision number: 10
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   059   051   006    Pre-fail  Always       -       109303022
  3 Spin_Up_Time            0x0003   097   096   000    Pre-fail  Always       -       0
  4 Start_Stop_Count        0x0032   098   098   020    Old_age   Always       -       2548
  5 Reallocated_Sector_Ct   0x0033   100   100   036    Pre-fail  Always       -       0
  7 Seek_Error_Rate         0x000f   088   060   030    Pre-fail  Always       -       672815973
  9 Power_On_Hours          0x0032   084   084   000    Old_age   Always       -       14573
 10 Spin_Retry_Count        0x0013   100   100   097    Pre-fail  Always       -       0
 12 Power_Cycle_Count       0x0032   088   088   020    Old_age   Always       -       13158
194 Temperature_Celsius     0x0022   040   051   000    Old_age   Always       -       40
195 Hardware_ECC_Recovered  0x001a   059   051   000    Old_age   Always       -       109303022
197 Current_Pending_Sector  0x0012   100   100   000    Old_age   Always       -       0
198 Offline_Uncorrectable   0x0010   100   100   000    Old_age   Offline      -       0
199 UDMA_CRC_Error_Count    0x003e   200   182   000    Old_age   Always       -       49
200 Multi_Zone_Error_Rate   0x0000   100   253   000    Old_age   Offline      -       0
202 Data_Address_Mark_Errs  0x0032   100   253   000    Old_age   Always       -       0

SMART Error Log Version: 1
ATA Error Count: 47 (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 47 occurred at disk power-on lifetime: 4600 hours (191 days + 16 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 44 00 00 e0  Error: ICRC, ABRT 1 sectors at LBA = 0x00000044 = 68

  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 01 44 00 00 e0 00      00:00:58.520  READ DMA EXT
  25 00 01 44 00 00 e0 00      00:00:57.828  READ DMA EXT
  25 00 01 44 00 00 e0 00      00:00:57.159  READ DMA EXT
  25 00 01 44 00 00 e0 00      00:00:56.520  READ DMA EXT
  25 00 01 44 00 00 e0 00      00:00:55.855  READ DMA EXT

Error 46 occurred at disk power-on lifetime: 4600 hours (191 days + 16 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 44 00 00 e0  Error: ICRC, ABRT 1 sectors at LBA = 0x00000044 = 68

  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 01 44 00 00 e0 00      00:00:58.520  READ DMA EXT
  25 00 01 44 00 00 e0 00      00:00:57.828  READ DMA EXT
  25 00 01 44 00 00 e0 00      00:00:57.159  READ DMA EXT
  25 00 01 44 00 00 e0 00      00:00:56.520  READ DMA EXT
  25 00 01 44 00 00 e0 00      00:00:55.855  READ DMA EXT

Error 45 occurred at disk power-on lifetime: 4600 hours (191 days + 16 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 44 00 00 e0  Error: ICRC, ABRT 1 sectors at LBA = 0x00000044 = 68

  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 01 44 00 00 e0 00      00:00:50.781  READ DMA EXT
  25 00 01 44 00 00 e0 00      00:00:57.828  READ DMA EXT
  25 00 01 44 00 00 e0 00      00:00:57.159  READ DMA EXT
  25 00 01 44 00 00 e0 00      00:00:56.520  READ DMA EXT
  25 00 01 44 00 00 e0 00      00:00:55.855  READ DMA EXT

Error 44 occurred at disk power-on lifetime: 4600 hours (191 days + 16 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 44 00 00 e0  Error: ICRC, ABRT 1 sectors at LBA = 0x00000044 = 68

  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 01 44 00 00 e0 00      00:00:50.781  READ DMA EXT
  25 00 01 44 00 00 e0 00      00:00:50.780  READ DMA EXT
  25 00 01 44 00 00 e0 00      00:00:57.159  READ DMA EXT
  25 00 01 44 00 00 e0 00      00:00:56.520  READ DMA EXT
  25 00 01 44 00 00 e0 00      00:00:55.855  READ DMA EXT

Error 43 occurred at disk power-on lifetime: 4600 hours (191 days + 16 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 44 00 00 e0  Error: ICRC, ABRT 1 sectors at LBA = 0x00000044 = 68

  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 01 44 00 00 e0 00      00:00:50.781  READ DMA EXT
  25 00 01 44 00 00 e0 00      00:00:50.780  READ DMA EXT
  25 00 01 44 00 00 e0 00      00:00:50.780  READ DMA EXT
  25 00 01 44 00 00 e0 00      00:00:56.520  READ DMA EXT
  25 00 01 44 00 00 e0 00      00:00:55.855  READ DMA 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%     14573         -
# 2  Short offline       Completed without error       00%     14572         -
# 3  Short offline       Completed without error       00%     14572         -
# 4  Short offline       Completed without error       00%     14569         -
# 5  Short offline       Completed without error       00%     14534         -
# 6  Short offline       Completed without error       00%     14530         -
# 7  Short offline       Completed without error       00%     11070         -
# 8  Short offline       Completed without error       00%      6900         -
# 9  Short offline       Completed without error       00%      4939         -

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.
Should I be worried about the drive? It does pass the manufacturer test just fine, but smartcrl says otherwise.
 
Old 07-04-2012, 06:13 PM   #2
linuxbird
Member
 
Registered: Feb 2006
Distribution: Slackware
Posts: 472

Rep: Reputation: 21
Did you cut out the model, etc?

Your error messages are similar to what I sometimes see when there has been a power fault or something similar at some point. The fact is that the drive is spinning up, and passing the long test. To me these are my prime indicators. (That said I had a drive fail 4 weeks ago, which passed all that stuff. I think the head control board may have failed. Post mortem showed good levels from the heads, and the platter was pristine (until I opened the case, of course).

Your drive temp as gotten a little high, and the drive has run for 10000 hours since the errors which are displayed.

Having said all that, you are wise for running smartctl, and I would run the long test periodically. I just cron the test for 3am, and have it message /var/log/messages. After the wait period is over, I dump the results.

Something like:

/sbin/smartctl -t long /dev/sda
/sbin/smartctl -a /dev/sda > /var/log/wherever

There are some tools which take smartmon to a new level, but I go for basic functionality.
 
1 members found this post helpful.
Old 07-04-2012, 06:22 PM   #3
TobiSGD
Moderator
 
Registered: Dec 2009
Location: Germany
Distribution: Whatever fits the task best
Posts: 17,148
Blog Entries: 2

Rep: Reputation: 4867Reputation: 4867Reputation: 4867Reputation: 4867Reputation: 4867Reputation: 4867Reputation: 4867Reputation: 4867Reputation: 4867Reputation: 4867Reputation: 4867
You have zero reallocated sectors, which indicates that the platters are fine. Also, as linuxbird pointed already out, these are really old errors. I wouldn't care about something like that. You have your backups anyway, don't you?
 
1 members found this post helpful.
Old 07-04-2012, 08:16 PM   #4
sk545
Member
 
Registered: Aug 2002
Posts: 312

Original Poster
Rep: Reputation: 30
Quote:
You have your backups anyway, don't you?
Funny you mention it, it was the reason I was testing it in the first place.

Looks like the errors are quite old then...wasn't sure how to read the log. It should be ok then, hopefully.

I had ran scans on the HD from Dr. Web and Kasperky bootable cd's, but had the hard drive lying on the side panel
of the computer case (flat side of HD was touching the side panel). The side panel was made of metal, so this could've caused a heat issue? Dumb move, since these virus scans last a very long time.

Last edited by sk545; 07-04-2012 at 08:24 PM.
 
Old 07-04-2012, 09:01 PM   #5
TobiSGD
Moderator
 
Registered: Dec 2009
Location: Germany
Distribution: Whatever fits the task best
Posts: 17,148
Blog Entries: 2

Rep: Reputation: 4867Reputation: 4867Reputation: 4867Reputation: 4867Reputation: 4867Reputation: 4867Reputation: 4867Reputation: 4867Reputation: 4867Reputation: 4867Reputation: 4867
I don't think so, normally harddisks reach higher temperatures when they are built into a case with insufficient airflow, not when they are used outside of the case. If possible you should maybe add a fan in front of the case that blows cold air towards the disks.
 
Old 07-04-2012, 09:11 PM   #6
linuxbird
Member
 
Registered: Feb 2006
Distribution: Slackware
Posts: 472

Rep: Reputation: 21
They can also get to higher temps when spindle bearings start failing, and driving up the case temp. If you see the temp +20C above ambient case temp, I would backup.

I had a drive with no spared blocks, and it was getting old, with about 80000 hours in a laptop. The temps were OK. It suddenly failed, and smartctl would not have caught it probably up to the minutes of failure. So smartctl is not a certain way of predicting failure, but it is a way.

Last edited by linuxbird; 07-04-2012 at 09:12 PM. Reason: spelling
 
Old 07-05-2012, 08:35 AM   #7
sk545
Member
 
Registered: Aug 2002
Posts: 312

Original Poster
Rep: Reputation: 30
There actually is a intake case fan in the front of the case, then one in the back, and then the PSU has a exhaust fan too. So, one intake fan and two exhaust fans. I did some manual temperature read with a thermometer and the inside case temperature is around 35C mostly, which seems to be ok but when converted to Fahrenheit that's 95F! That is quite hot in the summertime for most people, hope it means different when it comes to computers.
 
Old 07-05-2012, 12:18 PM   #8
jefro
Moderator
 
Registered: Mar 2008
Posts: 20,138

Rep: Reputation: 3178Reputation: 3178Reputation: 3178Reputation: 3178Reputation: 3178Reputation: 3178Reputation: 3178Reputation: 3178Reputation: 3178Reputation: 3178Reputation: 3178
Old errors do make me wonder. What changed. SMART errors are warnings. I think there was some way to clear them. Not sure that is good but if the OEM tests pass then that to me would be the best proof. Reset, if the errors come back then just junk it.
 
Old 09-01-2012, 06:49 AM   #9
H_TeXMeX_H
LQ Guru
 
Registered: Oct 2005
Location: $RANDOM
Distribution: slackware64
Posts: 12,928
Blog Entries: 2

Rep: Reputation: 1292Reputation: 1292Reputation: 1292Reputation: 1292Reputation: 1292Reputation: 1292Reputation: 1292Reputation: 1292Reputation: 1292
@ sk545
The drive looks fine.

@ mangotree
You should not hijack threads. If a long test has passed and all attributes are above threshold, then I would say the drive is fine. However, a drive can always fail unexpectedly, so backup regularly.
 
  


Reply


Thread Tools Search this Thread
Search this Thread:

Advanced Search

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is Off
HTML code is Off



Similar Threads
Thread Thread Starter Forum Replies Last Post
mount: wrong fs type, bad option, bad superblock on /dev/sdc1, New hard drive install ronniekl Linux - Hardware 4 05-03-2012 02:28 AM
Is My HDD bad? smartctl results Chomp Linux - Hardware 4 10-09-2009 10:33 PM
bad hard drive? phatbastard Linux - Hardware 6 06-11-2009 02:59 PM
Removed bad hard drive from computer, now flash drive won't mount. checkmate3001 Linux - Hardware 6 08-15-2008 12:03 AM
NMI, Machine check errors=bad hard drive? robber49 Linux - Hardware 1 04-08-2005 07:59 PM

LinuxQuestions.org > Forums > Linux Forums > Linux - Hardware

All times are GMT -5. The time now is 08:52 AM.

Main Menu
Advertisement
My LQ
Write for LQ
LinuxQuestions.org is looking for people interested in writing Editorials, Articles, Reviews, and more. If you'd like to contribute content, let us know.
Main Menu
Syndicate
RSS1  Latest Threads
RSS1  LQ News
Twitter: @linuxquestions
Open Source Consulting | Domain Registration