Cool! So why 10.9.4 or earlier - is there some problem doing this with 10.9.5?
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 no longer 'easy' in Yosemite
- Thread starter Sharky II
- Start date
- Sort by reaction score
Cool! So why 10.9.4 or earlier - is there some problem doing this with 10.9.5?
I mistakenly thought so, but it turns out there's no problem. Sorry about that.
Last edited:
Are you sure? I am quite sure that I did few PRAM reset on 10.9.5 with TRIM enabled, no problem at all.
Last edited:
Okay, cool. I'm mistaken then. I could have sworn they changed that in 10.9.5 too, but I'm glad to be wrong
----------
I thought that was the case, but it turns out I'm incorrect, and happy for it
^^^^No, I the issue with kext never arose until Yosemite IIRC. Early on in Yosemite, like with the first developer and Beta releases.
I didn't want to disagree with Mr. Jackson again
Lou
Why not? I respect your opinions. If I'm wrong, I'm wrong. It's not personal, and I appreciate the knowledge
I was running both Mavericks and Yosemite PB at the same time too. For some reason I was thinking 10.9.5 had the same new policy.
Last edited:
I haven't yet tried this myself, but this seems to be a good measure to take. You should be able to do PRAM resets without losing Trim or getting the no boot condition.
https://forums.macrumors.com/posts/20286850/
UPDATE: Okay, so I ran the command below in terminal, left Trim Enabled, and did an NVRAM reset 4 times to test. The modification held, Trim is still working fine, Trim Enabler is working fine. This seems like a good fix.
https://forums.macrumors.com/posts/20286850/
UPDATE: Okay, so I ran the command below in terminal, left Trim Enabled, and did an NVRAM reset 4 times to test. The modification held, Trim is still working fine, Trim Enabler is working fine. This seems like a good fix.
Code:
sudo /usr/libexec/PlistBuddy -c "Set :'Kernel Flags' 'kext-dev-mode=1'" /Library/Preferences/SystemConfiguration/com.apple.Boot.plist
Last edited:
Are u sure “Repair Disk” will trim unused blocks?
I know "Erase Free Space" or running fsck in single mode would ...(assuming trim is active)
.
If you are talking about booting Yosemite into single user mode and running from there... Never tried that.
I installed Mavericks 10.9.5 on a separate physical disk, enabled Trim with Trim Enabler, then ran repair on the Yosemite disk (non-CoreStorage volume). I don't have the Mavericks disk anymore, but I can reinstall it and re-check it if you like. You could be right that it was erase free space I used, but IIRC I ran the repair.
I installed Mavericks 10.9.5 on a separate physical disk, enabled Trim with Trim Enabler, then ran repair on the Yosemite disk (non-CoreStorage volume). I don't have the Mavericks disk anymore, but I can reinstall it and re-check it if you like. You could be right that it was erase free space I used, but IIRC I ran the repair.
Yes ... it will trim unused blocks.
You must:
- have trim enabled for the SSD (i.e. no USB attached SSDs. Only SATA, eSATA, or Thunderbolt)
- select the named logical drive, not the top physical drive in disk utility
- can't be your boot disk, boot from a Mavericks partition with trim and repair your Yosemite disk.
Towards the end of the repair dialog, you will see "trimming unused blocks" displayed.
Last edited:
Actually before i posted, i test it by booting from the recovery partition (w/trim enabled) & the dialog didnt report trim unused blocks ..
So, maybe ur right as long as no boot from recovery partition (restore boot disk utility) I just have no way to test that (my drives almost full).
-------------
Thanks.
btw, did u have the chance to test it by booting from the recovery partition (restore boot disk utility) or it has to boot from a full OS partition/disc?
.
Are you sure you booted "from recovery partition (w/trim enabled)"?
How did you enable Trim while booted to the recovery partition?
Last edited:
I updated Trim when the Yosemite update was available. The day Yosemite was released I obviously upgraded (couldn't wait!) and all is working fine. From the 'about this Mac' Trim enabled is marked yes. This could mean that that the KEXT signing security is altered?
If you don't have TRIM support, can't you just erase the SSD and restore from a clone every few months?
Another question: under what circumstances does a PRAM reset occur without doing it manually?
OS Update, perhaps?
Currently, i've simply turned TRIM off.
OS Update, perhaps?
Currently, i've simply turned TRIM off.
Sorry, I wasn't clear in my post ...
If you are running Mavericks, you can boot from the recovery partition and use that Disk Utility to "Repair Disk" and it will trim unused blocks. Sorry ... this won't work.
If you are running Yosemite, you need a small bootable partition with Mavericks and trim enabled which you can then use to "Repair Disk" on your Yosemite SSD and it will then trim unused blocks.
Last edited:
Yes. I had “TrimEnabler active.
btw, I haven’t switch to Yosemite yet (still on Mavericks)
--------------
You were clear, btw. I’m the one who didn’t post enough info ..
I test it with Mavericks (w/trim enabled) but the repair dialog didn’t report … trim unused blocks ..
did u actually test it using the recovery partition? Or u used another Mavericks/Ml partition? (assuming u used Mavericks)
I ‘ve been using fsck for years (w/trim enabled) & that works fine. i also used "Erase Free Space" in the past, it works but its not practical & time consuming. So when "crjackson2134" posted “Repair Disk” as another trim option I was hoping the recovery partition would do it (maybe it does & the issue in my end).
Q, does Yosemite install recovery partition? (same as Mavericks)
.
Yes. I had TrimEnabler active.
btw, I havent switch to Yosemite yet (still on Mavericks)
--------------
You were clear, btw. Im the one who didnt post enough info ..
I test it with Mavericks (w/trim enabled) but the repair dialog didnt report trim unused blocks ..
did u actually test it using the recovery partition? Or u used another Mavericks/Ml partition? (assuming u used Mavericks)
I ve been using fsck for years (w/trim enabled) & that works fine. i also used "Erase Free Space" in the past, it works but its not practical & time consuming. So when "crjackson2134" posted Repair Disk as another trim option I was hoping the recovery partition would do it (maybe it does & the issue in my end).
Q, does Yosemite install recovery partition? (same as Mavericks)
.
I generally use a different bootable disk as I have several in my cMP. Be sure you select the "named logical disk" in Disk Utility ... this will be the bottom icon for that drive. If you select the top icon, the physical disk, you will not see the trim message. Also, be sure "trim" is enabled before you start, and that the target drive is not an external USB SSD as USB doesn't do trim.
Tried it again, no go.
-------------------
@Gav Mack
(if u still on Mavericks & got a chance) could u give it a try - boot from the recovery partition - Repair Disk & see if the repair dialog reports trim unused blocks?
thx
It sounds like you were booted to the OS and enabled trim, then booted to the recovery partition and tried to run the disk repair (believing that Trim would be enabled there too).
Activating Trim from the normal OS, does not enable Trim for the restore boot partition. That's why I wanted to know how you enabled Trim for a restore boot partition. It can be done I assume, but I don't personally know how.
I booted into full install of Mavericks (on a different physical disk), enabled Trim, then ran the repair.
A ton of posts that would unnecessary if Apple simply used the industry standard APIs to ask the drive if it supported TRIM (like the other x64 operating systems do).
Regarding trimming a disk from the recovery partition:
Hmmm ... I believe you are correct here and I was mistaken above (it has been a long time since I booted a recovery partition). I have several bootable system disks in my Mac and it is easier just to reboot to one of them with trim enabled and then repair disk the other drive to trim unused blocks. Thanks for correcting this!
I will correct my post above ... sorry for misleading anyone here.