Skip navigation

osx lion upgrade - computer boot VERY slow

1118 Views 6 Replies Latest reply: Aug 29, 2011 1:41 AM by Arnd Gehrmann RSS
Jonny Apple Seed Level 1 Level 1 (20 points)
Currently Being Moderated
Jul 30, 2011 10:58 AM

after upgrade to OSX Lion, my computers boot very slowly.  they also have a hard time waking from "sleep", sometimes running fans then going back to sleep again.  disk verified, permissions repaired before and after install.  any ideas?  it's happening on more then one machine so it appears to be related to the software.

  • The hatter Level 9 Level 9 (58,535 points)
    Currently Being Moderated
    Jul 30, 2011 11:15 AM (in response to Jonny Apple Seed)

    Burn Lion image DMG to DVD

     

    clone what you have

     

    Do clean install and good test for a few days first

     

    Roarinngapps has a table and compatibility checker

  • Arnd Gehrmann Calculating status...
    Currently Being Moderated
    Aug 23, 2011 11:24 PM (in response to Jonny Apple Seed)

    same at me!  MBP 15",I7,early 2011

     

    Inspecting /var/log/system.log shows many of those error-messages:

    ...

    Aug 23 07:18:31 inachos Dock[289]: ERROR: Failed to find child 3 of 377

    Aug 23 07:18:31 inachos Dock[289]: ERROR: Failed to find child 11 of 377

    Aug 23 07:18:31 inachos Dock[289]: ERROR: Failed to find child 14 of 377

    Aug 23 07:18:31 inachos Dock[289]: ERROR: Failed to find child 28 of 377

    Aug 23 07:18:31 inachos Dock[289]: ERROR: Failed to find child 32 of 377

    Aug 23 07:18:31 inachos Dock[289]: ERROR: Failed to find child 4b of 377

    Aug 23 07:18:31 inachos Dock[289]: ERROR: Failed to find child 50 of 377

    Aug 23 07:18:31 inachos Dock[289]: ERROR: Failed to find child b3 of 377

    Aug 23 07:18:31 inachos Dock[289]: ERROR: Failed to find child bd of 377

    Aug 23 07:18:31 inachos Dock[289]: ERROR: Failed to find child d6 of 377

    Aug 23 07:18:31 inachos Dock[289]: ERROR: Failed to find child dc of 377

    ...

    Aug 23 07:18:31 inachos Dock[289]: ERROR: Failed to find child 268 of 389

    Aug 23 07:18:31 inachos Dock[289]: *** process 289 exceeded 500 log message per second limit  -  remaining messages this second discarded ***

     

    After booting, for more than a minute, most of the Apps work very slowly. Most buttons have to be pressed an second, a third time to work. After using Yasu (http://jimmitchell.org/yasu/) it seems to be a little bit better but after two/three bootings appears the same effect.

     

    Than i decided to install Lion again but with the same result.The activity-display, showing ALL(!) processes, sorted for cpu-usage dont show no very consuming process ???

     

    A.

  • Arnd Gehrmann Level 1 Level 1 (0 points)
    Currently Being Moderated
    Aug 23, 2011 11:50 PM (in response to Arnd Gehrmann)

    ... and, like told in another thread, two times the MBP dont wake up after night long sleep-mode so i had to do a "brute power down" pressing the powerbutton for more than a few seconds. Another very curious thing, starting a time-machine-backup needs a very long time for "preparing backup", even when only a few MBs have to be stored ???

     

    Toltaly another feeling, Lion on an old Mac Mini (Late 2009). It works significant better, than before. Boots very quickly and works very well!!!

    Very curious!

    A.

  • Arnd Gehrmann Level 1 Level 1 (0 points)
    Currently Being Moderated
    Aug 23, 2011 11:54 PM (in response to Arnd Gehrmann)

    ... just seen: A very detaild description of the same in this thread:

    https://discussions.apple.com/message/15738767#15738767

  • cksum Level 1 Level 1 (10 points)
    Currently Being Moderated
    Aug 26, 2011 2:56 PM (in response to Arnd Gehrmann)

    The "Dock[289]: ERROR: Failed to find child" warning is LaunchPad. The database has been corrupted and LaunchPad fails to retreive the necessary information for those items.

     

    You'll see this behaviour every time you reboot or log out. Visually, it is represented by LaunchPad re-arranging your items (this ones in particular), throwing off your own app sorting strategy.


    For example, if you had Calculator, iChat, Console, and Terminal in one screen (ordered in that sequence) and Launchpad failed to retreive the required information for iChat, you will notice that it won't remain the desired position after reboot/log off.

     

    Also 377 (in my case, I have 90) items is how many apps LaunchPad has registered.

     

    To fix this, you will need to manually delete LaunchPad's database and reboot. Your LaunchPad will be reset to it's default parameters and if you look at your logs, you'll notice the errors will be no more. You can then begin the arduous task of re-organizing the screens how you see fit. Log out and back in again, should show them being in the persistent arrangement you had placed them in.

     

    This fixed the problem for me and hopefully, the corruption won't occur again.

  • Arnd Gehrmann Level 1 Level 1 (0 points)
    Currently Being Moderated
    Aug 29, 2011 1:41 AM (in response to cksum)

    Hi, "cksum",

     

    thanks for this! after a short search, i found this tool:

    http://chaosspace.de/launchpad-control/

    and the "reset" does the job for me.

    Now the "ERROR: Failed to find child.."-msgs are away from syslog.txt

     

    But the process of booting the MBP is not significant quicker (may be a little!) :-(

    Special the time before changing colour of the "apple-startscreen" from light blue to grey seems to be very long, significant longer, than on a brand new Mac mini (I5) with less CPU-Power than my MBP (I7) ???.

     

    A.

Actions

More Like This

  • Retrieving data ...

Bookmarked By (0)

Legend

  • This solved my question - 10 points
  • This helped me - 5 points
This site contains user submitted content, comments and opinions and is for informational purposes only. Apple disclaims any and all liability for the acts, omissions and conduct of any third parties in connection with or related to your use of the site. All postings and use of the content on this site are subject to the Apple Support Communities Terms of Use.