"FileVault Failed" Unable to enable FileVault on Fusion drive 10.11.1

[reptarwilleatu]

Has anyone run into this since upgrading to El Cap?

I had major issues with Yosemite and my entire system slowing to barely a crawl when FileVault was encrypting (as well as when it was done), but it was only the last few versions before El Cap came out. The fusion drive that i have is a self made one, i added an OWC SSD to my 2011 iMac and left in the spinning drive and merged those into a fusion drive with OS X. I tired erasing the fusion drive and rebuilding it to no success in getting it to work and since i had been able to encrypt it previously, i wondered if maybe the new System Integrity Protection in 10.11 was preventing it for some reason, but i tested temporarily disabling it and i was still receiving the same message.

Any ideas on what might be going on or how to fix it?

 

[aldrinjtauro]

Can you post the outputs of "diskutil list" and "diskutil cs list" from Terminal? It's hard to figure out what's going on without much info.

 

[reptarwilleatu]

Can you post the outputs of "diskutil list" and "diskutil cs list" from Terminal? It's hard to figure out what's going on without much info.

oh right, sorry bout that. here you go

/dev/disk0 (internal, physical):

#: TYPE NAME SIZE IDENTIFIER

0: GUID_partition_scheme *60.0 GB disk0

1: EFI EFI 209.7 MB disk0s1

2: Apple_CoreStorage Fusion 59.7 GB disk0s2

3: Apple_Boot Boot OS X 134.2 MB disk0s3

/dev/disk1 (internal, physical):

#: TYPE NAME SIZE IDENTIFIER

0: GUID_partition_scheme *500.1 GB disk1

1: EFI EFI 209.7 MB disk1s1

2: Apple_CoreStorage Fusion 499.2 GB disk1s2

3: Apple_Boot Recovery HD 650.0 MB disk1s3

/dev/disk2 (internal, virtual):

#: TYPE NAME SIZE IDENTIFIER

0: Apple_HFS OS X +553.4 GB disk2

Logical Volume on disk1s2, disk0s2

32AECBA3-253F-420D-B1B3-EB15FDFB8A1D

Unencrypted Fusion Drive

/dev/disk3 (external, physical):

#: TYPE NAME SIZE IDENTIFIER

0: GUID_partition_scheme *1.0 TB disk3

1: EFI EFI 209.7 MB disk3s1

2: Apple_CoreStorage WD 999.9 GB disk3s2

3: Apple_Boot Boot OS X 134.2 MB disk3s3

/dev/disk4 (external, virtual):

#: TYPE NAME SIZE IDENTIFIER

0: Apple_HFSX WD +999.5 GB disk4

Logical Volume on disk3s2

A39D0EEF-6416-4464-9993-895C3C70D5ED

Unlocked Encrypted








CoreStorage logical volume groups (2 found)

|

+-- Logical Volume Group 013DAC5B-A966-41DD-A5A8-F353849F4DA9

| =========================================================

| Name: Fusion

| Status: Online

| Size: 558926610432 B (558.9 GB)

| Free Space: 8192 B (8.2 KB)

| |

| +-< Physical Volume E1DD3AF6-689F-4A0C-A66C-E5E50DEFC709

| | ----------------------------------------------------

| | Index: 0

| | Disk: disk1s2

| | Status: Online

| | Size: 499248103424 B (499.2 GB)

| |

| +-< Physical Volume 7A5B7CCA-6D64-490D-9459-BA655A6540BF

| | ----------------------------------------------------

| | Index: 1

| | Disk: disk0s2

| | Status: Online

| | Size: 59678507008 B (59.7 GB)

| |

| +-> Logical Volume Family 3E61B2AE-19BE-42E4-A08F-8D972E7C070F

| ----------------------------------------------------------

| Encryption Type: None

| |

| +-> Logical Volume 32AECBA3-253F-420D-B1B3-EB15FDFB8A1D

| ---------------------------------------------------

| Disk: disk2

| Status: Online

| Size (Total): 553406955520 B (553.4 GB)

| Revertible: No

| LV Name: OS X

| Volume Name: OS X

| Content Hint: Apple_HFS

| LVG Type: Fusion, Sparse

|

+-- Logical Volume Group 01E90E62-15F6-4948-85A4-8BF001F637D8

=========================================================

Name: WD

Status: Online

Size: 999860912128 B (999.9 GB)

Free Space: 18923520 B (18.9 MB)

|

+-< Physical Volume 128CA09E-F85A-4669-8111-9F53750E5584

| ----------------------------------------------------

| Index: 0

| Disk: disk3s2

| Status: Online

| Size: 999860912128 B (999.9 GB)

|

+-> Logical Volume Family D3121E30-0395-4F07-BA69-3B4C0DFBE254

----------------------------------------------------------

Encryption Type: AES-XTS

Encryption Status: Unlocked

Conversion Status: Complete

High Level Queries: Fully Secure

| Passphrase Required

| Accepts New Users

| Has Visible Users

| Has Volume Key

|

+-> Logical Volume A39D0EEF-6416-4464-9993-895C3C70D5ED

---------------------------------------------------

Disk: disk4

Status: Online

Size (Total): 999489667072 B (999.5 GB)

Conversion Progress: Complete

Revertible: Yes (unlock and decryption required)

LV Name: WD

Volume Name: WD

 

[Falcon16]

possible OS reinstall from the recovery partition might fix that.

 

[reptarwilleatu]

possible OS reinstall from the recovery partition might fix that.

why would that fix it? like i said, i've broke apart the drives (which erases them) and put them back as a Fusion Drive and reinstalled from a backup.

 

[Falcon16]

My thought is possibly the system that actually does the encryption is borked and reinstalling might fix any files that are corrupted. If you wanted to try something before a reinstall from recovery I'd possibly attempt a first aid on each drive in the fusion drive set. See if there are any errors in either one

 

[reptarwilleatu]

My thought is possibly the system that actually does the encryption is borked and reinstalling might fix any files that are corrupted. If you wanted to try something before a reinstall from recovery I'd possibly attempt a first aid on each drive in the fusion drive set. See if there are any errors in either one

there isn't. i'm pretty sure that can't be what's going on given that i have an external hard drive that i just encrypted a few days ago as well as my Time Machine backups on the drive i use for that. If what you're saying is the case, i believe i wouldn't be able to do that with those since those depend on FileVault for the full disk encryption system. Obviously those aren't Fusion Drives like my internal drives, but it still relies on the same system.

 

[Falcon16]

OK given that information that points to something with the specific drives or perhaps a bug with the OS

 

[JohnDS]

Are there error messages in the Console logs for the time just before you got the error message, and if so, what are they?

 

[JohnDS]

I found this comment on using File Vault with a DIY fusion drive here: http://blog.macsales.com/15617-creating-your-own-fusion-drive


Mark @ 11:54 pm on March 16, 2014

I had an issue that I not sure everyone is aware of. If you reformat and destroy the Recovery partition you are not going to be able to install one after the core storage is made. you must look at the drive when you do the diskutil list and make sure that you don’t use the entire drive for the CORE Storage. Instead you may see something like this..disk0..disk0s1 and so on in my setup my recovery partition is in disk0s3. Obviously disk0 is my SSD so when listing it you have to in my example list the drives like this diskutil cs create “drive name” disk0s2 disk1 that way you leave the Recovery partition intact. Otherwise FileVault and other service won’t work plus you will have to be sure to have a thumb drive with a OSX install on it.

Don't know if that helps or means anything to you.

 

[reptarwilleatu]

Are there error messages in the Console logs for the time just before you got the error message, and if so, what are they?

here is the error message that is in the Console logs

12/9/15 12:43:05.000 AM kernel[0]: CoreStorageFamily::commitFamilyProperties: lv_commit_properties returned 28
12/9/15 12:43:05.000 AM kernel[0]: CoreStorageFamily::updateFamilyProperties: commitFamilyProperties returned 28
12/9/15 12:43:05.000 AM kernel[0]: CoreStorageLogical::resumeBackgroundTransform: couldn't get state, or state is not Converting'
12/9/15 12:43:05.393 AM com.apple.preference.security.remoteservice[1445]: *** CoreStorage conversion failed with mainError: -69694; detailError: -536870212

 

[reptarwilleatu]

so i tried it again yesterday and Filevault decided to work except that now it's stuck on this.

I've tried rebooting off a external install flash drive, running First Aid, it says it's repairing and then that it's trimming unused blocks, but no luck as far as getting it to resume the process of encrypting. any ideas?