Beowolfs

Q: El Capitan update 10.11.1 freezes at login

I'm Unable to log into El Capitan after installing the update.  Once I type my password, the cursor turns into the beachball and never logs in.

I have to press the power button until the system turns off.  Funny thing is, once at the log-on screen I can select restart or shut down. However if I try signing in, its all over.

I can't believe this! Rather than fixing problems it created a huge one for me! I don't want to re-install the OS or start with another Fresh install.

 

Any solutions would be much appreciated. 

Mac Pro, OS X El Capitan (10.11), 2012 Mac Pro 5,1

Posted on Oct 22, 2015 7:36 PM

Close

Q: El Capitan update 10.11.1 freezes at login

  • All replies
  • Helpful answers

  • by blueCdreams,

    blueCdreams blueCdreams Oct 22, 2015 10:40 PM in response to Beowolfs
    Level 1 (9 points)
    Mac OS X
    Oct 22, 2015 10:40 PM in response to Beowolfs

    Do you have external HD backup from which to restart? If so, turn off MacPro and let it sit for 30 seconds, then restart with option key depressed and boot up the external drive, when the icons of the drives appear on the screen. I have both, Yosemite and ElCapitan clones on ext HD just for this type of situation. Also use Drop Box & iCloud for b/u.

  • by Beowolfs,

    Beowolfs Beowolfs Oct 23, 2015 6:35 AM in response to blueCdreams
    Level 1 (0 points)
    Oct 23, 2015 6:35 AM in response to blueCdreams

    Thanks for the reply.

    I do have a cloned backup, but its missing a ton of programs I've installed since El Capitan's fist installation not to mention documents and other changes live made.  But it looks like that's my only best option.

    Booting in safe mode didn't help either.  It repeated the same behavior.

    Honestly, I've experienced so many small problems with OS X 10.11 that I thought of just going back to my trusty Mountain lion.

     

    Thanks BlueCdreams

  • by mfuhrer,

    mfuhrer mfuhrer Oct 23, 2015 8:23 PM in response to Beowolfs
    Level 1 (0 points)
    Oct 23, 2015 8:23 PM in response to Beowolfs

    I have exactly the same problem after the OS X 10.11.1 upgrade. Can no longer log in to my primary user account. Fortunately I have a Guest account on the login screen that I can log into with no issues. From the Guest account I can open up a Terminal session and look at the diagnostic logs (from the terminal I need to "su - username" to login to my primary account, and then do "cd ~/Library/Logs/DiagnosticReports" and "ls -lt" to view the names of the logs ordered by most recent.  Here I see a number of crash reports with time stamps matching the time of my unsuccessful login. They all contain similar content and point to a problem with /usr/libexec/lsd. Not sure what to make of this at the moment but thought I'd post in case other users are observing the same thing.

     

    [Eve.local] more lsd_2015-10-23-071952_Eve.crash

    Process:               lsd [697]

    Path:                  /usr/libexec/lsd

    Identifier:            lsd

    Version:               728.4

    Code Type:             X86-64 (Native)

    Parent Process:        ??? [1]

    Responsible:           lsd [697]

    User ID:               501

     

    Date/Time:             2015-10-23 07:19:51.315 +0400

    OS Version:            Mac OS X 10.11.1 (15B42)

    Report Version:        11

    Anonymous UUID:        3BC9B386-5784-71EE-A925-588400691133

     

     

    Time Awake Since Boot: 690 seconds

     

    System Integrity Protection: enabled

     

    Crashed Thread:        0  Dispatch queue: com.apple.main-thread

     

    Exception Type:        EXC_BAD_ACCESS (SIGSEGV)

    Exception Codes:       KERN_INVALID_ADDRESS at 0x0000000109d33958

    Exception Note:        EXC_CORPSE_NOTIFY

     

    VM Regions Near 0x109d33958:

        Dispatch continuations 0000000108c00000-0000000109c00000 [ 16.0M] rw-/rwx SM=PRV 

    -->

        mapped file            000000010a1df000-000000010baf0000 [ 25.1M] r--/r-x SM=ALI 

     

    Thread 0 Crashed:: Dispatch queue: com.apple.main-thread

    0   com.apple.LaunchServices            0x0000000102d5ba4d _LSClaimRemove + 327

    1   com.apple.LaunchServices            0x0000000102d5a6bc _LSBundleRemove + 277

    2   com.apple.LaunchServices            0x0000000102d7a8dc _LSServerItemInfoRegistration + 1905

    3   com.apple.LaunchServices            0x0000000102d76d0e _LSDispatchRegistration(LSContext*, char const*, LSRegistrationInfo*, __CFData const*, __CFData const*, __CFData const*, __CFURL const*, __CFDictionary const*, unsigned int*, __CFArray**, unsigned char*) + 212

    4   com.apple.LaunchServices            0x0000000102d072f1 _LSRegisterDirectoryNode(LSContext*, FSNode*, FSNode*, LSRegistrationInfo*, __CFData const*, __CFDictionary const*, __CFArray**, unsigned char*, unsigned int*) + 86

    5   com.apple.LaunchServices            0x0000000102d07040 _LSRegisterBundleNode(LSContext*, unsigned int, FSNode*, FSNode*, unsigned int, __CFDictionary const*, __CFArray**, unsigned char*, unsigned int*) + 863

    6   com.apple.LaunchServices            0x0000000102cd5749 _LSFindOrRegisterBundleNode + 912

    7   com.apple.LaunchServices            0x0000000102d5fa06 _LSDatabaseClean(LSDatabase*) + 456

    8   com.apple.LaunchServices            0x0000000102d5f2bd _LSDatabaseCreateFromPersistentStore + 225

    9   com.apple.LaunchServices            0x0000000102d3d935 -[LSDatabaseBuilder createAndSeedLocalDatabase:] + 53

    10  com.apple.LaunchServices            0x0000000102d0a409 -[LSServerDelegate beginListening] + 172

    11  com.apple.LaunchServices            0x0000000102d0c056 _LSServerMain + 175

    12  libdyld.dylib                       0x0000000103ccd5ad start + 1

  • by Beowolfs,

    Beowolfs Beowolfs Oct 23, 2015 9:24 PM in response to mfuhrer
    Level 1 (0 points)
    Oct 23, 2015 9:24 PM in response to mfuhrer

    This has me scratching my head.

     

    After experiencing the problems of not being able to log in, I decided to use super duper to clone the drive before formatting it. Reason is, I have many documents, photos, etc that I could still retrieve by booting to a drive that contains Mountain Lion.

     

    Once I cloned the defunct El Capitan drive, I decided just for kicks to boot from from the clone.  Guess what... After signing  in, I got the beach ball for about 3 seconds then it continued onto a grey screen asking to join to my iCloud account. After typing my credentials, It proceeded to try and join with iCloud and it hung/froze once more. Once again,  I shut down the computer and re-started it  This time however, after signing in, it went straight to the desktop without any problems.

     

    Over the past couple of hours I've restarted, shut down, logged off many times to test the integrity.  It works perfect. So I cloned the drive back onto the original.  Before you ask why do so? The original drive are 2 SSD's in Raid 0 mounted on a PCIe board.

    Once Superduper was done I removed the clone drive and booted from Raid.  It works perfect.

    Now... If only I could solve the problem with Handoff not working all would be well!

  • by steamio,

    steamio steamio Oct 24, 2015 1:47 AM in response to mfuhrer
    Level 1 (0 points)
    Oct 24, 2015 1:47 AM in response to mfuhrer

    mfuhrer, I'm having the same issue and really don't feel like installing from scratch.

    Did you get pass this?

    Really annoyed with apple lately.

  • by mfuhrer,

    mfuhrer mfuhrer Oct 24, 2015 10:55 PM in response to Beowolfs
    Level 1 (0 points)
    Oct 24, 2015 10:55 PM in response to Beowolfs

    Beowolfs, thanks for your interesting (and puzzling) observations about resolving the login with the Superduper clone. Like steamio, I'm not quite ready to wipe my drive and copy over a clone, so I tried an alternative approach. From my Guest account, I downloaded the El Capitan 10.11.1 update once more and tried reinstalling. No luck - I still got the endless spinning beach ball when I try to log in to my primary account.  Did a hard reboot and went back into the Guest account, and confirmed from the Terminal that "/usr/libexec/lsd" was still crashing at login. Then I noticed that I still had the original El Capitan installer (the 10.11.0 release) in my Applications folder. I tried running this, and the installer proceeded to install the original release. After this downgrade, I am now able to log in to my primary account with no problem.

     

    I will probably wait until the 10.11.2 release to try the upgrade again. If the upgrade locks me out of my primary account, I may go ahead and try the cloning solution. I have to agree that the promises of increased stability of El Capitan leave a lot to be desired...

  • by bartis2,

    bartis2 bartis2 Oct 30, 2015 8:10 AM in response to mfuhrer
    Level 1 (0 points)
    Oct 30, 2015 8:10 AM in response to mfuhrer

    Would you happen to have a way to share your 10.11.0 software?

  • by bartis2,

    bartis2 bartis2 Oct 30, 2015 8:33 AM in response to bartis2
    Level 1 (0 points)
    Oct 30, 2015 8:33 AM in response to bartis2

    mfurher, Would you happen to have a way to share your 10.11.0 software?

  • by bartis2,

    bartis2 bartis2 Oct 30, 2015 2:27 PM in response to mfuhrer
    Level 1 (0 points)
    Oct 30, 2015 2:27 PM in response to mfuhrer

    mfuhrer, I had the exact same issue with /usr/libexec/lsd.  It appears to have been related somehow to my password for iCloud account being the same as the one being used for my primary OS X account.  I called Apple support and they had me change the password for my OS X account which freed me up from getting the spinning beach ball; however, it kept kicking me back out to the login screen whenever i tried to login.  I kept fooling around with it until I finally got it to work.

     

    I went did the following:

    1. Went System Preferences->Users and Groups. 

    2. Right-clicked on the primary user account and clicked Advanced Options. 

    3. Selected "Change" for the Apple ID and removed the Apple ID shown. 

    4. Clicked "Ok" and went back into the Advanced Options settings to make sure it was indeed gone. For good measure, I changed the UUID as well. 

     

    I then tried to login to my primary account and voila, it worked!  I had been working on this thing all night long as I didn't have a good Time Machine backup.  I did however clone my drive last night just in case I needed it as a fallback to salvage my documents, pictures, music, etc.  So I am running 10.11.1 and will NEVER update again without BACKING UP FIRST!

     

    I hope this helps someone else that comes across this issue.  This one had me going for a while...

  • by RobPH,

    RobPH RobPH Dec 14, 2015 10:18 AM in response to bartis2
    Level 1 (0 points)
    Dec 14, 2015 10:18 AM in response to bartis2

    Thanks that did the trick!

    First I removed the Apple ID but that didn't fix it, then I also redid the UUID and it worked.

  • by scuc,

    scuc scuc Jan 21, 2016 8:16 PM in response to bartis2
    Level 2 (355 points)
    Jan 21, 2016 8:16 PM in response to bartis2

    bartis2,

    i had the exact same issue with the lsd process on login.

    thank you for posting this solution, it totally fixed my issue!!

  • by toddhamilton,

    toddhamilton toddhamilton Jan 26, 2016 4:35 PM in response to scuc
    Level 1 (0 points)
    Jan 26, 2016 4:35 PM in response to scuc

    I experienced a similar lsd crash, even on accounts w/o iCloud associated with them, and I was having problems launching applications:

     

    Re: El Capitan: You can't open the application 'app name' because it may be damaged or incomplete