-
All replies
-
Helpful answers
-
Jan 5, 2015 10:56 PM in response to rolearyby SC::UK,Don'l hold your breath for a fix in the next version/patch of Yosemite. It's not fixed. All they've done is fixed the apparently erroneous message about connecting the power adapter. However, the encryption will remain in the paused state indefinitely. Not fixed.
-
Jan 7, 2015 3:57 AM in response to zinnjdby Groovysoul,This solution, http://www.macissues.com/2014/12/16/fix-your-mac-stuck-on-encrypting-with-fileva ult/, worked just as described for me. Hope it will for you. It's pretty frustrating and I accidentally knocked out the power chord for a second, but quickly plugged it back in. To my relief, the encryption resumed!
-
Jan 11, 2015 1:12 PM in response to SC::UKby aitormagan,I've been testing the latest beta and the problem is not fixed. The message for connecting the power adapter is not shown but the encryption is paused yet. I'm very disappointed with Apple: their computers are very expensive and the software is very poor. I haven't been able to fix the problem with the FileVault but this is not my only problem since I have serious problems related with the WiFi connection.
-
Jan 11, 2015 5:08 PM in response to aitormaganby owenw4rd,The only sure-fire fix is to do a clean reinstall after erasing the disk, or do a full backup to external drive with TimeMachine, erase the Mac partition and restore. Then enable FileVault. Both methods work, but the latter is faster.
-
Jan 12, 2015 7:07 AM in response to owenw4rdby jetpilotmrg,Correct. I wouldn't even trust Time Machine for the backup and restore job. I used Carbon Copy Cloner on the migration and it copied the files much better. Time Machine is flaky.
-
Jan 12, 2015 9:38 PM in response to zinnjdby yaz999,Thanks to scafede(Federico) [Discussion page #4] useful information. Your solution is just working for my trouble! Thanks.
But my experience is too bad. Because after the disc recovery, restarting encryption is only 10 minutes, but optimization is 7 DAYS....too long to wait.
If I know it, I'll select format and clean install to my disk.
But this is my case, Federico's solution is perfect for me.
-
Jan 18, 2015 1:06 AM in response to zinnjdby MacManX,After failing with the suggestions mentioned in this thread, I attempted an old-fashioned wipe and reinstall and stupidly nuked my boot partition. The good news is, this brought me into the Genius Bar for both help and answers.
It turns out, this is a known Yosemite issue affecting machines after a Time Machine migration, but not a Time Machine restoration, that’s the key.
The following is what I did to fix the issue (after the Genius wrangled me a new boot partition). It took me about 6 hours for almost 300 GB of data, so plan accordingly.
- Create a fresh Time Machine backup, duh.
- Reboot holding command-r.
- Choose to restore from a Time Machine backup. This will erase everything before restoring, so I hope you didn’t skip step 1.
- Once done, your computer will restart, and FileVault will be off. You can now safely switch it on via System Preferences -> Security to start the encryption process without issue.
-
Jan 18, 2015 2:40 PM in response to loicsansby poohbearistao,what was your fix that "Federico" provided?
-
Jan 18, 2015 4:41 PM in response to poohbearistaoby yaz999,Please check Discussion page #4 of this topics.
Handle name scafede (He signs Federico) gives good solution.
-
Jan 19, 2015 1:26 PM in response to zinnjdby DarkCrow,Not happy with Apple at all. My old Macs warranty ended two months ago and today it just was dead. Nothing. So I bought a new one. Got home, took it out of the box, and now I have this issue. That this happens isn't weird either Yosemite has to be the single worst OS X version ever.
-
Jan 20, 2015 1:11 PM in response to zinnjdby gidztar,To begin, I will state that I have fixed the problem for my MacBook. I wanted to share my story, in the hope that I can provide some reassurance if anyone else finds they cannot boot their OS, that there is a solution, and you don't need Apple support if you are willing to experiment. If you have your data backed up, there's not too much damage you can do (I think).
I had the same problem yesterday as what others have mentioned on here when I started using my new MacBook Pro on Yosemite. During the initial configuration on first boot, I left FileVault enabled. During the encryption process after startup, it paused indefinitely. I followed the steps others suggested on here - resetting PRAM, clearing disk permissions, repairing disk etc. with varying order. None of that worked. I later made a Time Machine backup onto my external HDD and attempted a restore via Recovery (Cmd+R). This failed quickly, but I can't remember what the error was. I think it had something to do with not being able to modify an encrypted disk, even though it said it would turn off FileVault. Presumably this is because it hadn't finished, which is why you can't stop it in the UI either. This had a bad consequence in that the partition was deleted when I inspected in Disk Utility. I was also unable to create a partition as the options were greyed out. The Disk Utility was not able to modify the Macintosh HD drive, other than a Repair Disk button which didn't help.
After some research, I came across a post online which explained how to delete the CoreStorage volume without the need to decrypt the drive. This is useful if the encryption process messes up. I ran the command:
diskutil cs list
This produces a list of the volumes. The top Logical Volume Group was my drive. Be sure to find the correct one! I copied the UUID (long number) into my clipboard for use with the next command:
diskutil cs delete MyUUID
where MyUUID is that number I copied into my clipboard.
After running that, it reformatted the CoreStorage volume into an unencrypted (HFS+) one, with a blank partition. This looked promising.
Afterwards, I booted into Recovery again and attempted the restore from Time Machine again. This time it was successful and the drive booted up with FileFault turned off. I decided, since I know how to fix the problem if it happens again, I would be a daredevil and attempt the encryption again. This time, the encryption was also successful, completing in less than 1 hour. I decided not to do any other tasks while that happened.
This experience was rather stressful, especially since it happened within a few hours of booting up the first time. However, it was an educational task for me, coming from a Windows background. There is clearly some major bug in FileVault when run in a Yosemite environment. I don't know if it affects everyone and if it can go wrong again, but I will be interested to see if Apple come up with a patch fix.
-
-
Jan 21, 2015 5:42 AM in response to DarkCrowby gidztar,I only had one, and the name property value was "Encrypted HD". Your configuration may be different to mine so be careful what you do.
Note that this process is not for those with Fusion drives.
Source: https://derflounder.wordpress.com/2013/06/29/erasing-a-filevault-2-encrypted-vol ume/
-
Jan 21, 2015 11:15 PM in response to zinnjdby ninedragon,http://www.macissues.com/2014/12/16/fix-your-mac-stuck-on-encrypting-with-fileva ult/
This actually fix my problem and now that popup in battery never happen again. MacBook Pro Retina 13in base model. Apparently my drive have some issues with permission so that FileVault cannot encrypting it. -
Jan 24, 2015 10:15 AM in response to zinnjdby VSwaves,A simple disk repair worked for me and started the encription. It has about 20 minutes to finish. Brand new macbook air i5, etc.