Enabling Trim on 10.10.4. Slowdowns.

[east85]

I enabled Trim via Terminal on 10.10.4 and experienced excessive beachballing on my Crucial M4 SSD. My MacBook model is in my signature. This was pretty odd. Anyways, I eventually disabled native Trim via Terminal and re-installed the third party TrimEnabler application. I had disabled TrimEnabler and uninstalled prior to enabling Trim natively with Terminal, so everything should have been "clean" so to speak.

For whatever reason TrimEnabler works fine and I get no beachballing, while Terminal Trim that has been natively put into 10.10.4 has been a nightmare.

I'm just wondering if anyone might have any ideas as to why this is, or if anyone has had a similar experience.

 

[Gav2k]

Not all models are currently supported and excessive beach balling is the noted behaviour

 

[east85]

Not all models are currently supported and excessive beach balling is the noted behaviour

I'm curious, is there any official list of supported third party SSDs? Or a list of ones that exhibit problems?

 

[Gav2k]

To be honest it's bits from around the web and it's crucial and Samsung that are mainly effected but not all models. Intel seems to be the least problematic

 

[davidlv]

To be honest it's bits from around the web and it's crucial and Samsung that are mainly effected but not all models. Intel seems to be the least problematic

Just to add one more data point: Plextor M5P in a cMP SATA 2 sled works with the terminal Trimforce command, so does a Plextor M5S in a late 2011 MBP (SATA 3), both running the OSX 10.10.5 2nd public beta.

 

[chrfr]

To be honest it's bits from around the web and it's crucial and Samsung that are mainly effected but not all models. Intel seems to be the least problematic

Multiple Samsungs work fine for me. There was that Linux bug regarding Samsung trim that got everyone nervous but I haven't seen any legitimate, verified reports that Samsungs go slower when trim is enabled.

 

[Sean869]

I enabled Trim via Terminal on 10.10.4 and experienced excessive beachballing on my Crucial M4 SSD. My MacBook model is in my signature. This was pretty odd. Anyways, I eventually disabled native Trim via Terminal and re-installed the third party TrimEnabler application. I had disabled TrimEnabler and uninstalled prior to enabling Trim natively with Terminal, so everything should have been "clean" so to speak.

For whatever reason TrimEnabler works fine and I get no beachballing, while Terminal Trim that has been natively put into 10.10.4 has been a nightmare.

I'm just wondering if anyone might have any ideas as to why this is, or if anyone has had a similar experience.

Have you updated the firmware. There is a new version for Crucial drives. I updated my MX100 256gb and then enabled trim with no problems.

 

[Sean869]

The new version of the firmware is MU02 and one of the fixes is problems with Trim

 

[east85]

The new version of the firmware is MU02 and one of the fixes is problems with Trim

Thank you for the heads-up. Unfortunately the latest revision of firmware for my Crucial M4 2.5" drive was released in 2013 and has not been updated since (070H). So I am current on firmware. Glad to hear you found a way to make this work. For the time being, running TrimEnabler isn't much of a bother. Maybe El Capitan will be better, just have to wait and see, or wait for firmware.

 

[Fishrrman]

If it was me, and
If it was a matter of TRIM enabled with beachballs, or
TRIM DISabled with no beachballs,

I'd just DISable TRIM and go with "what works"...

 

[Yaboze]

Samsung 840 Pro here, no issues with Trim on.