Martin Montgomery

Q: Two iMacs will not boot after the 10.11.4 update.

Two iMacs will not boot after the 10.11.4 update.  Progress bar starts to move then text appears on the black screen saying unexpected sigkill of launchd.  It then gets stuck in a loop of trying to boot.  Tried resetting SMC and PRAM.  No success.  Booted into recovery mode and ran disk utility.  Drives reported OK.  Chose to reinstall OS X from the recovery mode option list (presume this would be 10.11.4).  Install completed but again fails to boot.  Reinstalled 10.11.0 successfully from a USB stick and downloaded the 10.11.4 combo updater.  The installation appears to work but again the macs will not boot.  Same "unexpected sigkill of launchd" error.  One mac is now back working properly with 10.11.3 the other will be shortly.  Is there a problem with the updaters?  Our IT support use Munki to push out updates overnight.  Thankfully we were able to stop this before the other 20 or so macs had the same problem.

iMac, OS X El Capitan (10.11.3)

Posted on Mar 22, 2016 8:44 AM

Close

Q: Two iMacs will not boot after the 10.11.4 update.

  • All replies
  • Helpful answers

first Previous Page 3 of 3
  • by Davert,

    Davert Davert Mar 26, 2016 4:51 PM in response to tom.francen
    Level 1 (5 points)
    Mar 26, 2016 4:51 PM in response to tom.francen

    I am not an expert but I would try disabling:

     

    • Kapersky
    • LogMeIn
    • Parallels

     

    Make sure XCode is up to date.  I don't have klif on my system as far as I can tell.

     

    If you can upgrade, get the LATEST versions and if you absolutely need them, reinstall.

     

    Oh, and make sure you are set to always boot in verbose mode so you can watch what is happening. I was going to video the boot so I could find the error messages.

  • by tom.francen,

    tom.francen tom.francen Mar 27, 2016 5:09 AM in response to Davert
    Level 1 (4 points)
    Mar 27, 2016 5:09 AM in response to Davert

    thanks davert ...

     

    while i could most certainly both uninstall and remove any of those listed .kext files, this seems like an exercise in *hackery* and not a methodical way to troubleshoot the root cause ... and having to revert to 10.11.3 each time i've tried updating, i think the only method would be to boot to a USB thumb drive and mount up the newly upgrade, yet not working 100%, 10.11.4  SSD ...

     

    after i'm able to mount up the 10.11.4 SSD, i would then need to know what log files to review to *hopefully* determine potential root cause(s) ...

     

    FYI:  i have logmein, parallels, and kapersky installed on the other 2 macs that updated to 10.11.4 just fine ...

  • by renaudManda,

    renaudManda renaudManda Mar 28, 2016 12:20 PM in response to Martin Montgomery
    Level 1 (4 points)
    Mar 28, 2016 12:20 PM in response to Martin Montgomery

    Just for people like me, if you got this kind of issue, just boot in "OS X Recovery mode", and then open a terminal (Tools>terminal).

     

    In the news terminal go to: "/Volumes/<HDD NAME>/Library/Extensions" and then remove (or move outside Library) "SUIDGuardNG.kext/".

     

    Reboot and it's done !

  • by tom.francen,

    tom.francen tom.francen Mar 29, 2016 2:18 AM in response to renaudManda
    Level 1 (4 points)
    Mar 29, 2016 2:18 AM in response to renaudManda

    1.  i downloaded the latest 10.11.4 combo update (just in case it was updated/changed)

    2.  installed ... update appears to take, requires a restart ... performed that

    3.  installation continued after the reboot ... offered up the BLACK SCREEN with CURSOR (attached picture #1)

    4.  performed your steps ... booted into recovery mode ... changed directory to the Ext library on the HD ... SUIDGuardNG.kext does not exist

    5.  restoring again (time #4) back to 10.11.3

    6.  once the restore back to 10.11.3 is complete, i'll dump my system information and attach that as well to the posting

     

    image2.JPG

    image1.JPG

  • by renaudManda,

    renaudManda renaudManda Mar 29, 2016 2:45 AM in response to tom.francen
    Level 1 (4 points)
    Mar 29, 2016 2:45 AM in response to tom.francen

    @tom.francen you're issue is different from mind. In my case after the initial reboot I got a Kernel Panic due to "SUIDGuardNG.kext".

    If you don't find "SUIDGuardNG.kext" it's probably because your trouble is different from mine.

     

    Renaud

  • by Mikrohelt,

    Mikrohelt Mikrohelt Apr 1, 2016 9:09 AM in response to Linc Davis
    Level 1 (8 points)
    Apr 1, 2016 9:09 AM in response to Linc Davis

    I have a similar problem with my 1 year old iMac 27", it failed to start after 10.11.4 download, and will not start in safe mode either (appears to boot - reaches end of progress bar and "freezes up"). Starting Disk Utility works, but it is unable to detect any volumes or start-up disk. Therefore unable to reinstall OSX. Any suggestions?

  • by Ender1978,

    Ender1978 Ender1978 Apr 1, 2016 1:37 PM in response to Mikrohelt
    Level 1 (0 points)
    Apr 1, 2016 1:37 PM in response to Mikrohelt

    Apole support directed me to restore my backup and wait for next update

  • by Mikrohelt,

    Mikrohelt Mikrohelt Apr 2, 2016 1:13 PM in response to Mikrohelt
    Level 1 (8 points)
    Apr 2, 2016 1:13 PM in response to Mikrohelt

    Problem solved after discussion with Apple support: disconnect power cable - reconnect - start with alt-cmd-R-P to clear everything, then connect ethernet cable (wi-fi not good enough) - Restart with cmd-alt-R - start Disk utility which then actually found the boot volume - restart with cmd-R and then reinstall OSX

    Reason for problem not really found, but procedure above solved problem.

  • by exanimaster,

    exanimaster exanimaster Apr 4, 2016 2:12 AM in response to Martin Montgomery
    Level 1 (4 points)
    Apr 4, 2016 2:12 AM in response to Martin Montgomery

    In my case, I am unable to login after I update my Mac to OS X 10.11.4. The login interface pops up, I enter my password and then a progress bar shows up, but it is stuck at 100%.

     

    Here is how I fixed it:

    1. Shutdown the Mac.
    2. Turn on Mac while pressing and holding Cmd + R to enter Recovery mode.
    3. On Recovery mode interface, open Disk Utility.
    4. If your drive is encrypted, click on the "Macintosh HD" from left tab, then choose File > Unlock.
    5. Enter the encryption password.
    6. Choose Disk Utility > Quit Disk Utility.
    7. Choose Utilities > Terminal.
    8. Inside the terminal window, enter the following command, press ENTER at the end of each line:
      cd /Volumes/Macintosh\ HD/Library/Extensions
      mkdir Unsupported
      mv *.kext Unsupported/
    9. Choose Terminal > Quit Terminal.
    10. Restart the Mac.

     

    Yes, in case you have not noticed, I tried to move some kext (kernel extension) files into a new folder, because I suspect that these kext files are causing issues with the new OS X 10.11.4.

     

    Hopefully it helps!

  • by star-affinity,

    star-affinity star-affinity Apr 28, 2016 3:42 AM in response to Martin Montgomery
    Level 2 (483 points)
    Apr 28, 2016 3:42 AM in response to Martin Montgomery

    Two computers at work would fail to boot after users tried to apply the 10.11.4 update onto 10.11.3.

     

    No SUIDGuardNG.kext present.

     

    Maybe there's an easier fix, but what helped in both cases involves having another Mac running OS X El Capitan (that you can startup into) and a Thunderbolt cable (to connect between two newer Mac) or a FireWire 800 cable (to connect between two older Macs).

     

    Do like this:

     

    1. Startup the Mac that has startup problems and immediately hold down the ”T” key on the keyboard. After some seconds you should see a Thunderbolt and/or FireWire icon on the screen. This is called starting into ”taget disk mode”. More info on this here: https://support.apple.com/kb/PH10725?locale=en_US This should make the drive of the problematic computer show up on the working Mac.
    2. Just in case it might be worth running ”First Aid” on the startup drive of the problematic Mac using Disk Utility (/Applications/Utilities/Disk Utility.app).
    3. Download the OS X 10.11.4 Combo Updater from Apple's website: https://support.apple.com/kb/DL1869?locale=en_US
    4. Run it and apply it on the drive of the problematic computer (make sure you change the correct target driver there in the installer as it will default to the drive of the currently used Mac).

     

    IMPORTANT: you have to have OS X 10.11 El Capitan running on the working computer, otherwise it will say that you can't run the Combo Updater since it requires El Capitan. There is a workaround for this that involves using the the software Pacifist, but I won't go into that here.

  • by Stalnoff,

    Stalnoff Stalnoff May 12, 2016 3:46 PM in response to exanimaster
    Level 1 (4 points)
    May 12, 2016 3:46 PM in response to exanimaster

    Many thanks! Its really helps!

first Previous Page 3 of 3