970 EVO Plus: Phoenix controller (S4LR020): NVMe
3D TLC (96-layer)
Available in 250GB, 500GB, and 1TB
PCIe 3.0 x4
Speeds: up to 3,500 MB/s read, up to 3,300 MB/s write
Datasheet
Compatibility status:
Is anybody booting from a 970 EVO Plus? I'm trying to find a decent deal on a 970 EVO and having a tough time.
Have you tried microcenter? They have 2 locations in your area.
This card uses the same PCIe switch as IOCrest/SYBA, it's a 8 lanes one and tops at little less than 3200MB/s (combined for the 4 blades).New 4 NVMe ASMedia 2824 riser card that I saw mentioned on a Mac Pro facebook group:
https://www.xt-xinte.com/XT-XINTE-S...upports-2242-2260-2280-and-22110-p563664.html
Anyone with any experience?
I can't say about 970 EVO Plus drives, but I have the exact same config as @crjackson2134 to the letter and don't have any problems. 970 Pro drives works fine for a lot of people here. This could be caused by a defective blade or maybe even caused by some kext incompatibility.I noticed some people are saying they are experiencing boot problems with 970 and 970 Plus drives in this thread. Should we update the compatibility status for those drives?
Hoping 141.0.0.0.0 MacPro firmware may help to fix these lingering issues.
Sorry to kill your hopes, but @crjackson2134 Mac Pro have 141.0.0.0.0 since day one.
It's the EVO Pulse that is the one not working in macos, not the plain EVO model. I, too, have an 970 EVO in my MP5,1 that's working like a champ.I'm personally using 970 EVO and do not believe the issue is widespread enough at the moment to broadly "not recommend" using them. Reporting firmware version on the blade when experiencing any issues would be helpful. My 970 EVO 1TB is 2B2QEXE7 with PX1.
Hoping 141.0.0.0.0 MacPro firmware may help to fix these lingering issues.
It's the EVO Pulse that is the one not working in macos, not the plain EVO model. I, too, have an 970 EVO in my MP5,1 that's working like a champ.
People, we are holding it wrong.That's not correct. The issue on client's machine was with EVO 970 (not PLUS model) and was with what I originally thought were two identical 500GB blades, but they had different FW numbers. Unfortunately, I did not write them down or take pictures of the blades.
The issue they were experiencing was/is nearly identical to what @crjackson2134 was/is experiencing and describing. Believe that machine is with a 970 PRO model.
Yes, it's the easiest way to do a clean install and then do the troubleshooting.Hi!
I just received my 5,1 with the 140.0.0.0 firmware and High Sierra.
I'm trying to reinstall High Sierra, but I can't boot to recovery: after booting while holding CMD+R I get a prohibited sign and it just proceeds to boot to High Sierra.
The boot drive is an NVME SSD, a Toshiba THNSF5256GPUK. There's also a 750 GB HDD in a bay.
The recovery partition on the SSD is present, cca. 500 megs, so that should be fine.
Should I create a USB High Sierra boot key?
Thank you!
Recovery works perfectly with NVMe/AHCI PCIe blades, no difference whatsoever between NVMe and SATA drives connected to the south bridge of Mac Pro.Thanks! There's nothing wrong with the machine that I can see, apart from the inability to boot to recovery, but I guess that's the NVME SSD.
I'll give the USB key boot a go.
Maybe the seller did some weird install. You should wipe your drives and do a clean install.Weird. So the prohibited sign is unusual I guess. I hope it's not a hardware fault.
I've seen a few hacked 4,1 machines present the prohibited sign. Many of these machines also incorrectly ID as iMac/iMacPro vs MacPro5,1 (or MacPro4,1). If you don't know the machine history, at least start by looking up the numbers on the back of the machine to see how it originated and with what configuration.