Hi,
After OS Yosemite was installed in some of our MacBooks, we had some boot at 50% and it stays stuck there. The first time I saw the issue, I power cycled the MacBook and I let it sit for an hour. It was still stuck at 50%. I power cycled the machine again and left it on for the whole night (5:00pm-8:00am). As I got back to the MacBook, it was still stuck at 50%.
I did some Google searching and I read this thread here: https://discussions.apple.com/thread/6603394 and tried booting to the recovery partition (Command + R). I booted to the recovery partition, turned off Wi-Fi, then restarted the machine using the menu bar.
After doing this method, the machine successfully rebooted and finally reached the login screen. I have done the same methods for another MacBook along with one MacBook Pro and they all managed to reach the login screen after booting into the recovery partition, turning off Wi-Fi, then restarting the machine.
I don't know if this is the "right" solution for this issue, but other ways to solve this issue would be greatly appreciated as we are planning to upgrade more and more MacBooks (and Pros) to OS Yosemite.
Thank You!
You should try a 2MB DSL that's shared. I'm firewalled from the App Store servers... so I have to go this route. If I lean in close I can hear the banjo picking away each bit as it comes down.
On related note...
Does anyone know if OS X Yosemite 10.10.3 (build 14D131) will "unify" all current Apple Mac hardware, including the newly-announced 2015 super-duper thin MacBooks?
Not sure about the new MacBooks - but our basic 10.10.3 image from AutoDMG works on a brand new 13" MacBook Pro Retina, and brand new MacBook Air. Previously They were using their own forked versions of 10.10.2.
@Shaffer Does AutoDMG work with the new 10.10.3 image? I am currently seeing a "Installer is newer than update profile" warning with AutoDMG 1.5.3
@dstranathan you'll be fine, the author is updating the update profile currently.
@dstranathan Yeah - I saw that, too but decided to give it a shot. Everything went through just fine. I'm guessing it has more to do with finding available updates (like newer safari, security updates, etc) than the main OS. My impatience paid off... this time :)
I'm more interested in iOS 8.3 (wireless CarPlay).
I can wait for the dust to settle for 10.10.3. :)
Don
Took less than 20 minutes to download. Started the AutoDMG process and went home.
Can anyone confirm this patch has fixed the hang on boot?
I have just imaged a 2 new machines with the 10.10.3 AutoDMG created image utilizing Casper Imaging and have not had any issues with the hang on boot. Also, I have noticed that AD bound systems off-network now authenticate MUCH faster when resuming from sleep whereas before we were seeing some systems lock up entirely when resuming.
In case anyone is curious.
MD5 (/usr/libexec/opendirectoryd) = e56b9036bdca0881e8b14c17e0dbff46
SHA1(/usr/libexec/opendirectoryd)= 110f78fc0a022e26019d013dfc452e2d97bf0414
I was having the same issue with the 50% progress bar on machines with 10.10.2 and FileVault enabled. I tested the 10.10.3 beta (seed 3 or 4) and it appeared to have fixed the issue. I haven't tested 10.10.3 (14D131) that was released yesterday.
I can confirm that a Macbook 2015 Air and MacBook Pro 2013 are booting fine with hard shutdowns.
FileVault2 boot/login is also working on/off network now with a mobile AD account created with the UNC path checked. Tested with the default BindTimeout and a custom setting of 15 seconds. The progress bar stalls about 1/3 through during the BindTimeout and then pushes through and you are displayed the usual, 'There was a problem connecting to the server "server-name".' This was a clean 10.10.3 build test not an upgrade.
Cheers! ;)
OT a bit, but just an FYI, Apple now gives us an option to not require unlocking your iPhone to use CarPlay.
New CarPlay pref
Hey All.
I am trying to image with the new 10.10.3 (to test the 50% boot) on a AutoCasperNBI running Casper Imaging 9.7 but getting an error -
Failed to delete Core Storage Information
Any ideas?
I've been following this discussion and tried everything without success, I can in some cases get the machine to start in safe boot, sometimes not.
The build having this issue has never been bound to AD. Tried all possible ways with upgrading to 10.10.3 without success, did a recovery, that is installing a fresh 10.10.3 on top, no show...
Luckily, I have a working older build backed up via DeployStudio, so I will continue using this one, patching and adding features to see if the problem occurs again.
Really frustrating.
So far, testing with an AutoDMG 10.10.3 .dmg on a 13" 2015 Air and 2015 13" Retina with multiple reboots and our configurations. We use Casper Imaging along with the lovely @rtrouton's First Boot Package Install to run our first boot script - and easily replicated this login issue as our bootstrapping process would get jammed up with the reboots after the Mac was bound to AD. I have not been able to replicate this problem yet with this update. Doing more testing, closing lids, and plenty of reboots with other models we have. Looks promising so far. I will update if anything changes.
@laurendc can you share the First Boot package Install that you referenced?
@chenderson https://github.com/rtrouton/First-Boot-Package-Install
You can use it in different ways but what we're doing is basically running our first boot script as a payload free package (priority 3 in the config) and posting the results of the script to the firstbootpackage install log (io redirects) in order to provide feedback to technicians on results on the LoginLog screen.
Hate to derail the thread so I won't continue outside of saying that it rocks.
@chenderson My bad - that's the old one. For 10.10, you want to follow the instructions for First Boot Package Install Generator: https://github.com/rtrouton/First_Boot_Package_Install_Generator
Bad news (hopefully its just me). In my lab of 37 iMacs, 10.10.3 failed to resolve the boot issue. These are late 2013 iMacs with 10.10.2 upgraded to 10.10.3 yesterday. They had @chris.hotte's rc.server fix applied to them. They are bound to Active Directory, NOT using a network-mounted home folder, NOT configured with FileVault 2 and I am still having boot issues.
I do not yet have an Enterprise support contract with Apple but am in the process of getting one purchased. I hate to rain on everyone's parade and sincerely hope the issue is something specific to my environment, but wanted to at least let everyone else know this update may not fix the issue.
The actual boot issue seems to be fixed for me but 3 times yesterday when waking my laptop from sleep, the machine would hang when trying to login again (either with the username/password field present or after with the spinning gear). Not sure if this is related. All three times required a hard reboot, I dumped all caches, etc, unbound/rebound to AD, rebooted this morning. Haven't put my machine to sleep today so don't know if that fixed it. My update to 10.10.3 was done with the combo updater.
My 10.10.3 laptop is in AD, encrypted with FileVault and I am still experiencing the 50% boot issue :(
@jrippy
Have you tested a clean install of 10.10.3? I've been testing it since it came out, no issue coming back from sleep or booting.
iMac 21' Late 2013 and Late 2014. Both using a network mount script, bound to AD and no FV2.
