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.
TRIM Support Enabler
- Thread starter Cindori
- Start date
- Sort by reaction score
TRIM is executed on space that is deleted.
Someone on Macbidouille suggested to use "Erase free space" in Disk Utility, to TRIM all the unused space on the disk.
Hello,
Remember: if you want to test the "without TRIM" speed, you have to test it before applying any TRIM, **ever**.
You can't just install it, test, remove it, test... Once the TRIM does its work, you have to remove it for a few weeks/months before being able to test it without TRIM.
It's not a speed boost in itself.
Loa
Remember: if you want to test the "without TRIM" speed, you have to test it before applying any TRIM, **ever**.
You can't just install it, test, remove it, test... Once the TRIM does its work, you have to remove it for a few weeks/months before being able to test it without TRIM.
It's not a speed boost in itself.
Loa
Wirelessly posted (Mozilla/5.0 (iPhone; U; CPU iPhone OS 4_3_1 like Mac OS X; en-us) AppleWebKit/533.17.9 (KHTML, like Gecko) Version/5.0.2 Mobile/8G4 Safari/6533.18.5)
So incase I want to go back to non-trim mode for whatever reason, how do I do that from my time machine backups?
So incase I want to go back to non-trim mode for whatever reason, how do I do that from my time machine backups?
i've got the same error, mb pro 15" mid 2010, with apple ssd, yesterday i put enabler 1.0
You download the 1.1 version, click Restore, and use either Default driver or browse for your IOAHCIFamily.kext that you can restore from the time machine.
Cindori. No luck for me on mid-2009 MBP using yesterday's version of the updater. Is mine one of the older, unsupported SSD drives? If so, I may just have to find a pillow for a good cry. My machine has gotten slower and slower to the point where simple stuff like opening System Preferences can take forever. I use Adobe CS and FCP every day for work it and the disk is used pretty intensively.
I maintain it pretty well (run various cron scripts, repair permissions, clean out logs and whatnot). Looks like I might just need to bite the bullet and do a full wipe and reinstall. I hate having to set up all of my preferences again. :-(
Edit: by the way, even if I don't get to enjoy the benefits, thanks for being generous with the Mac community and spearheading an effort like this.
I maintain it pretty well (run various cron scripts, repair permissions, clean out logs and whatnot). Looks like I might just need to bite the bullet and do a full wipe and reinstall. I hate having to set up all of my preferences again. :-(
Edit: by the way, even if I don't get to enjoy the benefits, thanks for being generous with the Mac community and spearheading an effort like this.
Attachments
Yes I'm admin, 10.6.7, after a few retry and reboots, I find out all the functions actually works..like I can restore to the original kext without trim enable, and then patch it again.
the only abnormal things are every time I'll got the error message, as well as the "Repairing Permissions..." with the little ball still looping on top...it just never ends...
Yeah, I don't think that SSD supports TRIM. Several people have reported that they can't get it working.
You could do some google research to find out if there is a firmware upgrade for it.
It worked for me!!!
Thanks
I haven't seen any significant improvement in performance yet.
Xbench score is 205.9 (before Trim) and 204.7 (after trim)
Hoping for long term benefits
Capacity: 240.06 GB (240,057,409,536 bytes)
Model: OWC Mercury Extreme Pro SSD
Revision: 343A13F0
Native Command Queuing: Yes
Queue Depth: 32
Removable Media: No
Detachable Drive: No
BSD Name: disk0
Medium Type: Solid State
TRIM Support: Yes
Partition Map Type: GPT (GUID Partition Table)
S.M.A.R.T. status: Verified
Volumes:
Capacity: 209.7 MB (209,715,200 bytes)
Writable: Yes
BSD Name: disk0s1
OWC SSD:
Capacity: 239.71 GB (239,713,435,648 bytes)
Available: 141.59 GB (141,589,094,400 bytes)
Writable: Yes
File System: Journaled HFS+
BSD Name: disk0s2
Mount Point: /
Thanks
I haven't seen any significant improvement in performance yet.
Xbench score is 205.9 (before Trim) and 204.7 (after trim)
Hoping for long term benefits
Capacity: 240.06 GB (240,057,409,536 bytes)
Model: OWC Mercury Extreme Pro SSD
Revision: 343A13F0
Native Command Queuing: Yes
Queue Depth: 32
Removable Media: No
Detachable Drive: No
BSD Name: disk0
Medium Type: Solid State
TRIM Support: Yes
Partition Map Type: GPT (GUID Partition Table)
S.M.A.R.T. status: Verified
Volumes:
Capacity: 209.7 MB (209,715,200 bytes)
Writable: Yes
BSD Name: disk0s1
OWC SSD:
Capacity: 239.71 GB (239,713,435,648 bytes)
Available: 141.59 GB (141,589,094,400 bytes)
Writable: Yes
File System: Journaled HFS+
BSD Name: disk0s2
Mount Point: /
Perfect now, "Patch applied! Reboot Now?"
Yeah, I'm gonna reboot again
Update : Lighting reboot time
Last edited:
I apologize in advance if this is a stupid question:
Should we "Erase free space" to fully utilize the TRIM functionality?
Understood. Thank you.
Let's say I am chicken to install the patch and leave it for fear of instability. What if I install the kext patch then "Erase Free Space" in Disk Util so the drive is "TRIM'd"... then I remove the patch. Theoretically this would make performance like new until I did a bunch more drive writes... yes?
TRIM is a command. It is executed when you delete a file.
So if you enable TRIM support, you still have alot of un-TRIMed free space on your disk. This space would have to be deleted with TRIM activated in order to speed up the writing on that space.
Understood. Thank you.
Let's say I am chicken to install the patch and leave it for fear of instability. What if I install the kext patch then "Erase Free Space" in Disk Util so the drive is "TRIM'd"... then I remove the patch. Theoretically this would make performance like new until I did a bunch more drive writes... yes?
Yeah! But if you would fill up the drive with data, and then delete it without TRIM, you would have untrimmed free space again.
I'm really not a TRIM expert so if anyone is, please stop me if I say something wrong.
Got it. But until I did enough writes to start to fill up "fresh" TRIM'd space, performance would be like new in theory anyway. At least this is my understanding of TRIM.
Just ran across this good explanation of how TRIM works.
Doesn't seem to work for me with 1.1
Maybe my SSD doesn't support Trim ?
SAMSUNG SSD PM800 Series 2.5" 256GB:
Capacity: 256.07 GB (256,071,352,320 bytes)
Model: SAMSUNG SSD PM800 Series 2.5" 256GB
Revision: VBM15D1Q
Serial Number: YCB710P933SY933C0940
Native Command Queuing: No
Removable Media: No
Detachable Drive: No
BSD Name: disk0
Medium Type: Solid State
TRIM Support: No
Bay Name: Bay 1
Partition Map Type: GPT (GUID Partition Table)
S.M.A.R.T. status: Verified
Volumes:
Capacity: 209.7 MB (209,715,200 bytes)
Writable: Yes
BSD Name: disk0s1
Macintosh SSD:
Capacity: 255.73 GB (255,727,378,432 bytes)
Available: 99.78 GB (99,784,540,160 bytes)
Writable: Yes
File System: Journaled HFS+
BSD Name: disk0s2
Mount Point: /
Maybe my SSD doesn't support Trim ?
SAMSUNG SSD PM800 Series 2.5" 256GB:
Capacity: 256.07 GB (256,071,352,320 bytes)
Model: SAMSUNG SSD PM800 Series 2.5" 256GB
Revision: VBM15D1Q
Serial Number: YCB710P933SY933C0940
Native Command Queuing: No
Removable Media: No
Detachable Drive: No
BSD Name: disk0
Medium Type: Solid State
TRIM Support: No
Bay Name: Bay 1
Partition Map Type: GPT (GUID Partition Table)
S.M.A.R.T. status: Verified
Volumes:
Capacity: 209.7 MB (209,715,200 bytes)
Writable: Yes
BSD Name: disk0s1
Macintosh SSD:
Capacity: 255.73 GB (255,727,378,432 bytes)
Available: 99.78 GB (99,784,540,160 bytes)
Writable: Yes
File System: Journaled HFS+
BSD Name: disk0s2
Mount Point: /
I think this applies to my MBP as well. Mid 2009, the first to come with SSDs. Ran the enabler twice (& rebooted, of course)... no change.
Sadly, I'm in the same boat as you. I've done some googling around but can't find any evidence that Apple has updated the firmware for the drive either.