You can make a difference in the Apple Support Community!

When you sign up with your Apple Account, you can provide valuable feedback to other community members by upvoting helpful replies and User Tips.

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

fpuk69 Author

Level 1

72 points

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

Top-ranking reply

dfsdfsdfzsdfxdfzsdfzsdfzsd

Level 1

4 points

Posted on Jan 19, 2018 11:37 AM

Success: I resolved this exact problem. When trying to install High Sierra, my Mac was stuck the black startup screen, stalling at either 90% or 100% completion between restarts.

I managed to get High Sierra installed without losing any of my files. Here is how I did it.

Failures:

Resetting a billion times.
Resetting PRAM.
Resetting CMD.
Using Safe Mode.
Using Recovery Mode (It would freeze upon attempting to re-install the OS, and Disk Utility couldn't detect my drive).
Using Internet Recovery Mode (Same as above).
Looking at Verbose startup mode -- it said "Error 13" on the drive IO.
Talking to the "geniuses" at an Apple Bar, as well as online tech support. They suggested either formatting my drive, or even buying a new drive. They had no inclination to dig into the problem and actually figure it out and fix it.

What worked:

I put my Mac in Target Disk mode (hold down T upon startup).
I connected my Macbook to another Macbook using a Thunderbolt cable. The other Macbook must be running High Sierra. If you don't have a friend with a Macbook, you might be sh*t out of luck.
I made a backup of my files, in case things went poorly. My Macbook appeared as a drive on my friend's High Sierra computer, but dragging files over in Finder resulted in an error. I had to use Terminal and "cp" my files over.
I opened Disk Utility on my friend's computer, and here are the steps I took:
- View -> Show All Devices
- My Macbook showed up, along with various "Container disks".
- I ran First Aid/Repair on all of the various things I saw. Some of them threw errors and refused to repair, but that seems to have been okay.
I then created a bootable USB installer as per How to create a bootable installer for macOS - Apple Support using my friend's computer.
I ejected my Mac, disconnected it from the other computer, and booted my Mac onto the USB booter. I ran the installer from the USB stick, and it succeeded! After it completed, High Sierra booted up, and all of my files were present, unharmed.

This was a huge headache for me, and I hope that this writeup helps save your files. Don't necessarily listen to the Apple "geniuses" who say that a format is necessary.

View in context

148 replies

Apr 8, 2018 2:07 PM in response to Natpeloggia

IDK if you saw my post above but I had the same thought as you do...my iMac was only 3 months old so it was also under warranty. When I took it into the Genius Bar they ran a complete check on my entire system & everything was fine. I was worried the HD was bad & was going to demand a new computer vs. a repair but it was fine. The problem was with High Sierra. All they needed to do was delete High Sierra & reinstall it so it was factory new again. It took less than 30 minutes from start to finish & it's ran fine ever since. I took my external HD with me in case it was needed but everything I had was in the Cloud so it loaded quick. I hope that helps & your unit is fixed as easily.

FLuViRuS

Level 1

4 points

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?

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

May 27, 2018 7:52 AM in response to edtechguro

So I found out too that the OS X installer is also corrupted, hence, I just reformatted all of the disks and had got an assist to install the OS X through an external USB drive. Problem was not fixed directly though.

Jun 1, 2018 3:02 PM in response to pbromelkamp

I'm newish with macs and haven't had any sort of problems until just now with this. I don't know what filevault is or how to get to it....looked at the article and put in the commands in the terminal but it just says basically no file exists.

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!

MSPhop

Level 1

9 points

Nov 26, 2017 1:04 PM in response to fpuk69

In short, I’m having the SAME EXACT PROBLEM.

vijvijk

Level 1

9 points

Nov 27, 2017 9:23 AM in response to fpuk69

Exact same problem with my mac OS (high sierra). no safe mode.. don't know how to fix it.

JeanFL

Level 1

8 points

Dec 18, 2017 6:26 AM in response to fpuk69

Jan 31, 2018 6:58 AM in response to dfsdfsdfzsdfxdfzsdfzsdfzsd

Creating a boot USB, hold option, Re-install High Sierra worked for me.

(Safe mode, Recovery mode from iMac, PRAM reset, install from wifi/ethernet did not work)

Philly_Phan

Level 7

20,725 points

Feb 7, 2018 5:15 PM in response to KAIJapanese

I would say that your iMac just might be a tad too old. Your purchase invoice is meaningless. Take a look at this and, ON THE MACHINE, compare with Apple > About this Mac.