As far as I know there's no need to worry, TRIM / OS X should take care of anything, no need to reformat or sth... But i am not 100% about this, that's what I've been told in another post...
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.
Mac OS X 10.10.4 Supports TRIM for Third-Party SSD Hard Drives
- Thread starter MacRumors
- Start date
- Sort by reaction score
If one is running FileVault 2 Full Disk Encryption(FDE), does enabling TRIM make any difference at all? Since you are never zeroing out any block but rather replacing a block of random bits with a different block of random bits I don't see how TRIM would have any benefit at all. If I'm wrong could someone explain how using TRIM with FDE helps.
Will it fix UI lagging issues?
Will it fix the many slow-downs and freezing?
Will it fix Spotlight lagging?
Will it fix bluetooth incompatibilities?
Will it fix battery to match the advertisement?
etc...
(Btw I'm on a brand new Macbook Pro from 2015, I've never been so disappointed).
Will it fix the many slow-downs and freezing?
Will it fix Spotlight lagging?
Will it fix bluetooth incompatibilities?
Will it fix battery to match the advertisement?
etc...
(Btw I'm on a brand new Macbook Pro from 2015, I've never been so disappointed).
Over time, it should indeed recover write performance (read performance shouldn't be affected by lack of TRIM), as the sectors containing files which you delete are TRIMed.
You could force it by writing lots of big files and then deleting them after enabling TRIM.
Garbage collection != TRIM
Just about every SSD sold in the last few years by a major brand (i.e. not some no name chinese supplier) supports garbage collection on it's own which is handled by the controller.
It's still helpful to have TRIM
http://arstechnica.com/gadgets/2015...garbage-collection-so-i-dont-need-trim-right/
No, they don't. There *MAY* be a bug with NCQ TRIM on certain Samsung SSDs (AFAIK only the Pro models are affected, not the Evo), but in any case nobody has ever encountered this on a Mac. In fact, since Apple themselves use OEM Samsung 8xx drives in many models, I'd be very surprised if there's a problem.
I've been using multiple Samsung 8xx drives for years with TRIM enabled and there's never been a problem.
Not gonna do it.
Any good SSD has enough overprovisioning that TRIM shouldn't make much of a speed difference. Plus, my root partition is so close to full, it REALLY wouldn't make any difference (TRIM's performance impact increases with the amount of free space in your file system). There MIGHT be a slight impact on longevity, but how much longer am I going to have this 17" MacBook Pro as my primary system anyhow?
I could cross-reference the exact model of my Crucial SSD against white lists and black lists, but I don't trust it. New devices get added to the blacklist all the time. It's not worth the risk for the extremely minor benefit.
Oh, and on my Linux box, I tried enabling TRIM, and it actually SLOWED DOWN. That's because it doesn't support queued TRIM, so the TRIM commands really hurt efficiency.
Any good SSD has enough overprovisioning that TRIM shouldn't make much of a speed difference. Plus, my root partition is so close to full, it REALLY wouldn't make any difference (TRIM's performance impact increases with the amount of free space in your file system). There MIGHT be a slight impact on longevity, but how much longer am I going to have this 17" MacBook Pro as my primary system anyhow?
I could cross-reference the exact model of my Crucial SSD against white lists and black lists, but I don't trust it. New devices get added to the blacklist all the time. It's not worth the risk for the extremely minor benefit.
Oh, and on my Linux box, I tried enabling TRIM, and it actually SLOWED DOWN. That's because it doesn't support queued TRIM, so the TRIM commands really hurt efficiency.
I've been running an 830 with TRIM in a Mac for about 4 years. It's totally fine. My 840 Evo and 850 Evo are both totally fine also.
- Don't buy into the talk. Thousands of users are running TRIM on their 830/840/850 and there have been no reports of issues with TRIM on OS X.
I've been running it for 3 years on my 830 with not so much as a hint of an issue.
Also see Hellhammer's post earlier in this thread. He's something of an authority on SSDs on these forums.
I just did it on a drive that has never had trim on, and I did get some beach balls when it started up, but after a few seconds/minutes they stopped. I don't know if it was trim just activating or if it was going through and doing a bunch of garbage collecting. I have re-booted a few times and those same beach balls did not show back up. Again, I don't know if it has anything to do with the cleaning of a drive that has never had trim enabled on it.
Over time it would, but you can restore write speeds to like new right now by doing a command-s boot into single user mode then run the command below at the command prompt.
Code:
fsck -fyYou will see a message at the end that all unused blocks have been trimmed. Then type reboot.
That will restore write performance to like new.
I just enabled the command via terminal. Computer got stucked. I forced restart with the power button down for a few seconds. Started the machine again. All seems fine. I´m running a raid 0, with new ssd's with latest firmware, samsung 840 evo. I had problems in the past with trim enabler, and i am sure i will have troubles now too. I have a TM connected all time though. Withough trim enabler, the performance of my previous single samsung 840 evo went down in just one year.
So if you go left, there are some issues, but if you go right, you will have issues too. that is reality folks. I will give it a try though, it is working in my ssd raid right now, no problem, yet.
So if you go left, there are some issues, but if you go right, you will have issues too. that is reality folks. I will give it a try though, it is working in my ssd raid right now, no problem, yet.
so...for those who don't go to rumor sites/ or someone who is not technical...they won't even know about this trim force. So I wonder how those people would know about it?
My TRIM tutorial has been updated to cover OS X 10.11 El Capitan, OS X 10.10.4+ Yosemite, and OS X 10.10.3 Yosemite all in one place:
https://github.com/Temptin/Documents/blob/master/OSX_TRIM_Tutorial.md
---
About Cindori's Disk Sensei and Trim Enabler:
I can already see the confusion growing due to Cindor's intentionally vague statements. The method that Cindori (Disk Sensei/Trim Enabler) is bringing out is *identical* to the "trimforce" command method in my guide. He has created his own .kext file that injects the "Force Data Set Management = YES" option in the exact same way as the official extension. His method is not "safer" at all. It's the exact same thing; with one small difference: He installs the injector to /Library whereas the trimforce tool installs the injector to /System/Library - and the latter is protected by "rootless" on El Capitan, but that seems like an oversight on Apple's part. Either way, you can easily disable rootless, run trimforce, and re-enable rootless on the current El Capitan beta (instructions for that are in the link above). Moreover, it's very likely that Apple is going to fix it before release so that you don't need to even temporarily disable rootless to run trimforce.
I'll say it one more time: There is no reason whatsoever to use Cindori's injector instead of Apple's injector; they do the *exact* same thing. I even suggest using Apple's since they're the ones who created the method, and if any of the implementation details ever change they'll be the first to update their official kext.
There are plenty of reasons to use Cindori's Disk Sensei: Disk space visualization, benchmarking, SMART health monitoring, various tweaks to prolong SSD life (like "noatime"). "TRIM enabling" is no longer a reason to own the tool.
---
As for people's questions about TRIM, GC, etc, I refer to these posts:
* Do we need TRIM? Does OS X use Queued TRIM? Do Samsung 8*-series SSDs break when TRIM'ing?: https://forums.macrumors.com/thread...ved-performance.1891936/page-10#post-21469307
* About Garbage Collection vs TRIM: https://forums.macrumors.com/thread...ved-performance.1891936/page-10#post-21469409
* Does TRIM work with Filevault 2 Full Disk Encryption?: Yes. Apple's FileVault driver sends the "TRIM" command to the disk, and zeroes out all unused blocks.
* Does TRIM work with Apple's Software RAID?: No. Their software RAID driver was last updated in 2009, and OS X didn't get TRIM support until mid-2011. Apple's RAID driver has no idea what TRIM is and does not send TRIM to the SSDs in your RAID. OS X cannot simply "pass through" commands to the underlying SSDs (as some people have wrongly assumed), since a RAID means that data is split across multiple drives, which means the OS has no idea "where the data is and which drive to TRIM in a RAID," - it's always the job of the RAID driver to re-map the TRIM requests to the real underlying drives and blocks, and Apple's RAID driver is over half a decade old and doesn't do that job at all. If you are using Apple's software RAID, TRIM will NOT take place (your individual drives will still say "TRIM Supported: Yes", but nothing will be done).
I should probably put all of this information into the TRIM guide document itself, since people bring up these misconceptions over and over again.
https://github.com/Temptin/Documents/blob/master/OSX_TRIM_Tutorial.md
---
About Cindori's Disk Sensei and Trim Enabler:
I can already see the confusion growing due to Cindor's intentionally vague statements. The method that Cindori (Disk Sensei/Trim Enabler) is bringing out is *identical* to the "trimforce" command method in my guide. He has created his own .kext file that injects the "Force Data Set Management = YES" option in the exact same way as the official extension. His method is not "safer" at all. It's the exact same thing; with one small difference: He installs the injector to /Library whereas the trimforce tool installs the injector to /System/Library - and the latter is protected by "rootless" on El Capitan, but that seems like an oversight on Apple's part. Either way, you can easily disable rootless, run trimforce, and re-enable rootless on the current El Capitan beta (instructions for that are in the link above). Moreover, it's very likely that Apple is going to fix it before release so that you don't need to even temporarily disable rootless to run trimforce.
I'll say it one more time: There is no reason whatsoever to use Cindori's injector instead of Apple's injector; they do the *exact* same thing. I even suggest using Apple's since they're the ones who created the method, and if any of the implementation details ever change they'll be the first to update their official kext.
There are plenty of reasons to use Cindori's Disk Sensei: Disk space visualization, benchmarking, SMART health monitoring, various tweaks to prolong SSD life (like "noatime"). "TRIM enabling" is no longer a reason to own the tool.
---
As for people's questions about TRIM, GC, etc, I refer to these posts:
* Do we need TRIM? Does OS X use Queued TRIM? Do Samsung 8*-series SSDs break when TRIM'ing?: https://forums.macrumors.com/thread...ved-performance.1891936/page-10#post-21469307
* About Garbage Collection vs TRIM: https://forums.macrumors.com/thread...ved-performance.1891936/page-10#post-21469409
* Does TRIM work with Filevault 2 Full Disk Encryption?: Yes. Apple's FileVault driver sends the "TRIM" command to the disk, and zeroes out all unused blocks.
* Does TRIM work with Apple's Software RAID?: No. Their software RAID driver was last updated in 2009, and OS X didn't get TRIM support until mid-2011. Apple's RAID driver has no idea what TRIM is and does not send TRIM to the SSDs in your RAID. OS X cannot simply "pass through" commands to the underlying SSDs (as some people have wrongly assumed), since a RAID means that data is split across multiple drives, which means the OS has no idea "where the data is and which drive to TRIM in a RAID," - it's always the job of the RAID driver to re-map the TRIM requests to the real underlying drives and blocks, and Apple's RAID driver is over half a decade old and doesn't do that job at all. If you are using Apple's software RAID, TRIM will NOT take place (your individual drives will still say "TRIM Supported: Yes", but nothing will be done).
I should probably put all of this information into the TRIM guide document itself, since people bring up these misconceptions over and over again.
Last edited:
Well it's up to the user to do his own research when installing new hardware, especially non-Apple add-ons and if he/she isn't technically inclined, he/she probably won't be upgrading to SSDs anyway. If he/she installs an Apple PCIe SSD, it will work OOTB with no user intervention. If he/she installs 3rd party he should already know about the related nuances through his/her research. If not, nothing will be noticed until performance degradation sets in (if ever). At that point I'd guess he/she will look for a solution and find out about the trimforce command.
Last edited:
They probably won't, but this step by Apple may be the prelude to simply having TRIM on by default in a future release of OS X.
After reading through some of the Linux-related threads, I suspect the situation is this:
Both the hardware and software manufacturers are looking out for us more than we realize. Probably many SSDs have had a few TRIM-related bugs. But Microsoft has made up for them so the end-user (and they!) don't suffer. And SSD manufacturers have also made adjustments so they work smoothly, even when they don't fully support every single command.
My suspicion is that Apple's tested many of the major SSD brands/models, without telling us. I'd be most concerned about using old or obscure brands or models. Popular models from the last few years are probably safe.
Addendum:
The prejudice is that hardware manufacturers only care about Windows. But the big ones usually test for OS X too - especially if they know Apple customers use their product. Yet for non-enterprise products, I imagine they avoid Linux testing, for a few reasons: 1) The consumer market is so small, 2) Linux is so fragmented (which complicates testing), and 3) Linux developers are so diligent about squashing bugs themselves.
Both the hardware and software manufacturers are looking out for us more than we realize. Probably many SSDs have had a few TRIM-related bugs. But Microsoft has made up for them so the end-user (and they!) don't suffer. And SSD manufacturers have also made adjustments so they work smoothly, even when they don't fully support every single command.
My suspicion is that Apple's tested many of the major SSD brands/models, without telling us. I'd be most concerned about using old or obscure brands or models. Popular models from the last few years are probably safe.
Addendum:
The prejudice is that hardware manufacturers only care about Windows. But the big ones usually test for OS X too - especially if they know Apple customers use their product. Yet for non-enterprise products, I imagine they avoid Linux testing, for a few reasons: 1) The consumer market is so small, 2) Linux is so fragmented (which complicates testing), and 3) Linux developers are so diligent about squashing bugs themselves.
Last edited:
Trim in OSX has caused beach balling on a bunch of my old Vertex drives. One of mine did it back in the Mountin Lion days from memory. My way around it was to simply run with trim support off, and then every few months boot into a backup osx installation on a usb stick with trim enabled, run fsck -ffy on the primary boot drive, to trim it completely, and then booting back into the real osx install. Not elegent, but provides the a full trim every now and again for peace of mind and avoids beach balls.
