Hi fellow ALUGgers,
Started getting fsck errors on a drive, ran smartctl -t long and smartctl -a.
Full output: http://pastebin.com/tQX0TX4m
Snipped output:
=== START OF INFORMATION SECTION === Model Family: Western Digital Caviar Green Device Model: WDC WD10EACS-11FBRB0
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.
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 0x002f 198 198 051 Pre-fail Always - 101 3 Spin_Up_Time 0x0027 123 114 021 Pre-fail Always - 6850 4 Start_Stop_Count 0x0032 099 099 000 Old_age Always - 1022 5 Reallocated_Sector_Ct 0x0033 200 200 140 Pre-fail Always - 1 7 Seek_Error_Rate 0x002e 200 200 000 Old_age Always - 0 9 Power_On_Hours 0x0032 089 089 000 Old_age Always - 8569 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 099 099 000 Old_age Always - 1000 192 Power-Off_Retract_Count 0x0032 200 200 000 Old_age Always - 53 193 Load_Cycle_Count 0x0032 180 180 000 Old_age Always - 60861 194 Temperature_Celsius 0x0022 130 102 000 Old_age Always - 17 196 Reallocated_Event_Count 0x0032 199 199 000 Old_age Always - 1 197 Current_Pending_Sector 0x0032 198 198 000 Old_age Always - 355 198 Offline_Uncorrectable 0x0030 199 199 000 Old_age Offline - 170 199 UDMA_CRC_Error_Count 0x0032 200 200 000 Old_age Always - 0 200 Multi_Zone_Error_Rate 0x0008 199 199 000 Old_age Offline - 260
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 Extended offline Completed: read failure 90% 8563 323143936 # 2 Extended offline Completed: read failure 90% 8560 323143936 # 3 Extended offline Completed without error 00% 8303 - # 4 Extended offline Completed without error 00% 732 -
Is the drive cooked?
Why does the self test execution status report all is ok? Why does offline data collection status report without error? Why is the overall status PASSED?
Thanks, Srdjan
On 22/10/14 18:24, Srdjan Todorovic wrote:
Hi fellow ALUGgers,
Started getting fsck errors on a drive, ran smartctl -t long and smartctl -a.
[SNIP]
Is the drive cooked?
I don't know - sorry.
Why does the self test execution status report all is ok? Why does offline data collection status report without error? Why is the overall status PASSED?
I'm not entirely sure about this, but is this because SMART tools and fsck are not necessarily testing the same thing?
fsck is checking the integrity of the file system. SMART reports any hardware errors and information on the disk. Hardware errors will probably result in errors in the file system, but errors in the file system are not necessarily caused by hardware errors. Is it possible that a machine suffers a power outage in mid-write could end with file system corruption.
Whatever, if funds allow, if in doubt, replace it. At the very least, back it all up.
Good luck. Steve
Some of the stats look a bit suspect, Unless you have your room very cold :) 17C sounds very low.
If the last two long tests failed then that's an internal firmware test and if it fails it isn't due to any smartmontools incompatibility..if the test fails the drive is toast and that result alone is enough to get it RMA'ed if it is still under warranty.
Also if any of the following stats are telling the truth
197 Current_Pending_Sector 0x0032 198 198 000 Old_age Always - 355 198 Offline_Uncorrectable 0x0030 199 199 000 Old_age Offline - 170 5 Reallocated_Sector_Ct 0x0033 200 200 140 Pre-fail Always - 1
Then the drive is dying. Overall Smart health is a pretty high threshold it usually only trips just before the drive dies completely in my experience.
I think the stats above mean something like:-
The offline uncorrectable errors mean that checksums were shot as well so the sectors couldn't be recovered and reallocated to the spare space.
Either way you have lost data there which explains the fsck results.
My rule is that if the first two stats there are showing counts higher than 0 then I need to ditch the drive asap. I have tolerated a low count on the reallocated sectors before but only if it isn't moving, and generally I would have a bit less faith in the drive.
Your load cycle count is also pretty high (though well within manufacturer life predictions to the data sheet) This was a problem for the WD green drives. load cycle is the number of times the heads do a takeoff from the "landing strip" on the drive surface and it happens during spin up..so divided by the number of operating hours that is too many spin ups which can result in the drive wearing out much faster.
On 22 October 2014 23:53, Wayne Stallwood ALUGlist@digimatic.co.uk wrote:
Some of the stats look a bit suspect, Unless you have your room very cold :) 17C sounds very low.
Yes well... It was cold outside, I had the windows open all day, heating was not on while I was at work, case side panels were removed, there's a 20cm fan blowing air onto the drive and system uptime was about 3 minutes :) I'm pretty sure I've seen it in the mid 20 degrees range before.
If the last two long tests failed then that's an internal firmware test and if it fails it isn't due to any smartmontools incompatibility..if the test fails the drive is toast and that result alone is enough to get it RMA'ed if it is still under warranty.
Sadly I don't think it's in warranty. I'll check the manufacture dates on the drive. Also sadly that drive may have come from one of those external WD Elements retail products, and I removed the drive and put in the desktop. I doubt that it would be covered by warranty in that situation.
Also if any of the following stats are telling the truth
197 Current_Pending_Sector 0x0032 198 198 000 Old_age Always
355198 Offline_Uncorrectable 0x0030 199 199 000 Old_age Offline
1701Then the drive is dying. Overall Smart health is a pretty high threshold it usually only trips just before the drive dies completely in my experience.
Ah, I had no idea it operated like that. I thought as soon as one of the values was bad it would report an overall status of "WARNING" or similar, instead of FAIL or PASSED.
I think the stats above mean something like:-
The offline uncorrectable errors mean that checksums were shot as well so the sectors couldn't be recovered and reallocated to the spare space.
So that's 170 sectors of 512 bytes of lost data? I had a peek in lost+found/ using sudo sunglasses, but saw nothing.
Either way you have lost data there which explains the fsck results.
I think all the fsck errors were regarding ext4 group blocks. I don't know what the implications are for file loss though. Never mentioned inodes having errors.
My rule is that if the first two stats there are showing counts higher than 0 then I need to ditch the drive asap. I have tolerated a low count on the reallocated sectors before but only if it isn't moving, and generally I would have a bit less faith in the drive.
Thanks for the advice - I'll keep an eye on this in the future. Do you also have some sort of periodic smart monitoring setup so that it alerts you if the drive's going bad?
Your load cycle count is also pretty high (though well within manufacturer life predictions to the data sheet) This was a problem for the WD green drives. load cycle is the number of times the heads do a takeoff from the "landing strip" on the drive surface and it happens during spin up..so divided by the number of operating hours that is too many spin ups which can result in the drive wearing out much faster.
Yeah... I'm farly sure I ran the special tool idle3-tools to lower the frequency of the head park. I've got a replacement drive, and that's also a WD Green, so I'll make sure I run the idle3-tools on it and record values somewhere safe (including smartctl output for it).
Thanks! Srdjan
-
Srdjan Todorovic -
steve-ALUG＠hst.me.uk -
Wayne Stallwood