Yosemite Macbooks stuck at 50% boot (Progress Bar)

So far, the /etc/rc.server workaround has been working for my Macs...until yesterday.

My Desktop techs had a support call for MacBook Air that had succumb to the boot hang issue. After further inspection, I determined that the /etc/rc.server file was in place. The fix/triage consisted of the usual voodoo: PRAM zap, boot into Recovery Mode, repair disk permissions, etc.

My environment consists of about 75 Macbook Pro retinas and Macbook Airs that are:
-ad bound
-10.10
-FileVault -Hangs at login

Booting to single user mode and running a fsck only fixes it temporarily in my experience. All of the other usual "voodoo" works for a while then back to square one as well.

Running a machine with 10.10.3 beta and it seems to be better, but no guarantees.
unbinding from AD seems to have fixed it. After I rebound it to AD the problem came back....Hope this helps some.

If only they would let me deploy Macs not bound to AD. It's my dream. Someday… someday……

I have a macbook pro.
I have tried the Pram Nvram Smc resets. No luck
I also did the disk utility verify and repair. no luck on that
I tried the sin-user mode I tried the fsck and mount tricks. no luck
I even tried the turn off wifi and reboot. no luck
Can anyone come up with any ideas.
This happened to me last night actually.
If it helps I did delete the IPMonitor in usr/library/systemconfig by accident
and I DO have sophos .
I did not backup so wiping clean would be harsh on me

When I went into disk utility and selected my MAC HD drive. I put in the password. I selected verify disk permissions I got this:
User differes on "private/var/db/displaypolicyd"; should be 0; user is 244
Group differs on "private/var/db/displaypolicyd"; should be 0; group is 244

When I repair permissions says same as above plus:
Repaired "private/var/db/displaypolicyd"

@Hikaru I was in the same boot nothing worked except for @mm2270 recommendation which is stated in this thread...

sudo defaults write /Library/Preferences/com.apple.loginwindow DisableFDEAutoLogin -bool YES

after running that I saw the error he described, the device was trying to connect to a network resource.

What are sudo defaults? @Potter and Do i go into single user mode or do i go into disk utility then bring up mobile terminal?

UPDATE*
I entered this into Single-User mode:
sudo /Library/Preferences/com.apple.loginwindow DisableFDEAutoLogin -bool YES
it responds with:
sudo /Library/Preferences/com.apple.loginwindow: Command not found
Any help?

@Hikaru Is this your own personal Mac, or a company owned system? This thread primarily discusses an issue that affects Macs joined to a Microsoft Active Directory domain and, in many cases also running FileVault 2 encryption.
It sounds like the problem you have is on a personal Mac. Is that the case? While its possible you have FileVault 2 enabled, its unlikely you are joined to an Active Directory domain, if its your own Mac.

Also, can you clarify the exact problem you're seeing? Is it hanging after it boots up at around the 50% mark in the progress bar?

I ask all this because you may be experiencing a problem different than what is described on this thread.
Have you tried booting from Recovery HD at any point? Wasn't clear in your post if you have or not.

This is a personal mac computer. I turn on my computer it loads with the apple logo then hangs at 50%

And what about the other stuff? Disk encryption that you know of? i.e, does it boot up and ask for a password with your user icon or just boot and get hung on the progress bar? Have you tried Recovery HD and checking the disk?

Also, take a look at this post in this very thread from Chris Hotte: https://jamfnation.jamfsoftware.com/discussion.html?id=12589#responseChild76389

You may be having the boot cache issue as described. If so, the fix Chris outlines may help. Follow the instructions exactly.
No guarantees it will help, since I honestly don't know how your Mac is configured. Good luck.

I do not see a recovery disk.
I turned off encryption via Disk Utility.

I did chris hottie's way and I am just confused. I get the window and everything but I do not know how to apply settings etc. I did it exactly but the thing is that I press enter and it just starts another line/ Is there a more thorough step by step version?

@emilykausalik ...that is my dream too! ....it'll happen one day....

@Hikaru

Are you an Admin, responsible for a company's workstations? If you are just an end user - this workaround/resolution does not make sense for you and likely you have another issue. If you do not have Active Directory enabled - this workaround is not the fix you are looking for.

If do not know how to use the command line and related editors - this is not the forum you are looking for. You need more basics first and this is not the platform for that instruction.

I haven't read the contents of this link, but at a glance it appears to be what you require to get started:
http://www.howtogeek.com/howto/42980/the-beginners-guide-to-nano-the-linux-command-line-text-editor/

I know its on Linux, but MacOS is just darwin based, so its essentially the same when on the command line.

10.10.3 Dev Beta users check the opendirectoryd build in the latest release. :D

@dgreening spead the news what is it?

Lets just say that it looks like the fix is in.

opendirectoryd (build 382.20.1)

Macrumors Thread

You can double check your opendirectoryd version by issuing /usr/libexec/opendirectoryd --version

Apple just released 10.10.3 which they claim fixes this issue.

@roiegat is that a public release of 10.10.3? I thought it was still beta.

Thanks @roiegat. This is another beta (14D98), correct?

http://wp.me/p1xtr9-1y6d

The beta that I was referencing is 10.10.3 (14D98g). I cleared the rc.server file and have not been able to get it to hang at login. This is with AD (mobile account - no UNC path) and FV2.

Came here to ask, saw the answer already posted. Thanks dgreening!

Thanks Apple. The fix came late, but at least it happened.

I haven't tested yet, but its beta. Its not too late for them to pull out the the fix. :)

Tested and confirmed fixed here as well.
As expected and as others have mentioned, opendirectoryd has been updated

admin$ md5 /usr/libexec/opendirectoryd 
MD5 (/usr/libexec/opendirectoryd) = 3dbc0c2e3653ace4dd92b43022daced9

$ /usr/libexec/opendirectoryd -v
opendirectoryd (build 382.20.1)

Good deal. Looking forward to testing in the morning. I'm hearing/hoping there might even be some love for 802.1x/Login Window issues we've experienced. Might be able to roll out Yosemite yet.

edit: 802.1x still rough. Yosemite rollout on hold.