How to Fix "Uninitialized" SSD After First Boot on Hackintosh
Having a drive work perfectly on the first boot but disappear or show as "Uninitialized" in Disk Utility on the second boot is a common issue with certain SSDs on macOS. Here is a step-by-step guide to resolving this problem, tailored for systems like the Dell Latitude 7300.
Step-by-Step Fixes:
- Check SSD Compatibility: Certain SSDs, such as the Samsung PM981, Samsung 970 EVO Plus (with older firmware), and specific SanDisk/WD models, have severe compatibility issues with macOS APFS TRIM implementation. These drives can corrupt their own partition maps after initial writes. If you have an unsupported NVMe, you may need to replace it.
- Add NVMeFix.kext: Ensure you have
NVMeFix.kextinstalled in yourEFI/OC/Kextsfolder and enabled in yourconfig.plist. This kext fixes power management and initialization issues for non-Apple NVMe drives. - Disable APFS TRIM: Some drives panic or corrupt data when macOS tries to trim them. Open your
config.plistand navigate toKernel>Quirks>SetApfsTrimTimeout. Change the value to0to disable TRIM and prevent further corruption. - Verify APFS Driver Settings: In your
config.plist, underUEFI>APFS, make sureMinDateandMinVersionare both set to-1. EnsureConnectDriversis set toTrueunderUEFI. - Recover the Drive: Since the drive is currently "Uninitialized", the APFS partition map is likely corrupted. You will unfortunately need to boot into the macOS installer, open Disk Utility, erase the drive completely (GUID Partition Map, APFS), and reinstall macOS after applying the OpenCore fixes above.
Post a Comment