Contribute
Register

<< Solved >> Do the Samsung 970 EVO Plus drives work ? New Firmware Available 2B2QEXM7

Joined
Jul 30, 2018
Messages
218
Motherboard
GA-Z370N wifi
CPU
i7-8700K
Graphics
HD 630 - RX 570
Mac
  1. MacBook Pro
Mobile Phone
  1. iOS
@BlvckBytes
Please give link to your post about long delay.
 
Joined
Mar 8, 2017
Messages
769
Motherboard
Dell XPS 9700 4K (OpenCore)
CPU
i7-10875H
Graphics
UHD 630, 3840x2400
Mobile Phone
  1. Android
Joined
Aug 4, 2018
Messages
15
Motherboard
Gigabyte Z390 AORUS PRO
CPU
i7-9700K
Graphics
RX 580
Mac
  1. MacBook Pro
Mobile Phone
  1. Android
@BlvckBytes I'm also experiencing long trim delays on boot after upgrading to Monterey (7 minutes boot delay). I don't have any *Brcm kexts, I only use BlueToolFixup kext. I also tried with and without nvme driver and kext, but I'm getting the same issue.

My current 970 evo+ firmware version is 2B2QEXM7, Samsung released 4B2QEXM7, I'm using that disk as my OS disk, but when I boot into Samsung SSD Firmware Update Utility (Ver. 3.1), it scans for disks and it says "No supported SSD detected for Firmware Update" Screen photo:

IMG_20211214_134550780.jpg

I tried every possible way I can think of to make the bootable usb, so I don't think that the issue is there, the only thing that I can think of is that maybe the update utility requires the 970 evo+ to be formatted in ntfs or fat format, mine is in APFS, and I really don't want to format my primary disk and then re-installing everything it is much more painful than waiting 7 minutes on each boot.

Additionally, I'm not sure if 4B2QEXM7 fixes the slow boot issue because of trimming, maybe someone who has the issue and then updated the firmware to that version can confirm the fix?

Thanks!
 
Joined
Mar 8, 2017
Messages
769
Motherboard
Dell XPS 9700 4K (OpenCore)
CPU
i7-10875H
Graphics
UHD 630, 3840x2400
Mobile Phone
  1. Android
@panosru

Hey there and sorry for my late response! I just downloaded smartmontools using homebrew, and then ran sudo smartctl --all /dev/disk<your-id>, to quickly check what firmware version I'm running. Funny enough, I'm on 2B2QEXM7 too, running Monterey.

If you don't mind, attach your full EFI folder, just so I can check whether or not there are any issues present which I can spot.
 
Joined
Aug 4, 2018
Messages
15
Motherboard
Gigabyte Z390 AORUS PRO
CPU
i7-9700K
Graphics
RX 580
Mac
  1. MacBook Pro
Mobile Phone
  1. Android
Hey @BlvckBytes, I'm attaching here my EFI folder, I removed the Apple and Boot folder, also the OC/Resources since they are not needed and to squeeze down the zip size.

I don't believe that I have an issue with my EFI though, but a second pair of eyes won't hurt! If you spot something unusual let me know, it might be on purpose for my system or I might miss something! I'm on OC v0.7.6 currently but I'll be upgrading to v0.7.7 this week.

From what I hear, the latest Samsung firmware won't solve the trim issue, but the response wasn't clear enough, therefore I'm waiting for someone to respond to that person here

Thanks!
 

Attachments

  • EFI.zip
    2.6 MB · Views: 13
Joined
Mar 8, 2017
Messages
769
Motherboard
Dell XPS 9700 4K (OpenCore)
CPU
i7-10875H
Graphics
UHD 630, 3840x2400
Mobile Phone
  1. Android
@panosru

Weird, I didn't see any difference between our configs, except that I have a trim-timeout of -1, which then again should be default, and should still yield slow boot times when trim doesn't work. You could just set it to like 500 and forget about it, although it's inefficient. But hey, better than long boot times, xD.

Also tried to boot the firmware update ISO, and my drive also doesn't get detected. After some research I found out that this seems to be a common problem that Samsung just doesn't go after fixing. What a joke.
 
Joined
Aug 4, 2018
Messages
15
Motherboard
Gigabyte Z390 AORUS PRO
CPU
i7-9700K
Graphics
RX 580
Mac
  1. MacBook Pro
Mobile Phone
  1. Android
@BlvckBytes yes indeed, I also had it to -1, I changed it to 4294967295 to allow trim to run, just in case it might fix the issue.

-1 stands for ~51.43 - 51.62 seconds, 999 stands for ~41.30 - 41.39 seconds and 4294967295 for ~1:45.62 - 1:46.87

Basically, -1 should be used in almost all cases. The issue here is that the trim-timeout is ignored. Check the following screenshot:

1639668996633.png


My second NVMe drive takes ~10 seconds to trim, but 970 Evo Plus takes ~384.5 seconds (that was with trim-time set to -1).

Samsung doesn't seem to be bothered with it and indeed, it's a joke of support.
 
Joined
Jan 15, 2022
Messages
1
Motherboard
A1565
CPU
i7
Graphics
MSI
Mac
  1. MacBook Air
  2. MacBook Pro
Mobile Phone
  1. iOS
Ok ; so basically it’d be better to get WD black SN750 to avoid issues?
or does the WD have its own problems? Is there a capacity limit ? 2TB ok ? I have a 2015 MacBook Air
 
Joined
Mar 8, 2017
Messages
769
Motherboard
Dell XPS 9700 4K (OpenCore)
CPU
i7-10875H
Graphics
UHD 630, 3840x2400
Mobile Phone
  1. Android
@deepblonde

I have no issues with the SN750, and 2TB should work just fine.
 
Joined
Jun 5, 2021
Messages
37
Motherboard
Gigabyte Z490 Gaming X
CPU
i7-10700
Graphics
RX 580
I have a Samsung drive issue running Big Sur/Catalina. One of my EVO Plus NVMe (Catalina) stops showing purgeable data (Get Info window) it is about 40% full and dose not reclaim space back when files are deleted (only when large amount is deleted and then not all the space is reclaimed).

On my main Samsung EVO plus (Big Sur) this is not happening. Both are APFS.

Any advice? Should I format it differently. I primarily use it for data.

Update: well this seems to be random. I had just performed a security update for Catalina, and now the disk info has updated to what it should be.
 
Last edited:
Top