How to Create a Fusion Drive on a Hackintosh (Sierra, High Sierra, Mojave)

To build a Fusion Drive on a Hackintosh, you pair an SSD and HDD into a single CoreStorage logical volume. Apple introduced this in OS X 10.8 Mountain Lion and kept it through macOS Mojave. On a custom PC, you need careful disk management, bootloader configuration, and awareness of version-specific pitfalls. This guide covers the process for Sierra, High Sierra, or Mojave Hackintosh builds, focusing on data safety and boot stability.

What Is a Fusion Drive and Why Use It on a Hackintosh?

A Fusion Drive is not a RAID array. It is a CoreStorage logical volume group (LVG) that presents a single CoreStorage logical volume (LV) to the operating system. The CoreStorage kernel extension (AppleCoreStorage.kext) moves frequently accessed files to the faster SSD tier and less used data to the HDD tier, all transparently. On a Hackintosh, the same kext works provided the system meets the same hardware abstraction requirements: a properly injected DSDT, working SATA controllers in AHCI mode, and a bootloader that can handle CoreStorage volumes.

Common motivations for building a Fusion Drive on a Hackintosh include extending the life of a small SSD by pairing it with a large spinning disk, or consolidating two physical drives into one volume without the overhead of RAID striping. However, the complexity of recovery if the volume becomes corrupted, and the fact that Apple no longer actively develops CoreStorage (replaced by APFS in High Sierra and later), means this setup is best reserved for older macOS versions where CoreStorage is still the native volume manager.

Prerequisites and Risks

• Two physical drives: one SSD (preferably 120 GB or larger) and one HDD (any capacity). Both must be internal SATA or properly passed through via a compatible controller.
• macOS version between 10.8 and 10.13 (High Sierra). Mojave still supports CoreStorage but Apple recommends APFS for SSDs; a Fusion Drive on Mojave will use CoreStorage with a special APFS container on top, which can cause boot issues on Hackintosh.
• Clover bootloader (minimum r4060 for proper CoreStorage injection, but r5123 is safer). OpenCore is not recommended for this legacy setup because its CoreStorage support is less mature.
• Full backup of all data on both drives. Creating or modifying a Fusion Drive will erase all existing partitions on both disks. There is no safe way to convert an existing installation into a Fusion Drive without reformatting.

Step 1: Prepare the Drives in Terminal

Boot your Hackintosh from a working macOS installation (preferably on a separate disk) or from a macOS installer USB. Open Terminal. Identify the disk identifiers of your SSD and HDD using diskutil list. They will appear as diskX (e.g., disk0 for SSD, disk1 for HDD). Double-check that you have selected the correct disks; this step is irreversible.

Erase both drives to a single partition each with a GUID Partition Table (GPT):

diskutil partitionDisk /dev/disk0 1 GPT JHFS+ "SSD" R
diskutil partitionDisk /dev/disk1 1 GPT JHFS+ "HDD" R

Replace disk0 and disk1 with your actual identifiers. This creates empty HFS+ journaled partitions. Do not format as APFS; CoreStorage works natively with HFS+.

Step 2: Create the CoreStorage Logical Volume Group

Now create the LVG containing both physical volumes:

diskutil cs create "Fusion" /dev/disk0s2 /dev/disk1s2

This command outputs a UUID string for the new LVG. Copy it. Then create a logical volume from the LVG:

diskutil cs createVolume  JHFS+ "FusionDrive" 100%

The volume will appear in Disk Utility as a single disk named “FusionDrive”. You can now install macOS onto it or migrate data.

Step 3: Enable TRIM for the SSD Tier

If your SSD is not an Apple model, you must enable TRIM via the trimforce command after the first boot into the new system. Run sudo trimforce enable in Terminal and confirm the restart. Without TRIM, the SSD performance will degrade over time, negating the benefit of the Fusion Drive.

Step 4: Configure the Bootloader for CoreStorage

Clover must see the CoreStorage logical volume to boot from it. In your Clover config.plist, under Boot:

• Set DefaultVolume to the UUID of the logical volume (not the LVG). You can find this UUID with diskutil cs info on the LV.
• Ensure InjectKexts is set to Yes or Detect so that AppleCoreStorage.kext loads.
• Add the boot flag csr-active-config as needed for SIP (usually 0x67 for legacy installations).

Clover’s EFI partition must remain separate from the Fusion Drive. The Fusion Drive contains only the macOS system volume; the bootloader resides on a dedicated EFI system partition (ESP) on one of the physical disks. Typically, you keep the ESP on the SSD for faster boot.

Step 5: Test and Verify

Reboot and select the Fusion Drive from the Clover boot menu. macOS should load normally. Once inside, run diskutil cs list to confirm the LVG is online and the volume is mounted. Check System Information → Storage to see the total combined capacity.

Known Issues and Workarounds

• Sleep/Wake Failures: CoreStorage volumes sometimes fail to remount after wake. This is rare but can be mitigated by disabling automatic sleep in Energy Saver preferences. For deeper troubleshooting, see our guide on AGPM editing for unsupported GPUs, though the issue is often ACPI-related rather than GPU-specific.
• macOS Updates: Installing a major macOS update (e.g., from 10.12 to 10.13) may break the CoreStorage volume structure. Always back up the entire Fusion Drive before updating. On High Sierra, Apple’s installer may attempt to convert the volume to APFS; you must decline this conversion if you want to keep CoreStorage.
• FileVault Encryption: Enabling FileVault on a Fusion Drive adds another layer of complexity and can make recovery nearly impossible without the original CoreStorage keys. Avoid it on Hackintosh.
• Disk Utility Recovery: If the Fusion Drive becomes corrupted, the standard Disk Utility First Aid may not repair it. Use diskutil cs revert to split the drives back into separate volumes, but this destroys all data. Advanced recovery requires rebuilding the LVG from the command line.

Final Verification Before Daily Use

After setting up, run a full disk verification: diskutil verifyVolume /Volumes/FusionDrive. Also confirm that the bootloader can locate the volume by checking the Clover GUI (press F2 at the Clover menu to save a debug log, then inspect /EFI/CLOVER/misc/debug.log for the CoreStorage entry). If you prefer to customize the system identity to match a Fusion Drive–native Mac model, refer to our article on customizing the About This Mac panel. After verification, your Fusion Drive should be stable for daily use. Still, keep a bootable installer USB handy—if the volume corrupts, you'll need it to run recovery commands.