Firevault has frozen, anyone know how to fix it?

Discussion in 'OS X Yosemite (10.10)' started by elcoopre, Jan 18, 2015.

  1. elcoopre macrumors newbie

    Joined:
    Sep 13, 2009
    #1
    I have a late 2011 macbook pro. I upgraded to Yosemite 10.10 recently and went ahead and started to encrypt my data to Firevault. My mac started to run really really slowly- about half speed and since Firevault was still encrypting I figured it must be that slowing me down. Rather than giving me an estimated remaining time, it seemed to have gotten stuck so I logged on to Terminal and disabled it thinking that would be the end of that.

    How wrong I was!

    Now it's started to decrypt Firevault and it's frozen on about 80.49%. I've checked the status on Terminal a bunch of times over the last 3 days and there's been no change. It's still not giving me an estimated time on system preferences though.

    I've tried to fire up Apple Hardware Test but it doesn't work.

    Does anyone know if reinstalling OS X or wiping my HD would fix the problem?
    Better yet if there's a quickfix to reset Firevault. So far all the info I've seen/ heard has told me I have to wait for it to finish what it's doing but it doesn't seem to be moving and hasn't for a few days now.

    Thanks!
     
  2. BasicGreatGuy Contributor

    BasicGreatGuy

    Joined:
    Sep 21, 2012
    Location:
    In the middle of several books.
    #2
    If you are absolutely positive it is stuck, you can boot into recovery mode (Command+R) to Disk Utility and erase the drive. Then you can install new again or restore from backup etc.

    If you have a stock drive, it will take anywhere from 12 - 17+hrs to encrypt, depending on how much is on your HD. It may not always show a time remaining.

    Best thing to do is be patient next time you run it.

    Edited to add: If the stock drive is 500 GB, it shouldn't take 3 days. You probably messed it up going into terminal.
     
  3. elcoopre thread starter macrumors newbie

    Joined:
    Sep 13, 2009
    #3
    I suspect you might be right! :)

    Thank you for the advice, I'm going to give that a try now.

    Thanks!
     

Share This Page