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

Jan 26, 2018 6:46 AM in response to McTann

I'm glad it worked for you McTann and hope it continues to. Unfortunately I'm on here again today because I thought I should mention that after about 7 consecutive good starts, my Mini (2012) choked on the boot progress bar again this morning. Twice. The second time I was trying to boot in safe mode, which it seems unable to do these days (perhaps because its dirty old M7803 keyboard doesn't work all that well by now, or the Mini doesn't like it, but I doubt those theories). For reasons beyond me, when I lost patience, let the shift key go, and pressed/held the power button, it restarted instead of simply shutting down, and the third time was the charm. Running fine now. I will try MacGallant's trick again—perhaps it serves to clean something up that will repeatedly get dirty while running under High Sierra. Frustrating to say the least. As Sejonmusic said, erase and recovery shouldn't be the only option for an OS glitch. (No, we don't *have* to erase, we can try the simple reinstall from recovery mode first, but even that's risky and extreme in my opinion.)

Jan 31, 2018 8:20 AM in response to fpuk69

What is interesting to me is that even though the progress bar is stuck at 100%, I can go to another Mac in the house and use Screen Sharing to find the frozen Mac login screen. In other words, the Mac is fully booted but literally stuck at the progress bar. I can interact with the remote Mac e.g. check email, use a browser but when I physically go back to it, its still stuck on the 100% progress bar. I have found that re-booting via Screen Sharing will get the Mac to fully boot on the second attempt. A hard shutdown/restart from the culprit Mac does not seem to help.

Feb 1, 2018 10:18 AM in response to Nina R

For the record I have a late 2017 iMac so for those who believe this issue is caused by their Mac's being too old (as advised by Apple), I wouldn't agree. If Apple allows High Sierra to be installed, it should work and leave it to the end user to decide if the potential slower experience outweighs the benefits of the newer OS. Although this issue doesn't help the cause to upgrade.


This issue most often occurred when I was booting back into MacOS from Boot Camp. As a rule of thumb, I enable either Screen Sharing or Remote Management on all installations. So to answer the question, if you haven't already enabled Screen Sharing on a Mac stuck at 100% progress bar, I am not aware of a way to enable Screen Sharing on that Mac via command line, from a remote Mac. From a security perspective I would be surprised if this is possible even if File Sharing was also already enabled. I have not Googled it.

Feb 6, 2018 1:50 AM in response to steve626

I can confirm this approach works and I had the same problem as everyone else with High Sierra (also, it wasn't just the one kext issue, it was multiple different ones each time I restored which was a bit weird).


This was the only way I could get anything back without repeating the same issue yet again.


I ended up reinstalling High Sierra about 6 times with multiple different settings and restores but to no avail. I eventually did exactly as steve626 describes and am still currently reinstating my software.


So far so good.


There is only one clincher...now my Command-R boot into Recovery mode hangs at 100% load screen and goes no further. Oh, the irony...


😐

Feb 24, 2018 12:40 AM in response to fpuk69

Hello, I have also experienced this very frustrating problem. I have tried all the steps mentioned in this thread multiple times. The only thing that worked was to restore a Time Machine backup to a previous OS version number.


I have a 2011 IMac, if this issue is due to the fact my machine is relatively old then Apple need to be advising users. I’m just happy we had a recent backup to avoid losing the 15k+ photos we have on there.


I hope that you get a satisfactory resolution to your issue.

Mar 20, 2018 2:19 PM in response to dfsdfsdfzsdfxdfzsdfzsdfzsd

I'm so glad I found this post because after trying a hundred other fixes this is what worked for me. Took my Mac from home to my work where the crashed iMac was. Got a Thunderbolt cable and my "Stuck" iMac's HD showed up right on the desktop of my other iMac. I had a lot of files backed up but there was quite a bit that was not. I just dragged everything over to an external HD I had plugged in and recovered everything I needed. I then restored the stuck iMac with a Time Machine backup from a year and a half ago, at least I didn't have to reinstall everything.

Apr 9, 2018 7:35 AM in response to hamosity

This helped me tremendously, except I could not get in using Safe Mode (progress bar stuck at 100%). Instead I used Recovery Mode (Command + R), then Disk Utilities. I clicked on First Aid to check the system. Report was OK. Then I proceeded with "Erase", and then to use Time Machine to get back to where I was.


I too downloaded MalwareByte but the scan was clear. Avast scan was also clear. Funnily enough, the reason that prompted me to attempt to reboot the system [inadvertently getting caught in the 100% progress bar issue] was that I noticed that my system suddenly became extremely sluggish and slow. It was like you described, as if a virus was using up nearly all of the RAM. But the virus scanners could not detect it.


So now I'm left like the OP - petrified of rebooting the computer as I could not identify the exact issue.


Has Apple or the community found out the issue?

Jun 1, 2018 5:02 PM in response to Steelemusic

If you don't know what FileVault is, you're very likely not using it, so it's not a factor. If the commands are entered in Terminal EXACTLY as presented, you won't get error messages that no such file exists. If you're as inexperienced as you seem to be, you should seek help from someone with more Mac experience. Having two sets of eyes, and two brains, working on a problem such as this is usually a good thing. This is pretty high-level troubleshooting, and not for everyone. (If you took the instructions to an Apple Store, or to the local Mac computer shop, or to an experienced friend, they could help you accomplish this fix in just a few minutes.) Good luck!

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.