Oct 27
jolle [OT] Time machine ML bug biting hard
Oct 27, 2013; 17:52
jolle
[OT] Time machine ML bug biting hard
A word of warning. If you're using Time Machine on Mountain Lion there's a bug that can bite hard. Just did for me.
Here's the story
I wanted to go for Mavericks and downloaded it. The install failed claiming that there was something wrong with my hard drive.
So I figured that I could wipe the drive knowing that I had a full, just made, Time Machine backup.
I wiped the drive.
(Side story is that I now had to download and install Mountain Lion again, in order to enable downloading Mavericks and installing it. Wasting a couple of extra hours.)
When it came time to restore from my backup, the Migration Assistant could't find the backup drive. That was about the same time I realized my backup was corrupt. Turns out there's a known bug that under certain, so far unknown, circumstances have Time Machine fail backing up top level Application and Library folders. That in turn disables Migration Assistant from seeing the backups.
Some digging revealed that at least the home directories where in the backup volume. But there were no easy way of having that data transferred back to the computer since Migration Assistant didn't work. Eventually I solved that by having rsync move my entire home directory to /Users/ on the Mac while logged in as another admin. After setting the ownership it seems that the home is intact.
Also as luck has it I had a fairly fresh duplicate of the Applications. I had made a clone of my regular computer to a Macbook Pro in order to bring it to the LDC at Niagara Falls. I don't think I have made any or very few changes in my Application setup after that so all vital apps are in place and seems to be working.
But, there is a loss I have to deal with. Since the Library folder was not part of the backup I had to settle with the Library folder I could get from the Macbook Pro. And, in the Library folder I have almost all Lasso code I write. Stupid maybe, but I've had it there to ease using it for local testing. Most of it was SVN handled so I've just had to update the working copies from our repo. That restored all client specific code.
But, all the experimental code I've been writing since I got back from LDC was not part of any repo, yet. It was only tested locally and not for any particular project. All of that is now gone.
Sorry, Ke, the handy grid type I wrote for DS. No more. Same with my AngularJS testings. And a lot of other cool stuff.
That sucks.
Now while writing I realize that I've probably lost all database work I've done locally too. Well, don't think that was critical...
If you want to avoid it and save yourselves from a world of hurt. Take a good look at your Time Machine backup volume. If you're running Mountain Lion and there're no Application or Library folders in it, then your backup is corrupt and will fail you when you're needing it the most.
Read more here:
https://discussions.apple.com/thread/5080333
HDB
Jolle
#############################################################
This message is sent to you because you are subscribed to
the mailing list Lasso
Lasso@lists.lassosoft.com
To unsubscribe, E-mail to: <Lasso-unsubscribe@lists.lassosoft.com>
Send administrative queries to <Lasso-request@lists.lassosoft.com>
Oct 28
Rick Draper RE: [OT] Time machine ML bug biting hard
Oct 28, 2013; 07:21
Rick Draper
RE: [OT] Time machine ML bug biting hard
Oct 28
Steve Upton Re: [OT] Time machine ML bug biting hard
Oct 28, 2013; 12:30
Steve Upton
Re: [OT] Time machine ML bug biting hard
Oct 28
Steve Upton Re: [OT] Time machine ML bug biting hard
Oct 28, 2013; 12:47
Steve Upton
Re: [OT] Time machine ML bug biting hard
Oct 28
John May Re: [OT] Time machine ML bug biting hard
Oct 28, 2013; 17:58
John May
Re: [OT] Time machine ML bug biting hard
Oct 29
Rick Draper RE: [OT] Time machine ML bug biting hard
Oct 29, 2013; 08:11
Rick Draper
RE: [OT] Time machine ML bug biting hard