Mac + Samsung SSD = TRIM?

I have upgraded my MacbookPro 15" Early 2011 with a Samsung SSD 840 Pro 512GB. It was performing extremely smooth and well using OS 10.9 (Mavericks).

Last week, I have upgraded the OS X to Yosemite and now I'm experiencing frequent significant slow down (significant waiting time for disk access). Is anyone experiencing the same problem and if there's any solution out there?

- MacbookPro 15" Early 2011

- 8GB

- Samsung SSD 840 Pro 512GB

Previously installed TRIM Enabler (which disabled the Kext signing). After experiencing significant hangover time, I have disabled TRIM and reenabling the Kext. However, it doesn't help. My laptop continues to experience significant random slow down and hangover. It didn't crash but the disk access is definitely not performing smoothly. Significant slowdown appears to be more problematic when running Parallels 10.

Thanks for your help.

Victor

Likewise, I have a MBP with 2x Samsung 512 SSDs installed with Trim Enabler

Thanks for your comment on SSD support only for Macs that had SSDs installed at time of purchase - as I have been looking around for Apple SSDs for an expensive re-retrofit for my MBP. I had waited to find out what any positive developments for trim for third party SSDs on Yosemite (and still waiting), so it looks like my Mac will also be staying on Mavericks (and therefore with trim enabled).

Taking your logic one set further though ... So if you have a Mac originally came with an SSD, you could upgrade it to a higher capacity Apple SSD, and maintaintrim natively? e.g. replacing a failed SSD under warranty?

Apple hardware is more and more evil, remember non upgradeable 2104 Mac Mini (only 1 SATA port, ***?)... This TRIM problem is making me to think about change of platform 😟

In a Q&A issued by Crucial it suggests allowing the machine to sit idle but powered up to allow the Garbage Collection process to take place.

It suggest leaving the machine quiet for 6 hours. Achieved by allowing the machine to stay in the drive selection option - achieved by pressing Option or alt during power on and not doing anything for a length of time

see

http://forum.crucial.com/t5/Crucial-SSDs/My-SSD-used-to-be-so-much-faster-What-h appened/ta-p/118310

Of course that's for a Crucial SSD, and depends on Crucial firmware. Since this topic is about Samsung 840EVO SSDs, it's going to be irrelevant. Why do people here bring up non-relevant information when others post specific hardware questions? Who knows.

Great news. As of June 12, 2015 it seems Trim Enabler will be allowed to run without comprising kext security in El Capitan and Yosemite 10.10.4.

See https://www.cindori.org/trim-in-os-x-el-capitan/

OS X 10.10.4 includes a command line tool that enables TRIM for 3rd party drives. I suspect this will be in 10.11.x El Capitan as well, so there is no need to go around installing random 3rd party drivers.

To enable TRIM, first save all your open documents as this will reboot your Mac.

1) launch Terminal.

2) Type "sudo trimforce enable".

3) Confirm that you want to enable trim.

4) Reboot your Mac.

To verify that TRIM is enabled, click the Apple icon in the top left of your screen. Choose "About this Mac" -> "System Report" -> "SATA/SATA Express" and look for the entry "Trim Support". It should say "yes" if trim has been enabled.

I have a Samsung 1TB 850 EVO running on my mid 2012 MBP since enabling trim in OS X 10.10.4 in July. Well this past Sunday I performed a reboot to clear the PROM in effort to resolve an odd Ethernet connectivity issue only to have the Samsung boot partition to not be seen at all. I was able to boot in recovery mode and run disk utility which marked the disk as corrupted/ not repairable. I had to wipe the drive and reinstall / restore from scratch. Naturally I suspect TRIM on Samsung to be at fault... especially after reading that the Linux kernel community has noted a bug and has black listed the Samsung and other SSD's.

/* devices that don't properly handle queued TRIM commands */

{ "Micron_M500*", NULL, ATA_HORKAGE_NO_NCQ_TRIM |

ATA_HORKAGE_ZERO_AFTER_TRIM, },

{ "Crucial_CT*M500*", NULL, ATA_HORKAGE_NO_NCQ_TRIM |

ATA_HORKAGE_ZERO_AFTER_TRIM, },

{ "Micron_M5[15]0*", "MU01", ATA_HORKAGE_NO_NCQ_TRIM |

ATA_HORKAGE_ZERO_AFTER_TRIM, },

{ "Crucial_CT*M550*", "MU01", ATA_HORKAGE_NO_NCQ_TRIM |

ATA_HORKAGE_ZERO_AFTER_TRIM, },

{ "Crucial_CT*MX100*", "MU01", ATA_HORKAGE_NO_NCQ_TRIM |

ATA_HORKAGE_ZERO_AFTER_TRIM, },

{ "Samsung SSD 8*", NULL, ATA_HORKAGE_NO_NCQ_TRIM |

ATA_HORKAGE_ZERO_AFTER_TRIM, },

/*

* As defined, the DRAT (Deterministic Read After Trim) and RZAT

* (Return Zero After Trim) flags in the ATA Command Set are

* unreliable in the sense that they only define what happens if

* the device successfully executed the DSM TRIM command. TRIM

* is only advisory, however, and the device is free to silently

* ignore all or parts of the request.

*

*/

I have not re-applied the trimforce option, nor do I plan to on this drive until Samsung addresses this issue or I replace it with a drive that is known to properly handle all TRIM specifications.