• On Metacritic: BioShock 2: How does it compare?
advertisement
mySimon mySimon mySimon Outdoor Gear mySimon Swimwear mySimon Home and Garden
February 13, 2009 6:00 AM PST

Security Update 2009-001: startup fails

by CNET staff
  • Font size
  • Print
  • 23 comments

A number of users have reported that system startup fails after installation of Security Update 2009-001. Reader reports include:

  • "After the update and reboot, my MacBook Pro stayed on the blue screen with the spinning wheel (not the beach ball). I waited about 20 minutes."
  • "I installed the Java 3 update and the 20009/001 security update. When my iMac tried to restart, it failed part of the way through and I got the 'insert boot volume and press any key' message. Nothing I did was able to get it to restart normally."

The first recommended procedure, if you are experiencing this issue, is to simply boot in Safe Mode -- accomplished by holding down the Shift key while your Mac is starting up. After the safe boot, restart normally. A number of maintenance tasks are performed during the safe boot, and you might not need to perform any additional troubleshooting. You might receive a message indicating that the update has finished installing after performing the safe boot.

You can also try temporarily disconnecting any USB, FireWire other otherwise-connected external peripherals then re-attempt startup.

Other possible include resetting the PRAM (hold options-command-P-R keys at bootup until the computer chimes, then resets and chimes again) and SMC resets (Portables, Mac Pro), as well as shutting the computer completely off and unplugging it for a few minutes before starting it back up.

Failing the aforementioned, peruse our tutorial titled "Startup fails (particularly after a system or security update); solving." One of the solutions listed there -- including delete specific caches, rooting out problematic kernel extensions, repairing drive damage, and disconnecting external devices -- might prove successful.

If worse comes to worst, you may need to reinstall the system (even though reinstalling the system isn't that bad), via our tutorial.

Feedback? http://www.macfixit.com/contact.

Resources

  • Portables
  • Mac Pro
  • "Startup fails (particularly after a system or security update); solving."
  • http://www.macfixit.com/co...
  • More from Late-Breakers
  • Recent posts from MacFixIt
    Address Book: Search not working properly
    iTunes 9.0.3 breaks AirTunes connection for some
    Apple releases Aperture 3.0
    Manage iCal's automatic e-mail generation for invitations
    CNET TV Apple Byte: Apple faces critics
    Weekly Utilities Update: Net Monitor, MiniUsage, TimeMachineEditor, more...
    Odds and Ends: Essential video codec packs for OS X
    Address Book: Unable to add, view contacts
    Add a Comment (Log in or register) Showing 1 of 2 pages (23 Comments)
    by macdad614 February 13, 2009 6:26 AM PST
    It would be nice to read one of these articles without having to stop to figure out what words had been overlooked and/or omitted. ESOL?
    Reply to this comment
    by Gennx30 February 13, 2009 12:04 PM PST
    security updates can cause problems
    best bet
    *Restart your computer holding down the: CMD-S untill you get a black screen which all sorts of code scrolls by
    you should see a:
    YOU/$:- type "FSCK -FY" return
    if all goes well, reboot
    If "SYSTEM FILE WAS MODIFIED"
    Run FSCK once again to make sure
    reboot, holding down the shift bar,
    until you get a login screen that says "SAFE BOOT"
    Log in
    Repair Permissions
    install update
    reboot- let it fully install-many times the screen will go black again-this is normal
    personally I do the FSCK and Repair permissions agian after all is done
    NEVER had a problem with a Sec Update
    IF you still have problems-do the same as above but run the 10.5.x Combo updater
    Reply to this comment
    by Gordon Alley February 13, 2009 12:04 PM PST
    >
    This is a reply to a previous comment by Gennx30


    I'm pretty sure that the Safe Boot procedure implicitly runs fsck (among other things) regardless of whether the filesystem was modified.
    Reply to this comment
    by giostudios February 13, 2009 12:04 PM PST
    >>
    This is a reply to a previous comment by Gordon Alley


    I used my friends G4 Still no luck. When I try to install anything it says sorry you cannot install in this Hard Drive. I get red flags on HD Icon. So what are you talking about?
    Reply to this comment
    by jstoller February 13, 2009 12:04 PM PST
    >
    This is a reply to a previous comment by Gennx30


    After many hours of trying many different solutions, I finally returned my PowerMac G5 to a fully functional state.

    I booted my G5 into Target Disk Mode and hooked it up to an older G4 I have laying around. From there I was able to reapply the security update to the G5's hard drive. Then I booted the G5 into single user mode and used Applejack to repair disk permissions. Then, jut to be safe, I did a safe boot, logged into my admin account and restarted the computer normally. Now everything works again.

    In the name of full disclosure, before applying the security update, I first tried applying the Mac OS X 10.4.11 Combo update to my G5, while it was in Target Disk Mode. This didn't work on its own, but it may or may not have done something to prime the system for my application of the security update.
    Reply to this comment
    by giostudios February 13, 2009 12:04 PM PST
    >>
    This is a reply to a previous comment by jstoller


    Not all of us have an extra G5 lying around so this was not a helpful tip.
    Reply to this comment
    by buildbblackclouds February 13, 2009 12:04 PM PST
    >>>
    This is a reply to a previous comment by giostudios


    Maybe not for YOU but for people who happen to have a second machine or who have friends with a Mac ? this IS helpful advice.
    Reply to this comment
    by m-bomb February 15, 2009 11:15 AM PST
    Better yet, download Applejack (from Versiontracker). Install it. (This is a preventive measure for last time ? it needs the GUI ? although if you can safe boot, that is another way.) Shutdown. Start up in safe mode (Apple S as it's booting). At the prompt, type "applejack auto restart". It will clean up everything (disk repair, permissions repair, cache flush, permissions check, virtual memory cleanup). It takes about 20 minutes with Leopard and fans will spin (fan control does not work in safe mode). I have saved several computers this way...
    Reply to this comment
    by m-bomb February 15, 2009 11:15 AM PST
    >
    This is a reply to a previous comment by m-bomb


    Sorry, I meant to say "then start up in single user mode (Command S held down while starting)" (safe mode is restart with shift held down, which will often work when a normal start won't; this brings up the GUI)
    Reply to this comment
    by cary3 February 15, 2009 11:15 AM PST
    >
    This is a reply to a previous comment by m-bomb


    Thanks for the tip. I got the blue screen but Applejack got me right back up and running.

    ---
    Model Name: iMac
    Model Identifier: iMac7,1
    Processor Name: Intel Core 2 Duo
    Processor Speed: 2.4 GHz
    Number Of Processors: 1
    Total Number Of Co
    Reply to this comment
    by giostudios February 15, 2009 11:15 AM PST
    >
    This is a reply to a previous comment by m-bomb


    How can u install it? The Mac has a blue screen and you can't proceed any further dummy ! Even after booting in Safe mode.
    Reply to this comment
    by Zammie2000 February 16, 2009 4:21 AM PST
    I always run Disk Utility>Repair Disk Permissions before any kind of install or update and I rarely have issues.

    -Zammie
    Reply to this comment
    by Razzledazzle February 16, 2009 6:42 AM PST
    Ok here is the best method (for me) I do Safe Mode and then Applejack and then allis OK. I find big problems with the Security update on my Intel Macs but not on my PPC Macs. It is best to let Applejack do the repair permissions in Single user Mpde as it will also do the rest (clear caches and virtual memory as well as check permissions.)
    Reply to this comment
    by listserv69 February 16, 2009 9:29 AM PST
    2 G4 macs with 10.4.11 had their system's hosed by this update. Neither machine has any wonky additions, files moved, or any of that business. A friend locally has a 'G4 sawtooth' and My nephew in California has an imac G4. I was able to get the sawtooth up by booting from an external firewire drive which I then used to run disk warrior.Rebuild and replace the directory. It fixed it. Nothing else had fazed it. NO safe boot, no single user boot, no Applejack , nothing until the DIsk Warrior directory fix. It appears that something in the directory structure is moved or tweaked which renders the machine unable to boot. They never get past the blank BSOD. My nephew went to the Apple Store in Century City,CA to just buy a new iMac(it was time to replace the 'Lampshade" )and have them fix the boot up then transfer his data to the new machine. Their response, "We don't work on a machine that old, you need to find someone to fix it for you" He left the store without buying an iMac. :-(
    Reply to this comment
    by rchang--2008 February 16, 2009 9:29 AM PST
    >
    This is a reply to a previous comment by listserv69


    Updating my Powerbook G4 (400MHz Titanium) hosed my Tiger partition too. It wouldn't reboot in safe mode or in single user mode. In single user mode, it gave some message about locating the boot files and got stuck --- never got a shell prompt.

    I still had a Panther and OS9 partition on that disk, so I could reboot into Panther and poke around. I tried deleting some files, but no luck. I ended up reinstalling 10.4.11 and going though 8 Java updates (why no combo updater for Java???)

    I finally had enough confidence in the health of the new system, I tried installing Security Update 2009-001 again. This time it started up fine. Although I did boot into single user mode (and ran fsck) and then booted into safe mode before doing a real reboot.

    During the reinstallation process, I did have to fix the disk a couple of times. So, I think there was already something wrong with my system. The Security Update just made the problems painfully obvious.

    -R.
    Reply to this comment
    by lcpguy February 17, 2009 12:47 AM PST
    I did nothing special. I just down loaded from Apple's Update like usual and went for it. No problems of ANY kind.

    Everything woks fine.
    Reply to this comment
    by demonvoicebox February 17, 2009 1:28 AM PST
    Same here, no problems at all. However, I did start up in Safe Mode and ran Applejack just to make sure!
    Usually I let Onyx repair permissions and empty the cache etc, but Applejack is such a neat piece of software that on these occasions it's always my first choice.
    Reply to this comment
    by brownkm52 February 17, 2009 8:39 PM PST
    I tried to do the update on my 2006 iMac Monday night... and get the empty blue screen on reboot. It won't boot into Safe Mode. I can boot into single-user mode - I ran fsck there, and the disk checked out ok. Reboot after that still gives me the empty blue screen.

    Inconveniently, one of my sons apparently disabled the disk drive by stuffing business cards into it, so I can't boot from the OS X disk by holding down -C- during the boot either.

    Am I screwed here? Or can I reset the permissions on the command line?
    Reply to this comment
    by lcpguy February 17, 2009 8:39 PM PST
    >
    This is a reply to a previous comment by brownkm52


    I never did anything special. Just installed from Apple's update and voila! All works perfectly.
    Reply to this comment
    by lazaros February 17, 2009 8:39 PM PST
    >>
    This is a reply to a previous comment by lcpguy


    Installed the secutity update on three machines (Power Mac dual G4, Powerbook G4 and MacBook Pro 2nd gen) without any problems. However, the update caused my Intel Mac Pro to be unable to reboot: gray screen and spinning wheel forever. Had repaired permissions before and had the package sitting on my /Library/Packages folder, so didn't let Software Update do everything automatically (I know better). Still refused to bring me to the login screen, but could ssh via terminal from another machine, so the system was alive. Ended up booting from an extrenal firewire clone and reapply the update, and then it worked!
    Reply to this comment
    Showing 1 of 2 pages (23 Comments)
    advertisement

    About MacFixIt

    MacFixIt is CNET's troubleshooting resource for all things Mac. The information here helps you navigate the ins-and-outs of Mac ownership with how-tos, troubleshooting information, news, reviews, and more.

    Add this feed to your online news reader