519      iPhone_iPad_Mac_apple

MacBook7,1 will not boot after updating from Si...

After updating to 10.12.1, the computer is unable to boot. There is just the boot screen with Apple logo and a progress bar that within 20–25 minutes reaches the right end, but instead of switching to users or desktop, it stops there and shows just the full progress bar.

Resetting PRAM doesn't help

Installing a brand new system helps, but it must not be updated to 10.12.1 and/or recovered from Time machine backup

In verbose mode, it writes hundreds times:

sandboxviolation: com.apple.geod(196) deny(1) file-read-data /private/etc/localtime

a little less times:

sandboxviolation: com.apple.geod(196) deny(1) file-write-create /private/var/root/Library/Caches

and then it just keep writing:

SmartBattery: finished polling type 1 >>> numbers vary from 1 to 4

and time to time it writes:

busy timeout[0], (240s), kextd wait(1): >>> and then there are a few words in gibberish text

Any idea how to quit this cursed cycle?

Hello Chris,

thanks for a suggestion, but safe boot was the first I've been attempting to before verbose mode. Unfortunately with the same results as classic boot – grey Apple screen with progress bar, that stays forever after being filled to very right end...

Startup Issues - Resolve

Startup Issues - Resolve (2)

Startup Issues - Resolve (3)

Startup – Computer Stops or Delays

Hello there! Same exact problem on my Macbook Air mid 2011 upgrading from EL Cap to Sierra.

Tried all the suggested way but the issue persists, the only way to make my mac boot up is by performing a clean install of Sierra loosing all previous account data or recovering the entire El Cap system from Time Machine backup (without Sierra however!). In other words it's impossible to me having my actual account updated to Sierra!

I encounter the same boot up problem either if i try to update to Sierra through App Store update nor from external bootable usb nor if i make a clean Sierra install and than use migration assistant to import my account from TM.

All suggestions are truly appreciated!

Thank you

I'm in the same situation After a minor appstore update (10.12.2)

HAve an old external drive with a clone of my OS (10.12) from about 3 months ago and can boot via USB with that.

HAve reinstalled sierra 3 times now and when I migrate data same thing happens. BIzzare

looked on apples SMC and bootrom versions and what I have is different rom what apple list.

there seems to be little or no support on this one.

MBP 8,3 is my machine (early 2011 17" i7 2.2)

Same problem here, MacBook Air Mid 2011

Interestingly, it appears that there is more knowledge in the forums for running MacOS on standard x86 than on the Official Apple forums, there goes any confidence in support.

BTW, in my case, the timeout is 60s, and the text is like the one in the photo.

Same here. In my case, it's an iMac mid-2011 that runs Sierra 10.12.5 just fine. But then I enabled the beta updates for 10.12.6, and got b2 installed, which worked as well. But since then, updating to b3 or now b4 always results in a similar behavior: It eventually shows (in verbose mode):

    busy timeout[0], (60s), kextd wait(1): some gibberish chars

Nothing obvious in the log that suggests what might be wrong.

I have a backup from before the update, so I can restore to 10.12.6b2 and then try the update again - same results.

Safe Boot (even by manually settings the boot-args to "-x -v") makes no difference, either. Nor do the other generic help suggestions in this thread.

My setup is not standard, though. My iMac came with a 1 TB hard drive, and I added a Crucial SSD (160 GB), from which I boot the Sierra OS. I had originally trimforce enabled, but even after disabling it, I still have the same problem. The next test will be to copy the OS to the original HD and see if that helps.

BTW, I've filed a bug report with Apple over a week ago but got no response on that, yet.

As per this article : Start up your Mac in single-user mode or verbose mode - Apple Support

To exit this mode and start up normally, type reboot, then press Return.

Are you a bot that posts generic suggestions when you find certain keywords in a new message? Because your reply is not helpful and rather disrespectful for the fact that it ignores everything that's been said here already.

Having exact same problem tried everything including fsck in single user, and reinstalling OS over the top to help fix any broken kext files, but no Luck.

Safe boot - apple loading screen but bar loading never starts and just hangs empty

Recovery boot - works ok and functions normally

Running Mac Pro 2010 6core with latest Mac OS.

OK GUYS!!! I have solved my issue!!! After HOURS AND HOURS of trying different things and reading etc I think I have managed to resolve it. (well at least bring it to a bootable state). I HOPE the result is the same for you too!!

NOTE- this process requires another functioning mac (unless you proficient with command line single user)

1 - boot the AFFECTED Mac in to "target disk mode" by holding "T" at boot up.

2 - connect the FUNCTIONAL Mac to the affected Mac by using a thunderbolt cable for newer models OR FireWire for older macs.

Once that's done, you should see the affected Mac's BOOT drive (Macintosh HD by default) mounted as an external disk on the functional Mac;

3 - navigate to the affected mac's drive and move these folders to the ~/desktop (on the same drive)

/Library/Extensions

/Library/LaunchAgents

/Library/LaunchDaemons

NOTE; Make sure you are moving the Above folders from the system library folder and not the user library folder as this is a system related problem and is not related to specific users on the machine.

Once that's done, shut done the Mac and boot normally.

It should then be ok and be able to login to the desktop.

There you will find the folders u just moved and the process of elimination begins to hunt down the culprit!

I hope this helps people out there. Please post results if it was successful or not. Would be much appreciated. As an ex-apple senior advisor I'm very interested if this method is the solution to the problem.

Thanks very much. That worked for me!

In my case the culprit was an Epson file in the Extensions directory. After I uninstalled the printer and removed the file, my Mac boots.

最后更新：2017-09-16 16:33:42

  上一篇： Sierra Apple Mail Crashes on Launching

  下一篇： Does Excel 2008 for Mac work on Sierra?