Jump to content


 


Register a free account to unlock additional features at BleepingComputer.com
Welcome to BleepingComputer, a free community where people like yourself come together to discuss and learn how to use their computers. Using the site is easy and fun. As a guest, you can browse and view the various discussions in the forums, but can not create a new topic or reply to an existing one unless you are logged in. Other benefits of registering an account are subscribing to topics and forums, creating a blog, and having no ads shown anywhere on the site.


Click here to Register a free account now! or read our Welcome Guide to learn how to use this site.

Photo

Recovering data from external hard drive using Parted Magic


  • Please log in to reply
9 replies to this topic

#1 Samuel Farid

Samuel Farid

  • Members
  • 5 posts
  • OFFLINE
  •  
  • Local time:09:17 AM

Posted 25 August 2014 - 02:16 PM

Hi!

 

I hava a 1TB WD My Passport and it was working fine, but one day it gave me an error: "Data error (cyclic redundancy check)" and sometimes " Parameter is incorrect" on both Windows XP and Windows 8.1 PCs. I have read an article on the internet about using Parted Magic which is a Linux kernel: html5.litten.com/how-to-fix-external-disk-drive-suddenly-became-raw/

But on doing deep scan it takes alot of time and read error at almost each cylinder as following:

TestDisk 6.14, Data Recovery Utility, July 2013
Christophe GRENIER <grenier@cgsecurity.org>
http://www.cgsecurity.org

Disk /dev/sdb - 1000 GB / 931 GiB - CHS 121597 255 63
Analyse cylinder    63/121596: 00%
Read error at 62/254/63 (lba=1012094)

  HPFS - NTFS              0  32 33 121597  37 40 1953456128













  Stop  

What can I do? Shall I wait or that will be in vain? Is there any other way to recover data?

 

Thanks!

Samuel

 

P.S.

When I try to mount my portable hard drive it gives me this error: "udevil: error 64: unable to determine device fstype - specify with -t"

 

Edit:

 

It is now finished and gives the following:

Christophe GRENIER <grenier@cgsecurity.org>
http://www.cgsecurity.org

Disk /dev/sdb - 1000 GB / 931 GiB - CHS 121597 255 63

     Partition                  Start        End    Size in sectors

 1 * HPFS - NTFS              0  32 33 121597  37 40 1953456128
























>[  Quit  ]  [ Write  ]
                              Return to main menu

But I think it is supposed that it will view another partition.


Edited by Samuel Farid, 25 August 2014 - 02:34 PM.


BC AdBot (Login to Remove)

 


#2 JohnC_21

JohnC_21

  • Members
  • 22,926 posts
  • OFFLINE
  •  
  • Gender:Male
  • Local time:04:17 AM

Posted 25 August 2014 - 02:21 PM

Hello, and Welcome

 

Constant read errors are not good. The drive may have totally failed.

 

On Parted Magic's desktop is an icon called Disk Health. Run that to determine if the drive is in a failed state. You can run the short test and post the results.



#3 Samuel Farid

Samuel Farid
  • Topic Starter

  • Members
  • 5 posts
  • OFFLINE
  •  
  • Local time:09:17 AM

Posted 25 August 2014 - 02:32 PM

Hello, and Welcome

 

Constant read errors are not good. The drive may have totally failed.

 

On Parted Magic's desktop is an icon called Disk Health. Run that to determine if the drive is in a failed state. You can run the short test and post the results.

It gave me the following on running short test::

 

smartctl 5.43 2012-06-30 r3573 [i686-linux-3.10.4-pmagic] (local build)
Copyright © 2002-12 by Bruce Allen, http://smartmontools.sourceforge.net

=== START OF INFORMATION SECTION ===
Device Model:     WDC WD10JMVW-11S5XS0
Serial Number:    "I have removed it"
LU WWN Device Id: 5 0014ee 2077fb430
Firmware Version: 01.01A01
User Capacity:    1,000,204,886,016 bytes [1.00 TB]
Sector Sizes:     512 bytes logical, 4096 bytes physical
Device is:        Not in smartctl database [for details use: -P showall]
ATA Version is:   8
ATA Standard is:  Exact ATA specification draft version not indicated
Local Time is:    Mon Aug 25 22:36:01 2014 UTC
SMART support is: Available - device has SMART capability.
SMART support is: Enabled

=== START OF READ SMART DATA SECTION ===
SMART STATUS RETURN: incomplete response, ATA output registers missing
SMART overall-health self-assessment test result: FAILED!
Drive failure expected in less than 24 hours. SAVE ALL DATA.
See vendor-specific Attribute list for failed Attributes.

General SMART Values:
Offline data collection status:  (0x00)    Offline data collection activity
                    was never started.
                    Auto Offline Data Collection: Disabled.
Self-test execution status:      (  73)    The previous self-test completed having
                    a test element that failed and the test
                    element that failed is not known.
Total time to complete Offline
data collection:         (17400) seconds.
Offline data collection
capabilities:              (0x7b) SMART execute Offline immediate.
                    Auto Offline data collection on/off support.
                    Suspend Offline collection upon new
                    command.
                    Offline surface scan supported.
                    Self-test supported.
                    Conveyance Self-test supported.
                    Selective Self-test supported.
SMART capabilities:            (0x0003)    Saves SMART data before entering
                    power-saving mode.
                    Supports SMART auto save timer.
Error logging capability:        (0x01)    Error logging supported.
                    General Purpose Logging supported.
Short self-test routine
recommended polling time:      (   2) minutes.
Extended self-test routine
recommended polling time:      ( 189) minutes.
Conveyance self-test routine
recommended polling time:      (   5) minutes.
SCT capabilities:            (0x70b5)    SCT Status supported.
                    SCT Feature Control supported.
                    SCT Data Table supported.

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   001   001   051    Pre-fail  Always   FAILING_NOW 20202
  3 Spin_Up_Time            0x0027   186   178   021    Pre-fail  Always       -       1675
  4 Start_Stop_Count        0x0032   100   100   000    Old_age   Always       -       130
  5 Reallocated_Sector_Ct   0x0033   200   200   140    Pre-fail  Always       -       0
  7 Seek_Error_Rate         0x002e   200   179   000    Old_age   Always       -       260
  9 Power_On_Hours          0x0032   100   100   000    Old_age   Always       -       124
 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   100   100   000    Old_age   Always       -       110
192 Power-Off_Retract_Count 0x0032   200   200   000    Old_age   Always       -       58
193 Load_Cycle_Count        0x0032   200   200   000    Old_age   Always       -       1552
194 Temperature_Celsius     0x0022   098   092   000    Old_age   Always       -       49
196 Reallocated_Event_Count 0x0032   200   200   000    Old_age   Always       -       0
197 Current_Pending_Sector  0x0032   182   182   000    Old_age   Always       -       3027
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

SMART Error Log Version: 1
ATA Error Count: 564 (device log contains only the most recent five errors)
    CR = Command Register [HEX]
    FR = Features Register [HEX]
    SC = Sector Count Register [HEX]
    SN = Sector Number Register [HEX]
    CL = Cylinder Low Register [HEX]
    CH = Cylinder High Register [HEX]
    DH = Device/Head Register [HEX]
    DC = Device Command Register [HEX]
    ER = Error register [HEX]
    ST = Status register [HEX]
Powered_Up_Time is measured from power on, and printed as
DDd+hh:mm:SS.sss where DD=days, hh=hours, mm=minutes,
SS=sec, and sss=millisec. It "wraps" after 49.710 days.

Error 564 occurred at disk power-on lifetime: 110 hours (4 days + 14 hours)
  When the command that caused the error occurred, the device was active or idle.

  After command completion occurred, registers were:
  ER ST SC SN CL CH DH
  -- -- -- -- -- -- --
  04 61 02 00 00 00 00

  Commands leading to the command that caused the error were:
  CR FR SC SN CL CH DH DC   Powered_Up_Time  Command/Feature_Name
  -- -- -- -- -- -- -- --  ----------------  --------------------
  e1 00 02 00 00 00 00 00      06:55:21.791  IDLE IMMEDIATE
  ec 00 01 00 00 00 00 00      06:55:21.763  IDENTIFY DEVICE

Error 563 occurred at disk power-on lifetime: 110 hours (4 days + 14 hours)
  When the command that caused the error occurred, the device was active or idle.

  After command completion occurred, registers were:
  ER ST SC SN CL CH DH
  -- -- -- -- -- -- --
  04 61 02 00 00 00 00

  Commands leading to the command that caused the error were:
  CR FR SC SN CL CH DH DC   Powered_Up_Time  Command/Feature_Name
  -- -- -- -- -- -- -- --  ----------------  --------------------
  e1 00 02 00 00 00 00 00      06:55:00.736  IDLE IMMEDIATE
  ec 00 01 00 00 00 00 00      06:55:00.735  IDENTIFY DEVICE

Error 562 occurred at disk power-on lifetime: 110 hours (4 days + 14 hours)
  When the command that caused the error occurred, the device was active or idle.

  After command completion occurred, registers were:
  ER ST SC SN CL CH DH
  -- -- -- -- -- -- --
  04 61 02 00 00 00 00

  Commands leading to the command that caused the error were:
  CR FR SC SN CL CH DH DC   Powered_Up_Time  Command/Feature_Name
  -- -- -- -- -- -- -- --  ----------------  --------------------
  e1 00 02 00 00 00 00 00      06:54:39.757  IDLE IMMEDIATE
  ec 00 01 00 00 00 00 00      06:54:39.756  IDENTIFY DEVICE

Error 561 occurred at disk power-on lifetime: 110 hours (4 days + 14 hours)
  When the command that caused the error occurred, the device was active or idle.

  After command completion occurred, registers were:
  ER ST SC SN CL CH DH
  -- -- -- -- -- -- --
  04 61 02 00 00 00 00

  Commands leading to the command that caused the error were:
  CR FR SC SN CL CH DH DC   Powered_Up_Time  Command/Feature_Name
  -- -- -- -- -- -- -- --  ----------------  --------------------
  e1 00 02 00 00 00 00 00      06:54:18.745  IDLE IMMEDIATE
  ec 00 01 00 00 00 00 00      06:54:18.744  IDENTIFY DEVICE

Error 560 occurred at disk power-on lifetime: 110 hours (4 days + 14 hours)
  When the command that caused the error occurred, the device was active or idle.

  After command completion occurred, registers were:
  ER ST SC SN CL CH DH
  -- -- -- -- -- -- --
  04 61 02 00 00 00 00

  Commands leading to the command that caused the error were:
  CR FR SC SN CL CH DH DC   Powered_Up_Time  Command/Feature_Name
  -- -- -- -- -- -- -- --  ----------------  --------------------
  e1 00 02 00 00 00 00 00      06:53:57.722  IDLE IMMEDIATE
  ec 00 01 00 00 00 00 00      06:53:57.721  IDENTIFY DEVICE

SMART Self-test log structure revision number 1
Num  Test_Description    Status                  Remaining  LifeTime(hours)  LBA_of_first_error
# 1  Short offline       Completed: unknown failure    90%       124         -
# 2  Conveyance offline  Completed: read failure       90%        88         934292
# 3  Conveyance offline  Completed: read failure       90%        88         934288
# 4  Extended offline    Interrupted (host reset)      90%        77         -
# 5  Short offline       Interrupted (host reset)      90%        77         -
# 6  Extended offline    Aborted by host               90%        42         -
# 7  Short offline       Completed without error       00%        42         -

SMART Selective self-test log data structure revision number 1
 SPAN  MIN_LBA  MAX_LBA  CURRENT_TEST_STATUS
    1        0        0  Not_testing
    2        0        0  Not_testing
    3        0        0  Not_testing
    4        0        0  Not_testing
    5        0        0  Not_testing
Selective self-test flags (0x0):
  After scanning selected spans, do NOT read-scan remainder of disk.
If Selective self-test is pending on power-up, resume after 0 minute delay.


Edited by Samuel Farid, 25 August 2014 - 02:38 PM.


#4 JohnC_21

JohnC_21

  • Members
  • 22,926 posts
  • OFFLINE
  •  
  • Gender:Male
  • Local time:04:17 AM

Posted 25 August 2014 - 02:41 PM

That is not good as the software cannot read the drive attributes any longer. Seatools for DOS is another diagnostic software that may pick up the drive. You have to burn the iso to create a bootable disk. Seatools for Windows is also available

 

http://www.seagate.com/support/downloads/item/seatools-dos-master/

 

http://www.seagate.com/support/downloads/item/seatools-win-master/

 

It's possible the bridge card on the drive failed but WD uses a propretary interface. The usb port is soldered to the bridge card so you cannot take apart the passport and put the drive in another enclosure.



#5 Samuel Farid

Samuel Farid
  • Topic Starter

  • Members
  • 5 posts
  • OFFLINE
  •  
  • Local time:09:17 AM

Posted 25 August 2014 - 02:45 PM

That is not good as the software cannot read the drive attributes any longer. Seatools for DOS is another diagnostic software that may pick up the drive. You have to burn the iso to create a bootable disk. Seatools for Windows is also available

 

http://www.seagate.com/support/downloads/item/seatools-dos-master/

 

http://www.seagate.com/support/downloads/item/seatools-win-master/

 

It's possible the bridge card on the drive failed but WD uses a propretary interface. The usb port is soldered to the bridge card so you cannot take apart the passport and put the drive in another enclosure.

OK, I will try it and give you feedback.

Many thanks for help.



#6 JohnC_21

JohnC_21

  • Members
  • 22,926 posts
  • OFFLINE
  •  
  • Gender:Male
  • Local time:04:17 AM

Posted 25 August 2014 - 03:03 PM

I did not see your edited post. The drive is failing now. The only option I believe to get your data back is to use a professional recovery service which is very expensive.



#7 Samuel Farid

Samuel Farid
  • Topic Starter

  • Members
  • 5 posts
  • OFFLINE
  •  
  • Local time:09:17 AM

Posted 25 August 2014 - 03:49 PM

I did not see your edited post. The drive is failing now. The only option I believe to get your data back is to use a professional recovery service which is very expensive.

Isn't there any other option? I am a home user not a company and it will be very expensive.



#8 JohnC_21

JohnC_21

  • Members
  • 22,926 posts
  • OFFLINE
  •  
  • Gender:Male
  • Local time:04:17 AM

Posted 25 August 2014 - 06:29 PM

I did find this.

 

RAW_READ_ERROR_RATE and UDMA_CRC_Error_Count are usually a sign of a bad cable or SATA controller/port

 

 

Have you tried a different cable. Also plug the drive into a different port. If the bridge card is bad, then it's possible WD could repair it for a reasonable cost but I can't be sure about that. But, this attribute differs between drive manufacturers.

 

 
1 Raw_Read_Error_Rate
  • This is an indicator of the current rate of errors of the low level physical sector read operations. In normal operation, there are ALWAYS a small number of errors when attempting to read sectors, but as long as the number remains small, there is NO issue with the drive. Error correction information and retry mechanisms are in place to catch and fix these errors. Manufacturers therefore determine an optimal level of errors for each drive model, and set up an appropriate scale for monitoring the current error rate. For example, if 3 errors per 1000 read operations seems near perfect to the manufacturer, then an error rate of 3 per 1000 ops might be set to an attribute VALUE of 100. If the rate increased to 10 per 1000, then the rate might be scaled to 80 (completely under manufacturer control, and NEVER revealed or explained to us!).
  • They are called Raw Reads to distinguish them from the more common term 'read errors', which represent a much higher level read operation. What we usually refer to as a 'read error' is an error returned by a read process, that has attempted a series of one or more seeks and raw reads, plus optional error corrections and retries. It either returns an indicator of total success plus the sector data (considered to be in perfect shape), or it returns an error code, and no sector data.
  • PLEASE completely ignore the RAW_VALUE number! Only Seagates report the raw value, which yes, does appear to be the number of raw read errors, but should be ignored, completely. All other drives have raw read errors too, but do not report them, leaving this value as zero only. To repeat, Seagates are not worse than other drives because they appear to have raw read errors, rather they are the only one to report the number. I suspect that others do not report the number to avoid a lot of confusion, and questions for their tech support people. Seagate leaves those of us who provide tech support the job of answering the constant questions about this number. Hopefully now that you understand this, you will never bother a kind IT person with questions about the Raw_Read_Error_Rate RAW_VALUE again?
  • [incomplete?]
  • Critical attribute - if its WORST falls below its THRESH, then the drive will be considered FAILED

 

 

If you want contiue with the recovry, Downloar Easeus Data Recovery. It will scan the drive and recover up to 1GB for free. If you can recover your files, you have the option to pay to retrieve the rest of your data.

 

Your pending sector count  is zero and so is the reallocated sector count. This may be good news. The only question mark is the proprietary board that WD uses on the drive.



#9 Samuel Farid

Samuel Farid
  • Topic Starter

  • Members
  • 5 posts
  • OFFLINE
  •  
  • Local time:09:17 AM

Posted 26 August 2014 - 05:52 AM

I did find this.

 

RAW_READ_ERROR_RATE and UDMA_CRC_Error_Count are usually a sign of a bad cable or SATA controller/port

 

 

Have you tried a different cable. Also plug the drive into a different port. If the bridge card is bad, then it's possible WD could repair it for a reasonable cost but I can't be sure about that. But, this attribute differs between drive manufacturers.

 

 
1 Raw_Read_Error_Rate
  • This is an indicator of the current rate of errors of the low level physical sector read operations. In normal operation, there are ALWAYS a small number of errors when attempting to read sectors, but as long as the number remains small, there is NO issue with the drive. Error correction information and retry mechanisms are in place to catch and fix these errors. Manufacturers therefore determine an optimal level of errors for each drive model, and set up an appropriate scale for monitoring the current error rate. For example, if 3 errors per 1000 read operations seems near perfect to the manufacturer, then an error rate of 3 per 1000 ops might be set to an attribute VALUE of 100. If the rate increased to 10 per 1000, then the rate might be scaled to 80 (completely under manufacturer control, and NEVER revealed or explained to us!).
  • They are called Raw Reads to distinguish them from the more common term 'read errors', which represent a much higher level read operation. What we usually refer to as a 'read error' is an error returned by a read process, that has attempted a series of one or more seeks and raw reads, plus optional error corrections and retries. It either returns an indicator of total success plus the sector data (considered to be in perfect shape), or it returns an error code, and no sector data.
  • PLEASE completely ignore the RAW_VALUE number! Only Seagates report the raw value, which yes, does appear to be the number of raw read errors, but should be ignored, completely. All other drives have raw read errors too, but do not report them, leaving this value as zero only. To repeat, Seagates are not worse than other drives because they appear to have raw read errors, rather they are the only one to report the number. I suspect that others do not report the number to avoid a lot of confusion, and questions for their tech support people. Seagate leaves those of us who provide tech support the job of answering the constant questions about this number. Hopefully now that you understand this, you will never bother a kind IT person with questions about the Raw_Read_Error_Rate RAW_VALUE again?
  • [incomplete?]
  • Critical attribute - if its WORST falls below its THRESH, then the drive will be considered FAILED

 

 

If you want contiue with the recovry, Downloar Easeus Data Recovery. It will scan the drive and recover up to 1GB for free. If you can recover your files, you have the option to pay to retrieve the rest of your data.

 

Your pending sector count  is zero and so is the reallocated sector count. This may be good news. The only question mark is the proprietary board that WD uses on the drive.

I have tried many recovery software but it takes endless time and didn't recover much data. I think that I will have to get hardware support. Do you think that in my case with all of these problems and bad sectors, can I recover my data through recovery software ?

Thanks!



#10 JohnC_21

JohnC_21

  • Members
  • 22,926 posts
  • OFFLINE
  •  
  • Gender:Male
  • Local time:04:17 AM

Posted 26 August 2014 - 06:24 AM

I do not think you will be able to recover the data using Recovery Software. Your only option now is to recover using a professional data recovery service.




0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users