Progress Bar Stuck on 100% on boot High Sierra

I have a Mac Mini (Late 2012).


Last month I upgraded the memory from 4GB to 16GB and installed macOS High Sierra; am currently on version 10.13.1


Yesterday (11th November 2017) I booted up my MAC at 9 am (ish) with no problems, during which time it successfully backed up twice to Time Machine at 9:15 and 9:50.


I shut down not long after this, then booted up again at about 13:10, and noticed the usual progress bar beneath the apple symbol was taking a particularly long time. I did a hard shut down and restarted, and still it took a long time, so I left it, then after about 20 (far longer than usual) minutes, it reaches 100% and stayed there: no log in screen.


I shut down and tried to reboot in Safe Mode (holding shift after the chime) but this made no difference as I never got to the log in screen.


I reset PRAM/NVRAM by rebooting and holding command+option+P+R at the chime. Nothing.


Reset SMC (unplugged, held power button, released, plugged back in) still no log in screen after 100%


I booted into recovery mode, opened Disk Utility and checked my hard disk. It returned ok with no errors found. Rebooted, still stuck at 100% with no log in screen.


This is where it starts to get scary.


I rebooted back into recovery mode, and reinstalled High Sierra (took about 3 hours), and, incredibly, it DIDN'T FIX THE PROBLEM!!(still can't believe this!!!) After installing, it rebooted, and again after half an hour the progress bar reached 100% and stayed there: no log in screen! How can actually reinstalling the entire operating system NOT FIX a start up problem? Does it not overwrite the system files it needs to reboot? I just don't understand how this is possible!?


I then went to bed and left my MAC on overnight. In the morning (about 7 hours later) still apple symbol with progress bar at 100%; no log in screen.


I booted in Verbose mode (command V) and saw lots of crashed processes "producing too many corpses"


I decided at this point to restore from a time machine back up. I didn't chose the ones from the morning before because it was after these back ups that my mac wouldn't restart, so opted for the back up the night before because I successfully restarted after this the following morning.


It took 8 and a half hours.


When it had finished, my MAC started just like it had before the problem occurred and everything was back the way it was before anything had happened.


The point is: I am now absolutely terrified to shut my mac down. I did nothing - install any new software, download anything etc - between booting up yesterday morning and yesterday afternoon which would have caused such a critical error, and I just can't believe that I couldn't boot into safe mode, and reinstalling High Sierra didn't fix it (still can't get over this), and am not going to be able to shut down until I know what caused it because I can't wait 8 and a half hours every time I need to use my MAC!!!


I read some articles about kext files, and booted in Verbose mode and saw some error messages about crashes and "too many corpses". I've also in Terminal compared the current system library with the one from the last back up that I successfully booted from and it's only found very few differences - mainly mobile assist fonts, and only 8 cash files - which is really surprising; are the files needed to start up kept somewhere else other than System/Library? I also read that other people managed to log into their macs after restoring from a back up like I have but after the next restart the problem still occured and they couldn't get back in.


Could all this have been caused because I interrupted it when it was being slow to start the first time? But why would it suddenly take so long to start when I haven't installed anything new, and there hasn't been any updates?


Would it be safe to wait for the next update and shut down then?


Is there any danger in leaving your mac mini on for a long time? (fan, heat etc)


Obviously the longer I leave it, the more data I will lose as I will have to restore from the last back up before the problem occurred which is currently the 10th of November, if it won't start again.


Anyone had the same problem and found a fix? Is it now safe to restart? I head something about Kext files in the Extensions folder and moved them but it didn't fix my problem. I can't think of anything I did between 9am and 1pm that would cause such a slow start up followed but such a fatal error; I installed High Sierra over a month ago, and installed the last update over a week ago.


What could High Sierra have done on it's own in the background between 9am and 1pm that now prevents it from starting up?


HELP!

Mac mini, macOS High Sierra (10.13.1)

Posted on Nov 12, 2017 1:12 PM

Reply
Question marked as Top-ranking reply

Posted on Apr 28, 2018 1:42 PM

I'm a very experienced Mac tech support consultant, yet I've been grappling with the "too many corpses" problem since yesterday. I tried a number of approaches, but was confident that a simple solution existed. YOU MAY NOT HAVE TO ERASE YOUR HARD DRIVE, or reinstall Mac OS. I found a couple of postings that explain this surprisingly quick solution. If you're able to get into Recovery Mode utilizing CMD-R, and you're not afraid to work in the Terminal program, THIS WORKS! If you follow these steps EXACTLY, a bad file named "mbr_cache" will be rebuilt and your Mac will reboot successfully (slowly the first time as the rebuild happens, then normal speed after that). This solution worked on my 2011-vintage 21-inch iMac (iMac 12,1) with Mac OS High Sierra. Someone should tell the Apple Geniuses and Tech Support Specialists about this. Or, better yet, they should be able to find these types of solutions themselves. Good luck!

The two articles where I found this solution are:

macos - Opendirectoryd too many corpses being created - Ask Different

https://mrsystems.co.uk/blogs/news/too-many-corpses-being-created


Steps from the articles:

  1. Boot and hold CMD-R to start up from macOS Recovery
  2. If Filevault is on, mount the disk with Disk Utility and enter password
  3. Enter these two commands in Terminal
  4. cd /Volumes/Macintosh\ HD/var/db/caches/opendirectory
  5. mv ./mbr_cache ./mbr_cache-old
  6. Exit from Terminal
  7. Restart the computer
148 replies

Feb 9, 2018 6:39 AM in response to steve626

If it was a third party software related issue, then High Sierra should properly boot in Safe Mode, but it's not.

I have this problem with an iMac 27" 5K (mid-2015 but I've bought it as new a few months ago) on an external brand new Seagate 2TB. I also tried to reinstall both from an USB stick and with internet restore (opt-cmd-R), on 3 different Mac. Still I can't boot.

It worked, more or less, for a few weeks and then one day I switched my iMac off and the day after it didn't load the login screen. Now I'm stuck.

I also tried to format (low level) the HDD and reinstall with Migration Utility, it worked for some days, then the same problem again.

I think High Sierra is the most unstable macOS I've ever seen in 20 years.

Feb 9, 2018 11:42 AM in response to fpuk69

Since this morning without warning without any reason without any technical issue I am experiencing the same crazy High Sierra bug / problem. I have lost a full day trying everything i read online. Nothing worked so far. Something that makes me super super mad is the fact that after spending a huge amount of money for Apple and after the billion of profits they make the quality of their OS is getting worse and worse,,, Who is paying me back the time spent on this????

Feb 10, 2018 4:10 AM in response to fpuk69

I just found the site below that claims to have a solution without needing to use a backup.

http://robinmonks.com/2018/01/crashed-too-many-corpses-being-created-how-to-reco ver-high-sierra/

It is exactly what you describe and what I experience. I will check out if it helps and will report later if it worked.

It really seems that it is a High Sierra issue and it is amazing that Apple does not react on it.

Feb 15, 2018 2:52 PM in response to fpuk69

All these work arounds for something your Mac doesn’t need. Why high Sierra? Because it’s free?For what reason is everyone doing this. You won’t even see a difference in the older units. Call me crazy but I value stability. I work hard who has time for this nonsense. Banging your head on a desk would be more productive than this rinky **** useless upgrade.

Feb 21, 2018 9:36 PM in response to fpuk69

500+ people have said they have this issue and still no clear answer? I tried to read the whole thread but so far it hasn't helped. Why don't they just say "hey we have a new OS... but it only works on the following products..." This is just like how they are killing off old iPhone after a few years. I am so glad that this happened on my old macbook, while my two other PCs are still working awesome! My Dads 2008 Dell is still running XP better than my 2012 Macbook trying to do high sierra....

Feb 22, 2018 5:35 AM in response to npegram

I totally agree. I basically spent 5 days a couple weeks ago dealing with this issue, and not working, which doesn't seem like much, but it's definitely crippling when you are trying to run a small business.

I did use this as an excuse to upgrade to a new iMac, which is fine since it was long overdue, and the tech at the genius bar was super helpful and issue on the laptop was dealt with, but I still don't have a clear reason as to why / what happened. They never really told me what cause the issue, and essentially denied that it was the upgrade to high Sierra. In fact, the tech even told me that some of the newer Macs are having trouble with High Sierra.


So long story long, I am up and working after spending $1600 to upgrade, but I am left with a stank taste in my mouth over it.

Feb 28, 2018 9:19 AM in response to hamosity

Thank you for posting this. I did what you suggested and it worked. I was talking to Apple and they were somewhat helpful but I just couldn’t get my machine to restart after the recent High Sierra software update. Thanks to you I didn’t have to go buy a new machine. I erased my hard drive and use Time Machine and now my iMac works perfectly. Thank you thank you thank you!

Mar 23, 2018 1:35 PM in response to fpuk69

Just wondering if anyone has had progress with this issue? I have a new 2017 iMac desktop I got for Christmas from my husband & have been stuck here as well for 3 days now. I spent 45 mins on the phone with tech support & after doing all the things mentioned here he had me load a copy of the HD in the utilities menu. It took over 2.5 hrs. to load & install only to end up in same place. Needless to say I am very upset as this is my only computer, it's brand new & I have taxes to file among other things. I made an appointment to take it in but their first appt. isn't for another week (snowbird season in FL 😭) so I'm stuck using my outdated iPad which isn't fun. 😡 I guess I am spoiled as this was a replacement for a late-2009 iMac that I never had an issue with the HD until last October. My husband replaced it for me so I wouldn't have this exact problem...go figure. 🙄😡😡

Apr 4, 2018 4:49 PM in response to melanniefrom239

Same issue here. My imac is only six month old and yesterday I was very upset when I turned on my computer and I experienced this problem. I reinstalled MacOS, tried almost everything I read on this forum - reseting NVRam, disk utility and nothing worked. Still stucked. I made an appointment for this Saturday by phone. I hope I can get my imac working again.

May 23, 2018 11:50 PM in response to fpuk69

Hi, I have this question too - I'm using a Mac Mini (I'm not sure regarding the model because it's no longer booting up properly but probably 2013s). I believe I made a system update, it rebooted, then the same thing happened - stuck on 98-100% progress bar. I already tried the different shortcut keys to attempt to boot it up and even tried accessing the drive via Target Disk on another Mac. It was only able to read the other partition which contained nothing (there were supposed to be 2 partitions). The 1st partition contains the Users files (or actually all of my files) but the partition is not mounting properly.


Via Recovery Mode, I tried to use the Terminal and also attempted to mount it via "diskutil mount /dev/disk0s2" but the result is "Volume on disk0s2 timed out waiting to mount". I believe this volume is 1TB in size. However, there was one time that I've seen the volume to mount again completely but it was just a very small chance because when I rebooted, it is no longer accessible again.


So is there anyway to fix this? Or is it that it just takes a longer time to mount itself? I'm not sure what I did before when all of a sudden, that volume mounted. But then again, I was not able to back it up so I'm stuck.

May 23, 2018 11:51 PM in response to fpuk69

Hi, I have this question too - I'm using a Mac Mini (I'm not sure regarding the model because it's no longer booting up properly but probably 2013s). I believe I made a system update, it rebooted, then the same thing happened - stuck on 98-100% progress bar. I already tried the different shortcut keys to attempt to boot it up and even tried accessing the drive via Target Disk on another Mac. It was only able to read the other partition which contained nothing (there were supposed to be 2 partitions). The 1st partition contains the Users files (or actually all of my files) but the partition is not mounting properly.


Via Recovery Mode, I tried to use the Terminal and also attempted to mount it via "diskutil mount /dev/disk0s2" but the result is "Volume on disk0s2 timed out waiting to mount". I believe this volume is 1TB in size. However, there was one time that I've seen the volume to mount again completely but it was just a very small chance because when I rebooted, it is no longer accessible again.


So is there anyway to fix this? Or is it that it just takes a longer time to mount itself? I'm not sure what I did before when all of a sudden, that volume mounted. But then again, I was not able to back it up so I'm stuck.

This thread has been closed by the system or the community team. You may vote for any posts you find helpful, or search the Community for additional answers.

Progress Bar Stuck on 100% on boot High Sierra

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