OS 10.5.8 update failure

Boot with your install disk, repair the disk and permissions on the clone, and when finished, reboot into the clone. Erase the hosed installation, clone the clone to it, and give the installer another go.

Just before the 10.5.8 download was complete, I got a message that the installation had failed. I clicked on About this Mac in the Apple menu and it showed that the machine was running Version 10.5.8

I had similar strange events with the 10.5.7 update.

Often times even if the update fails, the OS is still bootable. If so, you can reboot, download the standalone updaters from the apple support site and run that. If it works, it's a lot quicker than most other options.

I updated PMac 2x2 from 10.5.7 and noticed the whole updating process took longer than others have.
Mine also hung on the 1 min to go for a long time, to the point I almost gave up. Then after a couple
more minutes it completed. Its running fine.

FWIW, my 10.5.8 Combo update seemed to hang at the 'one minute' mark and during the 'running installer script' scenario as well - this one for quite a while. I assumed I didn't have anything to lose by waiting, and it finally finished. Oh, and there was a double restart as well.

Frank

Combo updater on my G5 PPC dual 2.0 and Macbook. All good. Macbook hung on the updating boot cache and after force quitting with the power key, it took a very long time to restart, but it did and is working just fine.

Power it down and reboot into the safe mode (hold down shift key at boot). At the login screen click restart and see if the computer restarts normally. This often fixes a "stuck" update.

Your choice, but, if after repairing the disk and its permissions, you might try the update and see if does what it's designed to do. If not, then use the 10.5.7 clone.

On the double restart, the first one writes the files to the disk, while using the original earlier version in RAM to run the machine, the second one loads the new 10.5.8 components into RAM to run the machine. Nothing to worry about.

My install in "Safe" mode stalled at the start of the Installer Script with 2 minutes to go. This is the first ever that I have had a problem with an Updater.

I rebooted and my machine came up as it should with the double reboot and not feeling that this is a completed deal, I am rerunning the Updater now and it stalled at the Installer Script again. Thank God I have a CCC cloned backup to fall back on. But not knowing exactly what the Installer Script does and that it looks like the files were successfully written, who knows it could be a good install. I'll play with it after I reboot and see what happens, but can have 10.5.7 reinstalled in minutes if need be.

Very disappointed to say the least. But I guess it's only because updating has been trouble free up to now. Now what the updates did afterwards is another subject.

We'll see.

Still stalled at 2 minutes left. Time to Force Quit, again, and see what damage is done. If any. Good Luck All.

OMG!
While writing the above and then going on to read more posts, all of a sudden the installer finished and I now have a Restart button. So I guess if you let if run long enough, it finishes. It must be the same person that did the timer for repairing permission that did this one. Delayed success?

TheGuyintheProjectionBooth wrote:
So I guess if you let if run long enough, it finishes.

Indeed, impatience has been the cause of more than a few "corrupted" updates I've seen. People think the "minutes" thing is real time. It's not. It never has been. Sometimes it coincides with real minutes - sometimes not. Then people panic and force the machine to quit - leaving an unstable system.

LET IT DO ITS THING! Go get a drink or something and come back in an hour.

If the installer script hangs again, download the COMBO updater and give that a go. That's why bootable backups/clones are invaluable.

Understood. But that should not be the case. Accuracy is a key factor. If the installer is not accurate in operation, what says that the install is accurate?

Just like the furvor that arose after the 10.5.6 or 7 update and you "repaired permissions", on this maintenance free OS, all kinds of things continuously showed up needing repair and when run again still needing repair.

Accuracy = Confidence.

My apologies, I did not mention that it was a Combo. As you have read many times before and commented on posts of mine you should know I am one of the original "Combo" only fanatics.