Skip to main content

Utah Data Recovery

About three years ago (so pre-Mozy and definitely pre-Mac Mozy) my brother had his powerbook hard disk die. As in, not just mostly dead -- it would not power up. It had a lot of stuff on it that he didn't want to lose, but he felt like the usual suspects who charge $1k to $2k for data recovery were a rip off. So he hung onto the disk in case a cheaper option came along.

Then just recently when I saw some people on a local linux group mailing list recommend utah data rescue I suggested to my brother that he give it a try. UTDR starts at "only" $300.

UTDR did indeed recover the data, although they charged $100 extra for this one. Mac fee? Tricky hw problem? I don't know. But it was still a lot cheaper than the other companies I googled for fixing a physically dead drive. (As opposed to a corrupt partition table or something where the hardware itself was okay.) At least, the ones that actually give you a price up front rather than hiding behind "request a quote!"

Comments

Anonymous said…
$400?! That's cheap. They probably just did a PCB swap and managed to get your drive up and running again. Good to hear you got your data back.
JT
6:34 AM
Stephen Thorne said…
Depending on the model, replacing the harddrive in a powerbook requires disassembling basically the entire computer. It's at least an hours work to properly disassemble, and then reassemble the machine, and that's just to replace the drive - let alone data recovery.
9:52 PM
Anonymous said…
Stephen,

I am an Apple portables tech. It does not take at least an hour to disassemble and re-assemble a powerbook. It takes roughly 20 minutes. All you need to do - in any model - 12" 867Mhz to 17" 1.67Ghz DL - is remove the screws around hte bottom case to release the top case. Then you just take the drive out and put the new one in. Really simple. In fact, it would still be the most simple take apart for a hard drive, but the macbook is now easier.

What takes a while is formatting, verifying and restoring the drive to an OS. That could take about 30 - 45 minutes.
9:57 PM
Unknown said…
Uggg, I am a data recovery technician and I absolutely hate having to touch anything in the Modern Mac lineup. Once you research the model you are working to determine which are the correct screws to "only remove the hard drive", fabricate a special disassembly tool to insert into the obscure crack to disengage the case brackets, peel back the "TV-Dinner" style aluminum foil with its incredibly adhesive properties without tearing it, unstick the micron thick PCB ribbon cables without breaking them in order to access what on 90% of PC based laptops is a quick remove tray to get the hard drive out. Then begins the different levels of diagnosing the nature of the actual failure. here is a shortlist of the categories: file based; unpurged write cache due to improper powerdown, vibration induced errors, deleted files, deleted partitions, bad software updates, reformatting, errant utilities like defrag or AV, virus activity, encrypted files and forgotten passwords, etc. Hardrive based; corrupted firmware, failed electronics package, internal calibration failure, impact damage, head crash, errored out S.M.A.R.T. drive deactivation, head actuator falure, motor failure, siezed bearings, overheating, foriegn objects, liquids, intermittant speeds, head sticking, harmonic vibration, excessive power either drain or supply.

Once you have isolated the failure you must use the proper recovery technique the recover the data. Some is software based, some of it requires temporarily repairing the failed drive. A simple PC board replacement isn't always so simple. There are a wide array of manufacturers and models and different firmware versions in the same models which have to be flashed to the board IF you can locate a replacement and must purchase. We have a vast array of diagnostic replacement parts to swap out but still have to locate and buy new parts (which are sometimes functional old parts)every day. So yes $400 is cheap and you must have had a simple to recover situation. And Yes, Mac products do take longer than PC products. I am having nightmares about the first "Air" that we will need to do a recovery job on. (shudder)
5:44 PM
Post a Comment

Popular posts from this blog

The Missing Piece in AI Coding: Automated Context Discovery

I recently switched tasks from writing the ColBERT Live! library and related benchmarking tools to authoring BM25 search for Cassandra . I was able to implement the former almost entirely with "coding in English" via Aider . That is: I gave the LLM tasks, in English, and it generated diffs for me that Aider applied to my source files. This made me easily 5x more productive vs writing code by hand, even with AI autocomplete like Copilot. It felt amazing! (Take a minute to check out this short thread on a real-life session with Aider , if you've never tried it.) Coming back to Cassandra, by contrast, felt like swimming through molasses. Doing everything by hand is tedious when you know that an LLM could do it faster if you could just structure the problem correctly for it. It felt like writing assembly without a compiler -- a useful skill in narrow situations, but mostly not a good use of human intelligence today. The key difference in these two sce...
Post a Comment
Read more

Why PHP sucks

(July 8 2005) Apparently I got linked by some PHP sites, and while there were a few well-reasoned comments here I mostly just got people who only knew PHP reacting like I told them their firstborn was ugly. These people tended to give variants on one or more themes: All environments have warts, so PHP is no worse than anything else in this respect I can work around PHP's problems, ergo they are not really problems You aren't experienced enough in PHP to judge it yet As to the first, it is true that PHP is not alone in having warts. However, the lack of qualitative difference does not mean that the quantitative difference is insignificant. Similarly, problems can be worked around, but languages/environments designed by people with more foresight and, to put it bluntly, clue, simply don't make the kind of really boneheaded architecture mistakes that you can't help but run into on a daily baisis in PHP. Finally, as I noted in my original introduction, with PHP, ...
30 comments
Read more

A week of Windows Subsystem for Linux

I first experimented with WSL2 as a daily development environment two years ago. Things were still pretty rough around the edges, especially with JetBrains' IDEs, and I ended up buying a dedicated Linux workstation so I wouldn't have to deal with the pain.  Unfortunately, the Linux box developed a heat management problem, and simultaneously I found myself needing a beefier GPU than it had for working on multi-vector encoding , so I decided to give WSL2 another try. Here's some of the highlights and lowlights. TLDR, it's working well enough that I'm probably going to continue using it as my primary development machine going forward. The Good NVIDIA CUDA drivers just work. I was blown away that I ran conda install cuda -c nvidia and it worked the first try. No farting around with Linux kernel header versions or arcane errors from nvidia-smi. It just worked, including with PyTorch. JetBrains products work a lot better now in remote development mod...
Post a Comment
Read more