Leopard backup boots, but apps crash? Try this.

[fl0]

How to start a shell script with sudo privileges without a shell?
(sorry i'm a unix'er)

BTW: My SD also doesn't work....so I cannot use the "after copy" option.

Should I make a new backup (in my running system) and include the script?

[dnanian]

Yes, make a new backup and run the script at the end of the backup. Don't do this from the backup itself.

[jeffhands]

Greetings,

I downloaded your zip file and unzipped it.

In the past I thought of myself as a power user, but now since OS-X, there's a lot "under the hood" that's unclear to me.
For example, I have never used Terminal and am reluctant to do so unless I have really detailed instructions.

What do I do with this "fix_prebinding.sh" file? I can see that it is a text file.
Is it something that I paste into Terminal, if so, where and how? Or what do I do?

My MacBook is at the local Apple repair; where they determined that it needs a new motherboard, so I don't have the original hard drive in my hands.

Can I implement this fix when I have booted from the cloned drive? Or do I need to get the MacBook back and use this fix before creating a new clone?

As you can see, I am bordering on clueless.

Thanks for the help.

Jeff Hands

[dnanian]

You don't have to use Terminal: the instructions I provided in the first post explains what to do. But if your Mac is already at the shop, it's a little too late to implement this particular fix.

Are you running from the copy now?

[jeffhands]

Thanks for the quick response.

Forgive me for being dense, but as I look at the instructions from the first post I can only understand the first point:

"To use it, do the following:

1. Unzip the attached to a convenient location (not your Desktop - I recommend an "Applications" folder in your Home folder).

OK, that I understand... but

2. Set the "fix_prebinding.sh" script that gets unzipped a the "After copy" script in the Advanced tab of Options.

Sorry this second step is utterly Greek to me.

How do I ... "set a script" ? Is Super Duper already open when I do this? Is the Advanced tab of Options in Super Duper?

When I get the MacBook back again on Friday I'll try this all over again, because I do want to have a usable clone always on hand.

Thanks again.

[dnanian]

Try:

- Open SuperDuper!
- Click "Options"
- Click the "Advanced" tab
- Check the "After copy" option checkbox, and choose the "fix_prebinding.sh" file as the script to run.

Hopefully that'll help.

[jeffhands]

Thanks for the extra explanation!
That was just what I needed. I made a new clone, after getting my MacBook back and the clone works just fine. What a relief!

Jeff

[sgmiller]

I upgraded to Leopard the other day and never thought to check my new clones. I had another reason to boot from the clone yesterday and found I had the problem with apps crashing which was fixed by the script as advised.
However, I found the whole experience a bit unnerving. Yes, I realize I should have checked the new clones after upgrading but, on the other hand, had I been in an emergency situation, I don't think I would have found that argument completely persuasive. I consider this to have been a situation requiring an emergency "patch" of some kind and, in that sense, I think some kind of notice should have been broadcast to users. Is it not possible to use the Update facility in some way for that?

[dnanian]

Not for something like this, no. It doesn't happen to all users, and it's relatively easy to 'fix' after the fact, so I didn't feel that rushing out a version that didn't address all the issues was appropriate... sorry that you found it scary!

[sgmiller]

By "after the fact", do you mean it would have been possible to apply to apply the script to a clone which was not working properly? If so, than I overestimated the problem and please disregard.

If not, and the user would have been left with a defective backup, then I stick with my original position. Even if it only impact a few users, the consequences for those users could have been catastrophic.

So, either I apologize or I don't.

[dnanian]

The script does run after the backup, actually, and what it does can be done to the backup without the script (in many different ways): the files themselves are all there, and fine.

[sgmiller]

I didn't realize it was possible to run the "fix" script after the backup had already been made, so I guess I am forced to apologize.

[ehofmeister]

I have a few questions - the first is in relation to this thread:

I have a bootable backup of my main HD that I successfully applied your script to as you have described here. Now I want to erase my main HD and restore the backup. Is it necessary to apply the script again - I use superduper to restore the drive using the "restore all" option - do I have to execute the script again after the restore has finished?

On a different note I would like to know if there are any reliability issues if you want to maintain two (or more) separate backups on two (or more) separate partitions on the same external HD? I know you don't recommend using images for critical backups, but they are very handy when you want multiple backups on the same HD. The only other way I can think of is to partition the drive up in 2 or 3 partitions in order to keep 2 or 3 separate backups. Is this an ok strategy?

The last thing I would like to hear about is the Intego VirusBarrier X5 issues that have cropped up lately - are they still around? Are you planning on an update to fix them in the near future or what is going to happen? If they mean that you cannot perform a backup with X5 installed it is pretty critical.

Thanks

[dnanian]

Yes, you should use the script on the restore the same way.

Maintaining separate backups on separate partitions is no problem. The issue is that if you lose the drive you lose all the backups -- it's better to have some physical redundancy.

The Intego problem is something for Intego to fix, as I've said elsewhere -- and I know they're working on it. If you turn off Real Time Scanning, the backup will be successful.

[Michel66]

Thanks much Dave. You save me hours of reinstall.