Douglas McLaughlin wrote:
Intel-based Macs can startup off a USB hard drive with Mac OS X installed on it. This gives you ability to access all files on the computer and will allow you to make a disk image with the Disk Utility.
Ok, so I plug the MacBook in to another computer, say a desktop, with a USB cable. The desktop computer will be used to create the disk image of the MacBook. I then boot the MacBook by holding down whatever key is used to boot it into USB Target Disk Mode and then make the Disk Utility backup that way? Is that how I do this? Since we don't have any USB drives at my job that we can use for this process, plugging directly into another computer would be our only option at this point. I typically have a spare computer in my office for just this reason.
A hardware failure of the drive will not allow you to use FireWire Target Disk Mode to recover files. If it's a software fault/file directory problem then booting from an external hard drive through USB will allow you to repair the file directory with Apple's Disk Utility or a more powerful utility like DiskWarrior.
I had meant a software failure. Sorry I wasn't clear. In the time I have been using computers (20+ years), I have come across only about a dozen hard drive failures where data could not be recovered without drastic measures. Any other time it would be something like software, a drive controller, a motherboard problem. More often that not when a drive stopped booting, It's because the user had gone in and changed the startup disk for whatever reason but didn't change it back. Then the computer sits there looking for something that doesn't exist anymore. An easy fix, but the user still get hysterical when their computer doesn't boot.
Really?
Nowhere?
Again, here is where target disk mode comes into play. The Migration Wizard doesn't work for our setup. This is because of the way the user accounts get setup on the computers. The accounts are handled through Active Directory. Because there isn't a lot of server space to keep all of the files up on a network share we have the home directory set to to be saved locally. We also have the accounts set to be mobile accounts if the AD server were to ever go down, uses can still log in to their computers.
Because the accounts are set up this way the Migration Wizard thinks that they are Network accounts and gray's out the user account not allowing for the migration to occur. The best way we have found to move the data over has been with FTDM.