Want to highlight a helpful answer? Upvote!

Did someone help you, or did an answer or User Tip resolve your issue? Upvote by selecting the upvote arrow. Your feedback helps others! Learn more about when to upvote >

Looks like no one’s replied in a while. To start the conversation again, simply ask a new question.

DIY Fusion Drive and RAID 5

Hi everyone!


I have spent several hours by reading various forums but haven’t found any definitive answers.


I have a 12 Core Mac Pro with the following setup: one 1TB SATA hard drive that carries the system and applications. For the files and storage there are three 2TB SATA drives in RAID 5 controlled by Apple RAID card. I am going to install a 512 GB Samsung 840 Pro SSD drive in the optical bay and have initially planned to use it just for the system and applications, but am curious if the following is possible.


1) Is it possible to combine the RAID 5 array with the SSD and create a Fusion drive?

2) If yes, will it retain all the features of the RAID 5?

3) Should TRIM be enabled?


Thank you in advance!

Mac Pro, OS X Mountain Lion (10.8.2)

Posted on Nov 16, 2013 8:40 PM

Reply
7 replies

Dec 10, 2013 7:05 AM in response to Yegor

I followed pretty much the same procedure to create a Fusion Drive with an SSD + 4x 750gb drives as an AppleRAID-0. The procedure is pretty simple:


  1. Make sure you have a separate disk that you can install OS X (with updates) onto and boot up from while creating your volume. I found setting up Core Storage volumes from the Recovery Partition very flaky. Once prepared, start up from that volume.
  2. Erase any existing volumes on your SSD and RAID volume (you're going to lose them anyway, so make sure they're backed up first!). If you have any existing logical volumes on these then make sure they are deleted first.
  3. Install OS X onto your SSD like you normally would. This is important as it will ensure your recovery partition is created properly. Once installation is complete, restart back into your separate boot volume. If you don't want OS X on your Fusion Drive then you can skip this step. If you want to create a bootcamp partition on your SSD then you'll want to do it before rebooting back into your separate boot volume, though you may be able to do it using your separate boot partition (I haven't tried).
  4. If you're using an Apple RAID volume (as opposed to a hardware one) then create it now.
  5. Create your Core Storage volume group using the command diskutil cs create VolumeName disk1 disk2 , where disk1 is the device identifier for your SSD, and disk2 is the identifier for your AppleRAID volume (use diskutil list to get these). Just make certain that the first is your SSD.
  6. Use diskutil cs list to find your newly created volume group and get its UUID, enter this into the command diskutil cs createVolume GUID jhfs+ MyVolume 100%, once this is complete you should now have an empty Fusion Drive volume spanning your SSD and RAID volume.
  7. Re-install OS X onto the newly created Fusion Drive (assuming you even want OS X on it, if not skip this step).


This all works fine, but to cover the answers to your other questions; your RAID-5 should continue to function normally (to OS X it's just a single volume), however it only partially retains RAID-5 features. Specifically, by adding the Fusion Drive SSD you no longer have true single disk redundancy anymore, as if the SSD fails you won't be able to recover the data on the Fusion Drive volume. However, if an HDD fails then you can replace it as normal for a RAID-5 volume, not sure exactly how that works for Apple's RAID card, but it should be no different.


Whether TRIM should be enabled; it depends a lot on your SSD controller, if it has automatic garbage collection then you probably don't need to enable TRIM, in fact it may perform better with TRIM disabled.

Dec 10, 2013 7:37 AM in response to Iain Simms

TRIM directly addresses the shortcomings of having only garbage collection available. SSD controller manufacturers and designers (including SandForce, the controller manufacturer for OWC's SSDs), recommends that TRIM be used with their products. So does Samsung.

For example, here's a 2011 ⚠ article from OWC describing how you don't need TRIM on their SSDs and how it can in fact hurt performance or reliability.

That article has been discussed here on MacInTouch before. In my opinion it's bad advice, and inaccurate in some of its assertions. It also ignores the recommendation made by SandForce to use TRIM with their SSD controllers. But even if one were to take that article at face value, applying that advice to SSDs other than OWC's makes little sense.

The reason I'm advising against TRIM is simply that it's yet another driver-level modification of the OS, and these always carry potential risk (as all the folks with WD hard drives who lost data can attest to).

Apples and oranges comparison, for a variety of reasons. The short of it is that TRIM is supported natively in all recent versions of OS X. The tools used to enable it for third party SSDs do not add a new kernel extension; they change the setting to allow Apple's native TRIM implementation to be used with SSDs other than those factory installed by Apple.

This shows that the 840s do work slightly better with TRIM than without, but the differences are (in my opinion) trivial, a 9% increase at best.

One of the major reasons for the skepticism that exists about TRIM is that so many people, the authors of both articles you linked to included, don't understand it.


TRIM is not, strictly speaking, a performance-enhancement technology -- though it is plainly obvious that most people think it is.


Though it can, in many circumstances, improve performance, there are also circumstances under which it will provide little or no noticeable benefit. Not coincidentally, a new SSD tested fresh out of the factory packaging is unlikely to show much (if any) benefit. Or rather, TRIM is providing a real benefit for new SSDs, but that benefit doesn't become measurable in terms of benchmark performance testing until every memory cell in the SSD -- including many gigabytes of cells hidden from visibility by the SSD controller -- have been written to at least once. Writing 128 GB of files to an SSD with a nominal capacity of 128 GB won't do it, as there are several gigabytes (exact number varies depending on the model) still unwritten.


Under real-world use conditions, having TRIM disabled means eventually having noticeable write performance degradation due to write amplification. It is far greater than "9%" -- it can be a 50% or greater drop in write performance, depending on various factors. Defining "eventually" is difficult because it depends on how the SSD is used. But given enough time and write cycles, it can happen to all SSDs used without TRIM, no matter how sophisticated their garbage collection algorithms are.


Under those same real-world use conditions, having TRIM enabled means that the SSD should almost never reach a state of having noticeable write performance degradation, as it should almost never get into a state where write amplification is happening.


I will concede that it is possible to design a lab test in such a way as to defeat the benefits provided by TRIM, but such tests do not reflect any real-world usage scenario I can imagine. Furthermore, those same contrived tests would put an un-TRIMmed drive into an equally-addled state even more quickly.

I would suggest reading through the rather lengthy previous discussions about TRIM. Here are a couple of my past posts that are most relevant to the current discussion:


A description of what TRIM is here.

I addressed some of OWC Larry's comments about TRIM use with OWC/SandForce SSDs here.

http://www.macintouch.com/readerreports/harddrives/index.html#d09dec2013

Dec 10, 2013 9:25 AM in response to Iain Simms

Iain, that is an excellent answer, thank you!


I have thought over and over: since I need more than 2TB of space (and growing), plus I will lose one disk redundancy, I decided to buy a 4TB drive to fuse with the SSD and then just back-up everything on the RAID5 volume. For now, as the solid state drives don't offer enough storage, or if they do they are too expensive, the above configuration is the best for me.


Thank you again!

Dec 10, 2013 9:32 AM in response to Yegor

SSDs are for - system / scratch / Lightroom or Aperture Catalogues, all separate and not for media storage.


Put a couple SSDs on a PCIe card to free up the SATA2 bus and bandwidth


750GB Samsung 840 EVO $425 (that is how much I paid for 160MB back in 1990 era) 128GB had been as low as $85 which is ideal for 90% of users system boot drives, back on Black Friday weekend / cyber Monday.


The idea is to separate system / user files / media and such onto different drives to get concurrent IO.

The system does not need to be on SATA 3 and SSD with its near zero seek and latency and 100,000 IO per sec and high read access is ideal for a system. Pairing with a standard drive to create Fusion type?

DIY Fusion Drive and RAID 5

Welcome to Apple Support Community
A forum where Apple customers help each other with their products. Get started with your Apple ID.