To recover the data you could probably do this on a Windows pc. Yea I know it goes against the grain but hey if it works. I would use a newer version of R-studio and mount those images as a volume set. Then scan the volume. If all goes well you should see the hfs+ partitions, the folders and the files.

I did actually try this but wasn't sure of the parameters to set for R-Studio. It's my understanding that although the Fusion volume operates similar to JBOD it cannot be rebuilt using standard JBOD parameters. Plus I think the Windows Bootcamp partition would throw off proper detect of the volume.

Here I would use a PC not a Mac running Bootcamp.
Not sure of the parameters but the R-studio support should know if this is possible. Might be worth asking?

Also Diskwarrior will support Fusion drives and might be a useful tool for recovery. Then after it can be used to attempt a repair.

Yes, I've check with Disk Warrior - no dice, when volumes are connect separately it doesn't detect it as a Fusion vol, when both are install in iMac system crashes immediately when iMac is connected via target disk mode or if you try to boot off USB so that is a no-go. I'm afraid volume is simply FUBARed.

I ended up using thunderbolt target disk mode and creating a 3.12TB R-studio image from the other connected mac. R-studio sees it as a Volume

Saves taking it to bits if drives are ok

I didn't do this on mine,but if you connect it via Target disk mode with the drives in the original positions and run Disk Warrior / Disk Utility on the Mounted volume you could get the thing to boot again if its just a wonky OS/X problem.


andy

_________________
Databusters Data Recovery Glasgow
http://www.datarecovery.co.uk/latest-data-recovery-jobs/

Can't do anything with target disk mode as it immediately prompts a kernel panic and spontaneous reboot if connected to another 10.8+ Mac via Thunderbolt. That is it goes into target disk mode but the moment you connect that cable to another Macbook / iMac the working system crashes and reboots, this happens regardless of whether it is booted into the OS, running off recovery volume, or booted off DiskWarrior 5 USB recovery volume.