How to Fix Help - OCLP Sonoma on SSD and SSD Data drive with Images conflict During macOS Boot or Installation
Boot failures need a predictable pass through firmware, USB, storage, EFI and verbose logs before reinstalling macOS. Most installer stalls come from firmware settings, an invalid config.plist, wrong SSDTs, bad USB mapping or unsupported storage/controller settings.
Quick Checks
- Backup current state: Save a copy of your working EFI and run a full system backup before changing settings.
- Identify hardware components: Note down your exact CPU, GPU, Wi-Fi card, and motherboard/laptop model.
- Ensure utility alignment: Keep OpenCore, OCLP, and ProperTree updated.
Fix Steps
- Create a rollback point: Make a Time Machine backup and keep a copy of your last working EFI folder before editing OpenCore, kexts or root patches.
- Boot verbose: Add
-v keepsyms=1 debug=0x100so the final visible line gives a real clue. - Check firmware settings: Disable Secure Boot and Fast Boot, set SATA to AHCI, disable CFG Lock if possible, and use UEFI mode.
- Validate OpenCore: Update OpenCore, Lilu and core kexts, then run ocvalidate or ProperTree clean snapshot.
- Recreate the installer: Use a fresh USB installer and try another USB port; older Macs may need a USB 2.0 hub for input during setup.
- Reset NVRAM: Reset NVRAM from the OpenCore picker before retrying the installer.
Do Not Continue If
- Do not continue if: you do not have a working EFI backup, a Time Machine backup, or another bootable macOS installer.
- Stop and capture evidence: if the machine stops booting, take a photo of the last verbose line before changing more settings.
Verify It Worked
- Verbose boot moves past the previous stopping line.
- The installer reaches Disk Utility and sees the target disk.
- Keyboard, mouse and USB remain active during recovery.
- OpenCore picker still loads after a cold boot.
Rollback
- Restore the last booting EFI folder.
- Use the officially supported macOS installer to recover the machine.
- Do not erase the internal disk until the installer can boot twice consistently.
Next Action
- Test now: reboot twice, reproduce the original problem, and confirm whether the same symptom returns.
- If it still fails: record the Mac model, macOS build, OpenCore or OCLP version, GPU, Wi-Fi/Bluetooth chipset, and the last visible error.
- Read next: use the related searches below for the nearest OpenCore or OCLP fix before making another change.
Related iATKOS Searches
- OpenCore · OCLP · EFI · kexts · config.plist · macOS troubleshooting
Original Question: "Help - OCLP Sonoma on SSD and SSD Data drive with Images conflict"
I have installed OCLP Sonoma on an external SSD which works fine on my mid 2015 iMAc. It also works fine when I attach my 2TB SSD data drive to the iMAC with my images that are managed in Lightroom ....but as soon as I switch off the iMAC with both the SSD's attached (OCLP Sonoma and my data drive) to the computer and then go back later to switch on I no longer see the Sonoma SSD boot option - it boots straight to my iMAC hard drive. When I remove the data SSD from the computer and switch on the computer I again have the Sonoma SSD boot option and I can boot and work with Sonoma on my OCLP SSD without any problems.
I would like to keep both my OCLP Sonoma SSD and my data drive with my images plugged into the computer because I work a lot with images and it is a pain to continually unplug the data drive drive each time I switch off and then back on later in the day and plug in my data SSD after Sonoma boot .
Does anyone have any ideas why it is doing this? I have tried the option key, space bar and everything in between but as long as the data drive is attached to the computer I cannot see the SSD Sonoma boot option. I have also reinstalled Sonoma on my SSD but nothing seems to work. I have spent literally hours on google trying to find someone else with the same problem or a solution but have found anything.
I have just found that if I try and eject the data SSD the Finder freezes and I couldn't get back into finder so an additional issue. I have to force quit the finder and to get it to work. Its really baffling.
Any help much appreciated
[link] [comments]
Post a Comment