541 Views 2 Replies Latest reply: Nov 19, 2012 11:28 PM by fausttiger
Every time I reboot my Lion Filevault Mac, the following FDERecoveryAgent items always appear in my console log. Firevault was installed AFTER upgrading to Lion.
If I understand FDERecoveryAgent
8/29/12 9:15:09.022 AM FDERecoveryAgent: Waiting for CoreStorage encryption be activated, will try again in 5 seconds
8/29/12 9:15:14.036 AM FDERecoveryAgent: Waiting for CoreStorage encryption be activated, will try again in 10 seconds
8/29/12 9:15:25.018 AM FDERecoveryAgent: Waiting for CoreStorage encryption be activated, will try again in 20 seconds
8/29/12 9:15:45.035 AM FDERecoveryAgent: Waiting for CoreStorage encryption be activated, will try again in 40 seconds
8/29/12 9:16:25.316 AM FDERecoveryAgent: No recovery record to post (this may be normal if you change keys more frequently then the recovery service can be contacted)
8/29/12 9:16:25.505 AM com.apple.security.FDERecoveryAgent: spawn: launchctl unload -w /System/Library/LaunchDaemons/com.apple.security.FDERecoveryAgent.plist
I have not changed my encryption keys since initial Filevault enablement (other than turn on encryption for my Time Machine volume).
If I understand the agent properly.
FDERecoveryAgent -- Full Disk Encryption Key Recovery Transmission Agent
FDERecoveryAgent sends encrypted CoreStorage key recovery information to Apple. It is run only when
"Store the recovery key with Apple" is selected, and even then only if the information could not be
transmitted when that option was first selected.
Then this means that my mac thinks that the CoreStorage recovery information was NEVER sent to Apple when Encryption first turned on, and hence Apple does not have a copy of it for restoration? (although it accepted all my info and questions/answers when Filevault turned on.
Firevault is enabled for both my boot partition and my time machine drive.
Recovery volume is in place, and can be booted from.