how-to block ads
|
|
Uniqs:
628 |
Share Topic
 |
 |
|
|
|
Reviews:
 ·Shaw
| [hard drive] Can somone look at my SMART Data please? The Read Error Rate has been creeping up since June. The drive was alreadhy RMAed back in January. I am also attaching an attachment. Thank you!
smartctl 5.43 2012-06-30 r3573 [i686-w64-mingw32-win7(64)-sp1] (sf-5.43-1)
Copyright (C) 2002-12 by Bruce Allen, »smartmontools.sourceforge.net
=== START OF INFORMATION SECTION ===
Model Family: Western Digital Caviar Black
Device Model: WDC WD1002FAEX-00Y9A0
Serial Number:
LU WWN Device Id: 5 0014ee 204bc249f
Firmware Version: 05.01D05
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: Exact ATA specification draft version not indicated
Local Time is: Fri Sep 28 22:57:25 2012 PDT
SMART support is: Available - device has SMART capability.
SMART support is: Enabled
AAM feature is: Unavailable
APM feature is: Unavailable
Rd look-ahead is: Enabled
Write cache is: Enabled
ATA Security is: Disabled, NOT FROZEN [SEC1]
=== START OF READ SMART DATA SECTION ===
SMART overall-health self-assessment test result: PASSED
General SMART Values:
Offline data collection status: (0x84) Offline data collection activity
was suspended 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: (17100) 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: ( 176) minutes.
Conveyance self-test routine
recommended polling time: ( 5) minutes.
SCT capabilities: (0x3035) SCT Status supported.
SCT Feature Control supported.
SCT Data Table supported.
SMART Attributes Data Structure revision number: 16
Vendor Specific SMART Attributes with Thresholds:
1 Raw_Read_Error_Rate 0x002f 200 200 051 Pre-fail Always - 14
3 Spin_Up_Time 0x0027 173 171 021 Pre-fail Always - 4333
4 Start_Stop_Count 0x0032 100 100 000 Old_age Always - 429
5 Reallocated_Sector_Ct 0x0033 200 200 140 Pre-fail Always - 0
7 Seek_Error_Rate 0x002e 100 253 000 Old_age Always - 0
9 Power_On_Hours 0x0032 098 098 000 Old_age Always - 1950
10 Spin_Retry_Count 0x0032 100 100 000 Old_age Always - 0
11 Calibration_Retry_Count 0x0032 100 100 000 Old_age Always - 0
12 Power_Cycle_Count 0x0032 100 100 000 Old_age Always - 428
192 Power-Off_Retract_Count 0x0032 200 200 000 Old_age Always - 4
193 Load_Cycle_Count 0x0032 200 200 000 Old_age Always - 424
194 Temperature_Celsius 0x0022 112 104 000 Old_age Always - 35
196 Reallocated_Event_Count 0x0032 200 200 000 Old_age Always - 0
197 Current_Pending_Sector 0x0032 200 200 000 Old_age Always - 0
198 Offline_Uncorrectable 0x0030 100 253 000 Old_age Offline - 0
199 UDMA_CRC_Error_Count 0x0032 200 200 000 Old_age Always - 0
200 Multi_Zone_Error_Rate 0x0008 100 253 000 Old_age Offline - 0
SMART Error Log Version: 1
No Errors Logged
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% 1931 -
# 2 Short offline Completed without error 00% 311 -
# 3 Short offline Completed without error 00% 24 -
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. | |
 koitsuPremium,MVM
join:2002-07-16
Mountain View, CA
kudos:20 | Looks perfectly normal/reasonable for a WD1002FAEX; nothing to worry about. The only time to worry in the case of a rapidly increasing Raw_Read_Error_Rate is if a) the performance of the drive, especially around specific LBA regions, is consistently atrocious (not "slower than others", but horribly, horrible bad), or b) if you start to see an increase in suspect LBAs (Current_Pending_Sector).
Furthermore, do not get in the habit of reading RAW_VALUE literally. Do not become OCD regarding your attributes. I cover this in a post here (read, do not skim; start at the 4th paragraph): »Re: [hard drive] Do these drive stats show a defective drive?
I see you did numerous short SMART tests. These don't check every LBA on the drive; selective scans or extended/long scans do (the latter behaviour varies per drive model however). But there's no indication per your attributes that you need to do this. Like I said above: don't get OCD about it.
Footnote / advice in passing -- There is absolutely no reason to hide drive information (shown in the screenshot), ditto with serial number. Nobody can do anything with that data unless they have the physical drive in hand. Just say no to paranoia.
--
Making life hard for others since 1977.
I speak for myself and not my employer/affiliates of my employer. | |
Reviews:
·Shaw
| Thanks, I did read your inital posts/comments previously so not to panick, lol. However, what got me concerned was that my much much older Hitachi drive has no raw read errors at all. And I read somwhere may be the SATA cables might too close or touching one another causing these errors. | |
koitsuPremium,MVM
join:2002-07-16
Mountain View, CA
kudos:20 | said by Bandito:However, what got me concerned was that my much much older Hitachi drive has no raw read errors at all. This means you're still continuing to look at the RAW_VALUE column as a counter. Please stop doing that.  It's a RATE, not a COUNTER. Just because something is non-zero does not mean you need to be concerned.
Hard disks experience degrees of errors constantly. When a drive reads from a physical sector, there is an associated ECC section with that sector (see 3rd paragraph) -- there is more stored per sector than just your data.
If a drive encounters a situation where it experiences a very brief (often unnoticeable) read error, it can automatically correct the bits using the ECC portion read from the same sector. The drive may choose to adjust some internal SMART attributes as a result; how it adjusts it is up to the drive firmware and is 100% proprietary/vendor-specific.
Repeated read errors from a single sector will cause the drive to mark the sector as "suspect", which is where Current_Pending_Sector comes into play. That attribute will increment if/when this happens. The sector then becomes unreadable (meaning you have lost the data stored in that sector), and the rest of how bad sectors work / etc. is outside of the topic of this discussion.
So the bottom line here is: please stop worrying when you see a SMART attribute's RAW_VALUE field show up as non-zero. No hard disk is perfect, especially considering how much data we're shoving onto platters of the same physical form factor/size these days.
said by Bandito:And I read somwhere may be the SATA cables might too close or touching one another causing these errors. You either misunderstood what you read, or what someone wrote is completely and entirely wrong. The only SMART attribute that can be affected by bad SATA cables (not "cables touching", but actual copper degradation or (more common) shoddy end connectors) is UDMA_CRC_Error_Count. This is in no way related to Raw_Read_Error_Rate.
CRC errors can be caused by many things (more than just cables), such as electrical and electronic interference, or a PCB with a shoddy soldering job. A CRC error results in a resubmission of the CDB to the drive and (usually) works the 2nd time -- you wouldn't notice it in most cases (or if you did, it would be a brief 1 second stall or so). A drive which experiences a few CRC errors over the course of a year is perfectly reasonable/fine, and most drives don't experience any during their lifetime. However, a drive with a rapidly incrementing CRC error count indicates something bad going on, and thus replacing cables + moving SATA ports is the best choice (and if they do not solve the problem, replace the drive or its PCB). CRC errors are significantly more common with eSATA-based devices, for a lot of reasons which I'd rather not go into.
--
Making life hard for others since 1977.
I speak for myself and not my employer/affiliates of my employer. | | |
|
Reviews:
·Shaw
| lol. I won't look at those rates again for the raw read error rate. I had to just clarify what my concern was initially....you set me straight
The person i was referring to posted on some other site, i can't recall which one but it wasn't here. he wrote about the SATA cables touching each other and being very close to one another. he felt that was the cause (in his case). After he rearranged the cables, he had no no futher increase in numbers. Obviously, that was a coincidence. Once again, thanks for checking my numbers for me. Have yourself a great weekend. | |
koitsuPremium,MVM
join:2002-07-16
Mountain View, CA
kudos:20 | Cables touching isn't the cause of that bloke's issue; chances are one of his cables is shoddy (so simply by readjusting the cables, diminishing stress on some areas, etc. he worked around the issue), one of his SATA ports is loose/has dust in it, a connector was slightly loose/ajar (common with SATA), or the drive PCB had one of these problems. All of these would manifest themselves as CRC errors (UDMA_CRC_Error_Count), not Raw_Read_Error_Rate.
Sadly most of the information on the Internet you'll read about SMART or even general "PC troubleshooting" comes from "enthusiasts" who really aren't engineers, just customers with lots of money, and know how to assemble a PC. There's a world of difference between the two types.
Glad I could help, and hope your weekend goes well (went well?) too!
--
Making life hard for others since 1977.
I speak for myself and not my employer/affiliates of my employer. | |
|
