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

TRIM Support Enabler

well I tried doing something else as well. here is the break down.

I have my 15" i7 ( 2010 ) with my OCZ Vertex 2 SSD ( one that is messed up ) and I also have my wifes 2010 13"

I took out the SSD and copied the IOAHCIFamily.kext file from my wifes 13" to my 15" via a usb enclosure. did the verbose mode and it couldnt find the IOAHCIFamily.kext file.

So I looked online and found this site / discussion http://www.hardmac.com/news/2011/03/25/how-to-activate-trim-on-any-ssd and used that download link for the IOAHCIFamily.kext file...still no go.. Same error that it couldnt find the IOAHCIFamily.kext.

I will now wait for the developer. Hopefully he can help me, so I dont have to completely start over.
 
Why GC vs TRIM?

Hi,

I just got an Intel 320 series SSD for my new MBP15 and installed it, and as first tweak added a launch-item that remounts with noatime (as there's no /etc/fstab where I can simply add noatime to the mount options).

Then I started reading up on whether it was a good idea to enable TRIM, and how to do that given that it's not automatic; the procedure itself seems pretty simple, either use the TrimEnable or just whip up some hex editor and change a few bytes in the right file to zero, then erase the free space to make sure that everything that's free is actually TRIMmed, fine.

However some posts on the web implied that there might be detrimental effects when enabling TRIM on a modern drive with good GC, to which I believe the Intel 320 series can be counted, and I have not understood which "evil interaction" this might be...

...because even the most sophisticated SSDs do not interpret filesystem meta-data, and would therefore require TRIM to let the GC be able to distinguish between data and garbage, or am I missing something?

Thanks

(For example I stumbled over this statement:"So then you add drive level GC which can mess up the way win7 looks after how it deals out TRIM commands as GC alters what the volume bitmap should look like." which doesn't really make much sense to me — the TRIM command works on the level of sectors, i.e. the unit of data on the host interface of the SSD, whereas GC, and wear-levelling, move around the internal larger data blocks; the SSD must have some mapping table so that it knows which sector is stored in which block, but I don't see this mapping table ever being exposed, and I don't see why the presence of GC should create an interference between TRIM and this mapping table as the quote implies...?)
 
Cindori said:
here is some discussion on trim vs gc:
http://www.ocztechnologyforum.com/forum/showthread.php?60690-Garbage-Collecting-vs.-Trim
Click to expand...

Thanks!

This thread mostly reinforces my original intuition, namely that GC and TRIM are mostly complementary, except that GC requires TRIM to do its job best. The only problem might arise on a small drive that is nearly full ("small drive" because presumably "full" would be relative to the total size, not just the user-visible one, and large drives have enough spare area) where there might be some performance degradation when there's a lot of GC going on that doesn't come to rest because it's always nearly full, and because of TRIM the GC knows where it might still shuffle around some data.

Since my 300 GB drive has at least 20 GB spare, I am coming to the conclusion that TRIM should work fine in my case...
 
sjm300 said:
After erasing the free space, I had to force reboot ( machine froze and I let it try to unfreeze for 15 min )

After hardbooting, thats when I couldn't boot up anymore.

With that being said, I couldnt run the commands in terminal via Single user or terminal within the install CD since its not doing the command off the boot driver per say.
Click to expand...

Well there's your problem.
Been noted a few times in this thread.

The erase free space may freeze for 15 min or more, and you have to let it finish.

By hardbooting you did not allow it to finish and the tmp file is not deleted, causing you to have 0k space, which is why you couldnt boot.

AKA; not trim enablers fault.




But now you started switching out the kext anyway, and instead are having the problem that your OS can't use the kext when booting. This is probably because you are moving it over from another OS. The permissions are not correct.

So repair the permissions by booting from the install disk and try boot again and see what happens.
 
Cindori said:
Well there's your problem.
Been noted a few times in this thread.

The erase free space may freeze for 15 min or more, and you have to let it finish.

By hardbooting you did not allow it to finish and the tmp file is not deleted, causing you to have 0k space, which is why you couldnt boot.

AKA; not trim enablers fault.




But now you started switching out the kext anyway, and instead are having the problem that your OS can't use the kext when booting. This is probably because you are moving it over from another OS. The permissions are not correct.

So repair the permissions by booting from the install disk and try boot again and see what happens.
Click to expand...

I'll try that.

thanks
 
Hi,

First, many thanks for making this patch. Very cool that people build and share...

I am afraid though, I am having a problem in running the Enabler on my system.

Here are the details - Macbook 4,1 - 10.6.7, 2.4Ghz C2D, 4GB Ram

The Intel X25M (Model: INTEL SSDSA2M120G2GC; Revision: 2CV102M3) I believe supports TRIM, and I have it running in the Optibay.

Unfortunately, I have tried to turn the Enabler, and after trying six times or so, TRIM does not show up. Likely I am doing something wrong, or...

If anyone has any ideas, thoughts, or comments, I would be grateful to read them.

Thanks,
H
 
Correct me if i'm wrong but isn't OS X TRIM support tailored to the Toshiba/Samsung controllers which power Apple's SSD drives? i.e. will they work with Sandforce, Marvell etc?

Also i've read conflicting reports on whether writing zeroes to your SSD is a bad idea or not. Yay or nay?
 
daneoni said:
Correct me if i'm wrong but isn't OS X TRIM support tailored to the Toshiba/Samsung controllers which power Apple's SSD drives? i.e. will they work with Sandforce, Marvell etc?
Click to expand...

What "tailoring" could have been done? TRIM tells the drive which sectors can be considered garbage because the files that occupied them were deleted, which sounds pretty straightforward, unless there's something strange that I'm not aware of.
 
Basic75 said:
Since my 300 GB drive has at least 20 GB spare, I am coming to the conclusion that TRIM should work fine in my case...
Click to expand...

...and at least for the first five minutes after enabling it nothing bad has happened yet ;-)

(I have version 2.0.6 of the IOAHCIBlockStorage extension, and used Emacs to overwrite the two occurrences of "APPLE SSD" with zero-bytes; that alone didn't work, but after an additional "kextcache -system-caches" and "kextcache -system-prelinked-kernel" I've now got it enabled. Btw, using Emacs as "root" saved me from having to fix permissions after the change.)
 
Basic75 said:
What "tailoring" could have been done? TRIM tells the drive which sectors can be considered garbage because the files that occupied them were deleted, which sounds pretty straightforward, unless there's something strange that I'm not aware of.
Click to expand...

All well and true but a significant amount of people have posted on these forums on adverse effects as a result of using this method to enable TRIM. Speed reductions, beachballs, kernel panics. Yet Apple's factory SSDs don't have these issues.

Why?
 
Cindori said:
your ssd supports trim, but you have to download the latest firmware for it.
Click to expand...

Hi Cindori,

Many thanks for your help and for the Enabler again.

I double checked, and I have the latest firmware - (Model: INTEL SSDSA2M120G2GC; Revision: 2CV102M3). The firmware is the 02M3, which is the latest, I believe anyway...

Must be something else I am over looking... do you, or anybody else have thoughts?

Thanks again,
H
 
I need some help here, please...

It was working great until today, I rebooted and it takes several seconds to boot up. I rebooted again and again and it keeps the same time.

So, I removed the trim patch, and it booted normal again.
I patched, and booted normal again (normal = fast boot). So I did an erase empty spaces again and it becomes slow again.

I removed trim and all becomes normal. Patched again and it is working fine, but I did not did the write empty spaces again...

So, two question:

If I don't wipe empty space again, the trim will not work?
Why I am getting these problems now?

Thank you
 
howman66 said:
Hi Cindori,

Many thanks for your help and for the Enabler again.

I double checked, and I have the latest firmware - (Model: INTEL SSDSA2M120G2GC; Revision: 2CV102M3). The firmware is the 02M3, which is the latest, I believe anyway...

Must be something else I am over looking... do you, or anybody else have thoughts?

Thanks again,
H
Click to expand...

I have the same disk with same firmware, I'am using trim enabler from day one without any problems or slowups.:)
Maybe momentus xt is the problem - hybrid drive.:confused:
 
Lunitik007 said:
I have the same disk with same firmware, I'am using trim enabler from day one without any problems or slowups.:)
Maybe momentus xt is the problem - hybrid drive.:confused:
Click to expand...

Thanks for your reply.

The XT is in the normal drive slot and not the startup...maybe (likely) I am a moron and I am doing something wrong.

Here is what I have tried -
1) Patch, Reboot, Erase Free Space, Terminal Commands, Patch, Reboot; (Nothing in trash to dump, so, no dumping of trash)

2) Patch, Erase Free Space, Terminal Commands, Patch, Reboot;

3) Patch, Reboot, Erase F. Space, Patch, Reboot;

4) Patch, loaf of bread, gallon of milk, and a stick of butta, reboot

Nothing seems to work.

When erasing free space, I get an error message that I am running out of free space (28GB used, 92GB Free), but this is what is supposed to happen, I think.

So, not sure what I am doing wrong.

Start up times have not changed at all though - it remains at about 25 seconds from pushing the on-button to desktop. Not sure why I am trying to fix something that is not (yet) broken...trying to explain that to the wife, so, any advice on this is also most welcome...
 
ZeD X said:
I need some help here, please...

It was working great until today, I rebooted and it takes several seconds to boot up. I rebooted again and again and it keeps the same time.

So, I removed the trim patch, and it booted normal again.
I patched, and booted normal again (normal = fast boot). So I did an erase empty spaces again and it becomes slow again.

I removed trim and all becomes normal. Patched again and it is working fine, but I did not did the write empty spaces again...

So, two question:

If I don't wipe empty space again, the trim will not work?
Why I am getting these problems now?

Thank you
Click to expand...

Boot time can again increase if you installed some software that installs kext drivers. you should then try running the terminal commands in the first post to maintain the kext library in perfect shape and minimize boot time.
This is just generally and not anything to do with trim really.
 
howman66 said:
Thanks for your reply.

The XT is in the normal drive slot and not the startup...maybe (likely) I am a moron and I am doing something wrong.
Click to expand...

Momentus XT uses flash memory only as an intermediate large "cache" and holds the most used files there. It is in fact a regular magnetic hdd with some more or less clever caching, nothing less. You will not benefit from TRIM with the Momentus XT at all. BTW, due to the concept behind, it will work best if the whole 4GB SSD "cache" is filled up to the top.
 
hwojtek said:
Momentus XT uses flash memory only as an intermediate large "cache" and holds the most used files there. It is in fact a regular magnetic hdd with some more or less clever caching, nothing less. You will not benefit from TRIM with the Momentus XT at all. BTW, due to the concept behind, it will work best if the whole 4GB SSD "cache" is filled up to the top.
Click to expand...

Thanks, and sorry for any confusion...

I have an Intel SSD in the Optical Drive as the startup drive for which I am trying, in vain, to enable the TRIM Enabler. (Correct Firmware, et al)

The XT is just (just?) the drive I keep music and useless crap on. I am not trying to enable TRIM on it.

I have just tried again to enable the enabler - Enable, Reboot, Erase, Terminal Commands, Enable, Reboot - this after I used Onyx to erase temp files, and still nothing. So, I am officially an egghead...
 
trim driver maybe doesnt check ODD sata (optical drive), try moving it to drive bay.
 
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