Description
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):
- Samsung 950 Pro
- Samsung 960 Evo/Pro
- Samsung 970 Evo/Pro
Working fine with TRIM:
- Western Digital Blue SN550
- Western Digital Black SN700
- Western Digital Black SN720
- Western Digital Black SN750 (aka SanDisk Extreme PRO)
- Western Digital Black SN850
- Intel 760p (including OEM models, e.g. SSDPEMKF512G8)
- Crucial P1 1TB NVME (SM2263EN) (need more tests)
Working fine with TRIM (SATA):
- SATA PLEXTOR M5Pro
- SATA Samsung 850 PRO (need more tests)
- SATA Samsung 870 EVO (need more tests)
Working fine with TRIM (Unbranded SSDs):
- KingDian S280
- Kingchuxing 512GB
Incompatible with IONVMeFamily (die under heavy load):
- GIGABYTE 512 GB M.2 PCIe SSD (e.g. GP-GSM2NE8512GNTD) (need more tests)
- ADATA Swordfish 2 TB M.2-2280
- SK Hynix HFS001TD9TNG-L5B0B
- SK Hynix P31
- Samsung PM981 models
- Micron 2200V MTFDHBA512TCK
- Asgard AN3+ (STAR1000P)
- Netac NVME SSD 480
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:
- Tested SSD is the boot SSD (i.e. macOS is installed on it).
- Tested SSD is APFS-formatted.
- Tested SSD must be actively used with macOS installation being at least a month old.
- OpenCore 0.6.7 or newer is used.
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)
- An SSD with a decent TRIM implementation should behave as follows. Value 1 will be negligibly the fastest. Value 2 might be slightly slower than 2 (way less than by 10 seconds, maybe 2-5). Value 3 should be equal to value 2.
- An SSD with a broken TRIM implementation, like Samsung, will have value 2 slower than value 1 by 10 seconds, and value 3 will be noticeably slower than value 2, usually by 30-60 seconds.
Please write include the following information in the report:
- SSD type (NVMe or SATA), model, and storage size
- Motherboard and CPU used
- macOS version used
- Test results grouped in 3 sections (a total of 6 or 9 values).
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
).