Damaged SATA Drive

[Frustrated]

I have a damaged SATA drive that Windows cannot read but can be read under Windows I need a software program that will transfer the data from the damaged drive to another under windows. Tried Spotmau but very slow, ubunta 6 cannot find the drives, only an external USB drive, suggestions please.

 

[Jory]

that Windows cannot read but can be read under Windows

You might want to try this again.

 

[Frustrated]

Thanks for your reply but what am I trying again?

 

[abe]

what do you mean cannot be read under windows but can be read under windows

 

[RonWood]

I believe that he is suggesting the hard drive will show up under My Computer and Disk Management but it can not be read from( open, explore, search, or otherwise extract data ).

You will need a software recovery program such as recuvra, R-studio, testdisk or any other popular recovery software if you wish to retrieve any data. Keep in mind if the drive is failing then it maybe very hard to save the data.

 

[Frustrated]

Windows XP cannot read the SATA disk as it is damaged. With an IDE drive in the same state I could use Linux, ubunta or Spotmau to transfer documents that needed to be saved to another drive. I would like a porgram that can find the SATA drives and will transfer any data in a non MS Windows environment quickly. This is going to become and ongoing problem with more SATA drives of bigger capacity being used.

 

[14049752]

Windows XP cannot read the SATA disk as it is damaged. With an IDE drive in the same state I could use Linux, ubunta or Spotmau to transfer documents that needed to be saved to another drive. I would like a porgram that can find the SATA drives and will transfer any data in a non MS Windows environment quickly. This is going to become and ongoing problem with more SATA drives of bigger capacity being used.

The only reason SATA comes into play is drivers in your Linux or recovery software not supporting the controller. An easy fix is to put the controller into IDE/Legacy/Compatible mode (whatever your bios calls it). Otherwise, you can make sure that your linux distro is up-to-date and has a variety of controllers built into the kernal. Unless it's in a disk-spanning raid set-up, you should be able to read the drive after doing one of the two options.
The other thing to consider is that the drive may simply be unreadable for some reason. Just because you can recover from one failed drive doesn't mean you can recover from all failed drives.