Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.
I also have a samsung 850 evo 500gb in an early 2011 13"mbp. I want to install but use it for work and home (its my only computer) and id hate to lose personal pictures or work files.

If you're backing up your SSD like you should be doing already, then you'll have nothing to worry about.
 
  • Like
Reactions: oneMadRssn
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.

I was waiting for Hellhammer to chime in. If he is unaware of any evidence showing an issue with OS X, then that's good enough for me to enable it. Besides I was running Trim Enabler (before 10.10) with my 840 Pro with no issues.
 
How should I go about enabling trim this way if I already have it enabled through Cindori's Disk Sensei? Should I disable trim though Disk Sensei first, disable Kext signing and reboot then run the terminal command? I am aware of the boot issues with kext signing as that has happened to me before...

OR should I simply enable trim through terminal over the already enabled Cindori and reboot, hoping for the best?

What's the best route to take? I'm sure the majority of us are in a similar situation.
I uninstalled Disk Sensei (in El Capitan) and used the terminal command. I see no benefit in running both at the same time, as both (essentially) do the same thing, minus a few visual graphics provided with Disk Sensei).
 
Now that we have real TRIM, is there any advantage to the Apple SSUAX/SSUBX PCIe SSD's over generic Samsung SM951's?

Speed and 1TB storage. A couple of 512mb SM951’s as media and boot drives would be a killer set up though.
 
Last edited:
  • Like
Reactions: crjackson2134
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.
- Indeed. I'm not buying it, either. TRIM has been rock solid on my 830 for 3 years.
Do you know if there are any differences between this command and what Trim Enabler does?
 
  • Like
Reactions: Weaselboy
If you're backing up your SSD like you should be doing already, then you'll have nothing to worry about.

my time machine backup hard drive stays here at church with an external monitor and power cord. every morning i get to church i plug in the power, the monitor, and the time machine hd and it stays that way until i leave for the day.

personally i have some study files, all my personal family photos and videos. and work related all sorts of files for the kids classes and youth camps etc. and logos which is like the photoshop or final cut of bible study software.

if data gets messed up, and its backed up to the time machine, would that mean the TM hd is corrupted as well?
 
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.
As far as I know this bug (which has seen firmware updates that supposedly fixed but then actually didn't, then followed by more firmware updates that really fixed it, so far it seems they still do) affects the Samsung 840/850 regardless of whether you have TRIM enabled or not. It is not TRIM that is buggy, it is SSDs that have bugs.
 
- Indeed. I'm not buying it, either. TRIM has been rock solid on my 830 for 3 years.
Do you know if there are any differences between this command and what Trim Enabler does?
I've also have run TRIM for almost three years on my 830 now. There should not be any functional difference to Trim Enabler (as TRIM Enabler just enabled the built-in in TRIM). The real difference is that you no longer need to disable the restriction to only use signed kernel extensions to get TRIM on third-party SSDs (and that you no longer run the risk of almost bricking your Mac if you run an OS update while TRIM Enabler was 'switched on').
 
  • Like
Reactions: ijbond
my time machine backup hard drive stays here at church with an external monitor and power cord. every morning i get to church i plug in the power, the monitor, and the time machine hd and it stays that way until i leave for the day.

personally i have some study files, all my personal family photos and videos. and work related all sorts of files for the kids classes and youth camps etc. and logos which is like the photoshop or final cut of bible study software.

if data gets messed up, and its backed up to the time machine, would that mean the TM hd is corrupted as well?
If your TM backup history is long enough to contain a clean copy of a file (from before the file got corrupted by the SSD) then you should be safe. Note however that to get a file into the 'permanent' TM history (ie, that it stays in the TM backup as long as there is space for it on the TM drive), it needs to stay up to one week (uncorrupted) on your SSD.
 
  • Like
Reactions: Mr. Retrofire
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

This ATA_HORKAGE_NO_NCQ_TRIM refers to drives that wrongly report support for NCQ (Native Command Queue) TRIM. Apparently a recent firmware update (since pulled) to the Samsung 850 Pro caused it to wrongly report to the OS that it supported queued TRIM commands, when in fact all Samsung drives, like most SSDs, do not support queued TRIM and never have.

See:
https://bugs.launchpad.net/ubuntu/+source/fstrim/+bug/1449005/comments/52

This is not actually a bug with the normal un-queued TRIM command, and all this code is doing is forcing it to use normal TRIM for Samsung drives despite what the drive's firmware reports.

If there was really a TRIM bug with recent Samsung SSD's, the Samsung fanboys would be up in arms about it. There was a (performance) bug discovered with the SSD 840 EVO last year, and the web never heard the end of it, until Samsung fixed via a firmware update.
 
Last edited:
  • Like
Reactions: ijbond



Earlier today Apple released OS X 10.10.4, an under-the-hood update to OS X that introduced several bug fixes and improvements. One improvement, according to Ars Technica, is support for TRIM for third-party SSD hard drives. We previously covered TRIM likely coming natively to the next version of OS X El Capitan but it appears support has already arrived.

You *DO NOT* want to enable this on Samsung SSDs. All 840s and 850s have the data killing bug.

https://blog.algolia.com/when-solid-state-drives-are-not-that-solid/
 
TRIM and GC are not the same thing.

GC is not a replacement for TRIM regardless of foreground or background type. TRIM can only make the GC process more efficient and lower the write amplification
Honestly, I've given up correcting people about that. This fact has been repeated often enough, that if someone really cared about being informed, they'd know by now that they are not the same thing. I blame marketing. It's often claimed by industry leaders that TRIM is not useful on X company's SSDs, while that technically isn't true for any SSD.
 
Last edited:
  • Like
Reactions: alvindarkness
This is good, but why is it stating data loss may occur ? It the third party SSD has not support nativly, then its not support natively.... and likewise any tampering may cause uncertain risk.... Thus, there would be more failures on third party SSD with trim hat is not supported vs Apple's own SSD where you know is will work and no loss would occur. (considering all others being equal)

This kind of sounds bad, that a small chance that data loss will occurs for third party ssd's by enabling trim that APpe has no knowledge of, and they are helping with data loss..

If there was no chance of data loss, then there would be no warning..

In other words, I think Apple implements TRIM in their own way

Trim is basically garbage collection, where hard drives are smarter at doing this. SSD's need help at making sure the blocks are prepared to be written over.
 
my time machine backup hard drive stays here at church with an external monitor and power cord. every morning i get to church i plug in the power, the monitor, and the time machine hd and it stays that way until i leave for the day.

personally i have some study files, all my personal family photos and videos. and work related all sorts of files for the kids classes and youth camps etc. and logos which is like the photoshop or final cut of bible study software.

Time Machine only backs up things that the filesystem sees as having changed. Even if the file changed due to corruption, Time Machine will not know it, and will not back it up. The type of corruption you're talking about would only be backed up when a change that the filesystem knows about occurs, so the old non-corrupted file will still exist, assuming that backup is still around. If TRIM is going around causing corruption though, you'll soon notice a wide variety of issues, and be made aware that you have to restore from backup. I wouldn't worry too much.
 
This is good, but why is it stating data loss may occur ? It the third party SSD has not support nativly, then its not support natively.... and likewise any tampering may cause uncertain risk.... Thus, there would be more failures on third party SSD with trim hat is not supported vs Apple's own SSD where you know is will work and no loss would occur. (considering all others being equal)

This kind of sounds bad, that a small chance that data loss will occurs for third party ssd's by enabling trim that APpe has no knowledge of, and they are helping with data loss..

If there was no chance of data loss, then there would be no warning..

In other words, I think Apple implements TRIM in their own way

Trim is basically garbage collection, where hard drives are smarter at doing this. SSD's need help at making sure the blocks are prepared to be written over.
Apple is covering its bases, so to speak. I wouldn't read anything nefarious into the warning.
 
I have a OCZ Vertex 3 and i'm getting a few beachballs randomly that weren't there before.
Gonna give it a couple of days and if it doesn't improve, going to disable it.
 
I've also have run TRIM for almost three years on my 830 now. There should not be any functional difference to Trim Enabler (as TRIM Enabler just enabled the built-in in TRIM). The real difference is that you no longer need to disable the restriction to only use signed kernel extensions to get TRIM on third-party SSDs (and that you no longer run the risk of almost bricking your Mac if you run an OS update while TRIM Enabler was 'switched on').
- That's my thinking, too. It'd be great if more people would chime in.

Interestingly, I've never had the issue during updates. I've never disabled TRIM prior to an update (latest being 10.10.4), and all the updates ever did was just disable TRIM. No issues with it. I'm not going to push my luck by trying it with SMC/NVRAM, but I'm actually thinking that should be fine, too (for me, that is; I know others have had issues).
 
OWC drives don't require TRIM as they have their own garbage collecting tech built-in.

http://blog.macsales.com/21641-with-an-owc-ssd-theres-no-need-for-trim

This is just does not make any sense. This company should go out of business. My 400$ lost on a owc SSD. Living in Germany, they wanted me to send their piece of junk back for analysis. SMART Status was just "dead" and OS X slow as hell. Any Disk I/O took ages. They are expensive, they didn't support TRIM.

GC and TRIM are not the same things. Every SSD has a GC Controller. They advertise it like its their invention.

DONT BUY OWC STUFF.
 
Does enabling TRIM for the first time on an SSD that had been used for several months reverse the effects of not having TRIM enabled from the beginning?

Very good question. I too would like to know the answer to this, or if there is anything I can do to help my 4 year old Intel SSD that until now has had no TRIM
 
Register on MacRumors! This sidebar will go away, and you'll see fewer ads.