iMac's Fusion Drive 128GB SSD + ST3000DM001

[ThomasH]

I think I just encountered my first fusion drive, from a 27" iMac.
I only have the 3TB DM001 seagate that's suffering from the regular problems, yet is still mostly clone-able.
To add to the fun, filevault2 is also being used.
I wasn't able to decrypt the data on the fly with just the 3TB Seagate, since I couldn't find the EncryptedRoot.plist.wipekey file on the 3TB drive in the location below. I assume it's on the 128GB SSD. Can anyone confirm they've found it on the SSD? (again, I don't have the 128GB SSD yet).

A quick google search shows: The key file is EncryptedRoot.plist.wipekey found in com.apple.boot.X /System/Library/Caches/com.apple.corestorage/ (where X can change among literals R, S and P).

In my case, I was able to create a 99.96% perfect clone of the 3TB drive. Unfortunately though, it doesn't detect on a Mac, or ask for a password like it normally would, I assume since apparently the SSD is combined/added to the 3TB, and doesn't behave like cache.

My plan is to acquire and clone the 128GB SSD and try plugging that into a Mac with the 3TB clone and see what happens.

I just thought I'd ask if anyone had confirmation that this might work or had other suggestions from experience with these.
Without the 128GB SSD, it seems I might be missing a key piece to the puzzle.

I also wonder if DE is able to decrypt on the fly from these drives if both the SSD and hard drive are both present.

[300ddr]

This should work and I believe there is no other option. That is: you need both drives from the "fusion drive" to recover any data.

My plan is to acquire and clone the 128GB SSD and try plugging that into a Mac with the 3TB clone and see what happens.

[ThomasH]

It seems like the SSD might have been formatted prior to me receiving it...Should I be seeing data / an encrypted partition on the SSD, or would it look like a blank/formatted drive (like mine does)?

[300ddr]

I'd expect it to be full of data, or at least something in the very beginning. If all zeros, I'd guess either formatted or wrong drive.