Looks like no one’s replied in a while. To start the conversation again, simply ask a new question.

crashed: too many corpses being created

After installing a Yosemite update on my laptop, when it boots, it seems to all be fine until about the loading bar is maybe 2/3 done, then slows to a crawl and takes another 20 minutes or so to reach full - where it stays. I have no cursor or anything else during this time, but my caps lock button light will go on an off when I press it.

I've tried:
-Resetting PRAM/NVRAM
-Booting into recovery mode and repairing the drive/partition. This seemed to be done successfully.
-Booting hardware diagnostics and doing a check. It says everything is fine.
-Safe boot. Takes the same length of time and hangs at the same place, so honestly not sure if I'm even doing it right.
-Verbose mode says every single process has crashed, with 'too many corpses being created.'. (picture - note that it's not actually blurry, just scrolling pretty fast so a photo wasn't the best)

It's a Mid-2011 15" Macbook pro, 2.2GHz with a 750GB hard drive and 16GB of RAM. I'm still doing a few other checks (currently re-installing 10.10 using a thumb drive to see if that fixes it), but has anyone got any ideas or had a similar problem?

MacBook Pro (15-inch Early 2011), OS X Yosemite (10.10.3)

Posted on Jun 27, 2015 2:24 PM

Reply
Question marked as Best reply

Posted on Apr 13, 2018 8:19 AM

So, here is the latest solution from Apple:


  1. Restart your Mac and hold down Command-R tostart up from macOS Recovery.
  2. If the startup drive has FileVault turned on, open Disk Utility and proceed with the next step. If FileVault is off, skip to step 5.
  3. Select the startup drive and click Mount in the Disk Utility toolbar. When prompted, select a login name and enter the password. Then click Unlock to mount the startup drive.
  4. Quit Disk Utility.
  5. Choose Utilities > Terminal from the menu bar.
  6. Type this command in Terminal:cd /Volumes/Macintosh\ HD/var/db/caches/opendirectory/
    Modify the command to reflect the name of the startup volume if it's not Macintosh HD. Remember to use an escape character \ before each white space in the command path.
  7. Press Return.
  8. Type this command in Terminal:mv ./mbr_cache ./mbr_cache-old
    The mv Terminal command is safer than the rm command. Errant white space in an rm command can destroy the user's data.
  9. Press Return.
  10. Quit Terminal.
  11. Choose Apple () menu > Restart.

The first startup after running these commands takes longer than usual as the cache is recreated. Subsequent startups will take the normal amount of time.

Hope this will help you 🙂

Frank

76 replies

Jan 3, 2018 5:14 PM in response to Zcomuto

So I had the same issue. Tried everything in the book while booting it up in verbose mode. Eventually, while trying to Reset PRAM, change boot options, reinstalling MacOS, etc, the command line in verbose mode said something along the lines of “ran out of...” at around 200 or so logs of “too many corpses created” and after that it started up like normal. Hope this helps

Jan 4, 2018 7:41 AM in response to Zcomuto

same problem

I've tried:

-Resetting PRAM/NVRAM

-Booting into recovery mode and repairing the drive/partition. This seemed to be done successfully.

-Booting hardware diagnostics and doing a check. It says everything is fine.

-Safe boot. Takes the same length of time and hangs at the same place, so honestly not sure if I'm even doing it right.

-Verbose mode says every single process has crashed, with 'too many corpses being created.

nothing happened....

Do you resolve this problem?

Jan 4, 2018 9:44 AM in response to ciamine

This path is under OS Yosemite. I have had the problem about one month ago, when I posted for the first time here, under OS High Sierra. The symptoms are the same everywhere, you do it right, I think, it is not solvable in my opinion. You will have to recover via Time Machine as I did. It's a shame on Apple.

By the way I wish to point out that I normally am a safe user, that means I make a backup before updating the OS to a new one (and after) with Time Machine. But the problem is particularly insidious because, at least in my case, it let 15 days pass without issues, and then (I believe after the infamous obligatory safety update) it struck! So I lost 15 days because I just connect my external Time Machine disk every ... you have guessed, 15 days! (this is a typical Murphy's law effect: it struck the day before my planned Time Machine backup). 👿

Regards

Claudio

Jan 9, 2018 12:08 PM in response to ciamine

I solved it 🙂, thanks to all who contributed to this thread, it really helped me, especially that I hate dealing with computer issues, and that I switched from PC to Mac mostly because I did not want to lose my time with blue screens and system failures.


I have a late 2009 iMac. For 8 years it has worked properly, and I am always updating quickly to new OS and patches. Last saturday, the computer was stuck on the grey/white screen with the Apple logo, with a bar progressing very slowly... and never completing. I tried everything I could find on the web, including this list (reset NVRAM, recovery mode, etc.). Safe boot never worked, and I sat like a fool pressing the key forever because I was not sure.


"Too many corpses being created" looping in the Verbose mode. I thought my hard drive was dead - an 8 year old mac could be obsolete right? But this was not a hardware issue.


I've been backing up with Time Machine on an external hard drive since 8 years, and never had to actually use Time Machine. So my last chance was to restore a backup from Time Machine.


CMD+R (with a bluetooth keyboard, wait for the Apple Chimes, press CMD+R and you can check it is working because the green led on the keyboard is flashing)


Interesting enough, I noticed in my time machine backup list that I updated to 10.13.2 in the night between Jan 4th and Jan 5th. I had forgotten - updates always working seamlessly.


I then found out I used the computer on the 5th, shut it down and all my issues came when I tried to open it again.


So I REALISED 10.13.2 WAS ACTUALLY THE ISSUE. For sure.


Recovered to my last time Machine backup under 10.13.1... and everything works perfectly fine again.


I kissed myself for using time machine, and promised myself to wait 6 months before updating my iMac in the future.

Jan 12, 2018 6:55 PM in response to Zcomuto

This is how I fixed it. I called apple support and they did jack for me. Told me to trouble shoot everything I already did.

safe boot, pram/nvram reset, recoverymode, yada yada yada. So after wasting time with them I realized I had to do it on my own. The stakes were high because I have no back ups or Time Machine stuff. I have a 2012 13" mac book pro.


So here is what I did. I made a partition on my hard drive with the disk utility on recovery mode. Only big enough to install a base operating system on the partition. "5gbs" Restarted the computer and back to recovery mode / disk utility. I then installed the operating system on my external hard drive. After the install, I started a new account on my external hard drive. I merged all my information from my old hard drive using migration assistant on to my external hard drive. After I had all my files and accounts that I still wanted, I then wiped and restored my old hard drive with my external hard drive. Basically returning my hard drive back to how it was before the dreaded "too many corpses being created" Boom, and thats how I saved my files with no back up.

-Good luck everyone. Took me like a day to figure out. Hopefully this will speed up the process for you.

-Maxx

Jan 12, 2018 7:03 PM in response to vinsticks

This is how I fixed it. I called apple support and they did jack for me. Told me to trouble shoot everything I already did.

safe boot, pram/nvram reset, recoverymode, yada yada yada. So after wasting time with them I realized I had to do it on my own. The stakes were high because I have no back ups or Time Machine stuff. I have a 2012 13" mac book pro.


So here is what I did. I made a partition on my hard drive with the disk utility on recovery mode. Only big enough to install a base operating system on the partition. "5gbs" Restarted the computer and back to recovery mode / disk utility. I then installed the operating system on my external hard drive. After the install, I started a new account on my external hard drive. I merged all my information from my old hard drive using migration assistant on to my external hard drive. After I had all my files and accounts that I still wanted, I then wiped and restored my old hard drive with my external hard drive. Basically returning my hard drive back to how it was before the dreaded "too many corpses being created" Boom, and thats how I saved my files with no back up.

-Good luck everyone. Took me like a day to figure out. Hopefully this will speed up the process for you.

-Maxx

Jan 14, 2018 3:26 AM in response to The Sticky bandit

Thank you, this helped me so much. I tried everything for an entire day and finally, I got my photos and documents back!


I have a question though: “I then wiped and restored my old hard drive with my external hard drive. Basically returning my hard drive back to how it was before the dreaded "too many corpses being created" Boom, and thats how I saved my files with no back up.”


How did you wipe the old drive and did you not install the same version of iOS that gave you the problems in the first place?

Jan 31, 2018 3:05 PM in response to Zcomuto

Had the same issue. Tried everything, even reinstalling the OS again (not deleting data) and it didn't help. I solved it by installing the os on an external HD through the recovery of mac (cmd+r on startup), booting my mac from that external HD, retrieving my data (with Migration Assistant), then deleting my internal HD, reinstalling the OS there, and migrating again from the external HD to the internal HD. Took me endless hours because the drives aren't SSD, but I finally managed to boot to my mac without being stuck after the login with almost no data loss. Hope that helps.

Feb 5, 2018 3:15 PM in response to Zcomuto

I have the same problem with the new osx high sierra update installed. i took it to apple and they reinstalled the operating system and now that i got home its still freezing at the loading bar. any idea what i could do since reinstalling the operating system isn't fixing it? should i try installing a older mac operating system maybe

Feb 5, 2018 3:29 PM in response to nilimma

It's not about installing the OS again, even if it's an old one (a friend of mine had the same problem with El Capitan a few days ago, while I had it with High Sierra). It's about ERASING the HD and then installing the OS. That's what fixes it. All the other processes that are described by various users of this forum are just to recover the info, but if you don't mind that, then just delete the drive on recovery mode (cmd+r at startup) and install the OS again.

crashed: too many corpses being created

Welcome to Apple Support Community
A forum where Apple customers help each other with their products. Get started with your Apple ID.