Progress Bar Stuck on 100% on boot High Sierra

I have downgraded to Sierra and the laptop is working as expected. SMART status was ok, this was no a hardware issue. They changed the Filesystem which as another user points out seems to cause issues on HDD's.

This may or may not solve everyone's issues, but my new iMac wouldn't get past 100% on load, nor could I boot in safe mode. I could boot in recovery mode however, and was able to use Disk Utility. Upon first try, I only used First Aid on the Fusion Drive, but this didn't work on a reboot.

I then used Disk Utility again and ran First Aid on every drive option available. I don't know which one did it, but on reboot it started up instantly again.

Just my experience and hopefully helpful! If not, I feel your pain!

I ran into this problem two days ago. Turned on MacBook Pro mid2012 and wouldn’t boot. Tried most of what was suggested here. What worked for me is the following. Went into recovery mode, command R, attached watermark hard drive I had used to do a backup in sept 2017. I haven’t backup since so I did a disk image of the hard drive and saved it to the external drive. Then did a restore from my sept backup. That restored is version 10.9.5. After restore system booted ups as normal. I opened the image file by double clicking on the .dmg file on my external drive, clicked on skip. I moved all the files since my last backup from the .dmg to the hard drive in their respective folders. Ran time machine backup. Now I’m going to install Sierra not High Sierra and see what happens.

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

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.

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.

Booting into safe mode allowed me to track down & remove the kext's that were causing my problems.

.

However, I think there is a combination of things happening here starting with how Apple is handling these kext problems when booting (after beta 4 10.13.2). I haven't definitely identified these changes and hopefully someone with more expertise can id this changes. 1. When booting in 10.13.2, decrypting the boot disk the progress bar sticks at 100% or less, I believe APFS my not be "clearing" errors or past problems with kexts, and isn't continuing with the decrypt. Booting into safe mode may "clear" these problem flags after the problem kexts are removed & allow decrypting to continue. 2. It may be connected to the "snapshots" APFS is creating. 3. When I change my boot volume back to HPFS, I don't see these problems.

I have had more problems with High Sierra than any other OSX versions. I would recommend if you need to run it, use HPFS formatted disks for ssd boot.

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.

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 .

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

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! 🙂

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.

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.

If the problem happens with a newly erased drive plus a fresh clean vanilla OS installation, that indicates a hardware problem. If it happens when you updated to 10.13.2 with your full setup, it’s very likely you have previously installed something that conflicts with or is incompatible with the latest OS.

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!

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.