Apple Event: May 7th at 7 am PT

Looks like no one’s replied in a while. To start the conversation again, simply ask a new 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 Nov 12, 2017 1:12 PM

Reply
Question marked as Best reply

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.

148 replies

Dec 18, 2017 6:35 AM in response to JeanFL

I also have this problem. Started on December 17th (yesterday). I chatted and talked on the phone with Apple support and all the efforts didn’t resolve the problem. It took 4 hours to reinstall High Siera and it went back to the same progress bar. Left it on over night still no log in page. I don’t have the time back up so I don’t know what’s going to happen now. I have three years of art work on my hard drive. The only suspicious things I saw on my Mac in the last month or so was a warning about a virus. I restarted my computer and it was fine after. I paid it no mind because I was always told macs don’t get viruses. This is also my first Mac. I’m going to a Genius Bar soon and hope they have a solution. I can’t afford to get a new Mac so I need this fixed and hopefully I can get my art works back. I’m really upset about this.

Dec 20, 2017 5:47 AM in response to tbirdvet

Hey there.


i've did the steps and first aid, it loaded pretty fast and after that i did a reboot again.

Still the same issue not bring me to login screen.


If there anything else i need to do in recovery mode? I'm quite careful with doing anything at the moment just in case i mess up the system.


Awaiting for your prompt respond.

Dec 30, 2017 12:24 PM in response to catwigs

I went to an Apple Store and they could not save my files. They restored it to its original OS and then I had to bring it home an install the new OS. Its a two day process, upgrading to High Sierra takes about 19 hours. My computer has been working like the day I bought it. Only thing is I lost all my files that were on my desktop. So now I'm trying to figure out if there's a way to retrieve those files. The tech at the store said there's a way to get them but I would have to go to another tech place. Also, The Apple Store didn't charge me anything because OS related issues are free of charge.

Dec 30, 2017 10:21 PM in response to fpuk69

I encountered something similar after a system update on 10.12.6 (Sierra, not High Sierra). The symptoms were the same, however, booting to 100% progress bar, then never completing.


I had two backups, one Time Machine and the other a SuperDuper clone.


After booting into Recovery and re-installing the OS but with the same problem, I then ERASED the boot disk entirely and reinstalled a fresh, clean OS. I then, on first boot, migrated everything from the Time Machine backup. The problem returned!


I then theorized that some kext or some other installed extension had caused the problem, so I had maybe just migrated the problem back to the new clean system.


I then repeated the erase and fresh install, but this time on first initial boot, I skipped EVERYTHING except to create one admin user account, nothing else. Then I applied all available system updates, including the one that led to the problem. Rebooting after that worked fine. I thus had a plain vanilla system with one admin user, no user files, and nothing installed except Apple original software.


Then I used Migration Assistant to migrate ONLY user accounts and user files, no settings and no applications. Then I proceeded to reinstall only some applications from scratch, such as MS-Office, Adobe Lightroom, TurboTax, and a few others, but not everything from before. After a week or so, everything seems ok.


Not sure this will resolve your issue in High Sierra, but if it is caused by something installed or a bad kext or some similar thing, the clean install followed by Migration of only user accounts and user files prevents that corruption from being brought over. The downside is reinstalling all one's software, but I found that to be fairly straightforward and not very time consuming in fact.

Jan 11, 2018 1:39 PM in response to MSPhop

Both external SSD drives with clean-installed High Sierra (MacOS 10.13.2; installed with USB installer which was created on Jan 10, 2018) boot fine as external drives in my MBP13 (early 2011). But it seems to take forever to shutdown.


After one of this bootable SSD drives was input as an internal drive, the progress bar stuck on 100% on booting, and login window never shows. With the external-drive booted, run First Aid at Disk Utility for the internal volume, resulting to be OK, and as mounted when exit the Disk Utility. But, the internal disk does not show at Startup Disk of System Preferences.


What could be wrong? Any suggestions or clues will be appreciated

Jan 14, 2018 4:59 AM in response to fpuk69

I had the same problem I tried everything so the only way I found is to reinstall Mac and delete everything in the HD as I didn’t have any backup. The only I had to solve was how to keep my files. I saw in the recovery mode “more infos” section based on safari and used this to login to my mas storage ( in my case fritzbox mas storage) http interface and I tranfer successfuly all my files to hd I connected on it! Is a way if you don’t have backup . You can always use iCloud or google drive too but with limited space and it’s very slow.

Jan 14, 2018 9:36 AM in response to fpuk69

This post now has more than 8K views. Another post about slow booting in High Sierra has more than 15K. Do we seriously have no guidance yet from Apple on this problem?


For me this has been an intermittent problem for perhaps two months. I am about ready to throw my 2012 Mini through a window if it doesn't stop sticking on the boot progress bar (sometimes at 100%, other times less). I have to force shutdown because of this several times a week. Usually, on the second try it succeeds. In a variation of this glitch, I will notice the mouse pointer flickering in the upper left corner of the black screen, telling me the boot actually is done. I move the mouse and voilà, the login screen appears.


Yes, I have booted into recovery mode and run first aid a number of times. Never seems to find anything wrong.


P.S. another stellar example of why I *will not* give up my Power Mac G5 (dual core 2.0), on which this post was written and sent.

Jan 14, 2018 11:30 AM in response to Nina R

A read of the various posts shows that there are different things that can cause this, as some people have resolved their issues and others have not.


Basically there are two possibilities: software and hardware.


Simply reinstalling the OS has in some cases apparently fixed the issue, but for others it has not. That could be because the user has previously installed something that prevents booting (a simple reinstall of the OS does not erase extensions and other software the user has installed), or because there is a hardware problem.


One way to isolate this: backup all files, then erase and install the Mac OS and just one admin user, don't migrate any software, settings, or extensions over. Then use the computer for a while, with many restarts, if the issues go away, then you have proven that a totally clean, vanilla system does not suffer from the problem -- the issue probably is with something that had been installed that is incompatible for the OS. If the problem persists, then you may have an intermittent hardware problem, which requires a different type of troubleshooting. The original poster had a 2012 Mac with this -- that's a 6-year old computer. Now I have a 2008 iMac that is still doing just fine, but people in the industry will tell you that some of the parts are not specc-ed to last that long. Also, the original poster had added memory within a few weeks of posting, it is possible something was unintentionally touched inside the unit during that process that now is making intermittent contact.

Jan 18, 2018 3:58 PM in response to fpuk69

Been on Apple Support again.


They took me through an attempt to reinstall OS using Internet Recovery. As the OS available on Internet Recovery was Lion, it wouldn't do it as a newer OS was installed. Good job it didn't work too, as I have now learnt that despite the advisor confirming to me three times that there would be no data loss, it actually would have completely wiped all data.


Apple needs to get a grip on this - it's absolutely no way to treat customers.

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 19, 2018 1:47 PM in response to FreeSoftwareServers

FreeSoftwareServers wrote:


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 have -- this happens when there is a hardware issue, possibly with the disk itself, or with the disk drive interface, or with other electronics inside the Mac. Having a perfect fresh new OS installed or running Disk Utility or Unix tools to repair the file system will not fix a hardware issue.

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 ID.