Yosemite and TRIM

[duffman9000]

Also, I don't see why people would even try running TRIM Enabler on a new OS? It works by patching a kernel extension, and with all the updates to SSDs it was highly likely that that extension would change, resulting in TRIM enabler breaking it, and that's if Yosemite doesn't introduce any security changes such as signed kernel extensions that are verified on startup.

I won't speak of Trim Enabler, since we can enable TRIM manually after every OS update. The manual approach patches an APPLE SSD string out of kext. This has worked for years and the only change with Yosemite is the signed kext verification.

As an aside though, how much benefit do people actually see when enabling TRIM for their third party SSDs? I've had several that actually performed worse with TRIM enabled, not necessarily the fault of the drive but possibly some oddity with OS X's handling of TRIM once (force) enabled. I've just found things to be more stable with it left off.

I've been using a 512GB Crucial M4 for about 2 years and I haven't had a problem. Crucial has issued several firmware updates to fix issues, but I don't know if anything was caused by OS X.

 

[Fangio]

[...] simply a "block" against third party/modified kexts that Apple added for Developer Preview 1, probably for debugging reasons. Once you use the boot argument to tell Yosemite to not use this block, Trim is enabled just fine.

Is Trim Enabler version 3.2.4 now working properly with DP3 too, without having to use that boot argument? It's from July 6.

The website mentions this about v3.2.3

Fixed an issue with code signing, Trim Enabler will now be correctly identified as software from a trusted developer.

Please clarify. Thanks

 

[KettyKrueger]

I got the 'no entry' sign the first time I installed the PB1, thought it was because I had enable Fire Vault but didn't connect to power source.

Anyways, I have a 480GB Transcend SSD in my '12 MBA, their software package, which includes the function to add TRIM, works fine.

 

[rjbruce]

I know this is an older thread, but I've been running the beta for a bit now and just went to enable trim and ran into this problem. The instructions on the Cindori site got me back up and running. Documentation was clear and concise and the trim application seems to be well written and up to date, not to mention reasonably priced. Even though I had the trim enabled, I went ahead and purchased the app. Being in IT I see a lot of the good and the bad and I really admire when someone stands behind their products and isn't trying to gouge their customers.

Bravo, Cindori.

 

[freeskier93]

I know this is an older thread, but I've been running the beta for a bit now and just went to enable trim and ran into this problem. The instructions on the Cindori site got me back up and running. Documentation was clear and concise and the trim application seems to be well written and up to date, not to mention reasonably priced. Even though I had the trim enabled, I went ahead and purchased the app. Being in IT I see a lot of the good and the bad and I really admire when someone stands behind their products and isn't trying to gouge their customers.

Bravo, Cindori.

Wait, you paid for an app to enable TRIM? Trim Enabler is free you know and the beta version has been working on Yosemite for a while now. Once Yosemite is officially released I'm sure someone will have a permanent fix through Terminal just like previous iterations of OS X.

 

[ecschwarz]

Wait, you paid for an app to enable TRIM? Trim Enabler is free you know and the beta version has been working on Yosemite for a while now. Once Yosemite is officially released I'm sure someone will have a permanent fix through Terminal just like previous iterations of OS X.

TRIM Enabler is free, but there is a $10 purchase to enable some additional functionality and support the developer. It gives you a license for 5 computers, so it's a good way to support development of this tool, especially if you use it in a business or lab environment.

 

[Che Castro]

To enable Trim on Yosemite, Trim Enabler needs to disable the kext signing requirement



is it safe to proceed ?

 

[duffman9000]

To enable Trim on Yosemite, Trim Enabler needs to disable the kext signing requirement



is it safe to proceed ?

Yes, it's necessary. I don't know care what Trim Enabler does since modifying the target kext via the terminal also enables TRIM. To modify the kext and still boot your system you have to disable kext signing. See more here:
https://digitaldj.net/blog/2011/11/17/trim-enabler-for-os-x-lion-mountain-lion-mavericks/

 

[Cindori]

Trim Enabler 3.3 is out, with improved Yosemite compatibility.

Read here for more info about Trim in Yosemite:

http://www.cindori.org/status-of-trim-enabler-in-yosemite/

 

[emagsamurai]

I just ordered my first SSD after updating my Macbook Pro (late 2011) to Yosemite, then I found out TRIM is not directly supported.


I'm still learning about how TRIM works, but can I just run TRIM periodically, or does it need to run actively after each file deletion?

Thanks in advance!

 

[emagsamurai]

Just to clarify, could I write a script to activate TRIM on Monday at 10:00, and let it run for an hour or so, and then turn it back off? Would that give the same benefits as leaving TRIM enabled all the time?

I'm going to guess not since I haven't seen anyone else doing this.

 

[ecschwarz]

Just to clarify, could I write a script to activate TRIM on Monday at 10:00, and let it run for an hour or so, and then turn it back off? Would that give the same benefits as leaving TRIM enabled all the time?

I'm going to guess not since I haven't seen anyone else doing this.

I don't think this is how it works - it's not a "scan" of your drive so to speak, but rather sending additional commands to the SSD when deleting files. While I do enable TRIM on my machine, I had it disabled all summer during the Yosemite betas and didn't notice any major issues. It does help the drive run more efficiently, especially if the drive doesn't do its own garbage collection. I'll let the experts chime in more on this, but the basics are that it has to be enabled while you're using the drive to see the benefit.

 

[emagsamurai]

I don't think this is how it works......

I sort of suspected that, but thought it was worth asking. I don't have a good feel for just how vulnerable changing the permissions to enable TRIM leaves my machine. Similarly, I don't have a good feel for the performance degradation I would see over the life of my SSD would be without TRIM enabled, or if it can be corrected at a later date.

 

[Weaselboy]

I sort of suspected that, but thought it was worth asking. I don't have a good feel for just how vulnerable changing the permissions to enable TRIM leaves my machine. Similarly, I don't have a good feel for the performance degradation I would see over the life of my SSD would be without TRIM enabled, or if it can be corrected at a later date.

It can be. Just enable TRIM then command-s boot to single user mode and run the command "fsck -fy" (without the quotes) and unused space on the drive will be TRIM and performance will be restored to like new.

 

[emagsamurai]

It can be. Just enable TRIM then command-s boot to single user mode and run the command "fsck -fy" (without the quotes) and unused space on the drive will be TRIM and performance will be restored to like new.

This is interesting. Is there any downside to doing this? Does this take long?

I, for one, wouldn't mind doing something like this once a month or so if it helped keep things in tip-top shape.

 

[Weaselboy]

This is interesting. Is there any downside to doing this? Does this take long?

I, for one, wouldn't mind doing something like this once a month or so if it helped keep things in tip-top shape.

No downside to running the command at all. The reboot itself actually takes longer than running the command. Once you hit the enter key the command usually completes in a few seconds. You will see text at the end that mentions "unused blocks trimmed."

What you could do is run a speed test when the drive is new and note the result, then every few months repeat the test. Then if write speeds have dropped significantly you can turn on TRIM and run the command to restore write speed.

 

[emagsamurai]

I like it!

Any recommendations on how to run the speed test, or should I return to teh Googles? This is my first SSD, so I'm pretty far behind the learning curve.

 

[Weaselboy]

I like it!



Any recommendations on how to run the speed test, or should I return to teh Googles? This is my first SSD, so I'm pretty far behind the learning curve.

Just get the black magic speed test app from the app store.

 

[NoBoMac]

See more here:
https://digitaldj.net/blog/2011/11/17/trim-enabler-for-os-x-lion-mountain-lion-mavericks/

I'd advise against using the Perl pattern in the above link, imo.

That pattern was for pre-10.9.4 Mavericks. 10.9.4 got a whole new extension. Pattern seems to work, BUT, really general (ie. might wipe out something critical down the road). The following post has a better pattern, imo, in that it's really specific where to change things. Looking at a hex dump of the Yosemite extension, the chunk relative to TRIM has not changed since the last update(s) of Mavericks (10.9.4 and .5).

https://forums.macrumors.com/posts/19305197/

 

[fastd]

Originally Posted by Weaselboy:
...Just enable TRIM then command-s boot to single user mode and run the command "fsck -fy" (without the quotes) and unused space on the drive will be TRIM and performance will be restored to like new.

No downside to running the command at all. The reboot itself actually takes longer than running the command. Once you hit the enter key the command usually completes in a few seconds. You will see text at the end that mentions "unused blocks trimmed."

What you could do is run a speed test when the drive is new and note the result, then every few months repeat the test. Then if write speeds have dropped significantly you can turn on TRIM and run the command to restore write speed.

Perfect! This is what I plan to do on mine with the Samsung EVO, maybe on a once a month schedule. I know I will forget to disable Trim the next time an update comes around. I also have a Crucial MX100 in the kids machine, but on those forums they seem to be recommending not to use TRIM for that model. I will also do this manual maintenance on that Macbook as well.

My one question is by not having Trim enabled, will Yosemite still track the unused blocks so that Trim can manually free them? Or does the drive track the unused blocks?

 

[Weaselboy]

My one question is by not having Trim enabled, will Yosemite still track the unused blocks so that Trim can manually free them? Or does the drive track the unused blocks?

It (OS) does not remember them if that is what you mean. What will happen is if your reenable TRIM and run that command it will TRIM what is unused at that moment in time.

 

[emagsamurai]

I'm planning to swap the drive in my MBPro tonight for my first SSD. Any last minute advice?

 

[Badagri]

Trim Enabler 3.3 is out, with improved Yosemite compatibility.

Read here for more info about Trim in Yosemite:

http://www.cindori.org/status-of-trim-enabler-in-yosemite/

I don't understand why Apple makes it hard for people with 3rd party SSD's. Microsoft doesn't do this with Windows.

All I see from Apple is screwing with something again and again to make it even harder.


I no longer see Apple as it just works.

 

[Headrush69]

I don't understand why Apple makes it hard for people with 3rd party SSD's. Microsoft doesn't do this with Windows.

All I see from Apple is screwing with something again and again to make it even harder.

Microsoft doesn't make their money selling a small line of computers either, it's not a fair comparison.

I don't like it either, but I'm sure in Apple's mind it is making the OS more resistant to hacking and 3rd party manipulation. In today's society sounds like a good idea, but for people like us who do modify our systems, it blows.

 

[yondertwins392]

I can confirm this as mine was running sluggish and slow; BlackMagic speed tests revealed below 100 MB/s and kept fluctuating lower and lower with every read. Once I enabled TRIM using that program, it is back up to 400-500 MB/s but sometimes it fluctuates down which is weird, don't understand why that is happening.