Filevault stuck at pending

Question

I&#x27;ve been trying to enable Filevault on both my system and backup drives and it seems to be stuck. The Security &amp; Privacy preferences show "Estimating time remaining..." however the Console says it&#x27;s having a hard time and just repeats this every few seconds:8/9/11 11:35:42.358 AM System Preferences: *** -[DMManager conversionProgressForLogicalVolumeDisk:] returned an error; error: -69808 (-[SecurityFDEController _checkFDEEncryptionStatusTimer:])When I run the diskutil command it shows that the conversion status is Pending for both and doesn&#x27;t change:        Logical Volume Family 54A5D401-9A8C-43F1-BC11-BDD8D5629FE5        ----------------------------------------------------------        Sequence:               3        Encryption Status:      Unlocked        Encryption Type:        AES-XTS        Encryption Context:     Present        Conversion Status:      Pending        Has Encrypted Extents:  No        Conversion Direction:   -none-        |        +-&gt; Logical Volume A83A7F2F-F92C-4ECA-A1C2-740CA9926A2B            ---------------------------------------------------            Disk:               disk3            Status:             Online            Sequence:           3            Size (Total):       499445116928 B (499.4 GB)            Size (Converted):   -none-            Revertible:         Yes (no decryption required)            LV Name:            Backup            Volume Name:        Backup            Content Hint:       Apple_HFSXNot sure if this is related but I do notice that the UserEventAgent crashes every few seconds as well. Has anyone seen any of these issues?

singerkd · Accepted Answer

It appears that the UserEventAgent crashes indeed were related. I finally found that the /System/Library/UserEventPlugins/ServerTMShares.plugin was the culprit. Once I moved that out of the folder the crashes stopped and corestoraged said:8/28/11 9:40:29.098 PM corestoraged: 0x7fff7ad80960 unlockLVF: LVF&#x3D;F66CAD51-3351-471A-9D46-50FFE47482B2, "AES-XTS", status &#x3D; "Unlocked"The FileVault pane in the Preferences was also able to report on the progress and "diskutil cs list" reports progress as well.Here is the info from the UserEventAgent crash report that was relevant:Application Specific Information:objc[1532]: garbage collection is OFF*** Terminating app due to uncaught exception &#x27;NSInvalidArgumentException&#x27;, reason: &#x27;-[__NSCFArray isEqualToString:]: unrecognized selector sent to instance 0x7fa951d17cb0&#x27;*** First throw call stack:(          0   CoreFoundation                      0x00007fff934e9426 __exceptionPreprocess + 198          1   libobjc.A.dylib                     0x00007fff89bd0d5e objc_exception_throw + 43          2   CoreFoundation                      0x00007fff9357552e -[NSObject doesNotRecognizeSelector:] + 190          3   CoreFoundation                      0x00007fff934d62d3 ___forwarding___ + 371          4   CoreFoundation                      0x00007fff934d60e8 _CF_forwarding_prep_0 + 232          5   ServerFoundation                    0x0000000107d5e250 -[XSSharePointRecord addAttributesFromDSDictionary:] + 536          6   ServerFoundation                    0x0000000107d5e656 -[XSSharePointRecord initWithDSDictionary:] + 45          7   ServerFoundation                    0x0000000107d5d767 +[XSSharePointRecord recordWithDSDictionary:] + 61          8   ServerTMShares                      0x0000000107d34704 ServerTMShares + 5892          9   ServerTMShares                      0x0000000107d3408a ServerTMShares + 4234          10  ServerTMShares                      0x0000000107d34a5b ServerTMSharesCallback + 68          11  ServerTMShares                      0x0000000107d34cc2 ServerTMSharesCallback + 683          12  UserEventAgent                      0x0000000107937dc7 start + 1103          13  UserEventAgent                      0x0000000107938260 start + 2280          14  UserEventAgent                      0x00000001079379ac start + 52          15  ???                                 0x0000000000000003 0x0 + 3)

Nicholas Pufal · Answer

Hey,Although this post is from 2011, I was having the exact same problem as you (same log output was printed to Console).Instead of following the backtrace, I decided to do something simpler: deactivate FileVault and try again. And it worked for me 🙂So I just did the whole process of enabling it again. After restart, I was prompted for my password and the FileVault pane was displaying "30 minutes remaining". One slight difference, however, was that I decided to not send the key to Apple. I don&#x27;t think this is related, but it&#x27;s worth to point it out.Btw, I read on many places that some SSDs brands (like OCZ) may be incompatible. Mine is a SanDisk SATA III 240GB.Thanks,Nicholas

FromtheOrange · Answer

Same problem here on Mountain Lion 10.8.4 and the same error in the console.The problem is that ther is no ServerTMShares.plugin on my system so I can&#x27;t follow.And neither helped restarting my MacBook Pro. I tried it 3 times: turning FileVault on, restarting, seeing that it stucks, turning it off, restarting and then again, 3 times.What can I do? Please help.

tonijjj · Answer

Hi,Did you fix it?Im having the exact same problem, and dont have that "ServerTMshares".Its stuck just calculating the time to encrypt, and has been doing so for +5 hours. On a MBA mid 2013, 128GB SSD. OSX 10.8.5Thing is,, I cant even turn off File Vault either...Would appreciate any help!

PaulWasmund · Answer

I have seen this happen every time I turn on FileVault when booted from a disk with 4k blocks. Use diskutil info and check the Device Block Size: line. If it&#x27;s 4096 bytes that is the problem. Mavericks solves this problem to a certain extent, you just need to restart a second time after turning on FileVault. I haven&#x27;t tried this on Lion lately so I&#x27;m not sure of a way out of the problem. On Mountain Lion if you reboot again the system turns off FileVault and all is well.

JohnDoa · Answer

Here is a solution that works for me under Mountain Lion. WARNING: Use at your own risk. I have not lost any data, but since the solution depends on Disk Utility fixing some problems produced during the solution, I would not try this on a disk that is not safely backed up.I have a MacBook with an FileVault encrypted internal disk "IntHD" and several large (e.g. 3 and 4 TB) external USB 3.0 disks, all of which have 4096 block sizes. I used Carbon Copy Cloner to create a bootable clone of IntHD on partition "IntHD Clone" on external disk "ExtHD". When I boot from "IntHD Clone" and turn on FileVault, I have the problem seen by singerkd above.  One sees "Estimating time remaining …" forever, or if one enters "diskutil cs list" in Terminal one sees that the conversion is "Pending" not "Converting".Here is how I solved the problem:1. Reboot from internal disk "IntHD" and run Disk Utility Repair Disk on ExtHD and all its partitions. If Repair reports problems, run it again until no problems are reported.  If you reboot from "IntHD Clone",  FileVault should now found to be turned off.  (Obviously, you should replace "IntHD, "IntHD Clone", and "ExtHD"  by the names of your own disks and partitions in the following procedure.)2.Reboot from  internal disk "IntHD" and in Terminal, type:          diskutil corestorage convert "IntHD Clone"     (Note: the quotes around "IntHD Clone" are needed.)     You will see some output saying the conversion is complete.3. Run Disk Utility Repair Disk on "InHD Clone" on ExtHD.     One will likely get errors such as "The volume … found corrupt and needs to be repaired." and "Incomplete or inconsistent CoreStorage Physical Volume Set". (Note: Read WARNING above. You really need a good backup in case something goes wrong at this stage.)4. Reboot (from same internal disk "IntHD"), and run Disk Utility Repair Disk on "IntHD Clone" again. Repeat until no further errors are seen. To be sure, you should run Repair Disk on the whole ExtHD disk. After one or two passes, ExtHD should be error free.5. Reboot from partition "IntHD Clone" on the external disk "ExtHD", and turn FileVault on.6. Reboot from "IntHD Clone".  Under System Preferences Security &amp; Privacy, it should now say that FileVault is turned on and it is "Encrypting …" with "X hours remaining".7. Reboot from internal disk "IntHD" and get on with your life while FileVault Encrypts "IntHD Clone".     Note that the conversion to an encrypted disk only happens whenever "ExtHD" is attached to your computer, so if you just put ExtHD on the shelf at this point, it will not be properly encrypted, you need to leave it attached (or at least reattach it when convenient) until the encryption is complete. One can monitor the status of the encryption of "IntHD Clone" while running from "IntHD" by opening Terminal and typtyping          diskutil cs listIn the resulting output, look for "IntHD Clone" and find "Size (Total)" and "Size (Converted)". Initially the latter will be much less than the former and it will also say "Fully Secure: No", but they will be the same once the encryption is complete. Once complete it will also say "Fully Secure: Yes".