Take the 2-minute tour ×
Super User is a question and answer site for computer enthusiasts and power users. It's 100% free, no registration required.

An external 3½" HDD seems to be in danger of failing — it's making ticking sounds when idle.

I've acquired a replacement drive, and want to know the best strategy to get the data off of the dubious drive with the best chance of saving as much as possible.

There are some directories that are more important than others. However, I'm guessing that picking and choosing directories is going to reduce my chances of saving the whole thing. I would also have to mount it, dump a file listing, and then unmount it in order to be able to effectively prioritize directories. Adding in the fact that it's time-consuming to do this, I'm leaning away from this approach.

I've considered just using dd, but I'm not sure how it would handle read errors or other problems that might prevent only certain parts of the data from being rescued, or which could be overcome with some retries, but not so many that they endanger other parts of the drive from being saved. I guess ideally it would do a single pass to get as much as possible and then go back to retry anything that was missed due to errors.

Is it possible that copying more slowly — e.g. pausing every x MB/GB — would be better than just running the operation full tilt, for example to avoid any overheating issues?

For the "where is your backup" crowd: this actually is my backup drive, but it also contains some non-critical and bulky stuff, like music, that aren't backups, i.e. aren't backed up.

The drive has not exhibited any clear signs of failure other than this somewhat ominous sound. I did have to fsck a few errors recently — orphaned inodes, incorrect free blocks/inodes counts, inode bitmap differences, zero dtime on deleted inodes; about 20 errors in all.

The filesystem of the partition is ext3.

share|improve this question
    
cross-posted on askubuntu and unix –  intuited Dec 29 '10 at 19:27
add comment

2 Answers

Use ddrescue instead. It starts reading the hard drive and will automatically skip around when it hits a problem, then go back and try to re-read those problem areas. It's really amazing how well it does when compared to some of the recovery programs I used to use on windows. You can also start and stop whenever you want, it saves a kind the progress state to a file. You can control-c, etc, however you want. There's also plenty of options for customizing the read like trying harder on certain areas.

(plus, the file that this outputs can be put through other recovery programs if needed)

http://www.gnu.org/software/ddrescue/ddrescue.html

share|improve this answer
add comment

I have had a recent experience with a drive that made a ticking noise too. You're right about the HDD failing. The read/right pin's air gap isn't acting write causing the pin to fall onto the drive and make a ticking noise. My HDD was able to stand this for about a week before I was able to send it back to Lenovo. I had no issues copying information off of the drive. If you have acted on the problem quickly enough you shouldn't have many issues. I would do it in 1GB chucks though. Good Luck at getting all of your data off.

share|improve this answer
add comment

Your Answer

 
discard

By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.