Brian Williams2

Q: 10.11.6 update has crippled my Mac Pro

Having trouble after update to 10.11.6 - System preferences panes won't open, can't seem to find any app that will open - reports of apps damaged, including disk utility, console, etc. Restart and shut down/restart don't clear it. Came looking for reports - problem seems not universal. Had successful update on my MacBook Pro, but my Mac Pro now seems in dire straits. Went the Recovery route and re-inatalled OS X . 10.11.6 was installed. Still no joy. Application folder shows only a bare few, and not the Apple applications. Cannot open any System Preferences panes. Safe Boot does not complete. Hardware OK - can boot successfully to a clone (CCC) of only a few days ago. Could do a restore (from Time Machine BU), but that is a last resort. Looking for others facing similar challenges and their success at resolving the issues.

Mac Pro, OS X El Capitan (10.11.6), 3.2 GHz Quad Xeon 16GB RAM, 12TB HD

Posted on Jul 18, 2016 2:58 PM

Close

Q: 10.11.6 update has crippled my Mac Pro

  • All replies
  • Helpful answers

first Previous Page 4 of 10 last Next
  • by Paul Cohen1,

    Paul Cohen1 Paul Cohen1 Jul 20, 2016 9:27 PM in response to Paul Cohen1
    Level 1 (10 points)
    Mac OS X
    Jul 20, 2016 9:27 PM in response to Paul Cohen1

    I re-stalled from a time-machine backup, disabled a WD and all login items(except for iTunes helper) and then ran the update, which ran properly this time. The resulting update is fine.   Retina MBPro 2012.

  • by swebb99,

    swebb99 swebb99 Jul 21, 2016 2:12 AM in response to Csound1
    Level 1 (10 points)
    Mac OS X
    Jul 21, 2016 2:12 AM in response to Csound1

    I had about 7 login items but only three were enabled all of which sit in the menu bar.... smcFanControl, TomTom and Garmin (express?).

  • by swebb99,

    swebb99 swebb99 Jul 21, 2016 2:14 AM in response to Detlef Schmitt
    Level 1 (10 points)
    Mac OS X
    Jul 21, 2016 2:14 AM in response to Detlef Schmitt

    I forget the one I tried, I created the lsd directory and all the other files specified, set permissions, restarted lsd ....... it didn't seem to do anything for me.

  • by alexfriedrich,

    alexfriedrich alexfriedrich Jul 21, 2016 2:46 AM in response to Brian Williams2
    Level 1 (4 points)
    Mac OS X
    Jul 21, 2016 2:46 AM in response to Brian Williams2

    Thanks Apple, my MacBook Pro 2015 is crippled as well, only Apple apps run, most apps like Curio, 1Password, IPVanish or GarageSale have a beach ball and the console shows

    21/07/16 11:37:22,000 kernel[0]: process Curio[2702] caught causing excessive wakeups. Observed wakeups rate (per sec): 2531; Maximum permitted wakeups rate (per sec): 150; Observation period: 300 seconds; Task lifetime number of wakeups: 45351

    ->

    21/07/16 11:37:28,897 spindump[537]: Saved wakeups_resource.diag report for Curio version 10.3 (10302) to /Library/Logs/DiagnosticReports/Curio_2016-07-21-113728_MacBook-Pro.wakeups_res ource.diag

  • by Roadhog56,

    Roadhog56 Roadhog56 Jul 21, 2016 4:14 AM in response to Brian Williams2
    Level 1 (4 points)
    Jul 21, 2016 4:14 AM in response to Brian Williams2

    Re: OS 10.11.4 broke all of my applications...

     

    I had the same problem. Here is what I ended up doing. Everything is working now.

  • by JollyJohn66,

    JollyJohn66 JollyJohn66 Jul 21, 2016 5:35 AM in response to Csound1
    Level 1 (13 points)
    Mac OS X
    Jul 21, 2016 5:35 AM in response to Csound1

    Are any of your MacBook Pro's fitted with a Retina screen?

  • by JollyJohn66,

    JollyJohn66 JollyJohn66 Jul 21, 2016 5:43 AM in response to Brian Williams2
    Level 1 (13 points)
    Mac OS X
    Jul 21, 2016 5:43 AM in response to Brian Williams2

    Are any of your MacBook Pro's fitted with a Retina screen?

  • by JollyJohn66,

    JollyJohn66 JollyJohn66 Jul 21, 2016 6:27 AM in response to Brian Williams2
    Level 1 (13 points)
    Mac OS X
    Jul 21, 2016 6:27 AM in response to Brian Williams2

    Same problem. In case it helps...

     

    I launched the upgrade, the system rebooted and did the whole "updating" thing as per normal (black screen, apple logo, slider with estimated time). I left it for some time (30 minutes) and when I returned it had restarted and was waiting for me to complete the Setup Assistant.

    Once done I went to the login screen. Upon logging in the only items to appear in the menu bar were the Apple supplied ones. Attempting to launch anything failed with a warning the app was damaged. The icon for the app was then replaced with a generic icon. At first the applications menu was full of empty icons, now it won't even open.

     

    Checking the log I see that update 031-61467 installed with no problems.

    Only other things that seem odd are reports by the task "MBFLOAgent" that

    1) flplugin.LaunchServices: Took so long something must of happened, killing it.

     

    and

     

    2) No more connections, mbbackgrounduseragent will exit...

    This is repeated many times with incrementing PIDs. Could be normal IPC stuff.

     

    Otherwise the log looked OK.

     

    System Details:

    OSX 10.11.6 (15G31)

    MacBook Pro (Retina, 15-inch, Mid 2014)

    MacBookPro11,3

    Boot ROM: MBP112.0138.B17

    Apple SSD SM1024F (Revision UXM6JA1Q)

    2.8 GHz Intel Core i7

    16GB 1600 MHz DDR3

  • by NorthTravler,

    NorthTravler NorthTravler Jul 21, 2016 1:49 PM in response to Brian Williams2
    Level 1 (4 points)
    Jul 21, 2016 1:49 PM in response to Brian Williams2

    Pretty much the same problem.  Some observations: The iMac (15,1) ran slow.  No apps would run, would always get the corrupt or incomplete message and then change to a generic icon.  Pretty much stuck.  One note that might make sense to some is iStat's menu bar CPU info was working.  Under processes I noticed "lsd" running, sometimes jumping as high as 60% of my cpu load.

     

    I called AppleCare, they had heard of the problem but didn't say much more about it even when I mentioned the "lsd" cpu load.  Their solution was for me to go into recovery mode and replace with my last 10.11.5 backup.  6.5 hours later everything is back to normal.  I knew that "App Store" would be indicating an update, which it is, and AppleCare strongly suggested I ignore it for now.  We'll see if Apple fixes it.  Sounds like from everyone here that it is definitely a repeating problem.  I am interested in how some of you solved the problem by disabling startup items, I have a number of them, though I think I will sit back and follow this for a while before attempting the update again.

     

    Again a TimeMachine backup from Recovery Mode fixes the problem it you want to wait for the time it takes to replace your files.

  • by Csound1,

    Csound1 Csound1 Jul 21, 2016 1:52 PM in response to NorthTravler
    Level 9 (50,871 points)
    Desktops
    Jul 21, 2016 1:52 PM in response to NorthTravler

    Did they at least explain why most of us are not affected at all?

  • by NorthTravler,

    NorthTravler NorthTravler Jul 21, 2016 2:41 PM in response to Csound1
    Level 1 (4 points)
    Jul 21, 2016 2:41 PM in response to Csound1

    No not really, but I'm glad to hear that many are being successful.  I know, like with the iOS 9.3 debacle, that sometimes only certain situations trigger the problem.

     

    I did get a call back from AppleCare.  I think your comment about most not being affected is Apple's position.  Though I know, personally, that when a problem strikes you it's serious.

     

    I did some searching and found that the "lsd" process is the Little Snitch Daemon.  I don't know what it does, but those of you that use Little Snitch, did you have this problem or not?  It would be interesting to know if this is the root cause of the problem.

     

    AppleCare, in the call back, did suggest that if an update is released it's important enough to install.  They did tell me that I should disable both my virus protection software and the Little Snitch firewall program before installing any Apple update.  I hate to admit, but I've been lax in this area, but will be much more stringent in the future.

     

    Hopefully my experiences will help someone.

  • by Detlef Schmitt,

    Detlef Schmitt Detlef Schmitt Jul 21, 2016 3:43 PM in response to NorthTravler
    Level 2 (283 points)
    Mac OS X
    Jul 21, 2016 3:43 PM in response to NorthTravler

    I have Little Snitch installed and had the problem. But according to this site lsd is LaunchServiceDaemon. That person there did not have Little Snitch installed.

     

    I looked in the Activity monitor. I can see there that I have 2 lsd processes  running. One root lsd and one lsd for my user account. The parent process is LaunchD. I have 3 Little Snitch processes running named "Little Snitch XXXX".

     

    That lets me conclude that for sure lsd is Launch Service!

  • by NorthTravler,

    NorthTravler NorthTravler Jul 21, 2016 4:15 PM in response to Detlef Schmitt
    Level 1 (4 points)
    Jul 21, 2016 4:15 PM in response to Detlef Schmitt

    I agree 100%!  I just launched Activity Monitor and listed my Processes alphabetically.  I do see two "lsd" processes and then I see "Little Snitch Daemon" listed separately. So they are not the same thing.

     

    I based my statements on two items.  When I googled "lsd" I got the references to Little Snitch and did not see anything about Launch Services.  The second was that the AppleCare tech didn't seem to know was lsd was even when I first stated it was an Apple process.  I then did the google and stated to him that it was Little Snitch.

     

    My feeling now is that Apple sure knows about this problem and is "hopefully" investigating.  They sure are being otherwise closed lipped about it and not wanting to admit any ties to their software.

     

    Now of course we are back to that many others are not having any problems.  It probably has something to do with launch services but tied into some other software that we, with the problem, have.

  • by Csound1,

    Csound1 Csound1 Jul 21, 2016 4:20 PM in response to NorthTravler
    Level 9 (50,871 points)
    Desktops
    Jul 21, 2016 4:20 PM in response to NorthTravler

    Of course they are different LSD is an Apple Component that should so what it says, Little Snitch is the digital equivalent of the school tattle tale, and no more accurate

  • by Detlef Schmitt,

    Detlef Schmitt Detlef Schmitt Jul 21, 2016 6:05 PM in response to NorthTravler
    Level 2 (283 points)
    Mac OS X
    Jul 21, 2016 6:05 PM in response to NorthTravler

    As Csound1 said: LSD/LaunchService does what it says. That is, launch the OSX and login items. It can be assumed that Apple took care of any problems that might come from launching OS X items. For that reason I think it is very likely that one or more third party product(s) cause the hangup of LSD. It may or may not be that only login items listed in the user preferences are effected. Some apps including LittleSnitch are loaded without being listed in the login items.

     

    Interestingly there was an Little Snitch update yesterday. But that may just be a correlation. There is currently no evidence that LittleSnitch is one of the problem apps. There is also no clear evidence that iStat is a problem app.

     

    It would be nice if somebody with a lot of OS X software knowledge would tell us in which log file we should look. Somewhere the lsd process must be logged. Perhaps that way we can find out the problem apps.

first Previous Page 4 of 10 last Next