Re: understanding smart logs

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Robert Nichols wrote:
> On 08/15/2010 12:05 PM, Suvayu Ali wrote:
>   
>>> 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   199   199   051    Pre-fail  Always       -       1354
>>>    3 Spin_Up_Time            0x0027   253   253   021    Pre-fail  Always       -       1158
>>>    4 Start_Stop_Count        0x0032   100   100   000    Old_age   Always       -       40
>>>    5 Reallocated_Sector_Ct   0x0033   200   200   140    Pre-fail  Always       -       0
>>>    7 Seek_Error_Rate         0x002e   200   200   000    Old_age   Always       -       0
>>>    9 Power_On_Hours          0x0032   099   099   000    Old_age   Always       -       1403
>>>   10 Spin_Retry_Count        0x0032   100   253   000    Old_age   Always       -       0
>>>   11 Calibration_Retry_Count 0x0032   100   253   000    Old_age   Always       -       0
>>>   12 Power_Cycle_Count       0x0032   100   100   000    Old_age   Always       -       38
>>> 192 Power-Off_Retract_Count 0x0032   200   200   000    Old_age   Always       -       21
>>> 193 Load_Cycle_Count        0x0032   200   200   000    Old_age   Always       -       18
>>> 194 Temperature_Celsius     0x0022   112   107   000    Old_age   Always       -       38
>>> 196 Reallocated_Event_Count 0x0032   200   200   000    Old_age   Always       -       0
>>> 197 Current_Pending_Sector  0x0032   199   199   000    Old_age   Always       -       172
>>> 198 Offline_Uncorrectable   0x0030   200   200   000    Old_age   Offline      -       0
>>> 199 UDMA_CRC_Error_Count    0x0032   200   200   000    Old_age   Always       -       0
>>> 200 Multi_Zone_Error_Rate   0x0008   200   200   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  Extended offline    Completed: read failure       90%      1393         1106820646
>>>       
>
> Your problem is the 172 sectors pending reallocation.  Those are sectors
> that are currently unreadable and will be reallocated to spare sectors
> the next time they are written.  The problem is that the drive has no
> way to know whether the current contents are important (part of some
> file, or file system metadata) or irrelevant (part of file system free
> space), so the drive _must_ continue to return an error on any attempted
> read of those sectors.
>   

Bob:

With 'modern' drives you should NEVER see these errors.  This drive is a 
time-bomb waiting to explode data all over the place.  Get on the phone 
with WD and get these drives replaced immediately.  Don't waste your 
time working on them.  The old Hitachi/IBM 'Deathstars' would exhibit 
the same behavior shortly before they died.  As I said, now it the time 
not to hope you have a viable backup of your important data as you will 
be exercising it soon.

James McKenzie
(And yes, I've been there, done that with backup/restore of a 20 GB 
drive when it failed...)

-- 
users mailing list
users@xxxxxxxxxxxxxxxxxxxxxxx
To unsubscribe or change subscription options:
https://admin.fedoraproject.org/mailman/listinfo/users
Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines


[Index of Archives]     [Current Fedora Users]     [Fedora Desktop]     [Fedora SELinux]     [Yosemite News]     [Yosemite Photos]     [KDE Users]     [Fedora Tools]     [Fedora Docs]

  Powered by Linux