Search results

Maybe a coincidence and non-Trim related, but the purgeable just went down. Didn’t do anything, pc was just idling.

It’s not really relevant. What I’m looking for are ways to test if Trim is working correctly:

According to the GitHub bug, these Samsung 970 Evos don’t perform Trim within the normal timeout time, although everything seems fine. The only way to test it, is to increase the “AFPS TrimTimeOut” parameter on OC, which I can’t because I’m on Clover. Based on that logic, since my boot times...

I’m on Catalina. I’m not saying it does (although many reports indicate that trim operational SSD’s usually have less purgeable). Just want to make sure everything is ok.

Here’s a print of both. I do have a 2TB for storage but I use this professionally so the ammount of data per year is huge.

Ok, I decided to re-apply the patch and this time was successful! I’m showing Trim support for both units But strangely, I don’t any see any increase in boot times. Purgeable ammount still the same (90GB in NVMe and 110GB on SATA). Are there more ways to test if Trim is performing correctly?

When I used the M2 shows Trim enabled but not the SATA. From what I read on GitHub, even if Trim was active it wouldn’t be working properly (unless I used OC and changed the timeout value). But yeah, they should both have Trim support on. When I applied the KextToPatch, the Apple logo...

Thanks for your effort. Could it be related to the bug on post #3 that affects this particular unit?

Update: tried the kext patch, was unable to boot even in safe mode Managed to replace my config.plist with a backup thru the Clover shell. Still no trim tho

Yes, I did the trimforce command properly (twice already). Enter password, accept, accept. System reboots. Still says “Trim support: No” for my Sata. Thanks, I’ll try the kext patch next.

Thanks! I’ve tried the 'sudo trimforce enable' with no success. I can try the Clover patch. There’s no need to mount EFI before or anything? Just select that patch and save? Also, is it supposed to have “disabled” ticked like mine does? Should I untick?

When I check my Disk Utility, both drives show a huge ammount of space as "purgeable". I believe this means Trim is not working properly? The NVMe's I think always say "Trim support Yes". But why does my Sata drive show Trim support: No?

Yeah, I see it’s a whole new bootloader. I really don’t want to risk boot failure, but I will check that guide. Also, what’s the best way to check if Trim is working correctly or not (despiste what system info says)? Thank you!

Sorry for the delay! I used Clover 5.11 for this install, and when I mount EFI and edit my config.plist, I dont see those variables (SetApfsTrimTimeout or ThirdPartyDrives). Is this normal? I can paste my config.plist if it helps. From what I see in that post they are using OpenCore. Can I just...

I was referring to this: https://github.com/dortania/bugtracker/issues/192 I don't remember my config.plist since it was 1 year ago, but I will check in a moment.

Hello guys and thanks in advance for any help, I've had this build for a year (Clover, Catalina 10.15.4, Gigabyte z390 Designare, i9 9900k, RX580) but recently was made familiar with the Trim bug on Samsungs. My 970 Evo NVMe is running my system. It's the latest revision (2B2QEXM7) and is...

Thanks @P1LGRIM I know it’s a long shot but maybe there’s someone in the same situation.

Anyone please?

Hello guys, I’m about to build my new hackintosh, thing is, I use Logic Pro 9 (can’t use X for now because of hardware, etc) but it seems to no longer work on High Sierra and above. My setup will be Gigabye z390 Designare + i9 9900k + Saphire RX580 4GB OC. Can I even install Sierra with...

Considering getting the 512gb NVMe version instead, for that extra 30% write speed. It never ends ‍o_O