Contribute
Register

Samsung 970 EVO PLUS M.2 NVMe SSD is ok

Status
Not open for further replies.
Just wanna confirmed that I've successfully installed Mojave with a 970 EVO Plus. Here's my simple guide.

Sounds great, how long have you been booted using the drive in the NVMe slot? Have you been able to do any sustained writes to the drive? duplicating a big movie, for example?

It seems to be mainly under heavy write loads that the crashes happen!
 
Just wanna confirmed that I've successfully installed Mojave with a 970evo Plus. Here's my simple guide.

1. Copy via image with CCC (Carbon Copy Cloner) any fresh installed macOS Mojave from a real Mac;
2. Use a USB3.1 NVMe adapter and restore it with CCC;
3. Run it 1st time externally via USB3.1 NVMe adapter and setup the EFI;
3. After that, install the 970 EVO Plus internally to the M.2 slot; and
4. Start your system and enjoy.

p/s - Sorry for my bad English.

Did nearly the same, but had no knowledge about the problems with the 970 EVO Plus. Copied a running system via CCC to the 970 connected via USB3.1-NVMe-adapter and put it in my iMac 2017 - system is booting but poor write performance and repeated kernel panics with "NVMe..." messages. :mad::mad::mad:
 
Hi everyone, I would like to update my ssd with a Samsung EVO ..., but I didn't understand which model works best for me. I have a Mac Pro (late 2013) and Mojave 10.14.4. Which do you advise me to install 970 EVO Plus or 970 Evo Pro? What steps to install?

Thank you all
 
Hi everyone, I would like to update my ssd with a Samsung EVO ..., but I didn't understand which model works best for me. I have a Mac Pro (late 2013) and Mojave 10.14.4. Which do you advise me to install 970 EVO Plus or 970 Evo Pro? What steps to install?

Thank you all
EVO Plus does not work with macOS.
 
The main problem with NVMe drives is that they must support 4K sectors to work natively on macOS.
As @RehabMan quoted on his Repository:
Special note regarding 4k block size capable drives
It may be that your drive is capable of being driven with a 4k block size instead of 512 bytes. If the drive is in 4k mode, you may be able to use the IONVMeFamily.kext without patches.
Read here: https://www.insanelymac.com/forum/t...erra-is-ready/?do=findComment&comment=2377304 A partial list of drives supporting 4k native:
  • Toshiba XG3 (Controller: TC58NCP070GSB)
  • OCZ RD400 (Controller: TC58NCP070GSB)
  • Intel SSD750 (Have Performance/Speed Issues)
  • WD Black (Controller: Marvell 88SS1093)
Read his repository: https://github.com/RehabMan/patch-nvme
There is a method on Linux to check if a NVMe drive supports 4K block size / sectors.
After using the tool if it does list 4K sector below, simply switch to that with the tool and NVMe issues with macOS permanently solved.
 
The main problem with NVME drives is that they must support 4K sectors to work natively on macOS.
As @RehabMan quoted on his Repository:

Read his repository: https://github.com/RehabMan/patch-nvme
There is a method on linux to check if a nvme drive supports 4K block size / sectors.
After using the tool if it does list 4K sector below, simply switch to that with the tool and nvme issues with macOS permanently solved.

Native support for 512b block size was added to macOS a long time ago...
 
Native support for 512b block size was added to macOS a long time ago...
I know that long time ago but that wasn't my point, I guess I wasn't clear:
NVMe drives that have trouble on macOS, if they happen to support 4K sectors, change that drive to 4K sectors and you shouldn't have issues anymore, 4K sectors are natively supported and cause no issues, while some NVMe drives have problems on 512GB, and they unfortunately don't support 4K, there's no known fix for them.

So someone should try to boot a Samsung 970 Plus model on Linux to see if it does support 4K sectors and change to that and see if the problem gets solved.
 
Samsung has released new firmware for 970 EVO Plus. Works flawlessly on Macs and Hackintosh!
Screenshot_2019-05-22_at_7_30_03_AM.png

Screenshot 2019-05-22 at 7.30.25 AM.png
 
Status
Not open for further replies.
Back
Top