I installed it on a SATA drive. Forgot about that point. Release version 0.21 says "
- Fix NVMe Crash on build
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 Manually Configured OpenCore on the Mac Pro
- Thread starter cdf
- WikiPost WikiPost
- Start date
- Sort by reaction score
- Status
It's a OCLP build/compilation issue that has nothing to do with macOS Big Sur 11.3+ problems with MacPro5,1.
Yes... that has been mentioned more than once before (11.3+ a no go)... hence my recommendation to stick with 11.2.3 on his cMP 5 1 and not try anything higher.
Personally, I am staying with Catalina so I at least get security fixes.
Personally, I am staying with Catalina so I at least get security fixes.
Thank you for that tip about using Ubuntu's official instructions. That along with the rest of your guide after that did the trick.The Ext4 driver is just for booting the kernel from the Linux disk. For the installer, the iso file needs to be converted and copied to the USB drive. If the steps in the guide are not working for you, then you might want to try Ubuntu's official instructions for creating the USB installer in macOS:
Create a bootable USB stick on macOS | Ubuntu
Ubuntu is an open source software operating system that runs from the desktop, to the cloud, to all your internet connected things.ubuntu.com
You might also want to try another USB drive.
Note that the guide is still considered a draft, and l've made several simplifications since the current version; I just haven't had the chance to write them up. These simplifications include not needing the Ext4 driver or having to go through Open Shell.
Hi Guys,
I have a Mac Pro 5,1 with two X5690s, Sapphire Pulse RX580 and been running Mojave 10.14.6 for over a year without a problem now. I also have an Amfeltec Squid Gen 3 carrier board on RAID0. I was trying to see if I can get the OCLP EFI on the RAID0 volume and install from there. That didn't work. I copied OCLP 0.7.0 EFI onto a usb and booted into recovery and set that USB as the boot volume, all according to the post #1 instructions. OC installation went well and bootpicker showed up on every boot. I prepared the RAID0 according to these threads:
forums.macrumors.com
forums.macrumors.com
The I tried installing the Big Sur 11.2.3 on the RAID0 from Mojave and it allowed me to proceed with installation but midway through installation it said an error occured during installation. I booted into recovery and tried installing from bootable USB installer having 11.2.3 and that didn't work either. At this point I am trying to get back to the Mojave but my Mojave which is running on an NVMe SSD on PCIe, is extremely slow now. I removed the USB with OC EFI and reset NVRAM, and booted back into Mojave again according to the post #1 instructions. Mojave is still slow, Safari or any other browser doesn't work, apps with system privileges elevated stop working too. I tried searching through 336 pages of this thread looking for RAID discussion but didn't find anything. Any help to get Mojave back up and running, is highly appreciated.
I have a Mac Pro 5,1 with two X5690s, Sapphire Pulse RX580 and been running Mojave 10.14.6 for over a year without a problem now. I also have an Amfeltec Squid Gen 3 carrier board on RAID0. I was trying to see if I can get the OCLP EFI on the RAID0 volume and install from there. That didn't work. I copied OCLP 0.7.0 EFI onto a usb and booted into recovery and set that USB as the boot volume, all according to the post #1 instructions. OC installation went well and bootpicker showed up on every boot. I prepared the RAID0 according to these threads:
Catalina on RAID with APFS on MacPro 5,1
It took me a really long time to get to the point where I am running Catalina on a RAID 0 using the Amfeltec Squid and 4 x 1 TB HyperX Predator blades. Part of the problem was getting the right information, part of it a blown power supply that almost had me retire my 4,1 (as one of the screws...
forums.macrumors.com
Mojave on RAID with APFS - a HOWTO
Edit: See this later post for a better solution. I've been able to get Mojave to install on to a RAID array of 4x 8GB USB sticks! The process is as follows: - Create RAID set using command line or disk utility. Format to HFS+ - Mount InstallESD from /path/to/beta/app/Contents/SharedSupport...
forums.macrumors.com
The I tried installing the Big Sur 11.2.3 on the RAID0 from Mojave and it allowed me to proceed with installation but midway through installation it said an error occured during installation. I booted into recovery and tried installing from bootable USB installer having 11.2.3 and that didn't work either. At this point I am trying to get back to the Mojave but my Mojave which is running on an NVMe SSD on PCIe, is extremely slow now. I removed the USB with OC EFI and reset NVRAM, and booted back into Mojave again according to the post #1 instructions. Mojave is still slow, Safari or any other browser doesn't work, apps with system privileges elevated stop working too. I tried searching through 336 pages of this thread looking for RAID discussion but didn't find anything. Any help to get Mojave back up and running, is highly appreciated.
I have no direct solution for you, but it might help your prossess to know that as you have removed the OC EFI your problems with Mojave are not related to OC anymore. You can use normal fault finding procedure.Hi Guys,
I have a Mac Pro 5,1 with two X5690s, Sapphire Pulse RX580 and been running Mojave 10.14.6 for over a year without a problem now. I also have an Amfeltec Squid Gen 3 carrier board on RAID0. I was trying to see if I can get the OCLP EFI on the RAID0 volume and install from there. That didn't work. I copied OCLP 0.7.0 EFI onto a usb and booted into recovery and set that USB as the boot volume, all according to the post #1 instructions. OC installation went well and bootpicker showed up on every boot. I prepared the RAID0 according to these threads:
Catalina on RAID with APFS on MacPro 5,1
It took me a really long time to get to the point where I am running Catalina on a RAID 0 using the Amfeltec Squid and 4 x 1 TB HyperX Predator blades. Part of the problem was getting the right information, part of it a blown power supply that almost had me retire my 4,1 (as one of the screws...Mojave on RAID with APFS - a HOWTO
Edit: See this later post for a better solution. I've been able to get Mojave to install on to a RAID array of 4x 8GB USB sticks! The process is as follows: - Create RAID set using command line or disk utility. Format to HFS+ - Mount InstallESD from /path/to/beta/app/Contents/SharedSupport...
The I tried installing the Big Sur 11.2.3 on the RAID0 from Mojave and it allowed me to proceed with installation but midway through installation it said an error occured during installation. I booted into recovery and tried installing from bootable USB installer having 11.2.3 and that didn't work either. At this point I am trying to get back to the Mojave but my Mojave which is running on an NVMe SSD on PCIe, is extremely slow now. I removed the USB with OC EFI and reset NVRAM, and booted back into Mojave again according to the post #1 instructions. Mojave is still slow, Safari or any other browser doesn't work, apps with system privileges elevated stop working too. I tried searching through 336 pages of this thread looking for RAID discussion but didn't find anything. Any help to get Mojave back up and running, is highly appreciated.
Thank you for the reply. That is correct, I have removed OC and it is not related to OC anymore, but I thought others have encountered the same problem when they tried to install OC or if this is a known issue while installing OC. The problem started when I booted back into Mojave after installing OC though.
It looks like my Mojave on the PCIe NVMe is corrupted somehow during OC installation, I had an older Mojave on an internal HD and booted into it and it's normal. I tried booting into recovery and re-installing Mojave on the PCIe NVMe, that didn't solve it. I guess my only course of action is re-installing Mojave on the PCIe NVMe.
I was very careful not to do that. I am 99.99% certain I did not do that. The EFI partition of my NVMe SSD is in fact empty except for some hidden files.
If that's the case. Removing the USB with the OC EFI and resetting NVRAM wouldn't get me back to the before OC state, as is my case right now. Is that right? If so, the EFI of Disk B (from post #1 instructions) needs to be backed up somewhere before doing OC related stuff.
If your OC was installed to a seperate USB..then Never mind...
Pull out the OC USB and clear NVRAM then Mac should attempt to boot your devices in some order, I am not sure where NVMe devices fit...I think perhaps they might attempt to be booted prior to drive bay #1, but I'm not sure.
But really OC does not mess with anything on your Mojave installation disk...so as much as it may seem like that might have happened...OC simply doesn't do that.
The EFI on my Native Mojave disk looks like this:
I actually have OC installed on the EFI of a USB flash drive, so that I can pull it out at will and boot up without OC, my Mojave drive is in drive bay #1, so that fallback default of clearing NVRAM will just boot up Mojave natively and it always has without any issue whatsoever.
Regarding backup, of course it goes without saying that you should have a backup..not only of your MacOS, but particularly of your BootROM...did you do that?
But in my experience.....OC has never corrupted my MacOS volumes ever. But its entirely possible your EFI partition is somehow not findable as a bootable volume now, so I would look there first before resorting to reinstalling macOS Mojave as a nuclear option.
Pull out the OC USB and clear NVRAM then Mac should attempt to boot your devices in some order, I am not sure where NVMe devices fit...I think perhaps they might attempt to be booted prior to drive bay #1, but I'm not sure.
But really OC does not mess with anything on your Mojave installation disk...so as much as it may seem like that might have happened...OC simply doesn't do that.
The EFI on my Native Mojave disk looks like this:
Code:
EFI
└── APPLE
└── EXTENSIONS
└── Firmware.scap
2 directories, 1 fileI actually have OC installed on the EFI of a USB flash drive, so that I can pull it out at will and boot up without OC, my Mojave drive is in drive bay #1, so that fallback default of clearing NVRAM will just boot up Mojave natively and it always has without any issue whatsoever.
Regarding backup, of course it goes without saying that you should have a backup..not only of your MacOS, but particularly of your BootROM...did you do that?
But in my experience.....OC has never corrupted my MacOS volumes ever. But its entirely possible your EFI partition is somehow not findable as a bootable volume now, so I would look there first before resorting to reinstalling macOS Mojave as a nuclear option.
Before doing anything more with OC I would recommend you backup your BootROM. There is another thread about a lot of that here: https://forums.macrumors.com/threads/mp5-1-bootrom-thread-144-0-0-0-0.2132317/
At a very minimum, while not in OC at all..and after you get Mojave working properly.....make a bootROM backup using DosDude's rom backup tool. it is sometimes possible to brick a Mac, that thread has a lot of info about this towards the end of the thread. At a minimum you should have a backup of your bootROM in case your bootROM becomes corrupted, but ideally I have chosen to pay @tsialex to build me a never-booted-rom in order to get a very clean bootROM, there is a lot more info at that thread...that is hopefully not why your Mojave is broken now..but never know...it could be. I am more suspicious of your EFI partition being corrupted. but anyway....I digress...
At a very minimum, while not in OC at all..and after you get Mojave working properly.....make a bootROM backup using DosDude's rom backup tool. it is sometimes possible to brick a Mac, that thread has a lot of info about this towards the end of the thread. At a minimum you should have a backup of your bootROM in case your bootROM becomes corrupted, but ideally I have chosen to pay @tsialex to build me a never-booted-rom in order to get a very clean bootROM, there is a lot more info at that thread...that is hopefully not why your Mojave is broken now..but never know...it could be. I am more suspicious of your EFI partition being corrupted. but anyway....I digress...
I performed the deep reset NVRAM and it booted into Bay 1 old HDD Mojave I have, then from there I rebooted into PCIe NVMe Mojave I have, and still the same.
Is blessing my PCIe NVMe necessary for things to go back to normal?
Not really. You need to have something to bless first.
1. Use https://github.com/corpnewt/MountEFI to mount your EFI partitions from the old spinner and NVMe. Make sure you can distinguish which one is which, as the BOTH will be called EFI and will have exactly the same icon.
2. Copy everything from your old HDD EFI partition to your NVMe EFI. If in doubt, make sure you show invisible files in Finder and copy literally everything. If in doubt, you may as well delete all the files on the NVMe EFI, empty trash, copy over from HDD EFI.
3. Shut down. Remove HDD. Cross fingers and clear NVRAM (old option-command-p-r until you hear the second chime).
4. After a while it should now boot Mojave from NVMe.
I performed the deep reset NVRAM and it booted into Bay 1 old HDD Mojave I have, then from there I rebooted into PCIe NVMe Mojave I have, and still the same.
I would wipe the NVME and reinstall Mojave. After you confirm that runs fine they you can move to OC. I don’t think you have a problem with the EFI partition on the NVME I think you have a problem with the Mojave install on the NVME. IF you want to work RAID I would search the forums and/or message @tsialex. If I recall raid support was dropped a while ago in macOS.
If that doesnt’ work or I have it wrong I would start a new thread so you are not troubleshooting a macOS install problem in the OC thread.
If I understand you correctly you have Mojave on a HDD that is working fine but Mojave on the NVME runs slow, etc…
I would wipe the NVME and reinstall Mojave. After you confirm that runs fine they you can move to OC. I don’t think you have a problem with the EFI partition on the NVME I think you have a problem with the Mojave install on the NVME. IF you want to work RAID I would search the forums and/or message @tsialex. If I recall raid support was dropped a while ago in macOS.
If that doesnt’ work or I have it wrong I would start a new thread so you are not troubleshooting a macOS install problem in the OC thread.
Apple only support bootable RAID arrays that are not identified as a single instance only up to 10.13.6 - AppleRAID and SoftRAID are not supported since Mojave for macOS booting.
You are right. I have tried all the suggestions above and none have worked. It looks like I have to reinstall Mojave on the NVMe. Thanks for the reply again.
About the RAID, I searched through the 337 pages of this thread and didn't find much other than people not be able to see their RAIDs after installing Catalina and Big Sur. I had used the now obsolete thread (https://forums.macrumors.com/thread...to-make-catalina-work-with-macpro5-1.2183978/) and (https://forums.macrumors.com/threads/catalina-on-raid-with-apfs-on-macpro-5-1.2216730/) where I was able to run 10.15.3 on my Amfeltec RAID but updating to 10.15.4 broke it.
There reason I tried using OC and RAID was that some people earlier in the thread mentioned that the way OC works may pave the way for running macOS off of RAIDs too. I guess I can start a new thread and find out. My intention was to use OC on the RAID if it works if not Update my NVMe Mojave to 11.2.3 using OC.
As for mentioning a potential macOS install problem here was to literally find out if it was an OC problem or not. It may look so at first but it is not, but if other users also run to the same problem as me when using OC then these posts are useful for them to point them to the right direction.