File Vault: Encryption Paused
fmontrelay
Posted messages
103
Status
Membre
-
nana -
nana -
Hello,
File Vault is enabled on my Mac. However, the File Vault tab in Security & Privacy has been showing "Encryption paused" for several weeks.
I tried to disable File Vault, but the system tells me that the encryption must be completed first.
See screenshot below.
What should I do???
Thanks!
Configuration: Mac OS X (10.10.3) / Safari 8.0.6
File Vault is enabled on my Mac. However, the File Vault tab in Security & Privacy has been showing "Encryption paused" for several weeks.
I tried to disable File Vault, but the system tells me that the encryption must be completed first.
See screenshot below.
What should I do???
Thanks!
Configuration: Mac OS X (10.10.3) / Safari 8.0.6
2 réponses
Hello,
It seems that FileVault is causing problems under Yosemite.
I have read several articles on the subject, but there is currently no really reliable solution. I am on the beta version 10.10.4, but I don't know if that fixes the issue.
I suggest a trial.
Turn off the Mac.
Restart the Mac from its recovery partition, which means holding down the cmd and R keys throughout the boot process. (until the display)
If after launching Disk Utility, the main drive is grayed out, therefore not accessible for repairs:
- Go to the Startup Disk submenu from the menu bar (Apple menu if I remember correctly...)
You should see the main drive, possibly grayed out if not mounted due to FileVault, select it... the system will ask for the FileVault password, enter this password, but do not start from this drive, it’s just to mount the disk and thus make it accessible.
Then, with Disk Utility, perform a disk repair, followed by a permission repair.
Exit Disk Utility and quit the OS X Utilities, then restart normally.
Good luck.
EDIT:
Another test:
If you type this command in Terminal, what does it say:
fdesetup status
The response should be:
FileVault is Off
or
FileVault is On
If it’s "On" and then you type:
sudo fdesetup disable
then validate with your Administrator password and confirm that password... (you won’t see what you’re typing when you enter your password, that’s normal...)
What does it say?
To get an appropriate response, always specify your exact system configuration.
Have a good day :-) - Francis
It seems that FileVault is causing problems under Yosemite.
I have read several articles on the subject, but there is currently no really reliable solution. I am on the beta version 10.10.4, but I don't know if that fixes the issue.
I suggest a trial.
Turn off the Mac.
Restart the Mac from its recovery partition, which means holding down the cmd and R keys throughout the boot process. (until the display)
If after launching Disk Utility, the main drive is grayed out, therefore not accessible for repairs:
- Go to the Startup Disk submenu from the menu bar (Apple menu if I remember correctly...)
You should see the main drive, possibly grayed out if not mounted due to FileVault, select it... the system will ask for the FileVault password, enter this password, but do not start from this drive, it’s just to mount the disk and thus make it accessible.
Then, with Disk Utility, perform a disk repair, followed by a permission repair.
Exit Disk Utility and quit the OS X Utilities, then restart normally.
Good luck.
EDIT:
Another test:
If you type this command in Terminal, what does it say:
fdesetup status
The response should be:
FileVault is Off
or
FileVault is On
If it’s "On" and then you type:
sudo fdesetup disable
then validate with your Administrator password and confirm that password... (you won’t see what you’re typing when you enter your password, that’s normal...)
What does it say?
To get an appropriate response, always specify your exact system configuration.
Have a good day :-) - Francis
Hello Francis and thank you for all this.
The first solution does successfully execute the disk and permissions repair, but in the end, it's still the same (encryption paused) after rebooting.
..
The second solution:
- FileVault is On
- Then, I enter the password twice and get three little dots ""..."" followed by the prompt line.
- Then the system preferences tell me the same thing again (encryption paused)
So, no progress.
It doesn't prevent me from working on the disk, but it's strange and - in principle - I would like to encrypt my data.
Should I wait for a Yosemite update?
Have a good day
The first solution does successfully execute the disk and permissions repair, but in the end, it's still the same (encryption paused) after rebooting.
..
The second solution:
- FileVault is On
- Then, I enter the password twice and get three little dots ""..."" followed by the prompt line.
- Then the system preferences tell me the same thing again (encryption paused)
So, no progress.
It doesn't prevent me from working on the disk, but it's strange and - in principle - I would like to encrypt my data.
Should I wait for a Yosemite update?
Have a good day
It seems that the problem has been around for a while and is still not resolved; however, I just read cases where the issue was suddenly fixed after repeating the operations to start from the recovery partition to repair the disk AND the permissions, and sometimes after repeating the command
sudo fdesetup disable
in the Terminal.
It doesn't seem very scientific, but several people say they succeeded after repeating one method or another...
EDIT: As long as this problem is not resolved, I strongly advise against enabling FileVault. The risk of losing everything due to permanent encryption seems far too high.
sudo fdesetup disable
in the Terminal.
It doesn't seem very scientific, but several people say they succeeded after repeating one method or another...
EDIT: As long as this problem is not resolved, I strongly advise against enabling FileVault. The risk of losing everything due to permanent encryption seems far too high.
What should I do? Am I at risk of losing all my data?
I await your response, thank you in advance.
You'll get just as much help, but clearer because you're not jumping into an already open thread; you have your own thread.
It allowed me to personally restart the encryption