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.
SATA Express meets the '09 Mac Pro - Bootable NGFF PCIE SSD
- Thread starter handheldgames
- Start date
- Sort by reaction score
My understanding is that every time you upgrade your OSX, the system files will be overwritten which automatically disable the TRIM.
^^^^Not my understanding! If you try and update the OS or modify it in any way (PRAM reset or etc) upon restart you'll boot to a white screen if you didn't disable TRIM Enabler beforehand. After the initial restart you reenable TRIM Enabler (and Kext Signing) and everything will be a go.
Lou
Lou
I've already did it quite a few times already, 10.10 -> 10.10.1 beta -> 10.10.1 -> 10.10.2 beta.
No problem at all. TRIM will be automatically disabled, I guess that's because the system file to tell OSX to enable TRIM was overwritten during upgrade. It's just exactly the same as kext signing, it will revert back to it's original state regardless if you re-enable it before the update or not.
It just make the TRIM status back to stock (no TRIM support for 3rd party SSD), that's all. And the user have to re-apply TRIM Enabler again (or it can remind you that TRIM is now disabled in the paid version).
Even though in 10.9, every OSX update did disable TRIM automatically. Same thing happen in 10.10, And since no TRIM is enabled for 3rd party SSD right after an OSX update, the system won't boot into write screen, or shows the no go sign regardless the kext signing status.
Of course there is nothing wrong to exercise extra precaution, because we can't tell what's actually happening during every single OSX update. And it doesn't cause any issue from the pass doesn't mean that won't cause trouble in the future.
No problem at all. TRIM will be automatically disabled, I guess that's because the system file to tell OSX to enable TRIM was overwritten during upgrade. It's just exactly the same as kext signing, it will revert back to it's original state regardless if you re-enable it before the update or not.
It just make the TRIM status back to stock (no TRIM support for 3rd party SSD), that's all. And the user have to re-apply TRIM Enabler again (or it can remind you that TRIM is now disabled in the paid version).
Even though in 10.9, every OSX update did disable TRIM automatically. Same thing happen in 10.10, And since no TRIM is enabled for 3rd party SSD right after an OSX update, the system won't boot into write screen, or shows the no go sign regardless the kext signing status.
Of course there is nothing wrong to exercise extra precaution, because we can't tell what's actually happening during every single OSX update. And it doesn't cause any issue from the pass doesn't mean that won't cause trouble in the future.
Last edited:
Exactly. But there are updates which may reset only the kext-signing and not the Trim driver, which leaves you in the "bad" state causing the gray stop sign. Because of this I recommend users to disable before updating.
I'm working on a major new disk utility software which will improve the situation with Trim in Yosemite. More on that soon.
So I know I asked this before but here goes again.
If I install an XP941 alongside my OWC Accelsior PCIe boot disk, will running TE adversely affect the OWC drive which provides its own trim solution on board?
This is on Mountain Lion 10.8.5 but I'm hoping I can upgrade to Yosemite if possible.
Cheers.
If I install an XP941 alongside my OWC Accelsior PCIe boot disk, will running TE adversely affect the OWC drive which provides its own trim solution on board?
This is on Mountain Lion 10.8.5 but I'm hoping I can upgrade to Yosemite if possible.
Cheers.
I don't think the Accelsior has it's own TRIM solution, it just has GC which is the same as many other SSD. TRIM can only improve it's performance or doing nothing to it. Can't think about a way that TRIM can adversely affect an Accelsior.
According to OWC webpage, the Accelsior actually works better in Windows which provide native support. AFAIK, TE will make OSX provide TRIM to all onboard SSD which support this function. If the Accelsior can't work with TRIM, they should not implant this function at the beginning.
My understanding is that OWC want to advitise the Accelsior that can work well in OSX without TRIM. And there is no evidence that the Accesior works better without TRIM.
I'm surprised no one has made a full PCI Express x16 card that can house 4 x M.2 or Apple equivalent PCI-e SSDs using something like the PLX Technology switches.
That way each PCI-e SSD would have access to 4 lanes.
That way each PCI-e SSD would have access to 4 lanes.
Thanks.
I asked OWC support and here's what they said:
"The speeds have nothing to do with TRIM. Also our SSDs do not require TRIM as they have their own built-in data management features. Using TRIM with our drives is not recommended as using two management features at the same time may result in unnecessary wear on the drive. Since the mac OS does not support TRIM for non-Apple SSDs, and since our SSDs do not require TRIM, I advise not to try to enable it at all."
Which seems odd because, as you mention, the two maintenance tasks would run together when installed on a PC. Will enquire with their actual tech guys later today what the difference is on a PC running TRIM but this isn't great news for me if true as I'm then excluded from drives like the SM951.
Thanks for hitting the breaks here Lou, I really wasn't sure about this! Disabled TE and done all my updates and maintenance, then re-enabled TE and I'm up-and-running again.
I'm now getting the sleep/wake issues with Slot #2. Does this just effect the XP941 or will I be ok with the Sintech/Apple setup? I guess running it in slot #4 will be slower? I don't have any other cards in slot #3, just the GPU in #1.
I'd imagine anyone who installs 10.10.2 (I'm on beta) will start suffering the sleep issues as they have fixed the problem where 10.10.1 would wake itself up every 2 hours or so like a newborn! Fix one thing, break another
I'd imagine anyone who installs 10.10.2 (I'm on beta) will start suffering the sleep issues as they have fixed the problem where 10.10.1 would wake itself up every 2 hours or so like a newborn! Fix one thing, break another
Hello Sam, I have this SSD. Slot 3 or 4 support much faster SSDs. I have read the sleep bug is for auto sleep only. Manual sleep all good.
Just installed My new 256GB XP941. I wonder, with Blackmagic and Stress 1GB test I get only a read spead of 120 MB/s. Write speed is up to 740MB/s. Even with my SSD I'm getting 200MB/s read. I'm using 10.9.5 and a x4 adapter in slot 3.
Is that a correct (max) value?
Is that a correct (max) value?
That is far from its best performance. You should get 800 read / 1100 write. Leave the test running and it should climb to peak values.
But I have good news for you all. Google 'SM951' and hit the News tab. The new SSD goes into mass production this week. There is also an SM953 which is a faster enterprise version.
It climbs after some time. I just wonder, because my SSD is showing directly 200MB/s write speed even connected as a normal HD.
No way. Write speed looks about right. Read should be over 1000MB/s. My copy of Blackmagic has decided to get messed up so I can't show you my score. I get this
