Sidebar Sidebar
Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.

Mac OS X 10.10.4 Supports TRIM for Third-Party SSD Hard Drives

ok so I havent' been able to do this particular update because I keep getting a not responding issue to App Store AND App Store Web Content. The device (my 2012 macbook air) was working fine and has a third party SSD from Transcend. Trim was enabled with their updated Trim enabler software when I installed the drive. I have a 2013 iMac with a 1tb ssd from apple and the update and appstore worked fine and continues to work fine.
 
Last edited:
I have Samsung 850 PRO 128GB the latest firmware is:
EXM01B6Q. Command "sudo trimforce enable" is worked or not?

I have tool Trim Enabler 3.3 and Trim works perfect my 850 PRO with Yosemite 10.10.4 without bugs no delete the wrong data my SDD.
 
Last edited:
... Apple still allows third party hardware?!? :confused:

That goes against their company slogan to create a magical user experience by having the world's greatest customers that they love so much pay through the nose for third-party hardware pre-installed in every machine by Apple.

They'll put a stop to this soon. :apple:
 
  • Like
Reactions: phairphan and Menneisyys2
Ledgem said:
Someone over at Ars Technica posted a warning about using TRIM with certain hard drives. I'll quote it here:


I haven't looked into it too heavily and I know that plenty of people use TRIM with these drives with no issues (I did in the past), but given that I use a Samsung 840, it gives me pause about enabling this feature. Just figured I'd put it out there for everyone else to see.
Click to expand...

Ah thanks for this. I have an 840 as well so I don't think I'll be enabling TRIM.
 
  • Like
Reactions: orbital~debris
Updated the firmware on my Crucial M550 and am enabling now, hope this doesn't ruin everything. :) Seen mentions of the Crucial drives on a Slashdot thread but then responses that the MU02 firmware (which it's shipping with, but my older one needed to be updated with) is safe with TRIM now. Hope that's true. :)
 
Ledgem said:
I haven't looked into it too heavily and I know that plenty of people use TRIM with these drives with no issues (I did in the past), but given that I use a Samsung 840, it gives me pause about enabling this feature. Just figured I'd put it out there for everyone else to see.
Click to expand...

What a load of nonsense. There are no TRIM bugs with Samsung 8xx SSDs, or indeed any SSD manufactured in the last 4-5 years.
 
  • Like
Reactions: ijbond and oneMadRssn
Reason077 said:
What a load of nonsense. There are no TRIM bugs with Samsung 8xx SSDs, or indeed any SSD manufactured in the last 4-5 years.
Click to expand...
Actually there are. Essentially though the bug seems to only affect queued TRIM commands which Linux and OS X use - in Windows it sends TRIM commands every once in a while along with data and flushes the queue to prevent issues. Linux and OS X on the other hand expect the drive to manage its own queue properly, which as it turns out, a lot of Samsung SSDs don't do.

Take a look at this article:
https://blog.algolia.com/when-solid-state-drives-are-not-that-solid/

Of note is that the Linux kernel has had a workaround written in for a while now. From the Linux kernel source code:
/* devices that don't properly handle queued TRIM commands */
Micron_M500*
Crucial_CT*M500*
Micron_M5[15]0*
Crucial_CT*M550*
Crucial_CT*MX100*
Samsung SSD 8*

You can see the code in question here:
https://github.com/torvalds/linux/b...35b5bc7/drivers/ata/libata-core.c#L4109-L4286
 
  • Like
Reactions: christarp, t0mat0, keysofanxiety and 1 other person
allanfries said:
Think, I will avoid any possible problems and just stick with the Trim Enabler by Oskar Groth (Cindori.org), that I've been using for the past 2 plus some years. Using a 240GB Kingston Hyper-X 3K SSD. Haven't had any issues.
But, nice to know there is a built in option now.
Click to expand...

The TRIM enabler does nothing else than the trim force command, i.e. activate the TRIM functionality built into Mac OS.
 
  • Like
Reactions: orbital~debris, Luap and Mr. Retrofire
YES! (I typed that in all caps because I am shouting in happiness.) :) While I knew from MacRumors reports that El Capitan will have TRIM support, I'm the type of Mac user who values stability and reliability above all else, so I only upgrade to the finalized version of a next-to-new OS as soon as the newest OS is released (for example, I upgraded from Snow Leopard to the final version of Lion when Mountain Lion was released, I upgraded from Lion to the final version of Mountain Lion when Mavericks was released, I upgraded from Mountain Lion to the final version of Mavericks when Yosemite was released, and I plan to upgrade to the final version of Yosemite as soon as El Capitan is released).

Due to my conservative upgrade habits listed above that value stability and reliability above all else, I am still using a mechanical hard drive instead of the latest and largest Samsung SSD because Mavericks never had native TRIM support. I am happy that I don't have to wait until the release of the successor OS to El Capitan (likely to be released in late 2016 after the final version of El Capitan is released) to finally enjoy using an SSD.

EDIT: Oh no! The article reports issues with Samsung and Cruical SSDs using Apple's TRIM support. Plus, it's a command line utility instead of being accessible through the GUI. I think I'll pass.
 
Last edited:
  • Like
Reactions: orbital~debris
Ledgem said:
Someone over at Ars Technica posted a warning about using TRIM with certain hard drives. I'll quote it here:


I haven't looked into it too heavily and I know that plenty of people use TRIM with these drives with no issues (I did in the past), but given that I use a Samsung 840, it gives me pause about enabling this feature. Just figured I'd put it out there for everyone else to see.
Click to expand...

So far there is no evidence indicating that the issue exists outside Linux. There are plenty of users running Samsung SSDs in Macs with TRIM enabled and I've yet to hear a single data loss issue.
 
  • Like
Reactions: alvindarkness, Weaselboy, ijbond and 8 others
One thing I don't know, is if the TRIM command Apple uses a queued one.

Many SSD controllers claim they support queued TRIM, but in fact they don't. Like Samsung 8*0 series, Crucial M550, the list goes on.
 
JoelTheSuperior said:
Actually there are. Essentially though the bug seems to only affect queued TRIM commands which Linux and OS X use - in Windows it sends TRIM commands every once in a while along with data and flushes the queue to prevent issues. Linux and OS X on the other hand expect the drive to manage its own queue properly, which as it turns out, a lot of Samsung SSDs don't do.
Click to expand...
I see no evidence that OS X uses or supports queued TRIM commands, even if the device firmware says that it supports queued TRIM commands. It is therefore impossible that the device firmware has a problem with queued TRIM commands.

The results of TRIM are also file system dependent (Linux ext4 vs. OS X HFS+ (Journaled)).

From:
http://www.opensource.apple.com/source/xnu/xnu-2782.1.97/bsd/hfs/hfscommon/Misc/VolumeAllocation.c
/*
* Validation Routine to verify that the TRIM list maintained by the journal
* is in good shape relative to what we think the bitmap should have. We should
* never encounter allocated blocks in the TRIM list, so if we ever encounter them,
* we panic.
*/
trim_validate_bitmap
Click to expand...

and

; Routine: hfs_unmap_free_extent
;
; Function: Make note of a range of allocation blocks that should be
; unmapped (trimmed). That is, the given range of blocks no
; longer have useful content, and the device can unmap the
; previous contents. For example, a solid state disk may reuse
; the underlying storage for other blocks.
;
; This routine is only supported for journaled volumes. The extent
; being freed is passed to the journal code, and the extent will
; be unmapped after the current transaction is written to disk.
Click to expand...

The HFS+ code uses the TRIM (unmap) command only, if the storage blocks on the device contain no longer necessary data.
 
Last edited:
  • Like
Reactions: alvindarkness, Temptin, oneMadRssn and 1 other person
Good news.

Seeing most of the Apple product line already comes with SSDs, happy to see that Apple still supports their older userbase.
 
  • Like
Reactions: Mr. Retrofire
so it is pretty much impossible to replace storage on anything that is current in the Apple lineup, but we have the TRIM support for 3rd party SSDs.
 
  • Like
Reactions: orbital~debris
I just ran a Black Magic disk test on my very old 2007 iMac with 120 GB Kingston SSD (cheapest at the time of buying) and it still performs the same (200 write and 400 read). No Trim enabled. Boot is under 13 seconds most of the time.
 
You must log in or register to reply here.
Register on MacRumors! This sidebar will go away, and you'll see fewer ads.
Top Bottom
Back