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

Apr 5, 2018 2:58 AM in response to Natpeloggia

Natpeloggia - Did you try my fixed.

Has worked on 2 new computers so far here in my office.

Its a tiny bit technical but actually easy to do:


Boot into Recovery Mode


Open Terminal


Create a new Directory on your Hard Drive by typing the line below into terminal.

mkdir /Volumes/"Macintosh HD"/kextbackup


Go to the Folder Extensions

cd /Volumes/"Macintosh HD"/System/Library/Extensions


Move the HuaweiDataCardDriver.kext to you new created directory by typing the line below into terminal.

mv HuaweiDataCardDriver.kext /Volumes/"Macintosh HD"/kextbackup


Close Terminal and reboot.

Jan 22, 2018 6:39 AM in response to fpuk69

FWIW… MacGallant wrote in the Slow Boot thread:


1. Go to System Preferences


2. Select Startup Disk


3. Click Lock to Unlock and enter Admin password


4. Click and select and highlight Macintosh HD


5. Click Lock to Lock back setting


5. Close System Preferences window


6. Upon reboot you should see that the boot and login to macOS High Sierra is faster again, just like in macOS Sierra and earlier!


Re: macOS High Sierra slow boot...


I did this and I've had five normal starts in a row. Worth a shot perhaps.

Jan 30, 2018 8:24 PM in response to fpuk69

I have a MacBook Pro (2011) and that happened to me twice before and after I used time machine. What I noticed is that if you have something plugged into any of the ports besides the adapter it will delay the boot. I think this is the case because sometimes when I plug in my external drive and my phone a message comes up saying that too much power is being used. Also what I did to resolve the boot issue is used first aid on the mac OS X and the macintosh HD drive and that did the trick .

Feb 16, 2018 3:03 AM in response to Josh_Jones

Hi Josh,


I had to take mine to the Genius Bar (I was there for over 5 hours !) in the end they wiped it after trying to back it up and re-installed just Sierra. They stated that they had seen many of the older Mac machines with the same issue and they suggested I just leave it on Sierra for a while and then make sure I back up on Time Machine before embarking on the upgrade if desired. It was all really annoying I had no intention of upgrading it and came over and found it upgrading I must have accidentally pressed ok to a later upgrade. I hope that helps (I have a 2010 MacBook), Lee

Apr 2, 2018 10:06 PM in response to melanniefrom239

I just wanted to update anyone who is still or started having the same issue as I have (stuck progress bar & nothing tech support did helped). I was FINALLY able to get my iMac to the Genius Bar Thursday (over a week from when my problem started). After the tech evaluated my computer's hardware everything was fine (no HD crash as I was fearing). Problem was with High Sierra & in the store he had only seen problems with it a couple of times & they were on older computers, not new like mine. Since I had my external HD with me with a recent save on it he suggested an erase & reinstall of the OS & I agreed since it would only take about 15-20 mins. that way. Everything went smoothly & I was in & out in 37 minutes. I explained my internet can be a bit slow at times & there is nothing I can do about it as far as upgrading. My internet provider (Centurylink) only provides 8 Mbps service in my area & there are no other providers here. He said it's possible the OS was in the process of updating & something happened to interrupt it & it hung up like that. He suggested getting a new modem since mine was over 3 yrs. old (something I've been thinking about myself). So I got a new one from CL on my way home that day & the internet is definitely running smoother & stronger so hopefully no more problems. This was definitely not something I could've done with a tech over the phone & by doing it in the store they used a cable so no WiFi hiccups to interrupt the process. Fingers crossed no more trouble! 🙂

Jan 19, 2018 12:59 AM in response to fpuk69

I am helping somebody with this issue and here is what I have found...


First I tried repairing the superblock, that said it worked, but same problem stuck at 100%. I then backed up all data manually over a day and then wiped entire HD and downloaded a new installer and re-installed High Sierra. It installed, loaded to desktop, I rebooted and first reboot, stuck at 100%. Personally, I don't use Mac OS, and after this fiascle, plus them being found out for intentionally slowing down old iphones, makes me wonder if they are intentionally causing this issue too. I have NEVER in my life seen a brand new formatted disk with fresh installed OS failed to reboot immediately. 0 Updates, no changes whatsoever. I am very disappointed in mac products and won't be encouraging them to anybody I know.


Here is a log of repairing the SuperBlock via a LiveISO:


Welcome - Parted Magic (Linux 4.6.3-pmagic64)



root@PartedMagic:~# df -h

Filesystem Size Used Avail Use% Mounted on

devtmpfs 3.9G 0 3.9G 0% /dev

tmpfs 3.9G 0 3.9G 0% /dev/shm

tmpfs 3.9G 312M 3.6G 8% /run

/dev/loop252 57M 57M 0 100% /run/br_fu

/dev/loop253 25M 25M 0 100% /run/br_m

/dev/loop254 310M 310M 0 100% /run/br_sqfs

tmpfs 3.9G 960K 3.9G 1% /run/br_ram

aufs 3.9G 960K 3.9G 1% /

tmpfs 3.9G 8.0K 3.9G 1% /tmp



root@PartedMagic:~# blkid

/dev/loop252: TYPE="squashfs"

/dev/loop253: TYPE="squashfs"

/dev/loop254: TYPE="squashfs"

/dev/sda1: LABEL="EFI" UUID="2860-11F4" TYPE="vfat" PARTLABEL="EFI system partition" PARTUUID="00007cfa-0bc4-0000-bb5f-0000c55c0000"

/dev/sda2: UUID="1b157782-e82b-3af2-b883-8c4e148f75f3" LABEL="Macintosh HD" TYPE="hfsplus" PARTLABEL="Macintosh HD" PARTUUID="00004d0b-0f7e-0000-0472-0000c2610000"

/dev/sda3: UUID="87d689d5-cec6-3ddb-af02-172cf83b1242" LABEL="Recovery HD" TYPE="hfsplus" PARTLABEL="Recovery HD" PARTUUID="f0c892a9-5c98-44df-81bb-718cd90e78ab"

/dev/sdb1: LABEL="PARTED MAGI" UUID="1B1B-0C49" TYPE="vfat" PARTUUID="0e3a6f32-01"



root@PartedMagic:~# mount /dev/sda2 /mnt/local/

mount: wrong fs type, bad option, bad superblock on /dev/sda2,

missing codepage or helper program, or other error



In some cases useful info is found in syslog - try

dmesg | tail or so.



root@PartedMagic:~# dmesg | tail

[ 49.356203] usb 3-2: reset high-speed USB device number 2 using xhci_hcd

[ 49.520429] sd 6:0:0:0: [sdb] tag#0 UNKNOWN(0x2003) Result: hostbyte=0x07 driverbyte=0x08

[ 49.520439] sd 6:0:0:0: [sdb] tag#0 Sense Key : 0x5 [current]

[ 49.520444] sd 6:0:0:0: [sdb] tag#0 ASC=0x20 ASCQ=0x0

[ 49.520452] sd 6:0:0:0: [sdb] tag#0 CDB: opcode=0x85 85 06 20 00 05 00 fe 00 00 00 00 00 00 40 ef 00

[ 125.105353] hfsplus: write access to a journaled filesystem is not supported, use the force option at your own risk, mounting read-only.

[ 133.793658] hfsplus: invalid secondary volume header

[ 133.793665] hfsplus: unable to find HFS+ superblock

[ 173.451955] hfsplus: invalid secondary volume header

[ 173.451961] hfsplus: unable to find HFS+ superblock



root@PartedMagic:~# fsck.hfsplus -f /dev/sda2

** /dev/sda2

** Checking HFS Plus volume.

** Checking Extents Overflow file.

** Checking Catalog file.





** Checking multi-linked files.

** Checking Catalog hierarchy.

** Checking Extended Attributes file.

** Checking volume bitmap.

** Checking volume information.

Volume Header needs minor repair

** Repairing volume.

** Rechecking volume.

** Checking HFS Plus volume.

** Checking Extents Overflow file.

** Checking Catalog file.

** Checking multi-linked files.

** Checking Catalog hierarchy.

** Checking Extended Attributes file.

** Checking volume bitmap.

** Checking volume information.

Volume Header needs minor repair

(2, 0)

** Repairing volume.

** Rechecking volume.

** Checking HFS Plus volume.

** Checking Extents Overflow file.

** Checking Catalog file.

** Checking multi-linked files.

** Checking Catalog hierarchy.

** Checking Extended Attributes file.

** Checking volume bitmap.

** Checking volume information.

** The volume Macintosh HD was repaired successfully.

Jan 24, 2018 10:24 AM in response to fpuk69

I had this problem yesterday after I updated my Mid 2012 MacBook Pro from Sierra at the weekend. The installation worked fine and my Mac rebooted ok at the time. I used it for a couple of days then shut it down, when I came to restart the following morning the progress bar also got stuck at 100%. I spoke to Apple support via IM and they made me do all the checks everyone else on this thread has been doing.... Safe Mode, Recovery Mode and running First Aid on the hardware etc....


Nothing resolved the problem then with another call to Apple I was instructed to reinstall the High Sierra OS from Disk Utilities in Recovery Mode. That didn't resolve the issue, so another call to Apple who I made aware of this thread, said they had no prior knowledge of this being a problem. I had to erase my Mac and recover everything from a Time Machine backup over about 3 hours - TF I backed up just before updating!


Apple really need to figure something out because erase and recovery shouldn't be the only option for an OS glitch. One thing's for sure High Sierra is definitely 'high', maybe too high to function properly for some Macs.....so keep it Sierra and leave getting high for a trip to Denver.....or backup before you do!

Jan 30, 2018 11:39 PM in response to ayn

I don't think it's a problem of old macs: yesterday I got my iMac Pro with High Siera pre-installed (10.13.12) and after the update to 10.13.13 I started having same boot issues...My brand new mac got stuck for 2 hours and it wouldn't boot in any way...I tried to reset SNC, VRAM, PRAM, boot into recovery and repair permissions with disk utility and nothing worked out.


What did the trick at the end was when in recovery mode for the 100th time, I decided to reboot choosing the start up disk rather than the usual restart the computer option...and it worked. But I don't know for how long will that last. I'm tempted to format everything again.

Feb 3, 2018 12:01 PM in response to fpuk69

I have the same behavior with almost all updates since High Sierra came out. I tried a lot, but at least one thing I found out helped a bit: when starting in verbose mode (cmd v) my MacBook Pro (2017) boots into the normal desktop. But it does not heal the problem. It's getting stuck at 100% progress bar on the next normal reboot and after logging in.

The only help for me was to reinstall from scratch and migrate back my user and data from a Time Machine backup.

Mar 16, 2018 5:21 AM in response to fpuk69

i had the same problem and sometimes a disk read error and other times it's stuck with login user photo, i tried somone's steps here it didn't work so i lost hope, however just after doing this, i inserted a bootable usb flash with sierra install files and it automatically chose to boot from it. i unplugged the usb memory while the progress bar wasn't complete. My mac then restarted and i was surprisingly able to login normally. Hope this help anyone

Mar 29, 2018 6:25 PM in response to fpuk69

The past week or so there had been days when my iMac (27-inch lated 2013, running High Sierra) got really sluggish. After a reboot and/or just given time, it had seemed to fix itself.


But today my iMac got unusably slow. I reset the SMC and it booted normally. I then reset the PRAM, and I got the progress bar stuck on 100%.


Eventually I was able to fix it (at least it seems fixed for now) by rebooting into recovery mode and using Disk Utility. It took so long booting into recovery mode that I thought it was locked up again. But eventually the screen went black, with a flickering cursor in the upper left. I clicked the mouse and the recovery mode UI was revealed.

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.