After 10.5.3 update the system doesnt start up

My instance of this problem has been solved:

DeepFreeze 4.01 was installed on my machine, and after updating the OS to 10.5.3 the DeepFreeze hook into the boot sequence caused kernel panic.

Solution: Update DeepFreeze to ver. 4.03.

Suggestion to others whose problem is similar, but who don't have DeepFreeze: look for programs or processes that run during the boot-up or shut-down sequences, perhaps security programs that mediate with the OS to manage user control over the system. Try removing such programs from your machine before updating the OS to 10.5.3.

At least most people here get the freeze on a working machine,I installed the 10.5.3 updater today on a brand new,baby clean imac 2.4 ghz,and got the grey screen...nothing works to get out of there,busy installing again as we speak.

Good thing this is a new system,no data lost now.

But thanks Apple,it looks like it's getting worse with every OS update and every new machine.
You never had bs like this on the "old" ppc....or at least I didn't the last 18 years and 8 machines.

I work at a school. We set up a lab of 25 macs. After loading 10.5.3 images and booting up we then pushed deepfreeze 4.01 then kernel panic on all 25 comps. Is there anything we can do to upgrade to deepfreeze 4.03 without re-imaging the machines?

So, I move across the country and finally I'm in a new apartment (after 4 weeks of looking and one week of paperwork) I get broadband connected and what's one of the first things I do? Update my MacBook to 10.5.3 and it quite literally kills my hard drive. Now, my black 2GHz 1GB RAM MacBook won't get past the gray Apple logo and the startup sprocket. It just spins and spins for about three minutes and powers down--and by that I mean dies. Power cuts and the screen goes black--not a pleasant thing.

I've tried booting from my install disc and tried to use disk util to repair the disk, but the repair button is grayed out and when I try to verify the disk it tells me verify and repair has failed.

I am really, really upset. Apple should know better than to allow an update like this into the wild. It has literally screwed my hard drive to ****. When I put my MacBook in target drive mode and connect it to my MacBook it just hangs for many minutes and finally only admits the hard drive is connected, but disk util won't actually do anything.

In my five years with Apple computers I've learned that little things don't go wrong with Apple computers--HUGE things do. I had the iBook with the logic board problem (that also happened to have a bad HD installed) and it took me literally a YEAR to get that iBook problem sorted (it ended in Apple giving me a total refund).

Also, all you people who have had no problem with your Macs just keep your mouth closed--don't tell us how wrong we are for having problems with beloved Apple computers. If you're not having trouble with yours, I'm happy for you, but commenting about how you've "never had a problem with Macs" is like rubbing our faces in our own bad luck. So, please, unless you have a possible solution, just refrain from commenting. Thanks.

So, now, I can't access my hard drive, have at least a few gigs of stuff I CANNOT lose and have no way to get to it. Yes, I should have been backing up but guess what--I just moved from Los Angeles to New York City and have been living out of bags and then boxes since May 19. Backing up is a little hard to do when your back up drive is buried someplace. Also, I shouldn't HAVE to back up before I install a simple OS update.

Apple products are supposed to "just work" well, this apple product "just wiped out my hard drive."

I doubt we'll be seeing that as a slogan any time soon.

Wee. I just love it when no one has anything to suggest. Can't wait to see how much Apple will charge to replace my hard drive and NOT save my data, despite their update being the cause of the problems.

Sure would be nice if (at the very least) someone from Apple could hang around these forums.

Did you ever get this resolved? (I just read this now, 9/29/2008.)

Richard Bonomo wrote:
Did you ever get this resolved? (I just read this now, 9/29/2008.)

The original poster, Laximus, solved his problem a long time ago.
When others hijack a thread this is what happens - confusion. Nobody knows who is commenting to whom.

When people are too lazy or shy to start a new thread, this is the result.
As I noted the original issue was solved a long time ago.
We are already up to 10.5.5 and this thread was about 10.5.3. It's a dead issue.

Message was edited by: nerowolfe