TRIM Support no longer 'easy' in Yosemite

[Gav Mack]

There's no point in taking the time to send TRIM commands to spinners, and it might cause problems.

Ask the drive if it supports TRIM, and if "yes" send it TRIM commands.

I agree - and if feedback is to be sent that sounds like a best suggestion to send to Apple. If you have an equally pointed way to describe dropping the kext madness maybe you will have another good short and sharp point for Apple to do something about that too!

 

[Badagri]

Apple has become the new Microsoft.
So sad.

How exactly? Microsoft isn't as stealth as Apple.

 

[flowrider]

Updated to the final released version of 10.10.1 this morning. A few more steps involved, but installation relatively easy.

1. Downloaded 10.10.1 Updater.

2. Disabled TRIM Enabler and reenabled Kext Signing

3. Restarted

4. Repaired Disk Permissions

5. Installed OS Update

6. Restarted

7. Reenabled TRIM Enabler and disabled Kext Signing

8. Restarted

9. OS updated to 10.10.1 and TRIM enabled.

Lou

 

[h9826790]

I simply apply the update over my TRIM enabled 10.10.1 beta.

TRIM disabled as expected, but the update itself has no issue at all.

However, when re-enable TRIM, and restart, I only get a white screen without nothing else (not even the mouse cursor) on the screen after the Apple logo disappear.

Wait for about 2min, no change. Apart from CAPS LOCK key, the computer has no respond for any other input (e.g. brightness adjustment, CMD+ALT+ESC, etc).

Press "CMD + CTL + power button" to reboot the machine. And now everything back to normal.

 

[Badagri]

So it is intentional. Apple is just being an ass.

 

[crjackson2134]

I had the same expeirence as Lou, only difference was that I switched his step #1 and step #2.

All working perfectly.

 

[rjtiedeman]

Yosemite 10.10.1 update with SSD on Velocity SOLO X2

The 10.10.1 update stopped on reboot with a grey screen with a ?. I forced a restart and reset PRAM 4 times. Then the Mac Pro 5,1 found the SSD and completed the process. Trim Enabler has been off since I installed 10.10 last week and I screwed up the Pro and had to rebuild from back up. So far I have given up on TRIM for the SSD, my CALDIGIT FASTA-6GU3 no longer allows the mac pro to start if my RAID is connected to the SATA port, CUDA drivers won't load and the Nvidia drivers are toast again. I need to take a hint this old dog is on it's last hunt. No point in investing more money in adapters since apple is shutting them out.

All is working for now. Just a little scary on restart.

 

[crjackson2134]

The 10.10.1 update stopped on reboot with a grey screen with a ?. I forced a restart and reset PRAM 4 times. Then the Mac Pro 5,1 found the SSD and completed the process. Trim Enabler has been off since I installed 10.10 last week and I screwed up the Pro and had to rebuild from back up. So far I have given up on TRIM for the SSD, my CALDIGIT FASTA-6GU3 no longer allows the mac pro to start if my RAID is connected to the SATA port, CUDA drivers won't load and the Nvidia drivers are toast again. I need to take a hint this old dog is on it's last hunt. No point in investing more money in adapters since apple is shutting them out.

Well you are using a discontinued and unsupported Caldigit card unless you just forgot to type in the word PRO afterwards. No doubt that is causing some issues.

TrimEnabler works just fine. I've had no problems through several upgrades (including today). Just turn it off and reboot before installing System updates. Then turn it back on again. Seriously, OS X core system updates don't come out every day, so it's not really a hassle at all.

CUDA drivers / Nvidia drivers have nothing to do with your system being a MP 5,1. If you are just looking for an excuse to replace the 5,1 you don't need to find reasons. Just do it. Picking the right hardware for your machine & OS isn't unique to Mac. You have to do that windows / Linux too if you expect to get great performance.

 

[m4v3r1ck]

The 10.10.1 update stopped on reboot with a grey screen with a ?. I forced a restart and reset PRAM 4 times. Then the Mac Pro 5,1 found the SSD and completed the process. Trim Enabler has been off since I installed 10.10 last week and I screwed up the Pro and had to rebuild from back up. So far I have given up on TRIM for the SSD, my CALDIGIT FASTA-6GU3 no longer allows the mac pro to start if my RAID is connected to the SATA port, CUDA drivers won't load and the Nvidia drivers are toast again. I need to take a hint this old dog is on it's last hunt. No point in investing more money in adapters since apple is shutting them out.

All is working for now. Just a little scary on restart.

Sorry to hear of your mishaps updating to 10.10.1.

Thanks for sharing your finding in regards to the update whilst the SSD was on the SOLO X2! I have my test drive OSX 10.10 in bay #1 so I can't give you any feedback about the SOLO myself, second I updated to the DUO.

Perhaps other SOLO users could share some of their update experience in that matter.

I would like to update my RAID0 on the DUO X2 but holding of for update 10.10.2/3. Depending on the development of the Trim Enabler app by Cindori, I'll just clean install OSX 10.10.2/3 on the RAID0 whith the SSD on it using the 10.10 and the combo update. Using Migration Assistent to restore the rest.

I hope your Mac stay will stays with you! Fingers crossed!

Cheers

 

[crjackson2134]

Posts #153 & 156 are 10.10.1 updates to SSDs installed on Apricorn Velocity Solo X2 PCIe cards.

 

[VirtualRain]

I just updated my Mac Mini (with Crucial SSD) to 10.10.1 by disabling Trim Enabler, applying the update, and re-enablng Trim Enabler (with a reboot after each step) and it all worked fine.

 

[Cindori]

The 10.10.1 update stopped on reboot with a grey screen with a ?. I forced a restart and reset PRAM 4 times. Then the Mac Pro 5,1 found the SSD and completed the process. Trim Enabler has been off since I installed 10.10 last week and I screwed up the Pro and had to rebuild from back up. So far I have given up on TRIM for the SSD, my CALDIGIT FASTA-6GU3 no longer allows the mac pro to start if my RAID is connected to the SATA port, CUDA drivers won't load and the Nvidia drivers are toast again. I need to take a hint this old dog is on it's last hunt. No point in investing more money in adapters since apple is shutting them out.

All is working for now. Just a little scary on restart.

The grey question mark is totally different from the grey stop sign.

The grey question mark means that your Mac could not find a disk with an operating system on. It happens before the OS is even loaded so it's 100% unrelated to Trim.

 

[rjtiedeman]

Well you are using a discontinued and unsupported Caldigit card unless you just forgot to type in the word PRO afterwards. No doubt that is causing some issues.

TrimEnabler works just fine. I've had no problems through several upgrades (including today). Just turn it off and reboot before installing System updates. Then turn it back on again. Seriously, OS X core system updates don't come out every day, so it's not really a hassle at all.

CUDA drivers / Nvidia drivers have nothing to do with your system being a MP 5,1. If you are just looking for an excuse to replace the 5,1 you don't need to find reasons. Just do it. Picking the right hardware for your machine & OS isn't unique to Mac. You have to do that windows / Linux too if you expect to get great performance.

You are right. But if I was looking for an excuse to upgrade my 5,1, Yosemite has caused more problems than Mavericks. And yes I did leave the PRO off the Caldigit card name. I have talked to tech support on the FASTA card. The issue would not resolved by buying a FASTA PRO. The problem has no solution as yet. Tech support suspected that because both cards are using similar Marvell SATA controllers they might be having a resource conflict (caused by 10.10). Upgrading to the new FASTA PRO will not fix the problem with the Velocity X2. They suggested ditching the Velocity X2 and just using the FASTA PRO internal connections for my boot SSD. However then I have rig up power wires for the SSD. Best to for ditch the SATA raid since it's getting old and it works just fine with firewire as a back up.

By the way when I ran disk utilities after updating 10.10.1 from the recovery disk. I noticed that disk repair Trimmed all the unused blocks at the end of the repair process. Is that the same as what TRIM enabler would do?

 

[crjackson2134]

You are right. But if I was looking for an excuse to upgrade my 5,1, Yosemite has caused more problems than Mavericks. And yes I did leave the PRO off the Caldigit card name. I have talked to tech support on the FASTA card. The issue would not resolved by buying a FASTA PRO. The problem has no solution as yet. Tech support suspected that because both cards are using similar Marvell SATA controllers they might be having a resource conflict (caused by 10.10). Upgrading to the new FASTA PRO will not fix the problem with the Velocity X2. They suggested ditching the Velocity X2 and just using the FASTA PRO internal connections for my boot SSD. However then I have rig up power wires for the SSD. Best to for ditch the SATA raid since it's getting old and it works just fine with firewire as a back up.

By the way when I ran disk utilities after updating 10.10.1 from the recovery disk. I noticed that disk repair Trimmed all the unused blocks at the end of the repair process. Is that the same as what TRIM enabler would do?

Regarding TRIM, yes, the disk repair you observed does the same, just not on a continual basis and not when trying to Trim from the drive's own restore partition. You need to be booted from a different partition, and mount the partition you want to Trim.

Regarding your USB conflict. Somehow I missed that you were running the Solo also. HighPoint makes a card with the same features but a different chipset (ASMedia). It's called the 1144E, I have the USB only version (1144C) and the SoloX2. There are no conflicts. I would research the 1144E if I were you, it probably fits the bill in your case. Contact HighPoint Technologies directly and they will let you know. Don't depend on there marketing material, they tend to leave out information / undersell their products for some reason.

The FASTA PRO never did work properly for me even before I had my SoloX2. Please don't blame your MP for CalDigit short comings. I fully understand being disgruntled about Yosemite though, I've considered reinstalling Mavericks until issues are resolves, but I've not had to do that yet. I'm aggravated about the TRIM status, but honestly, it's not been much of a problem once TE is properly installed.

 

[Sharky II]

So can I just do a disk repair on the OS ssd and it will 'trim' the drive? I don't mind doing that at all.

 

[flowrider]

^^^^Yes, but of course, Disk Repair doesn't work on the Boot Drive.

Lou

 

[Macdctr]

I found this thread interesting to read but wish I had read it before upgrading from Mavericks to Yosemite. I had TRIM support for my Samsung SSD and haven't had any issues. Once I did the upgrade to Yosemite, I noticed I no longer had TRIM support however everything seemed to work perfectly.

I used the app Chameleon SSD Optimizer to enable TRIM support for my SSD and haven't had any difficulties. Just wanted to put that out for you guys/gals. Here's the link: http://chameleon.alessandroboschini.com

As you can see in the below pic, I now have TRIM support with Yosemite

From what I have read in this thread, there were issues. I guess I was lucky because I didn't experience any of those issues when I did the upgrade from Mavericks to Yosemite.

 

[DPUser]

From my reading, I understand Chameleon turns off Kext signing. I like Cindori's approach - transparent dissemination of the gory details - better.

 

[VirtualRain]

From what I have read in this thread, there were issues. I guess I was lucky because I didn't experience any of those issues when I did the upgrade from Mavericks to Yosemite.

The issues people are having are not upgrading from Mavericks to Yosemite... they are upgrading point releases of Yosemite AND/OR doing a PRAM reset because of a new security setting in Yosemite. You will likely encounter the same problems if/when you do one of these unless you follow the advice in this thread. The good thing is that we know what exactly Trim Enabler is doing and as a result, when it's good to "undo" it to avoid issues. Who knows what that tool you're using does behind the scenes?

 

[Badagri]

I found this thread interesting to read but wish I had read it before upgrading from Mavericks to Yosemite. I had TRIM support for my Samsung SSD and haven't had any issues. Once I did the upgrade to Yosemite, I noticed I no longer had TRIM support however everything seemed to work perfectly.

I used the app Chameleon SSD Optimizer to enable TRIM support for my SSD and haven't had any difficulties. Just wanted to put that out for you guys/gals. Here's the link: http://chameleon.alessandroboschini.com

As you can see in the below pic, I now have TRIM support with Yosemite

Image

From what I have read in this thread, there were issues. I guess I was lucky because I didn't experience any of those issues when I did the upgrade from Mavericks to Yosemite.

You should have updated the firmware on your Samsung to 09.

 

[flowrider]

The issue is still being talked about on various Mac Sites. Here's another one:

http://www.macworld.com/article/2849366/mac-wont-boot-about-yosemite-and-your-third-party-ssd.html

It has some errors, but hopefully Apple is reading.

Lou

 

[crjackson2134]

I don't have a link, but ZIff Davis (ZD net) just did a story this too.

 

[cinealta]

Is disabling kernel extensions a big security risk or minor?

 

[VirtualRain]

Is disabling kernel extensions a big security risk or minor?

If I understand it correctly, you're just disabling Kext signing to allow unofficial kernel extensions... Since this is a new security feature, there is no added risk (in my opinion) that wasn't already present in every previous version of OS X. However with more malware targeting Macs I could see why Apple went this route. I guess it's possible you download some malware that installs a hacked Malicious Kext... If that possibility concerns you because of your surfing and downloading habits, then don't disable it. But in my case, I personally don't consider it risky for my HTPC Mac Mini, but I wouldn't dare disable it on my work laptop (thankfully I don't have to). Everyone's tollerance for risk is different with more or less at stake if the risk materializes.

 

[cinealta]

If I understand it correctly, you're just disabling Kext signing to allow unofficial kernel extensions... Since this is a new security feature, there is no added risk (in my opinion) that wasn't already present in every previous version of OS X. However with more malware targeting Macs I could see why Apple went this route. I guess it's possible you download some malware that installs a hacked Malicious Kext... If that possibility concerns you because of your surfing and downloading habits, then don't disable it. But in my case, I personally don't consider it risky for my HTPC Mac Mini, but I wouldn't dare disable it on my work laptop (thankfully I don't have to). Everyone's tollerance for risk is different with more or less at stake if the risk materializes.

Good to know. Thanks for info!