Re: Disk failure

[email protected]
Newsgroups gmane.linux.utilities.smartmontools
Message-ID <[email protected]>
As others have mentioned, you need to clear the 3 pending sectors. Since
you mentioned you want to clone the drive, I'll assume there is data you
care about on it. In which case, use hdparm to test, and likely, overwrite
the sectors.

To do so, first you have to figure out the sector number. The short test
gives you the [likely] first number: 673565131. So...
hdparm --read-sector 673565131 <drive; likely /dev/sda>

Can it read the sector? No? The overwrite it:
hdparm --write-sector 67356131 --yes-i-know-what-i-am-doing <drive; again
likely /dev/sda>

Now look at SMART again. Has the pending sectors changed? How about
reallocated?

Now re-run the short test. Do you get a different LBA number? Yes? Good.
Repeat above for the new error number.

Keep repeating until all the pending are gone. If something goes wrong,
write back.

> On Thursday, April 30, 2015, Tim Small wrote:
>> Briefly...
>>
>> Yes, I would clone the drive if you have a spare, use ddrescue or
>> similar to ignore read errors.
>
> I got an Icy Box docing station for 2 SATA disks that can be used to clone
> a disk.
> I will try to use that one first.
>
>> smart long self test will halt at the first unreadable sector, and you
>> already know that there are at least 3.
>
> Do I? :)
>
> I just completed a long test and got this:
>
> 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   200   200   051    Pre-fail  Always
>     -       956
>   3 Spin_Up_Time            0x0027   186   176   021    Pre-fail  Always
>     -       3675
>   4 Start_Stop_Count        0x0032   100   100   000    Old_age   Always
>     -       45
>   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   093   093   000    Old_age   Always
>     -       5548
>  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
>     -       43
> 192 Power-Off_Retract_Count 0x0032   200   200   000    Old_age   Always
>     -       34
> 193 Load_Cycle_Count        0x0032   200   200   000    Old_age   Always
>     -       10
> 194 Temperature_Celsius     0x0022   106   103   000    Old_age   Always
>     -       41
> 196 Reallocated_Event_Count 0x0032   200   200   000    Old_age   Always
>     -       0
> 197 Current_Pending_Sector  0x0032   200   200   000    Old_age   Always
>     -       3
> 198 Offline_Uncorrectable   0x0030   200   200   000    Old_age   Offline
>     -       1
> 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
>     -       56
>
> 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 without error       00%      5547
>   -
> # 2  Short offline       Completed: read failure       90%      5529
>   673565131
> 1 of 1 failed self-tests are outdated by newer successful extended offline
> self-test # 1
>
> Seems like the long test did not find anything wrong. That that mean it
> isn't that bad after all?
>
>> Pending means currently unreadable, and you must overwrite this sector
>> for that status to go away.
>>
>> You will want to ascertain which files (if any) "own" the unreadable
>> sectors, as they will have lost data.  If the sectors are contiguous on
>> disk, this is probably just one file, but best to find out which it is.
>>
>> hdparm will allow you to read/write individual sectors (you can use this
>> to check that the sector you think is unreadable really is before
>> zeroing it out - then check smartctl output to confirm that pending
>> count has decreased).
>>
>> If you can't find this on a wiki somewhere, then wiki it...
>>
>> Tim.
>
> Once again, thanks for the info.
>
> --
> Jørn Dahl-Stamnes
> homepage: http://www.dahl-stamnes.net/dahls/
>
> ------------------------------------------------------------------------------
> One dashboard for servers and applications across Physical-Virtual-Cloud
> Widest out-of-the-box monitoring support with 50+ applications
> Performance metrics, stats and reports that give you Actionable Insights
> Deep dive visibility with transaction tracing using APM Insight.
> http://ad.doubleclick.net/ddm/clk/290420510;117567292;y
> _______________________________________________
> Smartmontools-support mailing list
> [email protected]
> https://lists.sourceforge.net/lists/listinfo/smartmontools-support
>



------------------------------------------------------------------------------
One dashboard for servers and applications across Physical-Virtual-Cloud 
Widest out-of-the-box monitoring support with 50+ applications
Performance metrics, stats and reports that give you Actionable Insights
Deep dive visibility with transaction tracing using APM Insight.
http://ad.doubleclick.net/ddm/clk/290420510;117567292;y
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.