Yes I did. In fact I can't yet install 11.4 beta 1.has anyone successfully run macOS Big Sur 11.3 RC as a fresh install
Yes I did. In fact I can't yet install 11.4 beta 1.has anyone successfully run macOS Big Sur 11.3 RC as a fresh install
Thanks for your information!Yes I did. In fact I can't yet install 11.4 beta 1.
It might have been an update. No USB, if it was a full installer it was over the existing one from another partition.Fresh new installation via a UBS drive right? No update?
NVRAM and SMC resets did not help again.
I'm really getting desperate, because I have no idea what the problem is.
Thank you...Only one OC per computer. You have two (on the Big Sur and on the Catalina disks).
Remove OC from either disk, bless it properly.
bless --mount /Volumes/EFI --setBoot --file /Volumes/EFI/EFI/BOOT/BOOTx64.efi --verbose.
Where /Volumes/EFI is your actual boot EFI partition.
Select Big Sur from the OC boot picker and once booted set as default boot in System Preferences.
No. As I mentioned in that post: even if OC starts up automatically on boot, it may not actually be blessed. You'll need to rebless it, either with RequestBootVarRouting disabled or from a natively booted recovery environment.Hmmm, interesting. Thanks! But shouldn't OC be blessed? I was able to boot into 11.4 Beta 1 after the NVRAM resets.
Thanks again! Sorry for the stupid question just now, somehow I did not read or understand your post correctly! I am still unsure if it is because of that. I did not have a boot loop. It looks like the OTA update to 11.3 RC is not working for me. Via the 11.3 recovery from my SSD, which can no longer boot, I was able to install 11.3 RC on an HDD partition. The installation is not quite finished, but this time it looks good! Could it be that I have to turn on VMM after all to install the update via OTA? However, that would be weird because I was able to do an OTA update from 11.2.3 to 11.4 DP 1 without VMM enabled. Do you maybe have another idea why it didn't worked for me?No. As I mentioned in that post: even if OC starts up automatically on boot, it may not actually be blessed. You'll need to rebless it, either with RequestBootVarRouting disabled or from a natively booted recovery environment.
I'd say it's unlikely.Could it be that I have to turn on VMM after all to install the update via OTA?
I will go back to 11.2.3 for now. When 11.3 is released to the public, I won't install it for now unless it works for me. If it doesn't work at all, I will skip 11.3 and then just update to 11.4 beta. Thanks for your efforts and the efforts of @startergo!I'd say it's unlikely.
Only one OC per computer. You have two (on the Big Sur and on the Catalina disks).
Remove OC from either disk, bless it properly.
bless --mount /Volumes/EFI --setBoot --file /Volumes/EFI/EFI/BOOT/BOOTx64.efi --verbose.
Where /Volumes/EFI is your actual boot EFI partition.
Select Big Sur from the OC boot picker and once booted set as default boot in System Preferences.
OK thanks so I guess its Normal.Yeah, PCIe probing takes forever.
It's NVME, by the way.
It's very common knowledge by now that the cMP (specifically 4,1/5,1) is not compatible with 11.3, especially if you're trying to boot from PCIe storage (SATA SSD on PCIe, NVMe, etc.). You need to stay at 11.2.3 until there is a solution (assuming there will be a solution).Okay so I wanted to install macOS Big Sur 11.3 RC from a fresh reinstall of macOS Big Sur 11.2.3 and OpenCore 0.6.8 (VMM was off). However, my cMP has now "hung up" and won‘t start anymore. In OpenCanopy it never showed me that the update was even being installed. I have already reseted the NVRAM, however this did not solve my problem. Does anyone have the same problem or know how I can solve this? Thanks in advance.
Apple upgraded IONVMeFamily.kext in 11.3b3, and this issue has persisted in 11.3b3/4/5/6/7/8/RC, and 11.4b1 - you need to run 11.2.3 until someone figures out a fix for this issue (IF someone figures out a fix).I'll give it a try, but that's weird isn't it? By the way, I have the same problem even if I try it with another SSD that also has a fresh install of macOS Big Sur 11.2.3. The problem has been with me since the early beta versions of 11.3. So far I have never been able to get macOS Big Sur 11.3 to run on my cMP even with OpenCore 0.6.7 not. Do you have macOS Big Sur 11.3 running?
Does this problem persist if OC is in an EFI on an older SATA drive for boot device selection with BS located on an NVME?Apple upgraded IONVMeFamily.kext in 11.3b3, and this issue has persisted in 11.3b3/4/5/6/7/8/RC, and 11.4b1 - you need to run 11.2.3 until someone figures out a fix for this issue (IF someone figures out a fix).
Yes - my test machine has OC and Mojave on an SSD in sled bay 1. I have an HDD in sled bay 4, and a SATA SSD on a PCIe card. The HDD updated and booted every version of 11.3 beta just fine, but the SSD on PCIe required several hard power cycles to install, and sometimes boots properly. Same machine. No USB3 card, only a GPU, original WiFi/BT.Does this problem persist if OC is in an EFI on an older SATA drive for boot device selection with BS located on an NVME?
Even with the PCIe drive present?The HDD updated and booted every version of 11.3 beta just fine
I don't think that the issue is present if it is not booted from an NVME drive with beta installed on it.Even with the PCIe drive present?
In that case, the issue with USB 3 cards is different, because those cards are certainly not being booted from.I don't think that the issue is present if it is not booted from an NVME drive with beta installed on it.
I have a USB card too, but whether it was plugged in or out it did not make a difference. But the dependencies will be affected if NVME fails:In that case, the issue with USB 3 cards is different, because those cards are certainly not being booted from.
Kernel Extensions in backtrace:
com.apple.iokit.IONVMeFamily(2.1)[204D1783-899F-353F-84CB-D7F6862AE265]@0xffffff8010001000->0xffffff801002afff
dependency: com.apple.driver.AppleEFINVRAM(2.1)[055F51C0-3FE9-31C1-8CC8-2ADC456E3C28]@0xffffff800ecf1000->0xffffff800ecfafff
dependency: com.apple.driver.AppleMobileFileIntegrity(1.0.5)[08C786C4-D093-3AE9-A378-7A716759967F]@0xffffff800eeab000->0xffffff800eec0fff
dependency: com.apple.iokit.IOPCIFamily(2.9)[368F5229-F604-3F4F-B877-05DAB5072243]@0xffffff80102c0000->0xffffff80102e8fff
dependency: com.apple.iokit.IOReportFamily(47)[21571942-1055-35FE-935F-544ADB4A43A5]@0xffffff80102f7000->0xffffff80102f9fff
dependency: com.apple.iokit.IOStorageFamily(2.1)[063C627D-49F0-356D-9B37-EE3D587BECC2]@0xffffff80103c3000->0xffffff80103d4fff
IOPCIFamily
Yes. Not only that, but after a successful boot from my SATA SSD on PCIe card, I copied many TB's to/from the SSD (to/from sled bay HDD's), and never a kernel panic or issue of any kind. At least in my case, with a mostly-stock 2010 Mac Pro, the only issue is BOOTING from PCIe storage. I'll soon be testing 11.4 on my primary machine, from a sled bay, with upgraded everything, so that could reveal more issues.Even with the PCIe drive present?
Right now I have an NVMe drive (BS boot) in a PCIe adapter. Is one solution to move the NVMe to a SATA adapter and put it in the drive bay? I'll wait to see if an OC solution comes about first - I have faith in you all.I have a USB card too, but whether it was plugged in or out it did not make a difference. But the dependencies will be affected if NVME fails:
Code:Kernel Extensions in backtrace: com.apple.iokit.IONVMeFamily(2.1)[204D1783-899F-353F-84CB-D7F6862AE265]@0xffffff8010001000->0xffffff801002afff dependency: com.apple.driver.AppleEFINVRAM(2.1)[055F51C0-3FE9-31C1-8CC8-2ADC456E3C28]@0xffffff800ecf1000->0xffffff800ecfafff dependency: com.apple.driver.AppleMobileFileIntegrity(1.0.5)[08C786C4-D093-3AE9-A378-7A716759967F]@0xffffff800eeab000->0xffffff800eec0fff dependency: com.apple.iokit.IOPCIFamily(2.9)[368F5229-F604-3F4F-B877-05DAB5072243]@0xffffff80102c0000->0xffffff80102e8fff dependency: com.apple.iokit.IOReportFamily(47)[21571942-1055-35FE-935F-544ADB4A43A5]@0xffffff80102f7000->0xffffff80102f9fff dependency: com.apple.iokit.IOStorageFamily(2.1)[063C627D-49F0-356D-9B37-EE3D587BECC2]@0xffffff80103c3000->0xffffff80103d4fff
Also Dortania guys concluded that the problem is more probably withIOPCIFamily
Every 11.3 beta version has upgraded and booted fine on my HDD in an HDD sled bay. Every 11.3 beta version has NOT upgrade OR booted fine from my SATA SSA on a PCIe card. It takes several hard power cycles to get the install to take on a PCIe card, and sometimes it boots fine. I'm running 11.4b1 on both, with the same results.Right now I have an NVMe drive (BS boot) in a PCIe adapter. Is one solution to move the NVMe to a SATA adapter and put it in the drive bay? I'll wait to see if an OC solution comes about first - I have faith in you all.