I had it (re) enabled on each and every version of 10.10, but kext signing has to be switched of otherwise your system won't boot, but this can be fairly easy fixed with a few commands in Terminal after booting up in Recovery Mode.
Got a tip for us?
Let us know
Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.
OS X El Capitan Opens Door to TRIM Support on Third-Party SSDs for Improved Performance
- Thread starter MacRumors
- Start date
- Sort by reaction score
I had it (re) enabled on each and every version of 10.10, but kext signing has to be switched of otherwise your system won't boot, but this can be fairly easy fixed with a few commands in Terminal after booting up in Recovery Mode.
Why would they? It's a Terminal command for a reason, and there's a disclaimer when you try and use it. Besides, most every SSD is compatible with TRIM.
Garbage collection was never a replacement for TRIM, and Crucial support were idiots for suggesting it. If TRIM isn't enabled, the SSD will think that blocks that contain no data, still have important data that must be kept, and Garbage Collection will work around that. Further more, the thing with keeping the machine on boot screen really isn't necessary. If you have idle time when the Mac is on,, it'll do the same. Fairly sure it even works when it's on full standby.
TRIM Enabler has always worked on Yosemite. It just requires you to disable kext signing on boot.
It works fine, it disables kext signing. Check out their website for an explanation.
That is/was not completely true, it does in later versions but AFAIK not in earlier version, actually I am pretty sure it didn't in the beginning, I ended up with a System which refused to boot, but, it was fairly easy to fix.
Works fine for me. I don't even have to disable it when upgrading OS X. On upgrade it disables itself, then pops up a reminder on next boot to re-enable it by clicking on a radio button, reboot again and all done.
There two different drives. The EVO is Samsung's cheap drive. Go with the Samsung Pro and it beats the Crucial.
Crucial has many different drives that perform differently. As does Samsung. End of story. To properly compare, compare drives that are intended for the same market segment, and that cost the same.
It would help if Apple shared the work they already had done. if there is a prototype lab that qualifies some SSDs for use in Apple systems and they test some as "OK" and others as very clear failures then listing that is helpful. They don't have to test all possible drives on the market, but for what they are going to do away if is more information for the folks who may want to buy a 2nd or 3rd or alternative drive.
Drive X with firmware A.B.C. is OK
Drive Y with firmware A.E.F has known interaction problems with OS X.
Throw another disclaimer on that list that it is limited in scope ( not exhaustive test of market and never will be. )
They do it with 3rd party 4K monitors ( at least list the ones that pass )
https://support.apple.com/en-us/HT202856
These monitors work with OS X 10.x.y. That is a useful starting place for customers to look for options. That is waaaaaaay better than leaving the users in a fog.
Secondly it would lend some credibility to their disclaimer that there is a possibility of data failure/corruption. "We had tested and got some failures" is confirmation. "We only pass stuff that we sell" is without much substantive proof.
File system allocation/deallocation isn't the only source of Garbage. The SSD controller moves data around also ( wear leveling , block consolidation , etc. ). The notion that the garbage collector is completely lacking in information unless handed to it by an explicit TRIM call is far more dubious than the than Crucial suggestion.
It is not Mac user idle time, it is disk time. OS X runs many processes than just the. The "stop the OS from running" is remove the condition you end with there from being part of the equation no matter what the user workload is or isn't. Stop the OS from running, put there far more simpler bootloader into pause mode and pretty much can guarantee there is disk idle time. Background Time Machine running? No. Twitter/social media caching notifications on the disk? No. myriad of background processes doing storage updates? No.
If the idle time being allowed isn't really all that idle then this is a first step work around.
TRIM doesn't change the data ( some data de-duplication of zeroed blocks may make it look like it, but that isn't mandated by the standard. ). It only feeds metadata to the SSD ( and its garbage collector). When something is actually done with the info is later. If don't give drive a idle time to do housekeeping it won't get done.
Crucial's recommendation is that "put disks to sleep" is turned off. For normal users and usage that is probably enough. But if usage is abnormal then the boot idle trick pretty much will remove any OS X impediment to allowing the drive time to do some housekeeping.
If the OS says "go to sleep" then it very likely won't. Garbage collection means moving ( writing) data. SSDs can't do writing in a low power state. Writing is actually the highest power mode of a SSD.
Windows 7 supported TRIM too. It took Apple nearly a decade to realise this?!OMG THANK YOU APPLE! I requested this feature tooDD! SSD Upgrade for my iMac inbound!
@RosynaKeller
what do you think about this litte shell schript posted over at cindori's forum ->
https://www.cindori.org/forums/topi...-that-your-drives-trim-does-not-corrupt-data/
would you say that this proves that Apple is still using the non-queued (sequential) trim command and that we're good?
regards,
michael
what do you think about this litte shell schript posted over at cindori's forum ->
https://www.cindori.org/forums/topi...-that-your-drives-trim-does-not-corrupt-data/
would you say that this proves that Apple is still using the non-queued (sequential) trim command and that we're good?
regards,
michael
PLEASE NO MORE POSTS ABOUT THE GREEN-BUTTON ISSUE!
stay on topic, this thread is about OS X El Capitan and SSDs + TRIM!
stay on topic, this thread is about OS X El Capitan and SSDs + TRIM!
ZFS is the answer and it's been ask for for years
That would explain why my trim commands have been ignored
Most contributions to Linux are corporate and that includes Apple.
===
I've not had any issues with my Samsung drives in either OSX or Linux with or without TRIM they all just worked fine.
So happy to hear this. I just did an ATA-Secure Erase a few days ago on my Samsung 840 and did a fresh install of Yosemite and happy and surprised to see that my read/write speeds are at 500 MB/s Did they implement the TRIM support in the current version? Or am I missingn someting. I was never able to achieve those speeds before when I had Yosemite.
Yes, it appears to be. Ended up paying the 10$ and once activated more free space came up. Has been consistent during use anyhow.
I've investigated how "trimforce" works and written up a method for doing stable, patchless TRIM enabling on OS X 10.10.3 or higher. No more boot issues, and no more loss of the TRIM settings after OS updates. Trimforce + Yosemite = Yes!
The link has been moved here: Post #232.
(Be sure to read the whole page so that you understand the legal implications.)
The link has been moved here: Post #232.
(Be sure to read the whole page so that you understand the legal implications.)
Last edited:
Trimming an SSD doesn't free up space in the filesystem. You must have had something else happening.
This is not OK! Apple has chosen not to support my early Mac Pro with Yosemite or El Capitan, so adding much needed TRIM support to an OS I can't even run is not great news.
My Mac Pro has more than enough horsepower to run both of those OSs, and I am disappointed in Apple's lack of support. Even if I had to buy an upgrade to the video card, at least I would have options...
Thank goodness TRIM support is provided by 3rd parties, because Apple certainly could not care much less about early adopters.
My Mac Pro has more than enough horsepower to run both of those OSs, and I am disappointed in Apple's lack of support. Even if I had to buy an upgrade to the video card, at least I would have options...
Thank goodness TRIM support is provided by 3rd parties, because Apple certainly could not care much less about early adopters.
The problem is the lack of a 64bit EFI. However, there are ways to trick your computer into running OS X versions after 10.7. See the references on the latest OS under the specifications for Mac Pros on this wikipedia page, and information at Everymac.com. Trim Enabler works with 10.7.
Does anyone else have any feedback on this approach? No disrespect to Temptin, and I sincerely appreciate both the effort in the investigation and the time taken to share the information.
However, due to Temptin having had joined just today, corroboration from others would be helpful.
@triptolemus: Heh, this was the only subject interesting enough to make me join the MacRumors forums. By sharing the research, I hope to provide people with an easy one-stop link in case Apple never brings "trimforce" to Yosemite.
You can verify the legitimacy of the linked file as follows:
* Unzip "AppleDataSetManagement", then right click it and "Show Package Contents". Go to Contents and open Info.plist in a text editor. You'll see that it says Apple Inc all over the place.
* Now to verify that it's really untouched, open a Terminal and type "codesign --verify --verbose ~/Downloads/AppleDataSetManagement.kext". It will say that it's valid.
* To see what would have happened if someone had tampered with it, you can try editing even a single character in Info.plist (or any other file) and saving it, and then try to verify again. It won't pass anymore after your edits.
Anyway; the method I describe on the site works on OS X 10.10.3 or later, and works exactly as if you had executed "trimforce" on the system. This is by far the best and most stable way of enabling TRIM on OS X. Simply read the full document in the original post for all the details and the legality of it all. Enjoy!
You can verify the legitimacy of the linked file as follows:
* Unzip "AppleDataSetManagement", then right click it and "Show Package Contents". Go to Contents and open Info.plist in a text editor. You'll see that it says Apple Inc all over the place.
* Now to verify that it's really untouched, open a Terminal and type "codesign --verify --verbose ~/Downloads/AppleDataSetManagement.kext". It will say that it's valid.
* To see what would have happened if someone had tampered with it, you can try editing even a single character in Info.plist (or any other file) and saving it, and then try to verify again. It won't pass anymore after your edits.
Anyway; the method I describe on the site works on OS X 10.10.3 or later, and works exactly as if you had executed "trimforce" on the system. This is by far the best and most stable way of enabling TRIM on OS X. Simply read the full document in the original post for all the details and the legality of it all. Enjoy!
Last edited: