Samsung 850 EVO & Mac Pro 4,1 - SATA II? TRIM or NOT?

[balan]

What you mean with “manually TRIM”?, and what was meaning W1SS by saying “give it time to trimming”?, thx to all for your quick help
[doublepost=1539073900][/doublepost]

AFAIK, that 840 Evo problem only affect read speed on old files (more than 3 months old), but not write speed. So, I don't think his problem is the 840 Evo's problem.

Also that issue was fixed with the latest firmware few years back. At this this is true on my 840 Evo.



TBH, I really don't know how this SSD perform in Mojave. I upgraded my cMP's boot drive to a 2TB MX500. And let the 1TB 840 Evo work inside my Hackintosh. Since it's a Windows gaming drive now, can't test its Mojave performance.

However, if TRIM is disabled, I won't be too surprised you only get 40-80MB/s write speed. That's pretty much a 840 Evo can do if all cells are full.

If you want the write speed back, you have to activate TRIM. AND manually TRIM the SSD. AND keep the SSD have at least 20% free space.

What you mean with “manually TRIM”?, and what was meaning W1SS by saying “give it time to trimming”?, thx to all for your quick help

ohh and is totally clean, i erased all SSD because i thought the bad performance was because of 70% used, so i made a clean Mojave Install but really bad performance

 

[h9826790]

What you mean with “manually TRIM”?, and what was meaning W1SS by saying “give it time to trimming”?, thx to all for your quick help

ohh and is totally clean, i erased all SSD because i thought the bad performance was because of 70% used, so i made a clean Mojave Install but really bad performance

Erase the SSD without TRIM will not make any difference (unless you perform a secure erase, but this is way beyond what you really need to do).

And even though you secure erase the SSD. It will only give you the write speed back initially, after all cells once are wrote once. The speed will drop to 40-80MB/s again.

If it's clean now, no need to erase / format it again. You can simply boot to recovery partition and run disk aid. This should manually TRIM the whole SSD.

Anyway, if he can fix the write speed issue, I think you also can.

https://forums.macrumors.com/thread...aphics-card-help.2127709/page-2#post-26270860

 

[balan]

Erase the SSD without TRIM will not make any difference (unless you perform a secure erase, but this is way beyond what you really need to do).

And even though you secure erase the SSD. It will only give you the write speed back initially, after all cells once are wrote once. The speed will drop to 40-80MB/s again.

If it's clean now, no need to erase / format it again. You can simply boot to recovery partition and run disk aid. This should manually TRIM the whole SSD.

Anyway, if he can fix the write speed issue, I think you also can.

https://forums.macrumors.com/thread...aphics-card-help.2127709/page-2#post-26270860

So should I:

1.- Erase
2.- From USB boot the installation app and partition on APFS
3.- click en “first aid” (this would enable TRIM manually)
4.- install MacOS
5.- apple logo->about this Mac->system report->check SATA and TRIM should be YES

I’m right?

 

[h9826790]

So should I:

1.- Erase
2.- From USB boot the installation app and partition on APFS
3.- click en “first aid” (this would enable TRIM manually)
4.- install MacOS
5.- apple logo->about this Mac->system report->check SATA and TRIM should be YES

I’m right?

1) No need, but of course you can erase the whole drive if you want to make a clean OS installation.

2) Not necessary, but nothing wrong to boot from a USB installer

3) "First aid" is NOT for activating TRIM, but will force the SSD to clear up the "free" cells.

4) No related (for performance restoration), but of course you can do that

5) You should check this AFTER running the following command in terminal

sudo trimforce enable

 

[balan]

1) No need, but of course you can erase the whole drive if you want to make a clean OS installation.

2) Not necessary, but nothing wrong to boot from a USB installer

3) "First aid" is NOT for activating TRIM, but will force the SSD to clear up the "free" cells.

4) No related (for performance restoration), but of course you can do that

5) You should check this AFTER running the following command in terminal

sudo trimforce enable

So, in the end, just must write on terminal

Sudo trimforce enable

Restart the OS and that would be enough?, nothing else to do?

Because I was a little confused when some other guy said “you must wait for trim take effect” or give it time, something like that :S

 

[h9826790]

So, in the end, just must write on terminal

Sudo trimforce enable

Restart the OS and that would be enough?, nothing else to do?

Because I was a little confused when some other guy said “you must wait for trim take effect” or give it time, something like that :S

Activate TRIM just like "you hire a person to clean up your home". After you hire him (her), you still need to give time for him (her) to work.

TRIM is just a function to tell the SSD controller which cells can be clean up safely. So, after you activate it, nothing will happen until the OS pass this info to the SSD controller, and the controller really clean up the cells.

Run "disk aid" in the recovery partition will actually force the OS to pass this info to the controller, and ask the controller to clean to the cells now. This is what we call it "manually TRIM".

In general, the whole process is fully automatic and no users involvement required.

 

[balan]

Activate TRIM just like "you hire a person to clean up your home". After you hire him (her), you still need to give time for him (her) to work.

TRIM is just a function to tell the SSD controller which cells can be clean up safely. So, after you activate it, nothing will happen until the OS pass this info to the SSD controller, and the controller really clean up the cells.

Run "disk aid" in the recovery partition will actually force the OS to pass this info to the controller, and ask the controller to clean to the cells now. This is what we call it "manually TRIM".

In general, the whole process is fully automatic and no users involvement required.

Well... actually done, amazing performance on read and write speed... but still getting the beachball... this doesn’t happen with my Corsair SSD 960GB...

What would be doing slow my Mac?

If I change the SSD right now for the Corsair 960GB will not get the beachball I think I’ll give it some time, in some hours I’ll tell to you the results, but the only fact is “change the Corsair Ssd and then no beachball if go back to Evo 840 get beachball”

 

[h9826790]

Well... actually done, amazing performance on read and write speed... but still getting the beachball... this doesn’t happen with my Corsair SSD 960GB...

What would be doing slow my Mac?

If I change the SSD right now for the Corsair 960GB will not get the beachball I think I’ll give it some time, in some hours I’ll tell to you the results, but the only fact is “change the Corsair Ssd and then no beachball if go back to Evo 840 get beachball”

How you "change" to another SSD? If your Corsair is not a clone of the 840 Evo, there is no way to tell if it's software issue or hardware issue.

 

[balan]

How you "change" to another SSD? If your Corsair is not a clone of the 840 Evo, there is no way to tell if it's software issue or hardware issue.

But on both I made same clean Mojave installation

And the Corsair works perfect, never beachball

On 840 EVO beachball appears even on the MacOS preferences section during the installation

 

[h9826790]

But on both I made same clean Mojave installation

And the Corsair works perfect, never beachball

On 840 EVO beachball appears even on the MacOS preferences section during the installation

Then use the Corsair, and leave the 840 Evo as backup / spare / scratch drive, etc (if it won't beach ball the whole system)

Did you check the SMART status of you SSD? If you never run it with TRIM enabled, the SSD's life span can be burned much quicker.

 

[balan]

Then use the Corsair, and leave the 840 Evo as backup / spare / scratch drive, etc (if it won't beach ball the whole system)

Did you check the SMART status of you SSD? If you never run it with TRIM enabled, the SSD's life span can be burned much quicker.

Has 2750 hours of use and just 7.5 TB wrote (since started to show the beachball and make impossible to use it) I just known about I HAD to ENABLE TRIM until I had the beachball problem.

But on SMART says is 100% OK all healthy

And if I use the Evo 840 on windows it runs AMAZING and works perfectly, and for windows, a plus is the Samsung Magician Optimizer utility, on windows always says to me Write is 533MB/s and read 559 MB/s

But before installing on it windows (3 days ago) for the very first time when I got that write/read speeds, is a fact that I had the 40Mb/s write and 300 Mb/s read, but after updating the firmware to last version worked AMAZING and got the correct performance, thought that would mean on Mac would happen the but sadly didn’t and have the trouble until now

I’ll report the situation later 1 or 2 days of regular use with the 840 EVO with TRIM enabled

Just to have a place where people could check if someone else has this problem

Thanks a lot for your help and explanations

U R an amazing community