Announcement: Upgrade to macOS Mojave

With features like Dark Mode, Stacks, and four new built-in apps, macOS Mojave helps you get more out of every click. 
Find out how to upgrade to macOS Mojave > https://support.apple.com/macos/mojave

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

Question:

Question: 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

Reply
Question marked as Helpful

Dec 7, 2017 3:52 PM in response to fringeli In response to fringeli

After starting in Safe Mode, disk utilities and erasing the hard drive, then using Time Machine to get back to where I was, I got a clean start. I uploaded Malwarebytes (free malware hunter) and found a virus. It also sequestered an app called Ad Block Master. I removed both. Haven't had any trouble since. The virus was using up nearly all of my RAM making start up impossible. My processing speed is back to normal as well.

There’s more to the conversation

Read all replies

Page content loaded

Nov 28, 2017 1:32 PM in response to fpuk69 In response to fpuk69

Exact same for me. Shut down computer for Thanksgiving break, came back and got 100 progress bar (after long wait) then nothing. I've tried every kind of re-boot, including reloading the OS, disk repair. Can't get it un-frozen.


Nov 28, 2017 1:32 PM

Reply Helpful (4)

Nov 29, 2017 3:52 PM in response to vijvijk In response to vijvijk

Tried that too. Same result. I finally had to swap computers and install from a Time Machine Backup. Currently erasing the old hard drive with the hope of starting all over again. System seems to turn on and off with the new alternate computer with the old backup just fine.

Nov 29, 2017 3:52 PM

Reply Helpful

Dec 3, 2017 12:26 AM in response to fpuk69 In response to fpuk69

I have the same problem.


My Mac Mini (Late 2014) was originally unable to upgrade High Sierra because of the "cannot unmount disk" error, brought it to Genius Bar and did a fresh install and it was able to boot for a few times.


I then recovered my data from a Time Machine backup and in turn starts up Docker and Virtual Box, it is where it gets unstable and the VM is crashing. So I went ahead for a soft reboot, it is when it stuck at 100% on boot.


My gut feeling is that APFS is not that HDD friendly and refuse to mount every now and then.

Dec 3, 2017 12:26 AM

Reply Helpful (2)
Question marked as Helpful

Dec 7, 2017 3:52 PM in response to fringeli In response to fringeli

After starting in Safe Mode, disk utilities and erasing the hard drive, then using Time Machine to get back to where I was, I got a clean start. I uploaded Malwarebytes (free malware hunter) and found a virus. It also sequestered an app called Ad Block Master. I removed both. Haven't had any trouble since. The virus was using up nearly all of my RAM making start up impossible. My processing speed is back to normal as well.

Dec 7, 2017 3:52 PM

Reply Helpful (11)

Dec 11, 2017 12:30 PM in response to fpuk69 In response to fpuk69

Had this same problem after doing my usual update procedure once High Sierra had hit .2. I wipe the drive, do a clean install, then do a migrate from a Time Machine backup to bring my stuff back. Hasn't failed...until now.


Even booting Safe Mode didn't work (would still hang). Finally ended up reinstalling High Sierra again over this newly-upgraded installation, which did the trick.

Dec 11, 2017 12:30 PM

Reply Helpful

Dec 11, 2017 1:05 PM in response to fpuk69 In response to fpuk69

I'm having similar problems. It started happening after beta 4 install (for 10.13.2). After installing beta 4 the next reboot resulting in a continue reboot cycle after entering the password to decrypt the startup disk. It didn't matter if I booted to the recovery partition and ran check disk or reset NVRAM. Same problem with beta 5,6 & the release version. I submitted a bug report ~ several weeks ago I got no response. With the release of 10.13.2 it caused both of my 2013& 2014 rMBP to do the same thing. Even when I used the recovery partition to reinstall 10.13.2 it didn't make any difference. I ended up booting to safe mode to try & track the problem down. I have the sysdiag dumps & trying to track down what is happening. It appears something is loading at the point the disk is being decrypted that crashes the system. Strange that it started after beta 4. Apple changed something.

Dec 11, 2017 1:05 PM

Reply Helpful

Dec 11, 2017 2:12 PM in response to fpuk69 In response to fpuk69

Just had the same issue. Was working fine, shut down, restarted and progress bar stuck at 100% and then went nowhere. I rebooted using my previous Sierra external drive, went to disk utilities, picked repair disk and it said found errors and after rebooted on internal drive and now OK again. Not sure how long this will last. I have 10.13.2.

Dec 11, 2017 2:12 PM

Reply Helpful

Dec 11, 2017 2:37 PM in response to tbirdvet In response to tbirdvet

I meant to say I used First Aid (not repair disk) in Disk Utilities to fix. This is the first time ever I have seen this issue from OS upgrades over the years..

Dec 11, 2017 2:37 PM

Reply Helpful (1)

Dec 11, 2017 4:24 PM in response to hamosity In response to hamosity

And after a weekend leaving it in sleep mode, I returned to work, was able to type in my password... and nothing, just the password window and nothing happening. Finally re-booted in Safe Mode, ran Disk Utilities and supposedly it found an issue. I restarted normally and so far OK. We'll see. I've never had an upgrade go wrong. 10.13.1 seems to have glitches.

Dec 11, 2017 4:24 PM

Reply Helpful
User profile for user: fpuk69

Question: Progress Bar Stuck on 100% on boot High Sierra