Shirt Pocket Discussions

Shirt Pocket Discussions (http://www.shirt-pocket.com/forums/index.php)
-   General (http://www.shirt-pocket.com/forums/forumdisplay.php?f=6)
-   -   Restore = disaster. (http://www.shirt-pocket.com/forums/showthread.php?t=5808)

bart 10-01-2009 10:37 PM

Restore = disaster.
 
Grrrr...I just spent half-an-hour crafting a long post and the damn discussion post must have time out. Ok. Here is the cliff notes version...

Used the free version of SuperDuper to backup a 250Gb internal drive to an external USM drive on an Intel MacbookPro (early 2008). Rebooting with the option key allowed me to then boot from the image on the external drive and that seemed to work. I then purchased SuperDuper to allow me to do smart updates and did that. I also had, all the while, been keeping Time Machine backups as a secondary measure.

When I tried to option--boot to the SuperDuper clone the after the smart update, it failed and all I got was a gray screen with the spinner. WORSE--when I tried to reboot from my internal drive, that gave me the SAME problem. I tried rebooting with every startup keyboard command I could think of. Safe mode--failure. Single user mode worked and I did an fsck -fy, but same problem. I tried to restore from SuperDuper clone via startup with apple disks but the disk util said it was the wrong type for a source (I don't remember exactly).

I restored from Time Machine, which seemed to complete but I was still in a continuous reboot cycle. Finally, in utter desperation, I installed Snow Leopard over top of the Time Machine restore and lo-and-behold, my laptop came back to life--AND it had the same state of files and folders as I originally had (which means the Time Machine restore worked).

Summary--when I needed it, SuperDuper failed to restore. Thank god I had Time Machine backups that were very current.

bart 10-01-2009 10:38 PM

USB drive (not USM drive)
 
Typo in original post.

dnanian 10-01-2009 11:05 PM

Well, given this narrative, it certainly sounds like your system was in a bad state when you did your last backup, and you hadn't noticed because you hadn't restarted. This corrupted your backup (since it was copying the state of the files on the drive), and then—when you tried to restart from the internal—you finally read the files that were messed up there.

Similarly, you had damaged Time Machine backups, and installed the OS fresh, which fixed them. It likely would have fixed your internal and your backup, too... but alas you didn't try that, so we can't be sure. But what I would have suggested, had you contacted me, was clean installing Snow Leopard to the internal, then pointing at the backup so it'd bring in the non-OS files, which should have worked fine.


All times are GMT -4. The time now is 08:58 AM.

Powered by vBulletin® Version 3.8.9
Copyright ©2000 - 2017, vBulletin Solutions, Inc.