OCLP 0.4.3 and Monterey OtA 12.3.1 update ran and rebooted the machine. After that, boot screen shows, progress bar gets to about 50% and stops. Hard powered off. Powered on again, startup chime, but nothing on screen. Hard powered off. Powered on again, progress bar to 50%, let it sit for about an hour. Powered off, removed all drives except PCIe NVMe housing Monterey 12.3.1. What should I do next?
Got a tip for us?
Let us know
Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.
MP 1,1-5,1 MP 5,1 Monterey 12.3.1 Update Won’t Finish Booting
- Thread starter MacForumsUser
- Start date
-
- Tags
- cmp monterey 12.3.1
- Sort by reaction score
The quickest way to receive help with OCLP is by joining the OpenCore Patcher Paradise Discord Server.
Not sure if it’s “quick.” I posted 5.5 hours ago, and nobody has responded. They did respond to other support requests though.
Samsung 970 EVO 1 TB SSD.
Last edited:
Did you tried enabling VMM and experimenting with SetApfsTrimTimeout?
970 EVO should use 4294967295, since is one of the drives that constantly fail to complete the TRIM process before the 10s standard timeout.
SSD hall of fame needs new entries · Issue #192 · dortania/bugtracker
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 k...
github.com
I did not, but I will. What do I need to do to make this happen? I can’t boot. I have a spinning drive with Mojave in the first slot of my Mac Pro 5,1.Did you tried enabling VMM and experimenting with SetApfsTrimTimeout?
970 EVO should use 4294967295, since is one of the drives that constantly fail to complete the TRIM process before the 10s standard timeout.
SSD hall of fame needs new entries · Issue #192 · dortania/bugtracker
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 k...
Boot Mojave and mount your OC ESP (EFI partition where you installed OpenCore/OCLP) and then edit the config.plist temporarily adding VMM spoofing and SetApfsTrimTimeout.
For more info on VMM spoofing, please go the first post of the thread below and read "Spoofing, enabling missing features and fixing power management":
OpenCore on the Mac Pro
This guide explains how to use the excellent OpenCore boot loader to install, run, and update the latest version of macOS on the MacPro5,1, resulting in a clean, unaltered operating system just like on a supported Mac.
forums.macrumors.com
Since your SSD is one of the affected by the failure of TRIM completion before the timeout, you will have to use 4294967295 instead of the recommended 9999999 (=10s) for the SetApfsTrimTimeout.
Thanks! And at this point, how do I boot Mojave? Do I have to reset NVRAM 3x? Because it doesn’t show in the boot picker.Boot Mojave and mount your OC ESP (EFI partition where you installed OpenCore/OCLP) and then edit the config.plist temporarily adding VMM spoofing and SetApfsTrimTimeout.
For more info on VMM spoofing, please go the first post of the thread below and read "Spoofing, enabling missing features and fixing power management":
OpenCore on the Mac Pro
This guide explains how to use the excellent OpenCore boot loader to install, run, and update the latest version of macOS on the MacPro5,1, resulting in a clean, unaltered operating system just like on a supported Mac.
Since your SSD is one of the affected by the failure of TRIM completion before the timeout, you will have to use 4294967295 instead of the recommended 9999999 (=10s) for the SetApfsTrimTimeout.
Weird that Mojave don't show on the BootPicker. If you remove the usual drive that you boot from your Mac Pro and reset the NVRAM, the Mac Pro firmware will boot any bootable drives that are available, preference is for the SATA drive installed on SATA bay one.
It shows in the boot picker, but when I select Mojave, I receive the circle with the line through it 🚫
You probably installed the OC ESP to the same drive as Mojave. If you are spoofing MacPro7,1 you can't boot Mojave since MacPro7,1 is only supported AFTER 10.15.1, you need to add -no_compat_check to your NVRAM boot-args.
Deep reset, reset the NVRAM continuously pressing and keep pressing CMD-ALT-P-R with a wired KB until you hear the 5th chime.
Well, I held it, but it only chimed twice, and next thing I knew, I was in Mojave! Keyboard was connected via Bluetooth.
I’ve manually updated the Monterey NVMe’s config.plist with the options suggested. Do I have to do anything else, like bless? Or just replace it in the EFI partition and reboot?
Last edited:
So I turned off the VMM flag - kept the TRIM timeout - turned off the machine, removed the Mojave drive, turned on, reset the NVRAM (3 chimes), and the installation finished! I am now running 12.3.1! Thanks again for your amazing help Alex! You’re the man!!
Saw you had to bug them to get some help a bit later. So that combined with tsialex you solved it. Maybe you should consider building your own as described here: https://forums.macrumors.com/threads/opencore-on-the-mac-pro.2207814/ then before updating you read that thread to be warned of new things happening. Also, if you run into problems, you will get help in that thread.