Got a tip for us?
Let us know
Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.
Can't Turn Off Encryption
- Thread starter Carlos-Pr7
- Start date
- Sort by reaction score
Well... my thinking is that if you set time machine to encrypt, then run a bunch of time machine backups (say a week's worth), then you'd have perhaps 50 gb on the time machine that is encrypted, so in order to turn it off, you would need to somehow un-encrypt all that data and rewrite it.
I'm suspecting that you would have to turn off time machine, erase the TM partition, and start over unencrypted.
I'm suspecting that you would have to turn off time machine, erase the TM partition, and start over unencrypted.
Code:
#: TYPE NAME SIZE IDENTIFIER
0: GUID_partition_scheme *160.0 GB disk0
1: EFI 209.7 MB disk0s1
2: Apple_CoreStorage 152.8 GB disk0s2
3: Apple_Boot Recovery HD 792.2 MB disk0s3
4: Apple_CoreStorage 6.2 GB disk0s4
5: Apple_Boot Boot OS X 134.2 MB disk0s5
/dev/disk1
#: TYPE NAME SIZE IDENTIFIER
0: Apple_HFS MACINTOSH HD *152.4 GB disk1
/dev/disk2
#: TYPE NAME SIZE IDENTIFIER
0: Apple_HFSX TimeMachine *5.8 GB disk2
carlos-paiva-raposos-macbook:~ carlospaivaraposo$I Tried to erase the Disk. Could you tell me a way to PERMANETLY DISABLE a disk?
Last edited by a moderator:
Try typing
in terminal it will tell if the disk is still being encrypted. It looks like a couple are but we don't know their state. That listing will tell us more.
Code:
diskutil cs list
Code:
carlos-paiva-raposos-macbook:~ carlospaivaraposo$ diskutil cs list
CoreStorage logical volume groups (2 found)
|
+-- Logical Volume Group AD97CE6D-F3D9-431A-B8BC-648662C4F77F
| =========================================================
| Name: MACINTOSH HD
| Sequence: 1
| Free Space: 0 B (0 B)
| |
| +-< Physical Volume D5B4A181-A7B9-4A18-86FF-E312A3E08F6E
| | ----------------------------------------------------
| | Index: 0
| | Disk: disk0s2
| | Status: Online
| | Size: 152753934336 B (152.8 GB)
| |
| +-> Logical Volume Family 3AFEA11B-960E-4609-881B-608663E5B4D9
| ----------------------------------------------------------
| Sequence: 9
| Encryption Status: Unlocked
| Encryption Type: AES-XTS
| Encryption Context: Present
| Conversion Status: Complete
| Has Encrypted Extents: Yes
| Conversion Direction: -none-
| |
| +-> Logical Volume AD7A4A45-6C15-49AD-A0A2-3D71A7CCBECA
| ---------------------------------------------------
| Disk: disk1
| Status: Online
| Sequence: 4
| Size (Total): 152435163136 B (152.4 GB)
| Size (Converted): 152435163136 B (152.4 GB)
| Revertible: Yes (unlock and decryption required)
| LV Name: MACINTOSH HD
| Volume Name: MACINTOSH HD
| Content Hint: Apple_HFS
|
+-- Logical Volume Group 34C1E9FD-2C07-49CB-89FD-4892FF8C6998
=========================================================
Name: Time Machine
Sequence: 1
Free Space: 276824064 B (276.8 MB)
|
+-< Physical Volume 6F4499B3-F859-4A4E-965A-B114DF29F388
| ----------------------------------------------------
| Index: 0
| Disk: disk0s4
| Status: Online
| Size: 6151802880 B (6.2 GB)
|
+-> Logical Volume Family 3DB844AD-FE06-4CA0-9628-9690D8455841
----------------------------------------------------------
Sequence: 2
Encryption Status: Unlocked
Encryption Type: AES-XTS
Encryption Context: Present
Conversion Status: NoConversion
Has Encrypted Extents: Yes
Conversion Direction: -none-
|
+-> Logical Volume 563706D1-8D30-4759-8CB7-DBA844EFCB31
---------------------------------------------------
Disk: disk2
Status: Online
Sequence: 3
Size (Total): 5833031680 B (5.8 GB)
Size (Converted): -none-
Revertible: No
LV Name: TimeMachine
Volume Name: TimeMachine
Content Hint: Apple_HFSX
carlos-paiva-raposos-macbook:~ carlospaivaraposo$
Last edited by a moderator:
You can the use the revert command,
diskutil cs revert disk0s4
If I'm reading the man page correct you should not need a passphrase if you are logged in, but being an external drive you might need to supply that since it is not an internal drive.
The GUI should work, and I have not used terminal with Core Services ( Filevault2), so beware.
Here is the man page info( man diskutil ) Core Services Section:
revert device | lvUUID [-stdinpassphrase] | [-passphrase passphrase] | [-recoverykeychain file]
Convert a CoreStorage logical volume back to its native type. The volume must have been created by means of conversion, e.g. with diskutil coreStorage convert.
If the volume was not created with a passphrase, then simple ownership of the affected disk is required; otherwise, a passphrase must be supplied, either interactively or via one of the parameters.
Backup your backup
before trying to decrypt, you might lose data.I don't think Carols can remove filefault 2 without formatting or repartitioning the drive.
Conversion Status: NoConversion (mine has "Complete")
Revertible: No (mine has "Yes (unlock and decryption required)")
Free Space: 276824064 B (276.8 MB) (mine has 0 MB) <-- I believe this is for the Logical Volume Mangement; the LVM should use 100% of the physical disk, then your "disks" are created inside the LVM container. I think this is the root cause of the problem; since the entire disk isn't used for LVM (core storage aka cs in Mac OS), it can't "go back."
I'm going to keep looking as time permits to confirm this.
Conversion Status: NoConversion (mine has "Complete")
Revertible: No (mine has "Yes (unlock and decryption required)")
Free Space: 276824064 B (276.8 MB) (mine has 0 MB) <-- I believe this is for the Logical Volume Mangement; the LVM should use 100% of the physical disk, then your "disks" are created inside the LVM container. I think this is the root cause of the problem; since the entire disk isn't used for LVM (core storage aka cs in Mac OS), it can't "go back."
I'm going to keep looking as time permits to confirm this.
Last edited:
Good catch, I just compared to mine. I have what you have. You might be correct, he might not be able to revert. Worth a try before a reformat.
Here is some info from a Mac OX Hint.
How did you encrypt your TM volume? Disk utility? Command line?
Last edited by a moderator:
Carlos:
If you are going to nuke the drive and start over, you may want to try this first.
or to enable encryption (which you already have, but may still need this):
and you'll be prompted to enter the password.
I personally would try the first one first (without the passphrase since it's already encrypted).
I don't know if this will cause any problems. I did this with a USB flash drive to encrypt it without formatting and had no problems, but since your disk is already encrypted, you are in unknown territory.
If it works and the disk is still encrypted, then you can try
This will take it back to the native format.
If you are going to nuke the drive and start over, you may want to try this first.
Code:
diskutil cs convert disk2s1or to enable encryption (which you already have, but may still need this):
Code:
diskutil cs convert disk2s1 --passphraseI personally would try the first one first (without the passphrase since it's already encrypted).
I don't know if this will cause any problems. I did this with a USB flash drive to encrypt it without formatting and had no problems, but since your disk is already encrypted, you are in unknown territory.
If it works and the disk is still encrypted, then you can try
Code:
diskutil cs revert disk2s1
Last edited:
You can only revert disks that were originally converted from plain-text. If you partioned your disk anew and had it encrypted at that point, decrypting it requires copying the data, formatting it again (this time without encryption) and copying it back.
I have not used the revert command but it is there for a reason, and the man page says it will ,
so using the GUI or the command line to encrypt, the revert command should not erase the data, but decrypt and leave the drive in the format it started in.
Note the language: it will convert it back to its native type. If it was created as a core storage volume, it can't do that because the information required to do so is missing (and there may be some header space issues, too.)
Also it quite explicitly says that the volume you're trying to convert has to have been a non-encrypted volume first, which was then converted by 'diskutil cs convert' (or something that has the exact same effect, such as time machine or filevault converting a disk.)
I read that as the native type being Mac OS Extended Journaled, or another format, so it would revert to what it was before the encryption. If Mac OS Extended Journaled before, then Mac OS Extended Journaled
after. I guess someone will have to test on some USB drives what the revert command does.
Yes, it says " The volume must have been created by means of conversion, e.g. with diskutil coreStorage convert", which is exactly what the convert command does. It encrypts the volume. The revert command does the opposite, as long as the volume was created with the CS convert command which an encrypted TM volume would be.
Last edited:
CyBeRino is correct. I just played with a spare flash drive.
If the disk is formatted with encryption, there is no "conversion" process since it was done "natively" during the format process. This means the only way remove encryption is to reformat.
If the disk is converted from a regular disk without reformatting or repartitioning, then it can go back to the pre-encryption state.
I'm now curious as to how Carlos encrypted the drive. My Time Machine was converted via the Time Machine applet in system preferences, so mine shows "conversion: complete."
If the disk is formatted with encryption, there is no "conversion" process since it was done "natively" during the format process. This means the only way remove encryption is to reformat.
If the disk is converted from a regular disk without reformatting or repartitioning, then it can go back to the pre-encryption state.
I'm now curious as to how Carlos encrypted the drive. My Time Machine was converted via the Time Machine applet in system preferences, so mine shows "conversion: complete."
Interesting. There is something Lion does not like about it. Quickest solution would be for OP to get his data off and start over I guess. Revert or not, I'm sure the OP does not have the time to figure it out. Sometimes easier to start over.
Yes yes, but what you're missing here is the volume in question was not made with the diskutil cs convert command. Therefore it cannot be reverted.
You posted without me noticing before I edited. The output from diskutil he posted tells us with certainty that didn't happen.