I have a long story behind this, so please bear with me. A good friend of mine has been going through a tough emotional load (divorce) and failed to run backups regularly on her main computer (MacBook Pro ~2009). It died on her about half a year ago and after some troubleshooting she just bought a new computer. I tried to get her to hand over everything, but she was in her own world. I finally got her to give me the drive and the computer a little while back. The computer's fine and I had it up and running in no time. The hard drive, not so much.
She tried it in an external case but it appeared dead. She took it to Fry's for data recovery services but they couldn't do anything. I took it to the best local person in town I could find, but it was going to cost WAY too much for her. So I got busy with it. The drive did spin up, but it was otherwise unresponsive. Some of my machines wouldn't boot with it attached at all, some would give a warning about it before booting, but it was dead to Windows, OSX, and Linux. After a lot of troubleshooting and web searching I figured out it had a known issue with many Seagate drives. I ordered a usb dongle, sent the terminal commands to the drive, and it magically came back to life. At this point I figured the drive was fine and started copying directories. I got a bunch of files off . . . but then everything went haywire. Some files weren't accessible, some were corrupt, so I immediately halted. I tried imaging the drive, but that wasn't happening. Seatools won't pass it on any tests. I ran GNU DDrescue on it, and managed to get most of the stuff off the drive. It clearly has some blocks suffering from hardware damage around the 2.8 GB mark, but I don't really care as it's unlikely there's anything in that region I care about (right? Those should all be OS files, shouldn't they?). After it got past that bad patch, DDrescue flew along recovering stuff left and right . . . until about the 128 GB mark, at which point it couldn't read anything until the end of the drive. Great, that's where the stuff she really wants is. I fired up HDD Regenerator 1.51 and it confirmed those bad blocks early on the drive are really bad. But it has been doing just fine on the end of the drive. Here's the problem: it's taking TOO long. At the rate it's currently going (on for ~2 days, recovered 17 megs) it'll be years before it finishes the drive. And I don't even know if it's really working! Since it seems to be, I'm just letting it run, but I'd have to run it through DDrescue again to see if there's any new data that can be pulled from it.
So here's my question: what the hell should I do? Given what HDD Regenerator does, would something like SpinRite be able to just go on in and recover the files without messing around with fixing the bad sectors? Is there some other software that could? Would HDD Regenerator run faster if I put more ram in the machine that's running it or if I used a machine with more processing grunt? It's fixed every bad sector it's come up against so far (35,000 of them), but I can't just run this machine forever on this.
Thanks for any sage advice anyone can give!
She tried it in an external case but it appeared dead. She took it to Fry's for data recovery services but they couldn't do anything. I took it to the best local person in town I could find, but it was going to cost WAY too much for her. So I got busy with it. The drive did spin up, but it was otherwise unresponsive. Some of my machines wouldn't boot with it attached at all, some would give a warning about it before booting, but it was dead to Windows, OSX, and Linux. After a lot of troubleshooting and web searching I figured out it had a known issue with many Seagate drives. I ordered a usb dongle, sent the terminal commands to the drive, and it magically came back to life. At this point I figured the drive was fine and started copying directories. I got a bunch of files off . . . but then everything went haywire. Some files weren't accessible, some were corrupt, so I immediately halted. I tried imaging the drive, but that wasn't happening. Seatools won't pass it on any tests. I ran GNU DDrescue on it, and managed to get most of the stuff off the drive. It clearly has some blocks suffering from hardware damage around the 2.8 GB mark, but I don't really care as it's unlikely there's anything in that region I care about (right? Those should all be OS files, shouldn't they?). After it got past that bad patch, DDrescue flew along recovering stuff left and right . . . until about the 128 GB mark, at which point it couldn't read anything until the end of the drive. Great, that's where the stuff she really wants is. I fired up HDD Regenerator 1.51 and it confirmed those bad blocks early on the drive are really bad. But it has been doing just fine on the end of the drive. Here's the problem: it's taking TOO long. At the rate it's currently going (on for ~2 days, recovered 17 megs) it'll be years before it finishes the drive. And I don't even know if it's really working! Since it seems to be, I'm just letting it run, but I'd have to run it through DDrescue again to see if there's any new data that can be pulled from it.
So here's my question: what the hell should I do? Given what HDD Regenerator does, would something like SpinRite be able to just go on in and recover the files without messing around with fixing the bad sectors? Is there some other software that could? Would HDD Regenerator run faster if I put more ram in the machine that's running it or if I used a machine with more processing grunt? It's fixed every bad sector it's come up against so far (35,000 of them), but I can't just run this machine forever on this.
Thanks for any sage advice anyone can give!
