[mythtv-users] Hard Drive Problems
David Brieck Jr.
dbrieck at gmail.com
Tue May 1 14:18:37 UTC 2012
On Tue, May 1, 2012 at 9:54 AM, John Drescher <drescherjm at gmail.com> wrote:
>> Thanks for the response John.
>>
>> I've checked the SMART data infrequently so I don't have a real point
>> of reference for when it could have started showing signs of a
>> problem. This isn't the first time I've lost drives on myth dedicated
>> systems in the past, but it's the first time two seem to be showing
>> problems at once.
>>
>> The only other drive I've ever lost that was still under warranty was
>> an IBM DeathStar.
>>
>
> At work where I have 200 to 300 drives, I ship back 10 to 20 annually
> for the last 3 to 4 years. Most of these are by a single manufacturer.
>
>>
>> Here's the SMART data for the drive you're thinking has file system corruption:
>>
>> ID# ATTRIBUTE_NAME FLAG VALUE WORST THRESH TYPE
>> UPDATED WHEN_FAILED RAW_VALUE
>> 1 Raw_Read_Error_Rate 0x000f 200 200 051 Pre-fail
>> Always - 601
>> 3 Spin_Up_Time 0x0003 180 180 021 Pre-fail
>> Always - 7991
>> 4 Start_Stop_Count 0x0032 100 100 000 Old_age
>> Always - 76
>> 5 Reallocated_Sector_Ct 0x0033 200 200 140 Pre-fail
>> Always - 0
>> 7 Seek_Error_Rate 0x000e 200 200 051 Old_age
>> Always - 0
>> 9 Power_On_Hours 0x0032 048 048 000 Old_age
>> Always - 38625
>> 10 Spin_Retry_Count 0x0012 100 253 051 Old_age
>> Always - 0
>> 11 Calibration_Retry_Count 0x0012 100 253 051 Old_age
>> Always - 0
>> 12 Power_Cycle_Count 0x0032 100 100 000 Old_age
>> Always - 74
>> 192 Power-Off_Retract_Count 0x0032 200 200 000 Old_age
>> Always - 101
>> 193 Load_Cycle_Count 0x0032 001 001 000 Old_age
>> Always - 649774
>> 194 Temperature_Celsius 0x0022 119 099 000 Old_age
>> Always - 33
>> 196 Reallocated_Event_Count 0x0032 200 200 000 Old_age
>> Always - 0
>> 197 Current_Pending_Sector 0x0012 200 200 000 Old_age
>> Always - 0
>> 198 Offline_Uncorrectable 0x0010 200 200 000 Old_age
>> Offline - 0
>> 199 UDMA_CRC_Error_Count 0x003e 200 200 000 Old_age
>> Always - 0
>> 200 Multi_Zone_Error_Rate 0x0008 200 200 051 Old_age
>> Offline - 19
>>
>> I'm tempted to try the ddrescue command, but the SMART data isn't
>> showing any bad sectors.
>
> I agree the SMART looks fine on this one. I would try what you said.
>
> --
> John M. Drescher
How does this sound... The drive with the questionable SMART data also
happened to be the main OS drive. I'm thinking maybe with that drive
going bad it caused some FS corruption on the other drive as it was
writing data from NFS coming from my slave system?
Seems pretty out there, but that's the best I can come up with the
explain what I'm seeing.
More information about the mythtv-users
mailing list