robertk1

Q: Fix for El Capitan stuck at login

Last month I updated to 10.11.1 and my system would no longer log in.  I would enter my password correctly and then the cursor would change to the spinning pinwheel and just sit there forever.  The only way out was a power off reboot.  I later found that when it was in this state I could SSH into it from another machine, and the system log revealed that /usr/libexec/lsd (the Launch Services Daemon) was crashing repeatedly.  I searched these forums and others and found lots of ideas, none of which helped. 

 

No problem, though, I've got hourly time machine backups, right?  Well, no.  Apparently El Capitan had not been doing the hourly backups so my most recent backup was from sometime in October, which was a month old at the time.  Not good.

 

Fortunately, I had an older boot drive that I put in an external enclosure and was able to boot from that to experiment.  The drive I normally boot from was fine -- permission checks and disk repair and all that all came back good, and I could read and write files to it just fine.

 

After lots of experimentation and frustration I was just about to give up and add another drive to do a clean install and start moving everything over -- a process that I *really* hate doing.  But one last web search and a bit of luck gave my one last shot at fixing it.

 

To do this, you'll either need to be in a recovery console, or ssh into the machine, or boot from an external drive, or otherwise somehow get to a command prompt.  Once you are there, do this:

 

find /private/var/folders/ | grep com.apple.LaunchServices | grep csstore

 

Note that if you boot from an external drive, you need to run that command against the boot drive you are trying to fix.  Just add the /Volumes/Whatever_Your_Boot_Drive_is to the path, like so:

 

find /Volumes/YourBootDriveHere/private/var/folders/ | grep com.apple.LaunchServices | grep csstore

 

That will find the cache databases that Launch Services is using.  They will have long and random-looking names that end in csstor.  Make a note of every file shown, then delete them, by a command like this (obviously using whatever paths the above command found instead of this example):

 

rm  /private/var/folders/cd/someLongRandomNameHere/someFolderNumberHere/com.apple.L aunchService-whatever.csstore

 

If you're more cautious, you can rename them instead of deleting them, so you can put them back if necessary.  That would look like this:

 

mv  /full/path/like/shown/above/to/whatever.cssstore /full/path/like/shown/above/to/whatever.csstore.backup

 

After removing or renaming those files, restart your Mac.  You should now be able to log in.  Or at least, that's what finally worked for me.  The login did take longer than normal -- a few minutes -- to rebuild those files, but the desktop finally appeared, and now I'm back to running on my normal boot drive. 

 

Hopefully this helps someone.

Mac Pro, OS X El Capitan (10.11.2)

Posted on Dec 13, 2015 3:47 AM

Close

Q: Fix for El Capitan stuck at login

  • All replies
  • Helpful answers

first Previous Page 3 of 6 last Next
  • by hijoncon,

    hijoncon hijoncon May 20, 2016 8:57 AM in response to robertk1
    Level 1 (4 points)
    May 20, 2016 8:57 AM in response to robertk1

    Thanks for your post, even apple don't know this fixed. BTW if your Guest Account is on.

    Another way to fixed without pulling out the hard drive.

     

    Follow this below:

     

    1. Login as guest
    2. Open Terminal (cmd + space then search terminal)
    3. enter su "your_account"
    4. enter your password
    5. sudo find /private/var/folders/ | grep com.apple.LaunchServices | grep csstore
    6. sudo rm /private/var/folders/cd/someLongRandomNameHere/someFolderNumberHere/com.apple.L aunchService-whatever.csstore
  • by pwp69,

    pwp69 pwp69 May 21, 2016 4:24 AM in response to robertk1
    Level 1 (4 points)
    May 21, 2016 4:24 AM in response to robertk1

    Thanks so much for this robertk1!

    hijoncon, Guest Account trick worked a treat - thank you.

     

    Sort this out Apple - it's a disgrace!

  • by ranpun,

    ranpun ranpun May 21, 2016 6:51 PM in response to robertk1
    Level 1 (8 points)
    Mac OS X
    May 21, 2016 6:51 PM in response to robertk1

    I had the same issue while updating from 10.11.4 to 10.11.5. I had to Sign in via guest log in, delete my original log in because no matter what I did, it would not let me in! Made a new administrator account and moved the files over.

  • by kakarox,

    kakarox kakarox May 22, 2016 2:32 AM in response to robertk1
    Level 1 (4 points)
    May 22, 2016 2:32 AM in response to robertk1

    Hi

    I had the same problem

    Logged in as a guest user and used terminal

    to remove al the directories mentioned

    use sudo rm -d  /private/var/folders/the name of the folders


    regards

    cvr

  • by OneTone,

    OneTone OneTone May 22, 2016 7:29 AM in response to robertk1
    Level 1 (4 points)
    May 22, 2016 7:29 AM in response to robertk1

    @robertk1

    Thank you bro.

    You saved my life!

  • by jimcdps,

    jimcdps jimcdps May 23, 2016 7:58 PM in response to robertk1
    Level 1 (4 points)
    May 23, 2016 7:58 PM in response to robertk1

    Simply Brilliant..

    Thank you SO MUCH!

    I am a new MacBook Pro User, and was getting really frustrated.

    Finding this post saved me!

  • by Joel Smith2,

    Joel Smith2 Joel Smith2 May 24, 2016 1:43 PM in response to robertk1
    Level 1 (4 points)
    Mac OS X
    May 24, 2016 1:43 PM in response to robertk1

    I am a novice, at best, when it comes to Terminal.  When I enter the command, I get the response of "no such file or directory". I feel like I'm entering the text after /folders/ wrong. Can anyone help?  Is there a space and then the letter "I" or is that a vertical slash, or something else? I've tried it both ways, but I still get the same error.

    I Wish I could just copy/paste but the computer with the problems isn't working, obviously.

     

    Thanks in advance.

  • by pwp69,

    pwp69 pwp69 May 24, 2016 2:24 PM in response to Joel Smith2
    Level 1 (4 points)
    May 24, 2016 2:24 PM in response to Joel Smith2

    i'm also a novice but with some patience worked it out. copy and paste this line 'as is' into terminal and enter:

     

    sudo find /private/var/folders/ | grep com.apple.LaunchServices | grep csstore

     

    copy the list that is revealed in terminal into textedit, then copy and paste the line below into terminal, copy each line from textedit (one at a time) and paste directly after sudo rm / and run each line one at a time.


    sudo rm /


    example:


    sudo rm /private/var/folders/cd/blahblahblah/blahblahblah.csstore

  • by SimonAntony,

    SimonAntony SimonAntony May 25, 2016 2:06 AM in response to pwp69
    Level 1 (8 points)
    May 25, 2016 2:06 AM in response to pwp69

    In reply to the previous two posts, the | symbol is the pipe symbol on your keyboard, just above the enter key. Took me a couple of tries to work it out, now back to trying to fix my login problem which is still spinning

  • by elchurles,

    elchurles elchurles May 25, 2016 3:51 AM in response to hijoncon
    Level 1 (4 points)
    May 25, 2016 3:51 AM in response to hijoncon

    Thanks for this summary and alternative option. This is the one that worked perfectly for me!

    I have got this problem with El Capital 10.11.5.

    Fortunatly for me Guest user was still functional so I was able to execute the procedure that, as I said, worked like charm.

    Amazing that Apple is not able to address this issue after more than two years!!

     

    Thanks again to all the community.

    elchurles

  • by Joel Smith2,

    Joel Smith2 Joel Smith2 May 25, 2016 10:36 AM in response to pwp69
    Level 1 (4 points)
    Mac OS X
    May 25, 2016 10:36 AM in response to pwp69

    Thanks, pwp69, your "patience" suggestion helped.  I finally figured out that since my boot drive has spaces in it's name, "Mac Pro 3 HD" I have to use the backslash and a 'space' when typing the 'space' into Terminal.   /Mac\ Pro\ 3\ HD/

    Unfortunately, it didn't help my situation.  I ended up installing a fresh copy of El Capitan on a new drive and starting from scratch.

     

    And SimonAntony, thanks for the 'pipe' character clarification. Now I know for next time.

     

     

    Joel

  • by SimonAntony,

    SimonAntony SimonAntony May 25, 2016 3:11 PM in response to SimonAntony
    Level 1 (8 points)
    May 25, 2016 3:11 PM in response to SimonAntony

    Just to update the thread, this fix worked for me too, however I needed to sudo as the user I wanted to fix, once I did I found all the dodgy files, renamed, rebooted and was able to log in fine :-)

  • by jansvarovsky,

    jansvarovsky jansvarovsky May 26, 2016 8:23 AM in response to robertk1
    Level 1 (4 points)
    May 26, 2016 8:23 AM in response to robertk1

    Thanks this worked perfectly for me too (OSX El Capitan)! And the login didn't even take that long afterwards.

     

    I ran the command you suggested from single-user mode after having mounted the file system as read/write.

  • by DMC440,

    DMC440 DMC440 May 30, 2016 3:17 PM in response to robertk1
    Level 1 (4 points)
    May 30, 2016 3:17 PM in response to robertk1

    This happened with 10.11.5 for me.  I searched but didn't discover this post until the Genius showed me. Turns out they just google until they find something that works.  I think it also happened to me with 10.11.1 but I just did a complete reinstall that time.  Now I know better.  Thanks for your efforts.

  • by idrojas,

    idrojas idrojas Jun 3, 2016 1:00 PM in response to robertk1
    Level 1 (4 points)
    Jun 3, 2016 1:00 PM in response to robertk1

    Genius.

first Previous Page 3 of 6 last Next