Ok, I've been away for a bit, and I'm normally loathe to ask, but I have a major issue at the moment with Mac OS X, and specifically, Time Machine and restoring.
Ok, so here's the gist:
I have two laptops, a MacBookPro, and a MacBook. They are both dwindling in HD capacity, so I thought, great, time to upgrade their internal hard drives. I purchased appropriately large HDs for each.
So I've used Super Duper in the past for a block cloning to upgrade my computer, but last time I did that, I had major issues with some software looking for old UUID on the HD. So my thought was, that it was messy at best - why not try the 'official' method of using Time Machine?
I used it previously for my sister's MacBook, and it seemed to work like a charm. Here's the process:
Take the new internal HD, and install it straight into the Mac.
Boot the Mac from the Snow Leopard DVD (holding opt), and use Disk Utility to format the new internal HD (GUID, Mac OS Extended, journaled).
Then plug in the Time Machine drive and do a restore from the Utilities menu.
After it's done, do the usual repair permissions, and reset PRAM etc.
No prob.
So here's how my MacBook Pro went:
I had recently transferred some old Time Machine backups to a new external drive. I had everything updated to as much as possible and then did the Time Machine transfer.
AFter the restore, the first weird thing I noticed was that some files (photos) were missing from a recent import. Weird. Checking the original internal drive, they are there - they simply don't exist on ANY of the Time Machine backups.
That was the only niggle I could find, and it seemed my computer ran fine otherwise.
Then I tried upgrading the other MacBook with the same technique.
updated the system to 10.6.7, and other updates, transferred old Time Machine backups to a new external, refreshed Time Machine, changed internal HD, restored.
First thing - it wouldn't boot. Hung on the white screen with the grey logo and spinning circle. On inspection, what is the issue? Apparently there's a little security package that hangs out in:
/System/Library/Frameworks/Security.framework/Versions/A/Security
that for what ever reason was NOT updated in Time Machine, thus never transferred to the new internal drive, and it's required for booting correctly. Strangely, it seemed to be fine on my other MacBook Pro. Transferring that package is the only thing that I could do to get the MAcBook to boot.
After booting, I figured, if that file is messed up, other files are probably older versions too. And indeed they are.
So I thought, hey, maybe I should run the 10.6.7 Combo updater to fix the old files. Ran it, and it does everything it requires to install EXCEPT move the files in place correctly, instead getting an "Installation Failed: The installer encountered an error that caused the installation to fail."
Uh oh.
So maybe the Combo updater doesn't like the current version? Well, running out of good ideas, I reinstalled Mac OS X from the SNow Leopard DVD, reverting it to 10.6.0. That's gotta clear the junk out, right? So it installed fine, back to 10.6.0, Safari reverts, and a bunch of other apps no longer work (as expected), and a gaping hole where the Mac Appstore should be. That's fine.
Then tried running the combo updater. NOpe, no go. Something is seriously messed up with Time Machine at the moment, making it so that some restores are worthless. Files not updated? Restores not complete? Unable to update from fresh reinstall?
I know some stuff around 10.6.6 was changed in Time Machine - for example, it now requires Admin passwords to even restore single files. And somewhere down the line (I think SL), it allowed to transfer a train of backups to a new drive.
So anyone have any ideas? I'm a bit loathe to go the CCC or SuperDuper route due to the UUID messing with my software (namely, it royally screwed up my Aperture Library of 40,000 files and time stamps -that was days of work to fix).
Maybe I should try a Time Machine backup that WASN'T transferred to a new drive?