TRIM for SSD?

I just bought a Samsung 840 PRO Series 128GB SSD to replace the HDD in my MacBook Pro Early 2011 13" running Mountain Lion. I installed it and it functions great and speeds up my Mac considerably. Having paid $150 for 128GB of storage makes me want to do what I can to ensure that my SSD will have a long lifespan. Are there any tweaks that I should perform? Such as "turning off sudden motion sensor" or "enabling TRIM"?
I am especially concerned about the TRIM feature. I read numerous forums online and it seems no one agrees on whether to enable TRIM or not. Some say enabling TRIM on a Mac with third party SSD's will be disastrous, since OS X cannot support TRIM on anything other than a hard drive with Apple firmware. Others say that performing a tweak that allows Mac to enable TRIM on a third party SSD is recommended. (Note: The Samsung 840 Pro DOES incorporate garbage collection algorithms.)
I plan to install Windows 7 using Boot Camp on my SSD so that I can run Windows on my Mac. I understand that Windows 7 automatically enables the TRIM feature for an SSD. If that is the case, do I still need to perform the TRIM tweak in Mountain Lion?
I would be more than happy for some up-to-date information regarding using third party SSD's in a MacBook. Thank you!

SSD Tweaks for Mac OS X
My personal recommendation is the "Disable file access time tracking" tweak, which I have applied on all three of my SSDs.
For advice on whether or not to force TRIM on an unsupported device, check with your manufacturer. OWC, for example, specifically advise against it.
Windows 7 automatically enables the TRIM feature for an SSD. […] do I still need to perform the TRIM tweak in Mountain Lion?
Yes. Windows 7's Trim is only used when booted into Windows 7.

Similar Messages

Does Mountain Lion support trim for SSDs? ...

I've been reading various forum posts and I find conflicting info. I did se several references to a tool called 'trim enabler.'
I have a late 2012 Mac Mini with Mountain Lion and installed a Samsung 830 SSD.
System Report shows that trim is not enabled for the drive. Does Mountain Lion support trim for these drives? How important is it to enable it?
Thanks in advance,
Chris

Apple does not support the 3rd party drives. To enable it (without installing another software package), you can visit the website:
http://digitaldj.net/2011/07/21/trim-enabler-for-lion/
I ran the series of commands on my Mac Pro and it did enable TRIM.
the webpage even has a backup/back-out procedure.
Without TRIM, my computer was running extremely slowly. After enabling TRIM, my computer ran substancially faster.

How to setup trim for 256GB SSD for Yosemite OS 10.10.1 on Mid 2010 MacBook Pro

What is the best way to setup effective TRIM for a newly installed SanDisk Ultra Plus 256 GB (old version) drive on a mid 2010 MacBook Pro 6,2 with 8 GB RAM and running just installed Yosemite OSs 10.10.1? The new operating system is not referenced by SanDisk. Thank you.

Thank you and to others that responded, I will take the advice to not enable trim at this time,but will visit the issue at a much later date. Maybe Apple will find a way to securely allow us to TRIM 3rd party SSDs. Iwill look at an annual manual TRIM in a year or so, if that is a good solution. Does this approach sound reasonable? This is my first ever post to this problem solving group. Thanks again also to ALL previous contributors.
Roger

Does Mountain Lion support TRIM for 3rd party SSD's? (I don't mean TRIM enabler)

I was planning on buying an SSD and doing clean install of Mountain Lion. I went to Mac Rumors and few other forums but they all gave simple answer like 'yes', not even verfying wether they're using Apple SSD's or 3rd party ones. I'm certain that it does support TRIM for Apple SSD's http://i1190.photobucket.com/albums/z451/yamanote/ScreenShot2012-06-29at30030AM. png)

We haven't got it installed, so you have to wait to the release

Enable Trim Command for SSD

How can I enable Trim Command for SSD in my Windows 7 O/S?

Unfortunately, using "fsutil behavior set disabledeletenotify 0" will not tell you if TRIM is actually working.
How do you know it is not already working?
You can try using this tool to check
http://files.thecybershadow.net/trimcheck/
Copy the exe you download to a folder on the drive you wish to test (eg c:\test) and double click it. Follow the instructions.

Erase free space in Disk Utilities grayed out for SSD

Is it normal that this function (erase free space) does not work for a SSD? It is grayed out on my iMac for SSD not for the 1 TB HDD.
Now that I installed Lion and Trim is working (on original Apple SSD) in my iMac I would like to erase free space. I read somewhere that you should do this if you did not have the Trim option before and you do have it now. Or is this BS?
peterwillem

Take a look at this link, https://discussions.apple.com/thread/3210131?start=0&tstart=0

HP dv7t CTO Corei7, Win7 . . . can this notebook run TRIM on SSD

I have a new HP dv7t CTO Notebook, Core-i7, 64bit Win7, 128GB Crucial SSD-SATA III. I also have a different, smaller SSD installed in the 2nd drive bay for data storage.
I have attempted to enable TRIM for the 128GB SSD with no success.
QUESTION: Can this notebook support TRIM ?
QUESTION: Could the trouble be that I have a 2nd SSD installed ?
Thanks for your help.
This question was solved.
View Solution.

You are welcome
//Click on Kudos and Accept as Solution if my reply was helpful and answered your question//
I am an HP employee!!

Is there a compatibility guide for SSDs in the late 2011 macbook pro model?

Is there a compatibility guide for SSDs in the late 2011 macbook pro model? I'm looking to purchase a 15.4" Late 2011 Macbook pro and was looking a SATA3 SSD that was supported (outside of the ones provided by Apple). Does anyone have any success stories they wish to share? I assume the problem with secondary bay and SATA3 has still not been resolved.

Have you looked at the OWC web site? They specialize in Mac peripherals and they have a good line of SSDs and secondary bays as well. My experience with them has been good but I am not ready for SSDs. For my needs the cost/benefits are not there.
Ciao.

SQL Server NTFS allocation unit size for SSD disk

Hi,
I have read that the recommended NTFS allocation unit size for SQL Server generally is 64 kb since data pages are 8 kb and SQL Server usually reads pages in extents which are 8 pages = 64 kb.
Wanted to check if this is true also for SSD disks or if it only applies to spinning disks?
Also would it make more sense to use an 8 kb size if wanting to optimize the writes rather than reads?
Please provide some additional info or reference instead of just a yes or no :)
Thanks!

Ok thanks for clarifying that.
I did a test using SQLIO comparing 4kb with 64kb when using 8kb vs 64kb writes/reads.
In my scenario it seems it doesnt matter if using 4kb or 64kb.
Here are my results expressed as how much higher the values were for 64kb vs 4kb.
Access type
IOps
MB/sec
Min latency (ms)
Avg latency (ms)
Max latency (ms)
8kb random write
-2,61%
-2,46%
0,00%
0,00%
60,00%
64kb random write
-2,52%
-2,49%
0,00%
0,00%
-2,94%
8kb random read
0,30%
0,67%
0,00%
0,00%
-57,14%
64kb random read
0,06%
0,23%
0,00%
0,00%
44,00%
8kb sequential write
-0,15%
-0,36%
0,00%
0,00%
15,38%
64kb squential write
0,41%
0,57%
0,00%
0,00%
6,25%
8kb sequential read
0,17%
0,33%
0,00%
0,00%
0,00%
64kb squential read
0,26%
0,23%
0,00%
0,00%
-15,79%
For anyone interested this test was done on Intel S3700 200gb on PERC H310 controller and each test was run for 6 minutes.

How to update firmware for SSD Toshiba Air 2012

How to update firmware for SSD Toshiba THNSNS128GMFP ??
My disk see on system as SandForse 200026BB 33Kb

https://discussions.apple.com/message/22108992#22108992
https://discussions.apple.com/thread/5120950?start=0&tstart=0
https://discussions.apple.com/message/22649139#22649139
https://discussions.apple.com/thread/5300125?tstart=0
Seems to be a real issue. Here's to hoping Apple will address this issue sooner rather than later.

Hibernation off for SSD ?

I like to close the lid without switching the laptop off for transport, idle time etc. I noticed that hibernation mode may not be that good for SSD disc. I switched it off using this instruction: http://blog.alutam.com/2012/04/01/optimizing-macos-x-lion-for-ssd/#hibernation (first and last code into terminal).
I got this message in the terminal:
What does it mean ? Is it good what I did ?

All the best,
Lennart

Trim support for SSD on Marvel controller?

I read somewhere that the 6Gbs Marvell 9128 ports do not support trim on an SSD. Is this true? I also heard that the RAID support for the Intel P67 ports are much more better than the Marvel Ports. This is what I am trying to do, and am wondering if it will work. I have an MSI P67A-GD65. I want to run Two WD Caviar Black 6Gbs (even though I know they achieve nowhere near that rate) on Sata ports 1 and 2 (the Intel P67 controller ports), in ports 3,4,5,6 (the Intel P67 3 Gbs ports) I would have 2 1TB storage drives, A Bluray drive, A DVD drive, and in the last ports 7 or 8 (the Marvell 9128) controller 6Gbs port) I wanted to have a Crucial C300 128Gb SSD drive as the boot drive. Would this work, or should I use port 7 and 8 for my RAID setup instead and use port 1 or 2 for the SSD? Any thoughts are appreciated. I love this mainboard and can't wait to get it up and running.
My System:
MSI P67A-GD65 (B3), Intel 2600k processor, XFX Radeon 6950 1GB graphics card, 8 GB G.Skill Ram, 1 Crucial C300 SSD (boot drive), 2 640GB WD Caviar Black in RAID 0, 1 Blu Ray Drive, 1 DVD drive, Corsair HX850w PS

Quote
I read somewhere that the 6Gbs Marvell 9128 ports do not support trim on an SSD.
Not true. TRIM has nothing to do with the SATA controller, it is dependent on the drive itself, and your operating system.
See: http://en.wikipedia.org/wiki/TRIM

[solved] Best Practice for SSDs with crypto on it regarding TRIM

Hi,
I was doing some research on this matter but did not find too much information on that that's more useful than confusing.
The setup is the following: I have an SSD (Crucial, Marvell-Controller) with two partitions: a small one for /boot and a bigger one for the rest, which is a LUKS-Container. I left some unpartitioned space at the end of the SSD. I'd like to *not* enable TRIM on the LUKS-device for security purposes.
I was wondering now:
I read that TRIM does reduce the write amplification of garbage collection. But shouldn't the garbage collection do not write at all, but just erase cells with no information on it?
If TRIM helps keeping up performance: do I need to explicitly trim the unpartitioned space? Or does this area behave like the spare area?
If TRIM of the unpartitioned space is necessary: what's the most elegant way to do so?
If someone could shed a little light on this matter, that would help a lot and would be greatly appreciated.
Last edited by Ovion (2015-03-09 19:20:13)

I have the same setup. Crucial SSD, LUKS, TRIM (cron.weekly fstrim). A full hexdump (minus gigabytes of random data) looks like this: https://bpaste.net/raw/505157 (tell me about it)
There is no issue with security. At least, none I care about. So the attacker can see how much free space there is [and where]. The where part is important since lots of small files give a different picture [lots of small free spaces in between] than a single very large file would [no free space in between], assuming there is no fragmentation worth mentioning [which Linux filesystems are usually good at]. So an attacker could probably make some guesses about your amount of data and file sizes. On the other hand I don't see how that's important, in ecryptfs you get this kind of info for free, and I have all sorts of files in all sorts of sizes either way, so it's not a big secret.
The question is, when all it takes to crack your encryption setup is a keylogger or a $5 encryption wrench, does it really matter?
Don't use TRIM on your SSD if you don't want to (there are lots of reasons not to TRIM... like better data recovery chances if you delete something by accident). But don't fool yourself thinking it's somehow really important for your security...
As for unpartitioned space, if it ever was in use before, you need to trim it once. Create a partition on it, then blkdiscard the partition, then delete the partition. That way it's good until it's "in use" again because you dd all over it or had it resynced in a RAID.
Apart from that, TRIM does all the things you said (reduce write amplification, performance, etc. etc.) but it's not like the SSD can't take it if you're not writing 24/7 because it's a database server burning up or something.
Last edited by frostschutz (2015-03-09 19:19:16)

TRIM Support For SSD

How does Arch Linux handle SSD's? Does Arch Linux or the 3.0 kernel natively support TRIM or some equivalent garbage collection mechanism? Is TRIM or whatever it uses enabled by default during an installation of Arch Linux or must I enable this in some way? Just trying to understand if making the switch to SSD versus traditional spindle drives is smart using Arch Linux.

Have you read https://wiki.archlinux.org/index.php/SSD ?
There's e.g.
DISCARD/TRIM feature is NOT SUPPORTED by device-mapper (but they are working on it, see here. August 2011 news: support will be in Linux 3.1, and involves a userspace dm-crypt update as well
https://wiki.archlinux.org/index.php/SSD#Mount_Flags
discard - The discard flag will enable the benefits of the TRIM command so long as one is using kernel version >=2.6.33. It does not work with ext3; using the discard flag for an ext3 root partition will result in it being mounted read-only.
Last edited by karol (2011-10-13 19:54:22)

Trim Support for SSD's

Is Trim Support required for Intel 320 series SSD's?

We haven't got it installed, so you have to wait to the release

TRIM for SSD?

Similar Messages

Maybe you are looking for