Hard Drive Recovery (yet another thread)

Rouxenator

Dank meme lord
Joined
Oct 31, 2007
Messages
46,376
Reaction score
22,389
Location
Stellenbosch
What is currently the best tools for this job?

Symptoms are a Seagate Barracuda 2TB LP that started having problems to boot into Windows. Had it in another machine but while copying data off it it stalled and now it is only detected as a RAW volume.

Last resort will be Southbit (due to the costs) but what tools can I use before that. Mechanically the drive sounds fine but when I took a peak at the SMART data it had a bad status, the reallocated sector count threshold was exceeded and there were a few pending sector reallocations listed.
 
What is currently the best tools for this job?

Symptoms are a Seagate Barracuda 2TB LP that started having problems to boot into Windows. Had it in another machine but while copying data off it it stalled and now it is only detected as a RAW volume.

Last resort will be Southbit (due to the costs) but what tools can I use before that. Mechanically the drive sounds fine but when I took a peak at the SMART data it had a bad status, the reallocated sector count threshold was exceeded and there were a few pending sector reallocations listed.

I quite like r-studio :)
 
R-studio looks nice, but its pricey, if we are talking of parting with money then it will be at Southbit.
 
My HDD recovery pattern.
Create a NTFS partition. Boot Hirens. Run HDD Regenerator. Boot into Windows. Run Get Data Back NTFS. Usually profit, if not call Southbit.
 
Wzup Roux? :)

If you're willing to gamble all your data, try to recover the partition with TestDisk.

But I don't do hardware, so don't come back to complain. :)
 
Depends how important your data is to you.. The more you try recover yourself the less chance of a specialized company has of retrieving your data.. I have seen this many times.. I suppose it boils down to how much is your data worth to you.
 
First step is to image a drive with gnu ddrescue. You NEVER work on a faulty/damaged drive, only an image of it.

Next step is to mount the imaged drive or file and use whatever utils to recover from the image. NEVER recover back to the original drive or image, select another drive or partition.
 
Some sound advise there...
First step is to image a drive with gnu ddrescue. You NEVER work on a faulty/damaged drive, only an image of it.

Next step is to mount the imaged drive or file and use whatever utils to recover from the image. NEVER recover back to the original drive or image, select another drive or partition.
 
Some sound advise there...

Got lots of experience :D

Currently doing a image of a 500GB drive (full of bad sectors) and it's been running since yesterday morning, will probably take another day or three I suspect.
 
Got lots of experience :D

Currently doing a image of a 500GB drive (full of bad sectors) and it's been running since yesterday morning, will probably take another day or three I suspect.

LOL, UPS, Aircon and air-movement all get verified before I even plug a damaged drive (in a board from an external drive) into the UPS+Laptop.
 
Got lots of experience :D

Currently doing a image of a 500GB drive (full of bad sectors) and it's been running since yesterday morning, will probably take another day or three I suspect.

I did an image of a failed lappy drive the other day for a work laptop. 3 Days later it finishes and the client says meh - don't worry about it,nothing they can't live without
 
I did an image of a failed lappy drive the other day for a work laptop. 3 Days later it finishes and the client says meh - don't worry about it,nothing they can't live without

My OCD would kick in and I would try recover the blerry thing anyway.
 
I am about 30% confident I will get something off the drive, so I am leaning towards having it taken to Southbit. Of the whole 2TB there is less than 50GB that actually needs to be retrieved.
 
LOL, UPS, Aircon and air-movement all get verified before I even plug a damaged drive (in a board from an external drive) into the UPS+Laptop.

Hopefully you are using eSATA & not USB. Those USB to SATA/PATA controllers can cause issues.
 
Southbit it is, gave my dad a whopping quote but that will teach him to backup from now on.
 
Hopefully you are using eSATA & not USB. Those USB to SATA/PATA controllers can cause issues.

USB 3 external drive's board (from an old verbatim) or an esata board from an old no-name brand external drive.
Both work without any issues.
 
Top
Sign up to the MyBroadband newsletter
X