Sidebar Sidebar
Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.

TRIM Support Enabler

Pulled the plug on TRIM on my MacPro OWC 120GB, too many beach balls, all is fine now.

However, I will keep it on my MBP 13" using an Intel 160GB G2, it really seems to have benefitted from the patch.
 
I've noticed opening OpenOffice, it pauses for a second or two (with a momentary beachball) with trim enabled. Using HandsOff! I found this is when it writes and deletes a bunch of folders to the temporary directory.

Now my question is, is there a way to move /private/tmp (and /tmp which is a symbol link too it) to another volume and have OSX continue to work? I tried creating a link to the directory to another drive, changed ownership and permissions so everything was the same, but OSX wouldnt log into any user accounts afterward. Any solutions or ways to do it?

update: seems its because tmp is used (and written too) before volumes are mounted during the boot process. any solutions would be greatly appreciated.
 
Last edited:
Just adding my name to list of folks who had to revert. 2011 17" Macbook Pro and Vertex 3 240 SSD is not a good combo for this TRIM hack unless you don't mind beach balls every now and again (for me it was around once an hour or so, sometimes more often, for about 20 seconds). This hardware combo now works great since undoing the hack.
 
walshlink said:
RS2...spin this off in a separate thread if necessary so we don't hijack this one, but can you explain this in more detail? I have restored images to my SSD using CCC with "Erase Destination", and don't have any problems... After restoring the image and repairing permissions using Disk Utility, I don't see any permission that need significant repair (there are a few, but not necessarily significant)...
Click to expand...

The issue with block-level copy is not related to disk permissions. You should recreate the volume structure with directory files on the new SSD. If you do block-level copy you will have an exact copy including the volume structure which is specific for the HDD. Bad blocks that are mapped out and hot-files within the metadata zone are also copied to the new SSD. For best performance and to avoid problems with the file system you should always do file copy to the new SSD. The volume and all files will also be defragmented if you do file copy to the new SSD. Block-level copy is faster and OK for backups but not suitable to create a new startup volume.
 
Macshroomer said:
Pulled the plug on TRIM on my MacPro OWC 120GB, too many beach balls, all is fine now.

However, I will keep it on my MBP 13" using an Intel 160GB G2, it really seems to have benefitted from the patch.
Click to expand...

i did aswell i noticed when i went back to when i had no trim support - the system boot-up was 7-9 secs, now its about 9-11 secs

however, i have noticed that the system is somewhat noticeably faster with trim enabled, and benchmarks confirm this

i have only ever gotten the beachballs on 3 occasions; no sleep/wake issues so went back to enabling trim
 
Since I rolled back from the patch I have not had any stability issues at all.

I don't boot my computer anyway, except when Apple forces me to for an upgrade, so I don't really care about boot times.
 
Cindori said:
To TRIM your disk after enabling TRIM:
1. Open Disk Utility
2. Select your SSD from the right-hand-side bar
3. Click "Erase" tab
4. Select "Erase Free Space..."
5. Select the fastest method (no need to add extra write cycles by doing it multiple times) and click "Erase Free Space"
Click to expand...

Guys I've just tried to run the erase free space command on my system (I've an OWC SSD drive with TRIM not enabled beacuse it just freeze the system) and now my free space is gone!!! :(

I have rebooted from another drive to free up some GB to make it boot again... do you have any idea on what should I do now? :p

UPDATE: problem solved loggin in as root and erasing again the free space on the SSD drive... uff! :D
 
Last edited:
Caesar_091 said:
Guys I've just tried to run the erase free space command on my system (I've an OWC SSD drive with TRIM not enabled beacuse it just freeze the system) and now my free space is gone!!! :(

I have rebooted from another drive to free up some GB to make it boot again... do you have any idea on what should I do now? :p
Click to expand...
Did you let the erase free space finish? When it is done (and it can take a while) the temp file that fills your disk is deleted. I guess too late now for you. You'll need to find where that file is (/tmp ?) and delete it.
 
Just ran this patch on my 2011 MBP with a X-25M G2 160GB Intel drive and everything seems to be running much snappier. Boot time has decreased for me.

EDIT: Says TRIM enabled under system profiler:
 

Attachments

  • Screen shot 2011-04-10 at 23.49.11.png
    Screen shot 2011-04-10 at 23.49.11.png
    62.4 KB · Views: 93
Last edited:
Hello,

Making a list of drives with good garbage collection and those without should clear things up for those wondering if their SSD will benefit or not from TRIM. Looks like Intel's G2s don't (and so will benefit) and OWC's do (so they benefit less or have problems).

Loa
 
brokeneck said:
Just adding my name to list of folks who had to revert. 2011 17" Macbook Pro and Vertex 3 240 SSD is not a good combo for this TRIM hack unless you don't mind beach balls every now and again (for me it was around once an hour or so, sometimes more often, for about 20 seconds). This hardware combo now works great since undoing the hack.
Click to expand...

Yeh same scenario on a Vertex 3 120 SSD. I'm just gunna run fsck_hfs to trim the drive every 2 weeks. In theory it'll make no differencing trimming once in a while rather than continuously, and we get the benefit of no beachballs in the meantime.
 
alvindarkness said:
Yeh same scenario on a Vertex 3 120 SSD. I'm just gunna run fsck_hfs to trim the drive every 2 weeks. In theory it'll make no differencing trimming once in a while rather than continuously, and we get the benefit of no beachballs in the meantime.
Click to expand...

I think you will need the hack installed for that fsck command to TRIM the drive. I suppose you could install the hack, run fsck, then uninstall the hack if you want to TRIM once in a while without leaving the hack on all the time?
 
Weaselboy said:
I think you will need the hack installed for that fsck command to TRIM the drive. I suppose you could install the hack, run fsck, then uninstall the hack if you want to TRIM once in a while without leaving the hack on all the time?
Click to expand...

Yeah exactly right. I just hexedited the ioahciblock kext, and made a copy of the original - easy to swap around when needed. Never tried the patch in this thread which essentially does the same thing I'd assume.

I usually have a backup install of osx on a usb stick or spare partition - just as easy to boot that up once a fortnight (with trim always enabled on it) and fsck_hfs from there. That way you have exclusive read/write access to the ssd.

I've already tried the above, running Lion DP2 as the spare osx install from a usb stick - and using that to trim my main install which is snow leopard on the ssd. Works fine. I think once a fortnight or even once a month should be enough.

On a side note, Lion doesnt come with a version of fsck_hfs that does trim, but if you copy it over (form a mbp2011) it works fine with the default libraries etc lion comes with.

I'm just hoping Apple use of trim improves by the time the golden master of lion is out.
 
Ok I was just able to get some weirdness out of my MBP that sounds a bit like the problems people are having here... including beachball and not being able to wake back up from sleep.

I plugged into an external Hard Drive to do a time machine back up. As it was backing up, everything started acting up... another problem I was having while I was plugged in, all my expose active corners weren't working. I was also plugged into my TV in clam shell mode as well...

On a side note though... I was also using my Bluetooth Keyboard and Mouse as well as plugged in my TV using clamshell mode... these could be contributing factors to my MBP acting up...

I just wanted to make note of it if any of you care to try to replicate any of the problems I had. I think it's more to do with being plugged into a hard drive and running time machine.

Trim and my laptop work like a charm so long as I don't have it plugged into the hard drive.

Thoughts?
 
2011 macbook pro with ocz vertex 3

i made an account just to add my thoughts on these hdd stutters that are occurring on the 2011 Macbook Pro with Vertex III SSD.

i had the same problem. installed trim enabler 1.1 and the OS was acting horrible. every 15 or 20 seconds the hdd would refuse IO for about 10 seconds. then i read further in the orginal post.

If your SSD had undeleted writes all over it previously, and you install trim enabler 1.1, those undeleted writes are still there. i dont know why they're all of a sudden a problem, but maybe that's why the stutters started to occur.

I opened disk utliity, as the OP states, and manually ran TRIM on the free space. This had been a big improvement, but has not fixed it completely. I got my first stutter while writing this post. Other than that, the stutters stopped... but seems like they're not completely gone yet...

Maybe the OP has some insight into this???
 
Cindori you are awesome man trim worked perfect boot times are alot faster like the first day I got this SSD put in. Its was slowin down and I was frustrated and looking to get a new SSD but no need now LIKE NEW AGAIN!!! awesome thanks again

SAMSUNG SSD PM800 2.5" 256GB:

Capacity: 256.06 GB (256,060,514,304 bytes)
Model: SAMSUNG SSD PM800 2.5" 256GB
Revision: VBM24D1Q
Serial Number:
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
Gamintosh HD:
Capacity: 255.72 GB (255,716,540,416 bytes)
Available: 183.31 GB (183,309,656,064 bytes)
Writable: Yes
File System: Journaled HFS+
BSD Name: disk0s2
Mount Point: /
 
This is more of a thanks, but I thought I'd submit my screenshot to show that it works on 10.6.7 with a Crucial C300 SSD. I will try this on my Lion DP2 partition later...
SolidStateDrive.png
 
Hmmm, my excitement for this has swiftly faded. It seems that you can add the Crucial C300 SSD to the list of SSDs that have problems with this TRIM enabler.
 
Thanks! Working with one of the two cards from Photofast G-Monster V5 raid SSD :D (second has died)
 
I believe it's working on my 2011 15" MBP with Intel 320 in the optibay plus stock drive (home folder) in the HDD bay. TRIM supported, and I ran "erase free space" in disk utility.

I'm just wondering if it's like in the video, that now that it's installed (and as long as Apple doesn't break it with an update, etc.) is it basically just running and doing it's thing in the background and I never need to worry about it again?

And as for those terminal commands in the original post, how would I know that I've entered them and they've registered correctly?
 
Last edited:
You must log in or register to reply here.
Register on MacRumors! This sidebar will go away, and you'll see fewer ads.
Top Bottom
Back