Mac Pro 5,1 - High Sierra - 970 EVO Plus NVMe on 4x PCIe adapter - getting periodic kernel panic “NV

[jdub9]

Hi. I’ve been trying to upgrade the storage and RAM in my Mac Pro 5,1 (Mid 2010).


After installing a 970 EVO Plus 1TB NVMe blade (https://www.samsung.com/semiconductor/minisite/ssd/product/consumer/970evoplus/) in a Micro Connectors Low-Profile M.2 NVMe PCIe x4 adapter (http://microconnectors.com/micro-co...-ssd-to-pcie-x4-adapter-with-heat-sink-for-1u )

I am periodically getting the following kernel panic:


panic(cpu 0 caller 0xffffff7f9d993e2b): nvme: " NVMe: Command timed-out and request found in the completion queue \n”@/BuildRoot/Library/Caches/com.apple.xbs/Sources/IONVMeFamily/IONVMeFamily-356.71.1/IONVMeController.cpp:5184


I can trigger this 100% of the time by running Blackmagic Disk Speed Test on the 970 NVMe APFS Volume - during which the Write test will start to ramp up the speedometer (to approx 600-750) and then hang and 15-30 seconds later the Mac Pro reboots.


Periodically the panic will just occur spontaneously without any user interaction with the NVMe volume.

I’ve also copied 100GB of directories/files to/from/within the APFS Volume on the 970 NVMe and sometimes that works ok and sometimes it hits the same stall/timeout/panic.


When running AJA System Test Lite, the write test will sometimes (but not always) stall for 1-2 seconds and then proceed to complete - leaving the write rate in the 700 range rather than 1500 - but it has never done a stall/panic as of yet.


Notes:

* the cMP is quite bare-bones right now (HD 5780 / 1x SATA SSD in HDD tray / 970 NVMe blade in PCIe 4x adapter card / 48GB RAM)

• ROM version is currently 140.0.0.0.0 - I started to update to Mojave and did the corresponding ROM update - but then decided I’d rather have access to the boot screen/options since the HD 5780 gives me sufficient display resolution - so I’m booting High Sierra 10.13.6 from a SSD in a HDD tray right now (eventually will put it in a PCIe/SSD-SATA card)
• There is NO heatsink installed on the 970 NVMe blade - but it is barely warm anyways.
• Panic issue occurs with either the HD 5780 card installed or a GT120 card installed
• Panic issue occurs with either the original 4x 4GB RAM sticks or with the upgraded 3x 16GB RAM sticks in slots 1/2/3 (and I ran memtest overnight with the 16GB sticks without any errors)
• I’ve done a reinstall of High Sierra and also reset NVRAM/SMC multiple times
• I moved the 970 NVMe stick/PCIe-card over to a Win7 box - deleted the partitions (diskpart) - created an NTFS volume - ran Samsung Magician which says the 970 firmware is the Latest - ran the Samsung Magician performance test with no issues - ran the “winsat disk -drive <drive-letter> ” disk performance test a few times with no issues - copied 50GB-100GB of data to/from/within the NVMe volume with no issues - also tried to run the Win version of Blackmagic, but without any actually Blackmagic cards install was unable to select a target drive
• I also tried another Micro Connectors NVME PCIe x4 adapter and the issue still occurs (http://microconnectors.com/m-2-nvme-80mm-ssd-pcie-x4-adapter-with-covered-heat-sink/)
• I do have a Lycom DT-120 M.2 PCIe card arriving tomorrow and will test with that (though I doubt that will resolve things given that it looks to be just a pass-through between the NVMe blade and the MB PCIe x4 slot)

Does anyone have any suggestions on next steps?


Thanks,

Jim



Anonymous UUID: 0F0C8485-1791-E425-4AEA-25C524345D04


Fri Mar 8 09:06:49 2019


*** Panic Report ***

panic(cpu 0 caller 0xffffff7f9d993e2b): nvme: " NVMe: Command timed-out and request found in the completion queue \n"@/BuildRoot/Library/Caches/com.apple.xbs/Sources/IONVMeFamily/IONVMeFamily-356.71.1/IONVMeController.cpp:5184

Backtrace (CPU 0), Frame : Return Address

0xffffff85820cbb60 : 0xffffff801b06e1c6

0xffffff85820cbbb0 : 0xffffff801b196a74

0xffffff85820cbbf0 : 0xffffff801b188d44

0xffffff85820cbc60 : 0xffffff801b0201e0

0xffffff85820cbc80 : 0xffffff801b06dc3c

0xffffff85820cbdb0 : 0xffffff801b06d9fc

0xffffff85820cbe10 : 0xffffff7f9d993e2b

0xffffff85820cbe30 : 0xffffff801b69f7ac

0xffffff85820cbea0 : 0xffffff801b69f6d6

0xffffff85820cbed0 : 0xffffff801b0a7624

0xffffff85820cbf40 : 0xffffff801b0a7185

0xffffff85820cbfa0 : 0xffffff801b01f557

Kernel Extensions in backtrace:

com.apple.iokit.IONVMeFamily(2.1)[1170C79B-9E09-3CD3-970B-C419EBF9037F]@0xffffff7f9d97f000->0xffffff7f9d9befff

dependency: com.apple.driver.AppleMobileFileIntegrity(1.0.5)[F314E6BA-45C5-3D8B-A3BF-C4CAE13DDADC]@0xffffff7f9bfaf000

dependency: com.apple.iokit.IOPCIFamily(2.9)[D91E9813-9717-31B8-BFE5-2F3A00F375F3]@0xffffff7f9b894000

dependency: com.apple.driver.AppleEFINVRAM(2.1)[F35A52E2-CF80-3BA9-92B5-25EFE216094F]@0xffffff7f9be32000

dependency: com.apple.iokit.IOStorageFamily(2.1)[F27A8A2A-6662-3608-83BD-415037509E01]@0xffffff7f9bb7c000

dependency: com.apple.iokit.IOReportFamily(31)[D2F2FBDF-4EE4-38BA-99F5-B699F886F413]@0xffffff7f9c377000


BSD process name corresponding to current thread: kernel_task


Mac OS version:

17G5019


Kernel version:

Darwin Kernel Version 17.7.0: Thu Dec 20 21:47:19 PST 2018; root:xnu-4570.71.22~1/RELEASE_X86_64

Kernel UUID: 4A5298BF-709E-37DF-B7F0-4298065CC266

Kernel slide: 0x000000001ae00000

Kernel text base: 0xffffff801b000000

__HIB text base: 0xffffff801af00000

System model name: MacPro5,1 (Mac-F221BEC8)


System uptime in nanoseconds: 103223670034

last loaded kext at 13248982798: com.apple.driver.AudioAUUC 1.70 (addr 0xffffff7f9ddf3000, size 32768)

loaded kexts:

com.apple.driver.AudioAUUC 1.70

com.apple.driver.AppleBluetoothMultitouch 92

com.apple.driver.AppleTyMCEDriver 1.0.3d2

com.apple.driver.AGPM 110.23.37

com.apple.filesystems.autofs 3.0

com.apple.driver.AppleMikeyHIDDriver 131

com.apple.driver.AppleMikeyDriver 281.52

com.apple.driver.AppleGraphicsDevicePolicy 3.20.14

com.apple.driver.AppleHDAHardwareConfigDriver 281.52

com.apple.AGDCPluginDisplayMetrics 3.20.0

com.apple.driver.AppleHDA 281.52

com.apple.driver.AppleUpstreamUserClient 3.6.5

com.apple.driver.AppleMCCSControl 1.5.5

com.apple.driver.AppleHV 1

com.apple.kext.AMDLegacyFramebuffer 1.6.8

com.apple.iokit.IOUserEthernet 1.0.1

com.apple.iokit.IOBluetoothSerialManager 6.0.7f12

com.apple.kext.AMDRadeonX3000 1.6.8

com.apple.driver.pmtelemetry 1

com.apple.Dont_Steal_Mac_OS_X 7.0.0

com.apple.kext.AMD5000Controller 1.6.8

com.apple.driver.AppleLPC 3.1

com.apple.driver.AppleOSXWatchdog 1

com.apple.driver.ACPI_SMC_PlatformPlugin 1.0.0

com.apple.driver.AppleFIVRDriver 4.1.0

com.apple.driver.AppleIntelSlowAdaptiveClocking 4.0.0

com.apple.iokit.IOBluetoothUSBDFU 6.0.7f12

com.apple.iokit.SCSITaskUserClient 404.30.2

com.apple.driver.AppleFileSystemDriver 3.0.1

com.apple.filesystems.hfs.kext 407.50.6

com.apple.AppleFSCompression.AppleFSCompressionTypeDataless 1.0.0d1

com.apple.BootCache 40

com.apple.AppleFSCompression.AppleFSCompressionTypeZlib 1.0.0

com.apple.AppleSystemPolicy 1.0

com.apple.driver.AppleFWOHCI 5.5.9

com.apple.filesystems.apfs 748.51.0

com.apple.driver.Intel82574LEthernet 2.7.2

com.apple.driver.AirPort.Brcm4331 800.21.30

com.apple.driver.AppleAHCIPort 329.50.2

com.apple.driver.AppleRTC 2.0

com.apple.driver.AppleHPET 1.8

com.apple.driver.AppleACPIButtons 6.1

com.apple.driver.AppleSMBIOS 2.1

com.apple.driver.AppleACPIEC 6.1

com.apple.driver.AppleAPIC 1.7

com.apple.driver.AppleIntelCPUPowerManagementClient 220.50.1

com.apple.nke.applicationfirewall 183

com.apple.security.TMSafetyNet 8

com.apple.security.quarantine 3

com.apple.driver.AppleIntelCPUPowerManagement 220.50.1

com.apple.driver.IOBluetoothHIDDriver 6.0.7f12

com.apple.driver.AppleMultitouchDriver 1614.1

com.apple.driver.AppleInputDeviceSupport 1614.11

com.apple.kext.triggers 1.0

com.apple.driver.AppleGraphicsControl 3.20.14

com.apple.driver.DspFuncLib 281.52

com.apple.kext.OSvKernDSPLib 526

com.apple.iokit.IOAVBFamily 683.1

com.apple.plugin.IOgPTPPlugin 680.15

com.apple.iokit.IOEthernetAVBController 1.1.0

com.apple.driver.AppleSSE 1.0

com.apple.iokit.IONDRVSupport 519.21

com.apple.iokit.IOSerialFamily 11

com.apple.iokit.IOAcceleratorFamily2 378.26

com.apple.iokit.IOSurface 211.15

com.apple.kext.AMDSupport 1.6.8

com.apple.driver.AppleSMBusController 1.0.18d1

com.apple.driver.AppleHDAController 281.52

com.apple.iokit.IOHDAFamily 281.52

com.apple.iokit.IOAudioFamily 206.5

com.apple.vecLib.kext 1.2.0

com.apple.driver.AppleSMBusPCI 1.0.14d1

com.apple.AppleGPUWrangler 3.20.0

com.apple.AppleGraphicsDeviceControl 3.20.14

com.apple.kext.AMDLegacySupport 1.6.8

com.apple.iokit.IOGraphicsFamily 519.21

com.apple.iokit.IOFireWireIP 2.2.9

com.apple.driver.IOPlatformPluginLegacy 1.0.0

com.apple.driver.IOPlatformPluginFamily 6.0.0d8

com.apple.iokit.IOSlowAdaptiveClockingFamily 1.0.0

com.apple.iokit.IOAHCIBlockStorage 301.40.2

com.apple.iokit.BroadcomBluetoothHostControllerUSBTransport 6.0.7f12

com.apple.iokit.IOBluetoothHostControllerUSBTransport 6.0.7f12

com.apple.iokit.IOBluetoothHostControllerTransport 6.0.7f12

com.apple.iokit.IOBluetoothFamily 6.0.7f12

com.apple.driver.AppleHIDKeyboard 205.1

com.apple.driver.usb.IOUSBHostHIDDevice 1.2

com.apple.driver.usb.cdc 5.0.0

com.apple.driver.usb.networking 5.0.0

com.apple.driver.usb.AppleUSBHostCompositeDevice 1.2

com.apple.driver.usb.AppleUSBHub 1.2

com.apple.iokit.IOSCSIMultimediaCommandsDevice 404.30.2

com.apple.iokit.IOBDStorageFamily 1.8

com.apple.iokit.IODVDStorageFamily 1.8

com.apple.iokit.IOCDStorageFamily 1.8

com.apple.filesystems.hfs.encodings.kext 1

com.apple.iokit.IOAHCISerialATAPI 267.50.1

com.apple.iokit.IOFireWireFamily 4.7.2

com.apple.driver.AppleXsanScheme 3

com.apple.iokit.IO80211Family 1200.12.2

com.apple.driver.corecapture 1.0.4

com.apple.driver.AppleUSBMergeNub 900.4.1

com.apple.iokit.IOAHCIFamily 288

com.apple.driver.usb.AppleUSBEHCIPCI 1.2

com.apple.driver.usb.AppleUSBUHCIPCI 1.2

com.apple.driver.usb.AppleUSBUHCI 1.2

com.apple.driver.usb.AppleUSBEHCI 1.2

com.apple.iokit.IONVMeFamily 2.1.0

com.apple.driver.usb.AppleUSBHostPacketFilter 1.0

com.apple.iokit.IOUSBFamily 900.4.1

com.apple.driver.AppleUSBHostMergeProperties 1.2

com.apple.driver.AppleEFINVRAM 2.1

com.apple.driver.AppleEFIRuntime 2.1

com.apple.iokit.IOSMBusFamily 1.1

com.apple.iokit.IOHIDFamily 2.0.0

com.apple.security.sandbox 300.0

com.apple.kext.AppleMatch 1.0.0d1

com.apple.driver.DiskImages 480.60.2

com.apple.driver.AppleFDEKeyStore 28.30

com.apple.driver.AppleEffaceableStorage 1.0

com.apple.driver.AppleKeyStore 2

com.apple.driver.AppleUSBTDM 439.70.3

com.apple.driver.AppleMobileFileIntegrity 1.0.5

com.apple.iokit.IOUSBMassStorageDriver 140.70.2

com.apple.iokit.IOSCSIBlockCommandsDevice 404.30.2

com.apple.iokit.IOSCSIArchitectureModelFamily 404.30.2

com.apple.iokit.IOStorageFamily 2.1

com.apple.driver.AppleCredentialManager 1.0

com.apple.driver.KernelRelayHost 1

com.apple.iokit.IOUSBHostFamily 1.2

com.apple.driver.usb.AppleUSBCommon 1.0

com.apple.driver.AppleBusPowerController 1.0

com.apple.driver.AppleSEPManager 1.0.1

com.apple.driver.IOSlaveProcessor 1

com.apple.iokit.IOReportFamily 31

com.apple.iokit.IOTimeSyncFamily 680.15

com.apple.iokit.IONetworkingFamily 3.4

com.apple.driver.AppleACPIPlatform 6.1

com.apple.driver.AppleSMC 3.1.9

com.apple.iokit.IOPCIFamily 2.9

com.apple.iokit.IOACPIFamily 1.4

com.apple.kec.pthread 1

com.apple.kec.Libm 1

com.apple.kec.corecrypto 1.0


EOF

Model: MacPro5,1, BootROM 140.0.0.0.0, 6 processors, 6-Core Intel Xeon, 3.33 GHz, 48 GB, SMC 1.39f11

Graphics: ATI Radeon HD 5870, ATI Radeon HD 5870, PCIe

Memory Module: DIMM 1, 16 GB, DDR3 ECC, 1333 MHz, 0x80CE, 0x4D33393342324737304248302D5948392020

Memory Module: DIMM 2, 16 GB, DDR3 ECC, 1333 MHz, 0x80CE, 0x4D33393342324737304248302D5948392020

Memory Module: DIMM 3, 16 GB, DDR3 ECC, 1333 MHz, 0x80CE, 0x4D33393342324737304248302D5948392020

AirPort: spairport_wireless_card_type_airport_extreme (0x14E4, 0x8E), Broadcom BCM43xx 1.0 (5.106.98.102.30)

Bluetooth: Version 6.0.7f12, 3 services, 27 devices, 1 incoming serial ports

Network Service: Ethernet 2, Ethernet, en1

PCI Card: pci144d,a808, NVM Express Controller, Slot-2

PCI Card: ATI Radeon HD 5870, Display Controller, Slot-1

Serial ATA Device: HL-DT-ST DVD-RW GH61N

Serial ATA Device: Samsung SSD 860 EVO 500GB, 500.11 GB

USB Device: USB Bus

USB Device: USB Bus

USB Device: BRCM2046 Hub

USB Device: Bluetooth USB Host Controller

USB Device: USB Bus

USB Device: USB Bus

USB Device: USB Bus

USB Device: USB Bus

USB Device: USB 2.0 Bus

USB Device: USB 2.0 Bus

USB Device: Keyboard Hub

USB Device: Apple Keyboard

FireWire Device: built-in_hub, Up to 800 Mb/sec

Thunderbolt Bus:




EtreCheck version: 5.2 (5029)

Report generated: 2019-03-08 09:17:19

Download EtreCheck from…

Runtime: 1:57

Performance: Excellent

Sandbox: Enabled

Full drive access: Disabled


Problem: Computer is restarting

Description:

panic(cpu 0 caller 0xffffff7f8bd93e2b): nvme: &quot; NVMe: Command tim

ed-out and request found in the completion queue \n&quot;@/BuildRoot/L

ibrary/Caches/com.apple.xbs/Sources/IONVMeFamily/IONVMeFamily-356.71.1

/IONVMeController.cpp:5184


Major Issues:

Anything that appears on this list needs immediate attention.


No Time Machine backup - Time Machine backup not found.


Minor Issues:

These issues do not need immediate attention but they may indicate future problems or opportunities for improvement.


Vintage hardware - This machine may be considered vintage.

32-bit Apps - This machine has 32-bits apps will not work after macOS 10.14 “Mojave”.

Limited drive access - More information may be available with Full Drive Access.


Hardware Information:

Mac Pro (2010 - 2012) - Vintage!

Mac Pro Model: MacPro5,1

1 3.33 GHz 6-Core Intel Xeon (Xeon(R)) CPU: 6-core

48 GB RAM - At maximum

DIMM 1 - 16 GB DDR3 ECC 1333 ok

DIMM 2 - 16 GB DDR3 ECC 1333 ok

DIMM 3 - 16 GB DDR3 ECC 1333 ok

DIMM 4 - Empty


Video Information:

ATI Radeon HD 5870 - VRAM: 1024 MB

V193W 1440 x 900


Drives:

disk0 - Samsung SSD 970 EVO Plus 1TB 1.00 TB (Solid State - TRIM: Yes)

External 5.0 GT/s x4 NVM Express

disk0s1 - EFI (MS-DOS FAT32) [EFI] 210 MB

disk0s2 [APFS Container] 1000.00 GB

disk1 [APFS Virtual drive] 1000.00 GB (Shared by 1 volumes)

disk1s1 - N*********S (APFS) (Shared - 1.90 GB used)


disk2 - Samsung SSD 860 EVO 500GB 500.11 GB (Solid State - TRIM: No)

Internal SATA 3 Gigabit Serial ATA

disk2s1 - EFI (MS-DOS FAT32) [EFI] 210 MB

disk2s2 [APFS Container] 499.90 GB

disk3 [APFS Virtual drive] 499.90 GB (Shared by 4 volumes)

disk3s1 - S**************B (APFS) (Shared - 15.38 GB used)

disk3s2 - Preboot (APFS) [APFS Preboot] (Shared)

disk3s3 - Recovery (APFS) [Recovery] (Shared)

disk3s4 - VM (APFS) [APFS VM] (Shared - 20 KB used)


Mounted Volumes:

disk1s1 - N*********S 1000.00 GB (997.89 GB free)

APFS

Mount point: /Volumes/N*********S

Owners enabled: No


disk3s1 - S**************B 499.90 GB (483.83 GB free)

APFS

Mount point: /


disk3s4 - VM [APFS VM] (Shared - 20 KB used)

APFS

Mount point: /private/var/vm


Network:

Interface en0: Ethernet 1

Interface en1: Ethernet 2

Interface fw0: FireWire

Interface en2: Wi-Fi

802.11 a/b/g/n

Interface en3: Bluetooth PAN


System Software:

macOS High Sierra 10.13.6 (17G5019)

Time since boot: Less than an hour


Notifications:

Notifications not available without Full Drive Access.


Security:

Gatekeeper: Enabled

System Integrity Protection: Enabled


32-bit Applications:

One 32-bit app


System Launch Agents:

[Not Loaded] 16 Apple tasks

[Loaded] 185 Apple tasks

[Running] 93 Apple tasks


System Launch Daemons:

[Not Loaded] 37 Apple tasks

[Loaded] 196 Apple tasks

[Running] 102 Apple tasks


User Login Items:

iTunesHelper.app (Apple - installed 2019-03-05)

(Application - /Applications/iTunes.app/Contents/MacOS/iTunesHelper.app)


Audio Plug-ins:

AppleTimeSyncAudioClock: 1.0 (Apple - installed 2019-03-05)

BluetoothAudioPlugIn: 6.0.7 (Apple - installed 2019-03-05)

AirPlay: 2.0 (Apple - installed 2019-03-05)

AppleAVBAudio: 683.1 (Apple - installed 2019-03-05)

BridgeAudioSP: 4.69.2 (Apple - installed 2019-03-05)

iSightAudio: 7.7.3 (Apple - installed 2019-03-05)


Time Machine:

Time Machine Not Configured!


Performance:

System Load: 2.41 (1 min ago) 0.86 (5 min ago) 0.33 (15 min ago)

Nominal I/O speed: 0.06 MB/s

File system: 26.66 seconds

Write speed: 261 MB/s

Read speed: 272 MB/s


CPU Usage Snapshot:

Type Overall

System 0 %

User 0 %

Idle 99 %


Top Processes Snapshot by CPU:

Process (count) CPU (Source - Location)

Other processes 3.90 % (?)

EtreCheck 3.51 % (App Store)

UserEventAgent 0.02 % (Apple)

SafariBookmarksSyncAgent 0.02 % (Apple)

Dock 0.02 % (Apple)


Top Processes Snapshot by Memory:

Process (count) RAM usage (Source - Location)

EtreCheck 419 MB (App Store)

Spotlight 48 MB (Apple)

NotificationCenter 46 MB (Apple)

Finder 44 MB (Apple)

loginwindow 44 MB (Apple)


Top Processes Snapshot by Network Use:

Process Input / Output (Source - Location)

mDNSResponder 15 KB / 10 KB (Apple)

cloudd 17 KB / 6 KB (Apple)

apsd 4 KB / 5 KB (Apple)

netbiosd 4 KB / 1 KB (Apple)

lsd 0 B / 0 B (Apple)


Virtual Memory Information:

Physical RAM: 48 GB


Free RAM: 43.12 GB

Used RAM: 3.09 GB

Cached files: 1.80 GB


Available RAM: 44.91 GB

Swap Used: 0 B


Software Installs (past 30 days):

Install Date Name (Version)

2019-03-05 Safari (12.0.3)

2019-03-05 iTunes (12.8.2)

2019-03-05 AJA System Test Lite (12.4.3)

2019-03-05 Display Menu (2.2.3)

2019-03-05 Disk Speed Test (3.2)

2019-03-05 XProtectPlistConfigData (2101)

2019-03-05 Gatekeeper Configuration Data (163)

2019-03-05 MRTConfigData (1.40)

2019-03-05 Security Update 2019-001 (10.13.6)

2019-03-08 EtreCheck (5.2)


Diagnostics Information (past 7 days):

Directory /Library/Logs/DiagnosticReports is not accessible.

Enable Full Drive Access to see more information.


End of report

 

[tsialex]

Install DriveDX and post the SMART details.

Seems the firmware of 970 EVO Plus is problematic with MP5,1s.

 

[handheldgames]

Install DriveDX and post the SMART details.

Seems the firmware of 970 EVO Plus is problematic with MP5,1s.

Windows requires a custom NVMe driver for Plus Pro compatibility. Perhaps the MacOS NVMe driver likely needs an update to support the drive or Samsung needs to provide one.

 

[freqrider]

EVO PLUS is a big MINUS on macOS. EVO and EVO PRO work fine! Go figure? I had the same issue with an EVO PLUS. Swapped regular EVO and it’s rock solid.

 

[w1z]

EVO PLUS is a big MINUS on macOS. EVO and EVO PRO work fine! Go figure? I had the same issue with an EVO PLUS. Swapped regular EVO and it’s rock solid.

There's no such thing as EVO PRO ... It is called '970 PRO'. The other models are 970 Evo and 970 Evo Plus.

 

[crjackson2134]

There's no such thing as EVO PRO ... It is called '970 PRO'. The other models are 970 Evo and 970 Evo Plus.

Thanks, I wanted to point this out earlier but figured I’d get dog piled

 

[JedNZ]

Have you considered disabling TRIM to see if that is the issue?

 

[freqrider]

There's no such thing as EVO PRO ... It is called '970 PRO'. The other models are 970 Evo and 970 Evo Plus.

Thats right!

 

[worx777]

Return it and buy the PRO version. There is a thread in this forum with a lot compatibility issues regarding the EVO plus.

Same stuff happened to me, bought EVO plus first, but now I'm happy with the 970 PRO.

 

[TheStork]

Return it and buy the PRO version. There is a thread in this forum with a lot compatibility issues regarding the EVO plus.

Same stuff happened to me, bought EVO plus first, but now I'm happy with the 970 PRO.

I'm running a 970 EVO (not Plus) in my MP5,1 w/o any issues. So, both the 970 Pro & EVO (non Plus) work well.

 

[jdub9]

I'm running a 970 EVO (not Plus) in my MP5,1 w/o any issues. So, both the 970 Pro & EVO (non Plus) work well.

I’ll have a 970 PRO this coming Monday. Will update after installing and testing it.
Thx.

 

[macguru9999]

I returned the evo plus and got a pro. It works great.

 

[jdub9]

I returned the evo plus and got a pro. It works great.

Ok, I just installed a 970 PRO NVMe 1TB in a Lycom DT-120 PCIe card in my Mac Pro 2010 and it works OK (i.e. NO kernel panics due to NVMe command timeouts)


I'm averaging Write 1430 MB/s and Read 1490 MB/s in BlackMagic Disk Speed Test.


Sure does look like the new 970 EVO Plus NVMe might have a firmware issue or at least some newly-introduced incompatibility with the Apple NVMe drivers (at least on a cMP running High Sierra 10.13.6).

A 970 PRO NVMe worked OK for me and other posts above had mentioned that the previous generation 970 EVO NVMe (not "Plus") also worked ok in a cMP.


Thx for all the replies and help.

 

[medhatraafat]

I have had same story Evo 970 Plus 1TB, after getting online OS recovery, OS complete installation then blinking folder with ? Mark ... i reset nvram but same... Then i worried if my SinTech adaptor was the issue, i test 3 new adaptors ! same result ...... Then guess what ? I installed Win10 Pro , worked without issues !!!!! although i dont want to use it but just to prove my hardware matches

The Story is MAC OS MOJAVE drivers

Ok, I just installed a 970 PRO NVMe 1TB in a Lycom DT-120 PCIe card in my Mac Pro 2010 and it works OK (i.e. NO kernel panics due to NVMe command timeouts)


I'm averaging Write 1430 MB/s and Read 1490 MB/s in BlackMagic Disk Speed Test.


Sure does look like the new 970 EVO Plus NVMe might have a firmware issue or at least some newly-introduced incompatibility with the Apple NVMe drivers (at least on a cMP running High Sierra 10.13.6).

A 970 PRO NVMe worked OK for me and other posts above had mentioned that the previous generation 970 EVO NVMe (not "Plus") also worked ok in a cMP.


Thx for all the replies and help.

 

[w1z]

I have had same story Evo 970 Plus 1TB, after getting online OS recovery, OS complete installation then blinking folder with ? Mark ... i reset nvram but same... Then i worried if my SinTech adaptor was the issue, i test 3 new adaptors ! same result ...... Then guess what ? I installed Win10 Pro , worked without issues !!!!! although i dont want to use it but just to prove my hardware matches

The Story is MAC OS MOJAVE drivers

Check this post for the solution

 

[ButtrflySwtchhes]

Currently upgrading a Mac Pro 5,1, and I'm somewhat torn between a 970 Evo, or a 970 Evo Plus with the new firmware update. After the firmware update, is the 970 Evo Plus considered to be as stable as the 970 Evo on High Sierra and Mojave? Hate to purchase an older drive just for compatibility reasons, but I need stability... If stability weren't a concern, I'd probably just pick up an Adata XPG SX8200 Pro and call it a day. Nothing against the Adata, by the way. I've heard it's pretty decent.

Thanks!

 

[tsialex]

Currently upgrading a Mac Pro 5,1, and I'm somewhat torn between a 970 Evo, or a 970 Evo Plus with the new firmware update. After the firmware update, is the 970 Evo Plus considered to be as stable as the 970 Evo on High Sierra and Mojave? Hate to purchase an older drive just for compatibility reasons, but I need stability... If stability weren't a concern, I'd probably just pick up an Adata XPG SX8200 Pro and call it a day. Nothing against the Adata, by the way. I've heard it's pretty decent.

Thanks!

No one tested the new firmware enough to affirm that 970 EVO Plus is stable. It was released last Monday, with most people knowing about it Thursday.

 

[ButtrflySwtchhes]

No one tested the new firmware enough to affirm that 970 EVO Plus is stable. It was released last Monday, with most people knowing about it Thursday.

Yeah, I know the 970 Evo has been out considerably longer, and Samsung's firmware fix for the 970 Evo plus is fairly new. I should have just requested opinions on general stability of the 970 Evo Plus on Mojave and High Sierra, not necessarily compared to the older 970 Evo.

Unrelated, but thank you for all of your hard work in relation to cMP boot ROM hacking. Pretty sure you, and a few others on this forum were likely the reason everyone now has officially supported bootable NVME on the cMP. Not much of a Mac person, but I like to pay respect where respect is due.

Thanks.

 

[MIKX]

There are so many "970 EVO PLUS : blades in the store in my town in Japan but it's a certainty that they will need the new firmware upgrade which for me would involve.

1. Mount the PLUS on it's own M.2 adaptor

2. Boot from my 970 EVO ( non-plus ) to Win7 & download Samsung Magician.

3. Flash the PLUS blade ( with sweat on my brow & hope for the best ) .

Instead of all that . . I could ask the computer shop staff to do the upgrade !
Japanese shop staff though largely ignorant of new trends are exceeding helpful to Gaijin = ( non-Japanese foreigners ).

But realistically, buying the now proven 970 Pro would be safer and easier until we get much more input from PLUS owners.

 

[mikehalloran]

Have you considered disabling TRIM to see if that is the issue?

TRIM is part of the Mac OS and not the issue.

When booting from a 970 EVO and 970 PRO, TRIM support is normally enabled as if they're Apple OE.

 

[ariethekid]

I have a 970 EVO plus 1tb. I did the firmware update with the Samsung Magic drive software in Windows 10. Its easy to do you just need a windows PC or bootcamp partition installed on your Mac to do it.. Haven't had any issues with Mojave 10.14.5.

 

[mikehalloran]

I have a 970 EVO plus 1tb. I did the firmware update with the Samsung Magic drive software in Windows 10. Its easy to do you just need a windows PC or bootcamp partition installed on your Mac to do it.. Haven't had any issues with Mojave 10.14.5.

A number of us were wondering if that would work.

I'll stick to the 970 EVO for now till I'm pretty certain that any of the Plus I'm likely to buy is after the firmware update.

 

[donluca]

I'm surprised people still haven't realized that the 970 EVO Plus is 100% compatible on Mac Pro with the latest firmware update. It has been reported several times in the other NVMe/Blade thread and there are several users (me included) happily using it.

If you don't want to boot Windows 10, you can download a bootable image from the samsung website, write it to a usb pen drive and boot off it and it will update your blade.

 

[giangio]

I'm surprised people still haven't realized that the 970 EVO Plus is 100% compatible on Mac Pro with the latest firmware update. It has been reported several times in the other NVMe/Blade thread and there are several users (me included) happily using it.

If you don't want to boot Windows 10, you can download a bootable image from the samsung website, write it to a usb pen drive and boot off it and it will update your blade.

Done it today, firmware revision updated to: 2B2QEXM7

Mac Pro 5.1 (Mid 2012), Samsung 970 EVO Plus as boot disk

As of now it seems to work properly (it kept disconnecting randomly before the update)

I had to use an old GPU in order to boot from USB.

I'll try to give you an update after a week or so.

 

[giangio]

I'll try to give you an update after a week or so.

All right till now, it's working, no problems at all.

Thank you for your comments and information guys!