Contribute
Register

New SSDs added to the recommended list of the Buyer's Guide

freesby said:
The SN750 SE version works just fine with Monterey.
Click to expand...
That's great. Just keep track of your boot times over the next few months. Report back if anything changes. After a a clean install of the OS, even on the Samsung NVMe drives, there isn't much slowdown in boot time with TRIM enabled. It would take a while before you'd notice any problems. We need more SN750 SE testers like you to know for sure if it's good to use as an APFS macOS boot drive.
 
Last edited:
Here's why we don't give a green light (recommendation) to the 750 SE version. The controller is the most critical part of the NVMe SSD. The SN750 and SN850 drives both use the same proprietary WD controller. The 750 SE version uses Phison. We really don't have test results or community feedback for the 750 SE yet. The WD Black/SN750 has lots of positive feedback here and we know for sure it works with no issues on drives filled with a lot of data. WD really should not have called it SN750 SE if it doesn't use the same controller. Nothing we can do about that.

Screen_Shot_7.jpg
 
Last edited:
trs96 said:
That's great. Just keep track of your boot times over the next few months. It would take a while before you'd notice any problems.
Click to expand...
Yeah, that's true too. Too premature for a full recommendation. I'll report back with any issues.

WD really should not have called it SN750 SE if it doesn't use the same controller.
Click to expand...
I agree. That was a slimy move by WD. But so far so good and hopefully stays that way.
 
Micron 9200/9300 cards works well for me, Western Digital SN200 series also (HGST SN200). Intel P3600/P3700 have very slow reading speed, and Samsung PM1735 also works very slow.
 
Just want to add maybe a couple of suggestions here:


1. The Hynix P31 appears to work perfectly fine out of the box with TRIM enabled for the 2TB version and only require a firmware update for the 1TB and 500GB versions. I am running one on my hack now. I can highly recommend it over the SN750 given its better power efficiency and performance being actually better in most use cases.

Screen Shot 2022-01-27 at 14.25.33.png


2. The Phison E12 based drives appear to also work just fine. I have run one on my previous hack 24/7 for over a year and just retested it. It was an old Inland Premium 1TB. They have mostly been replaced now by E12S which often are paired with Micron NAND instead of Kioxia/Toshiba and with DDR3 instead of DDR4.

3. Silicon Motion 2262 based ones also appear to work but add a mysterious delay during boot which doesn't change over time. Not sure if it is related to the Samsung TRIM problem. The 2262 and 2262G add ~15s of delay during OS boot. The 2262ENG ones add almost 40s. I have run one for well over a year as well, 24/7 and only recently discovered that I was living with a boot delay. See the table below for SSD models and controllers.
Screen Shot 2022-01-27 at 21.18.31.png


I have not tested the PCI4 on this table...
 
Having trouble with WD Black SN850 500GB SSD NVMe & Monterey 12.2...
About 90% of the times it crash after boot. The problem is always the same, the NVMe controller failing because one/both of the WD Black SN850 500GB SSD NVMe.

There was a couple of times the system was working without any failure, but after restarting, it can randomly crash during boot or after a while. Only once in a while it keeps working.

Am I the only one with this problem?

panic(cpu 0 caller 0xffffff800a73b836): nvme: "3rd party NVMe controller. Loss of MMIO space. Write. fBuiltIn=1 MODEL=WDS500G1X0E-00AFY0 FW=614900WD CSTS=0xffffffff US[1]=0x0 US[0]=0xd VID=0x15b7 DID=0x5011 CRITICAL_WARNING=0x0.\n" @IONVMeController.cpp:6053
Panicked task 0xffffff8b7377f670: 185 threads: pid 0: kernel_task
Backtrace (CPU 0), panicked thread: 0xffffff9040e8c000, Frame : Return Address
0xffffffe0ba2d3aa0 : 0xffffff8007e85ffd
0xffffffe0ba2d3af0 : 0xffffff8007fe6035
0xffffffe0ba2d3b30 : 0xffffff8007fd5803
0xffffffe0ba2d3b80 : 0xffffff8007e25a60
0xffffffe0ba2d3ba0 : 0xffffff8007e863cd
0xffffffe0ba2d3cc0 : 0xffffff8007e85b86
0xffffffe0ba2d3d20 : 0xffffff8008716409
0xffffffe0ba2d3d90 : 0xffffff800a73b836
0xffffffe0ba2d3da0 : 0xffffff800a71eac7
0xffffffe0ba2d3dd0 : 0xffffff800865dd25
0xffffffe0ba2d3e40 : 0xffffff800865dc28
0xffffffe0ba2d3e70 : 0xffffff8007ed93a5
0xffffffe0ba2d3ee0 : 0xffffff8007eda412
0xffffffe0ba2d3fa0 : 0xffffff8007e2518e
Kernel Extensions in backtrace:
com.apple.iokit.IONVMeFamily(2.1)[0DE31F96-AEED-31F5-84D4-4147BDC77799]@0xffffff800a716000->0xffffff800a742fff
dependency: com.apple.driver.AppleMobileFileIntegrity(1.0.5)[B0319B71-F6E6-39E1-AD7C-33CE7A82BDEC]@0xffffff800956c000->0xffffff800958dfff
dependency: com.apple.iokit.IOPCIFamily(2.9)[897B72E0-B98F-30BA-8CB2-4E5E469CE4B6]@0xffffff800a9e7000->0xffffff800aa11fff
dependency: com.apple.iokit.IOReportFamily(47)[FCE9B54C-4E85-371D-BB93-1B9AA324711A]@0xffffff800aa23000->0xffffff800aa25fff
dependency: com.apple.iokit.IOStorageFamily(2.1)[160B70B8-9236-38ED-8AC9-A215D071A76B]@0xffffff800ab28000->0xffffff800ab3efff

Process name corresponding to current thread (0xffffff9040e8c000): kernel_task
Boot args: -v alcid=12 watchdog=0 agdpmod=pikera dk.e1000=0 -revsbvmm

Mac OS version:
21D49

Kernel version:
Darwin Kernel Version 21.3.0: Wed Jan 5 21:37:58 PST 2022; root:xnu-8019.80.24~20/RELEASE_X86_64
Kernel UUID: 93729D02-FE6F-355B-BA76-BA930AA7103F
KernelCache slide: 0x0000000007c00000
KernelCache base: 0xffffff8007e00000
Kernel slide: 0x0000000007c10000
Kernel text base: 0xffffff8007e10000
__HIB text base: 0xffffff8007d00000
System model name: iMacPro1,1 (Mac-7BA5B2D9E42DDD94)
System shutdown begun: NO
Panic diags file available: YES (0x0)
Hibernation exit count: 0

System uptime in nanoseconds: 77345701799
Last Sleep: absolute base_tsc base_nano
Uptime : 0x0000001208e11097
Sleep : 0x0000000000000000 0x0000000000000000 0x0000000000000000
Wake : 0x0000000000000000 0x00000015ea9c1821 0x0000000000000000
Zone info:
Foreign : 0xffffff800e6e0000 - 0xffffff800e6ed000
Native : 0xffffff80403c4000 - 0xffffffa0403c4000
Readonly : 0xffffff850d090000 - 0xffffff86a6a24000
Metadata : 0xffffffe5f30c7000 - 0xffffffe6133e4000
Bitmaps : 0xffffffe6133e4000 - 0xffffffe61f3e4000
Click to expand...
 
alezmad said:
There was a couple of times the system was working without any failure, but after restarting, it can randomly crash during boot or after a while. Only once in a while it keeps working.
Click to expand...
I would try clean installing Windows or Linux on the SN850 to determine whether or not it's a hardware problem. If it is then an RMA is in order.
 
trs96 said:
I would try clean installing Windows or Linux on the SN850 to determine whether or not it's a hardware problem. If it is then an RMA is in order.
Click to expand...
Thanks, I performed an extended SMART check and it didn't detected any problem...

I'm thinking switching to Corsair MP600 Pro.
 
You must log in or register to reply here.
Copyright © 2010 - 2024 tonymacx86 LLC
Back
Top