Mac starting twice upon rebooting

[christarp]

Hey guys, quick question here about my late 2013 rMBP. I'm running the latest yosemite on it (10.10.2) and whenever I shut down and turn it back on, I get to my account password entry field, and type in my password, and the progress bar moves about 1/10th of the way and then the macbook just reboots. Upon that reboot I type my password again, and this time the OS loads perfectly fine and works great.

For some reason no matter what I do it needs to boot twice in order to reach the desktop, it doesn't matter if it's a proper shut down, reboot, or cold boot. It will only boot on the second attempt. Any ideas?

 

[MLinneer]

My Macbook Air has been doing this lately, though not every boot up does it happen. Yosemite 10.10.2 and File Vault active, which was what I though t was doing it.

 

[christarp]

My Macbook Air has been doing this lately, though not every boot up does it happen. Yosemite 10.10.2 and File Vault active, which was what I though t was doing it.

I also have filevault active and I'm not really looking to disable it. Did yours get fixed when you disabled it?

 

[MLinneer]

I'm sorry I left the wrong impression. I haven't disabled File Vault, just assumed that the decryption was what was hanging sporadically. Two reboots today and my MBA booted normally.

Possibly related though, since the 10.10.2 update my MBA and iMac both are slow after startup or wake from sleep for a long period. I never turn my iMac off, just let it sleep overnight. Anyway, both machines seem busier than before the update. It doesn't last long, just a few minutes, in fact I know the system is ready when Dropbox updates. Again this is assumption on my part, but Apple must have a lot of automated cleanup tasks running after start up. Perhaps File Vault decryption is part of it.

 

[5aga]

this happened to me last night on a new rMBP, and I also have Filevault enabled.

Hoping its just a Yosemite bug and not a hardware problem.

 

[VMukhtarov]

I also have this issue on Mid 2012 MBP 13 with 10.10.3 and FileVault enabled.

 

[christarp]

Hmm, very interesting. Perhaps it is something filevault is causing? Or maybe it's just 10.10.2+ that introduced the bug. I don't think I ever had it happen pre 10.10.2.