Mojave installation will change the fusion drive to APFS without option. Mine completely stopped working once that happened. I have an 850 evo on an OWC card and a SM951 combined into a fusion drive. I had to install Mojave on a different hard drive and CCC it over to the fusion drive. Works great when using Mac OS extended journaled on the fusion drive. Getting about 1500mbs up and down with the combined drive just like with HS. It confused me for a couple of days as Mojave worked fine on my backup HDD but then acted like the video card was the issue when installed on said fusion drive. Nope the APFS format of the drive was the issue. Just FYI for those of you using the fusion option.
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.
Heads up for NVMe/SATA FUSION drives in Mojave.
- Thread starter SneakyTLoD
- Start date
- Sort by reaction score
Thanks SneakyTLoD, but this post would really be more helpful if placed in the Mojave section. Probably there are fewer MP users using Fusion than any other systems.
I posted it here as it has more to do with unsupported aftermarket NVMe boot options which only Mac Pro user will be trying. I know a lot of people have opted for efi hacks for NVMe boots but there are some of us that chose the fusion route prior to that being an option and are happy with it.
Could you show your diskutil apfs list? I couldn't get Mojave to boot after install on a clean new apfs container with ssd-sata + nvme. So just adding a Mac osx extended partition would help the boot to see the drives?
I created the fusion drive with Mac OS Extended (Journaled) then used Carbon Clone Copy to clone the Harddrive that Mojave was successfully installed on. This allows you to keep the Mac OS Extended (Journaled) format on the fusion drive so that it is still bootable.
I'm beginning to prepare for my Mac 3,1 and Fusion drive upgrade but I'm not using a PCI card to make the SSD side of the equation happen. I would think that if both were on the main SATA bus, this might not be a problem. Still, I need to work this into the list of things that might go wrong. SoftRAID has just released a Mojave compatible version (5.7) so I'm good to go there.
Of course, backup twice before doing anything!
Of course, backup twice before doing anything!
The main reason my drive was created as a fusion drive was to allow the boot-ability of the sata ssd while retaining most of the speed of the NVMe. It's a rare use case for sure, though I know of a few others using it. I also tried software raid 0 but the performance dropped to the speed of the sata drive.
I would suspect that a traditional fusion drive would not have this problem and apfs would work as expected but I can't be for sure. Though I still feel like this belongs in the Mac Pro section as I doubt it affects anyone else.
I would suspect that a traditional fusion drive would not have this problem and apfs would work as expected but I can't be for sure. Though I still feel like this belongs in the Mac Pro section as I doubt it affects anyone else.
Update. I was able to get the fusion drive formatted to APFS and still be bootable. For some reason you have to disable SIP. Have no idea why but that did the trick. Maybe something to do with it showing as an external drive? If I re-enable it goes back to being non-bootable. Go figure.
May have spoken too soon. Though I am bootable once again it seems as though my speeds are restricted to SATA3. Guess it's time to split it up and go with nVME boot on the Mac Pro. Time to hack my ROM!
No, just wait for the release of 10.14.1, it has a firmware updater that includes BootROM 140.0.0.0 which has the NVMe driver already injected.. by Apple!
I'm trying the same thing and am having the same issue. I now have an APFS fusion drive with a 1TB SSD + the built in NVME. It's working normally (stable), however, I'm not the SSD speeds, not the NVME speeds.
EDIT: figured out a fix for this. The problem is that the fusion drive has the wrong drive selected as the main drive. Fix here: https://forums.macrumors.com/thread...-isnt-reaching-nvme-blade-ssd-speeds.2169105/
Last edited: