Read Errors on USB Drive

[Shawn Badger]

Put the drive in a freezer

On Sun, Dec 20, 2015 at 10:46 PM, Mark Phillips <mark at phillipsmarketing.biz>
wrote:

> I think you mean ddrescue? I have been running it for a few days and
> getting lots of errors.
>
> GNU ddrescue 1.17
> Press Ctrl-C to interrupt
> rescued:   328577 MB,  errsize:  85901 MB,  current rate:   12047 kB/s
>    ipos:   414478 MB,   errors:     321,    average rate:    6771 kB/s
>    opos:   414478 MB,    time since last successful read:       0 s
> Copying non-tried blocks...
>
> Any suggestions on how to cool the usb drive with the errors. I have it
> flat on a cold large faux granite desk surface which is very cold to the
> touch. But the drive is still very warm.
>
> Thanks!
>
> Mark
>
> On Sun, Dec 20, 2015 at 6:48 PM, George Toft <george at georgetoft.com>
> wrote:
>
>> There is a special version of dd that will retry on bad sectors and try
>> to formulate a best guess for the bad sector.  I've used it with some
>> success - took about 2 weeks to recover a 300GB drive.  I also had to keep
>> it refrigerated.
>>
>> Regards,
>>
>> George Toft
>>
>> On 12/19/2015 9:32 AM, Stephen Partington wrote:
>>
>> There is an application called test disk that might be handy for data
>> recovery. But this looks like your drive is in bad shape.
>> On Dec 19, 2015 9:25 AM, "Mark Phillips" <mark at phillipsmarketing.biz>
>> wrote:
>>
>>> I have a 2 TB WD USB drive that I formated with NTFS. I have a rather
>>> extensive movie/TV library on it for my plex media server, and I am getting
>>> read errors. I hope I haven't lost all of that data! It has been attached
>>> to one of my Netgear wireless access points, hence the need for NTFS.
>>>
>>> fdisk -l gives for the drive
>>> /dev/sdc1            2048  3906963455  1953480704    7  HPFS/NTFS/exFAT
>>>
>>> I tried running smartctl on the device, (which is now plugged into a usb
>>> 3.0 port on my laptop) and got this error after a few tests
>>>
>>> SMART Self-test log structure revision number 1
>>> Num  Test_Description    Status                  Remaining
>>> LifeTime(hours)  LBA_of_first_error
>>> # 1  Short offline       Completed: read failure       90%
>>> 10086         494859396
>>> # 2  Extended offline    Completed: read failure       90%
>>> 10073         494859396
>>> # 3  Extended offline    Completed: read failure       90%
>>> 10072         494859396
>>> # 4  Short offline       Completed: read failure       90%
>>> 10072         494859396
>>>
>>> I noticed this in the attributes section of smartctl -
>>> 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       -       122
>>>   3 Spin_Up_Time            0x0027   202   200   021    Pre-fail
>>> Always       -       4891
>>>   4 Start_Stop_Count        0x0032   100   100   000    Old_age
>>> Always       -       464
>>>   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   087   087   000    Old_age
>>> Always       -       10086
>>>  10 Spin_Retry_Count        0x0032   100   100   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       -       40
>>> 192 Power-Off_Retract_Count 0x0032   200   200   000    Old_age
>>> Always       -       17
>>> 193 Load_Cycle_Count        0x0032   198   198   000    Old_age
>>> Always       -       6187
>>> 194 Temperature_Celsius     0x0022   121   102   000    Old_age
>>> Always       -       31
>>> 196 Reallocated_Event_Count 0x0032   200   200   000    Old_age
>>> Always       -       0
>>> 197 Current_Pending_Sector  0x0032   200   200   000    Old_age
>>> Always       -       31
>>> 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
>>>
>>> Any thoughts on how I can fix this drive, or do I need to get a new one?
>>> What is the best way to copy the contents of the drive with these errors to
>>> a new drive?
>>>
>>> Thanks!
>>>
>>> Mark
>>>
>>> ---------------------------------------------------
>>> PLUG-discuss mailing list - PLUG-discuss at lists.phxlinux.org
>>> To subscribe, unsubscribe, or to change your mail settings:
>>> http://lists.phxlinux.org/mailman/listinfo/plug-discuss
>>>
>>
>>
>> ---------------------------------------------------
>> PLUG-discuss mailing list - PLUG-discuss at lists.phxlinux.org
>> To subscribe, unsubscribe, or to change your mail settings:http://lists.phxlinux.org/mailman/listinfo/plug-discuss
>>
>>
>>
>> ---------------------------------------------------
>> PLUG-discuss mailing list - PLUG-discuss at lists.phxlinux.org
>> To subscribe, unsubscribe, or to change your mail settings:
>> http://lists.phxlinux.org/mailman/listinfo/plug-discuss
>>
>
>
> ---------------------------------------------------
> PLUG-discuss mailing list - PLUG-discuss at lists.phxlinux.org
> To subscribe, unsubscribe, or to change your mail settings:
> http://lists.phxlinux.org/mailman/listinfo/plug-discuss
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.phxlinux.org/pipermail/plug-discuss/attachments/20151221/b55e90c1/attachment.html>