-
Notifications
You must be signed in to change notification settings - Fork 7
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
SSD hall of fame needs new entries #192
Comments
Gigabyte Z490i Aorus Ultra + 10900k
|
Crucial BX500 120GB SATA 2.5-inch
(sudo trimforce enable) From the motherboard logo to macOS system, pressing Enter immediately at OpenCore menu. |
WD Blue SN550 1TB NVMe
From Apple logo to macOS system. |
Crucial MX500 500GB SATA 2.5-inch
(sudo trimforce enable) From Apple logo to macOS system. |
Samsung SM951 256GB NVME (MZVPV256HDGL-00000)
From gigabyte splash screen to macOS Login screen (used stopwatch on iPhone to time each run) |
Samsung 830 256GB SATA SSD Asus P9X79WS + Xeon E5-2667v2 + 64GB ECC + MacPro6,1 SMBIOS Time in seconds from pressing enter in OC-Picker to login screen: sudo trimforce disable:
sudo trimforce enable (SetApfsTrimTimeout={999, -1, 4294967295}):
I expected 'trimforce disable' and 'trimforce enable' with 'SetApfsTrimTimeout:999' to be approximately equal. Why isn't that the case? 🤔 |
HideAuxiliary Enabled, ShowPicker, and Timeout Disabled. (I always use it this way.) ADATA XPG SX8200 Pro 1TB NVMe
It is always slow in any case. There is only one OS in this Build. |
Samsung 870 EVO 1TB SATA Times taken between Apple Logo and Login Screen
|
Corsair MP600 1TB NVMe
|
I don't know if you'll ever consider the following, but apparently many models of Phison E12 (like Sabrent Rocket NVMe 3.0 TLC 64 layers NAND) have a broken trim support and are going to failure of the disk. Please avoid buying NVMes with Phison E12 controller. |
Crucial P2 CT500P2SSD8
About 10 seconds more with trim enabled |
DELL XPS 7590 FHD | i7 9750-H | HP SSD EX920 512GB
Testing done from POST logo to macOS login screen |
Intel 660pSSD:
Model: INTEL SSDPEKNW010T8
type: NVMe
size: 1TB
motherboard: LattePanda Alpha 800s
CPU: m3-8100Y
macOS: macOS 11.4 (20F71)
Samsung 860 EVOSSD:
Model: Samsung SSD 860 EVO 500GB
type: SATA
size: 500GB
motherboard: GA–Z77–HD4
CPU: i7–3770K
macOS: macOS 11.4 (20F71)
Samsung 970 EVO PlusSSD:
Model: Samsung SSD 970 EVO Plus 1TB
type: NVMe
size: 1TB
motherboard: GA–X299–UD4
CPU: i9 7900X
macOS: macOS 10.15.7 (19H1217)
|
Samsung NVME 970 Pro 512GB Big Sur 11.4 VALUE | POST>OC | OC>OSX | TOTAL BOOT Confirms your findings about Samsung |
Hi! I’m using a Samsung 970 Evo Plus 500GB, but I’m on Clover. Is there anyway to test or implement this without OC? Thanks! |
Samsung SSD 960 PRO 512GBSSD:
Model: Samsung SSD 960 PRO 512GB
type: NVMe
size: 512GB
motherboard: GA–X299–UD4
CPU: i9 7900X
macOS: macOS 11.4 (20F71)
c.f. #192 (comment) for similar reports. |
Western Digital Black SN850 500gb (in PCIe Gen3 Environment):
From Apple logo to macOS system. |
Mine is Gigabite 240 GB M.2 PCIe SSD (GP-GSM2NE3256GNTD) and it hangs randomly. |
FWIW, I’ve tried Plextor M10P with Innogrit controller, and it does not work with macOS. Read operations cause disk I/O freeze, resulting in loss of the device from the macOS device tree (!) until a system reboot. |
WD Black SN 750 NVMe 500 GB Since motherboard beep to desktop active.
|
Hi - May I ask you what settings you've implemented for your SN750? I can't seem to get away from NVMe kernel panics happening eventually with my SN750 2TB -- thank you! |
威刚S70避坑,不能用 |
I went on kind of a shopping spree for new NVMe this holiday and have some data points. (Sorry I didn't follow the template) My machine is a Intel NUC i7-8809G running macOS 12.6.1 with FileVault enabled.
Some other thoughts: I think having FileVault enabled really exacerbates the issue. With any NVME that panics with a heavy IO load, it will also instantly panic when booting into my FileVault enabled installation. I don't see enough people talk about HMB and DRAMless SSDs which are the majority of "cheap" NVMEs. macOS does not support HMB and so will get worse random I/O throughput. The performance on sequential reads shouldn't be affected and that's what everyone seems to run on benchmarks. I found that "low throughput" seems to be one of the factors that cause macOS to panic. For example, here is a benchmark run on the Kingston NV2 on macOS: As you can see the write speeds are terrible and way under the rated speed of 2500MB/s. I'm not sure why the numbers are this bad, but I tried to also run a benchmark on my Windows install with the same drive put into a TB3 enclosure in order to simulate the lack of HMB and you see similar numbers for random writes. Compare that with the same drive installed internally (note that TB3 overhead probably contributes to the difference in peak read speeds) Moral of the story: go with WD if you are building a hackintosh. |
Haven't taken exact measures because I'm running debug verbose mode and could be misleading but I can confirm that my Samsung 980 (non Pro) loads in -1 as fast as in 4294967295. Probably around 20 to 30 seconds tops. I'm running this hackintosh since August in a 256gb partition out of 1 TB of space. I'm using the other partition in Windows as an expansion disk (not OS) for games. Health level remains at 100%, no wear detected (I purchased the disk around May / June). No slowdowns or slow boot times. |
Has anyone tested the WD SN770? I'm currently running a Samsung 970 Pro and considering the SN770 for replacement. |
Hi, i have this one, 2Tb, no issues so far. |
is there shorter 2260, 2242 smaller 128/250gb ok that works without this panic/nvme problem? thx |
WD SN850x will work? I've an Asus Z390E with i9900k. SN750 is out of market and high price too. |
@Kaisar870 read a couple posts up: #192 (comment) |
Thank you 😊 my concern is now does it work with z390 ? I mean PCI gen 3x4 |
Yes, I also had PCI gen 3x4. However, after months of usage, I did notice that there are some times (maybe 1-2 times a week) where the storage would cause macOS to freeze up for 10-15 seconds. I don't know if it has to do with this specific NVMe or if it is an issue with every NVMe. I only used SATA before and never had that issue. |
Thank you for your patience 😊 do you think this issues cause by SN850X? I've already 970 Evo plus and boot time 1 minute 30 sec. Some apps Open take long time specific Ms office. Also glitch the screen and freeze Evey week even multiple times a day. I've previously installed 850 sata SSD and this was incredibly fast both boot and opening apps. |
My advice: stick with the 850 SATA. I had a 860 SATA before and had 0 issues for years. You won't notice any speed increase in day to day use, especially since it's PCIe 3x4. |
Samsung SSD 980 500GB NVME (Non-Pro) motherboard: GA - Z490 Aorus Elite From Apple logo to Login Screen: 1 : 15 15 15 I can only assume the Trim is either working slowly or failing, I am unsure if I should leave it on -1 or 0 for day to day use until I can buy a more compatible SSD, any tips are welcome. |
Maybe not that great? https://www.tonymacx86.com/threads/general-nvme-drive-problems-fatal.316546/post-2324146 |
Is there a way to manually trigger the trim or some tool to do that? Because I rather trigger manually when I'm idle than waiting an infinite amount of time at boot. |
Hi All... am using the Dortania help guide to install the Ventura on my Dell G3 3579 laptop... I have the NVMe WDC SN550 M.2 NVMe drive and I have followed the NVMefix and Set the TRIM support to 3 value but still am getting the bellow error even after very long hours... Please help me out to fix this problem I have the attached EFI folder here... Current Config of my Laptop Model : Dell G3 3579 Processor Intel Core i5-8300H @ 2.30Ghz Memory : 16GB DDR4 2666Mhz ✅ SSD 1TB Samsung 860EVO ✅ NVMe M.2 Slot Western Digital Blue SN550 1TB ✅ iGPU Intel UHD Graphics 630 ✅ Sound Card Realtek ALC236 ✅ Ethernet Card Realtek RTL8111 ✅ |
@qin9125 > thank you wd sn550 works fine Bro I'm also using SN550 but I don't know why I'm getting this and stuck in this line only Thanks in advance. |
Hi, i have used samsung 970 EVO with no issues on big sur in the last years, now i want to upgrade to a newer version of osx. |
Best thing to do is switch to WD |
OK, but 1st post says: Working fine with TRIM: and found some reviews like this So should i give it a try? |
I looked at techpowerup.com and they agree on the controller and memory with sn 750/770, there is a high chance that it will work |
edit: |
Hi i recently built my hackintosh i don't know how you do those test.. i checked and my APFSTrim is set to -1 ASUS TUF Z690 D5 on my macos ventura with AmorphousDiskMark i got this result: Except the slow boot i don't see any issue or trouble... but if you can suggest the correct test to do .. i would be happy to do... |
Guide Anti-Hackintosh Buyers Guide (link)
After our discovery of a severe bug in the TRIM implementation of practically all Samsung SSDs we spent time investigating which SSDs are affected by all kinds of issues, and so far came with several names worth mentioning.
Working with TRIM broken (can be used with TRIM disabled, at slower boot times, or as a data storage):
Working fine with TRIM:
Working fine with TRIM (SATA):
Working fine with TRIM (Unbranded SSDs):
Incompatible with IONVMeFamily (die under heavy load):
There are several very good comparison charts containing various SSDs and their controllers: one, two. Since SSD compatibility usually is controller-based, picking up an SSD with a known to be compatible controller has a high compatibility chance as well.
In addition to that, I would like more people to run tests on their platforms to determine whether their SSD TRIM implementation is broken or not.
Preconditions:
The idea is to measure the boot time either between motherboard logo and macOS login screen or between Apple logo and macOS login screen. The former is strongly recommended due to possible GOP issues. All the measurements needs to be done with different
SetApfsTrimTimeout
values set in OpenCore. Each measurement must be made at least 2 or 3 three times to ensure no sporadic results. The values to test are as follows:0
(means TRIM is disabled)-1
(standard timeout, equals roughly 10 seconds, means TRIM is enabled and runs up 10 seconds during boot)4294967295
(maximum timeout, TRIM is enabled and runs as long as needed)Please write include the following information in the report:
Note: If you use FileVault 2, you can use
sudo fdesetup authrestart
command to skip UEFI login.AuthRestart
must of course be enabled. I would also advise to disable the OpenCore Picker (ShowPicker
=NO
).The text was updated successfully, but these errors were encountered: