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 6 of 6
  • by imrajan,

    imrajan imrajan Aug 14, 2016 11:22 PM in response to wizbang_fl
    Level 1 (4 points)
    Aug 14, 2016 11:22 PM in response to wizbang_fl

    Sir,

     

    I'm facing same issue. So, I follow steps provided by you, I'm unable to remove or move that launch services files.

    Its giving me error : Read Only File System.

     

    Can you please suggest me for further,

     

    Regards,

    Rajan

  • by Lindauson,

    Lindauson Lindauson Aug 17, 2016 6:55 AM in response to robertk1
    Level 1 (4 points)
    Aug 17, 2016 6:55 AM in response to robertk1

    Thank you Robert, this really helped me!

  • by telracs79,

    telracs79 telracs79 Aug 17, 2016 6:19 PM in response to robertk1
    Level 1 (4 points)
    Aug 17, 2016 6:19 PM in response to robertk1

    Confirmed this works on 10.11.5

     

    Thanks robertk1!!

  • by epr329,

    epr329 epr329 Aug 21, 2016 9:33 PM in response to robertk1
    Level 1 (4 points)
    Aug 21, 2016 9:33 PM in response to robertk1

    i'm having the same issue with 10.11.6 but deleting the launch file thing didn't help. I also tried reinstalling the OS to no avail. I can't even get to time machine in terminal. Getting the following error:

    "-bash: tmutil: command not found".

     

    i'd go to the Apple Store but my applecare just ran out at the end of July and I have the mid-2012 version so they'll likely charge me some ridiculous amount to get it fixed.

     

    any ideas on what I can else I can do? Can't afford a new computer at the moment and even if I could, I can't even backup the latest stuff to time machine.

     

    UPDATE: I gave up and decided to restore from my last backup (1 month ago) which was 10.11.5. Anything ive done since then should be pretty easy to recover/recreate. Hopefully this will fix it.

     

    <Edited by Host>

  • by smulvey7272,

    smulvey7272 smulvey7272 Aug 22, 2016 7:28 AM in response to epr329
    Level 1 (4 points)
    Aug 22, 2016 7:28 AM in response to epr329

    same issue here, still having issues here.  HOWEVER you can still backup your files by starting in safe mode.  restart computer holding down shift key.  I did 2 backups one of just my stuff, video, pics, docs, etc AS well as a full backup.  still trouble shooting not sure if it is a certain program causing the issue.  I had a guy look at this weekend (8 years at Apple as genius).  He believes my issue (since I have done all of the above) may be related to hardware issue.  While at the moment I do no have full use of computer is safe mode I can access files and most programs.

  • by dwathen,

    dwathen dwathen Aug 23, 2016 7:28 PM in response to robertk1
    Level 1 (8 points)
    Aug 23, 2016 7:28 PM in response to robertk1

    Awesome work and thanks. I tried to upgrade late last year and it failed so i rolled back. I then did some cleanups and tried again the other day. My login got stuck but other users were OK.

     

    I ran the above commands and just moved the 2 csstor files that my account owned and it logged back in fine.

  • by AppleMoeller,

    AppleMoeller AppleMoeller Sep 4, 2016 3:48 PM in response to robertk1
    Level 1 (4 points)
    Sep 4, 2016 3:48 PM in response to robertk1

    I had the same issue with 10.11.6 after the latest security update. Your solution work fine for me (only issue was a german keyboard )! I didn't need to reinstall anything, everything was ok after a reboot.

     

    Thank you so much for this solution.

  • by AppleMoeller,

    AppleMoeller AppleMoeller Sep 4, 2016 3:53 PM in response to imrajan
    Level 1 (4 points)
    Sep 4, 2016 3:53 PM in response to imrajan

    You need to set your root harddrive to read & write first. If you started your Mac in single user mode (using cmd-s after pressing the start button) the hdd is set to read only, but the shell tells you the command for setting it to read&write

    • /sbin/fsck -fy
    • /sbin/mount -uw /

    Hope that helps, it does with me.

  • by wizbang_fl,

    wizbang_fl wizbang_fl Sep 7, 2016 11:28 PM in response to Steve Dutton
    Level 1 (86 points)
    Sep 7, 2016 11:28 PM in response to Steve Dutton

    In my case I tracked it down to a piece of software I had installed that was not updated since Mavericks.  I needed to continue to use it for some tasks (I already use Parallels for VM of Windows) so setup a OS X VM for the legacy programs that I still need but that don't have an update compatible with 10.11 

     

    I haven't had the issue since I updated, removed, or moved the software that was out of date to a VM.

  • by RogerDennis,

    RogerDennis RogerDennis Sep 16, 2016 7:55 PM in response to robertk1
    Level 1 (4 points)
    Sep 16, 2016 7:55 PM in response to robertk1

    When you say casually "I hope this helps someone" you are being the Master of the Understatement.  I swear that if you were in the same room as me right now I'd hug you.  I've spent four hours trying to solve this issue, and was on the verge of a clean install when I found your post.  You are a goddam GENIUS - and a generous one too.  Thanks so much...

  • by w00dy788,

    w00dy788 w00dy788 Sep 18, 2016 2:36 AM in response to robertk1
    Level 1 (4 points)
    Sep 18, 2016 2:36 AM in response to robertk1

    thanks robertk1!!

     

    gosh! tried to run disk utility in recovery mode, safe boot the mac, file system consistency checks.. all up to no effects. was about to restore the mac from previous backups until i stumbled on this post. thanks again for sharing and u just save my 'life', literally ..

     

    the reply from @hijoncon is helpful too.. =D

  • by donpedro,

    donpedro donpedro Sep 21, 2016 2:05 PM in response to w00dy788
    Level 1 (4 points)
    Sep 21, 2016 2:05 PM in response to w00dy788

    The REAL question is how come Apple did not take action to come up with a fix? Unpleasant question, right?

     

    Luckily I had a guest account that I could access after several boots which let me open a terminal window, change user to root and then used SUDO with the commands robertk1 listed.

    Worked like a charm. YOU DA MAN!

first Previous Page 6 of 6