MP 1,1-5,1 Mac OS 11.3 has broken support for older Mac Pros

startergo · May 5, 2021

khronokernel said:
For anyone wanting to get better debug output, I've uploaded macOS 11.4 Beta 2's Kernel Debug Kit:

Kernel Debug Kit 11.4 Build 20F5055c : Free Download, Borrow, and Streaming : Internet Archive

Kernel Development Kit for macOS 11.4 Beta 2

archive.org

Don't have any machines personally with NVMe boot issues, though hope others find use for it

Direct link from the Apple developer account (no paid developer subscription needed)
Kernel Debug Kit 11.4 build 20F5055c.dmg

KevinClark · May 6, 2021

Maybe a solution one day

eVasilis · May 6, 2021

Syncretic said:
I have something I'd like to try, but I've hosed my BS 11.3 installation and I won't have time to reinstall until this weekend. Perhaps some kind (or curious, or desperate) soul will give this a try and report back:

First, you need to determine the Volume/Disk/Partition GUID of your Big Sur 11.3 (or 11.4 beta) boot volume.
In Terminal, run diskutil list and identify your boot volume - it should show up as "/dev/diskN (synthesized):", where N is some number, partition 0 is "APFS Container Scheme", there's a line that says "Physical Store diskXsY" (where X and Y are numbers), then partition 1 is an APFS Volume with a reecognizable name, presumably something like "Big Sur". There will be two such partitions, one named with the base name (e.g. "Big Sur"), the other with " - Data" appended to it (e.g. "Big Sur - Data"). Note the disk number ("/dev/diskN (synthesized)") and which partition number contains the base name WITHOUT " - Data" appended.
(Here's a concrete example:

Code:

/dev/disk5 (synthesized): #: TYPE NAME SIZE IDENTIFIER 0: APFS Container Scheme - +239.9 GB disk5 Physical Store disk3s2 1: APFS Volume Big Sur 11_1 - Data 5.3 GB disk5s1 2: APFS Volume Preboot 248.6 MB disk5s2 3: APFS Volume Recovery 613.6 MB disk5s3 4: APFS Volume VM 1.1 MB disk5s4 5: APFS Volume Big Sur 11_1 16.3 GB disk5s5 6: APFS Volume Update 413.7 KB disk5s6

In this example, the disk number is 5 (from "/dev/disk5"), partition 1 is the data partition ("Big Sur 11_1 - Data"), and partition 5 is the base ("Big Sur 11_1")).

Once you know the disk number and base partition number, run diskutil info diskNsY where N is your disk number and Y is the base partition number. You should see something like this:

Code:

Device Identifier: disk5s5 Device Node: /dev/disk5s5 Whole: No Part of Whole: disk5 Volume Name: Big Sur 11_1 Mounted: Yes Mount Point: /Volumes/Big Sur 11_1 Partition Type: 41504653-0000-11AA-AA11-00306543ECAC File System Personality: APFS Type (Bundle): apfs Name (User Visible): APFS Owners: Enabled OS Can Be Installed: Yes Booter Disk: disk5s2 Recovery Disk: disk5s3 Media Type: Generic Protocol: SATA SMART Status: Verified Volume UUID: D5711839-E42A-4782-9172-E0DF14B21CDF Disk / Partition UUID: D5711839-E42A-4782-9172-E0DF14B21CDF Disk Size: 239.9 GB (239855427584 Bytes) (exactly 468467632 512-Byte-Units) Device Block Size: 4096 Bytes Volume Total Space: 239.9 GB (239855427584 Bytes) (exactly 468467632 512-Byte-Units) Volume Used Space: 22.6 GB (22643900416 Bytes) (exactly 44226368 512-Byte-Units) (9.4%) Volume Free Space: 217.2 GB (217211527168 Bytes) (exactly 424241264 512-Byte-Units) (90.6%) Allocation Block Size: 4096 Bytes Read-Only Media: No Read-Only Volume: No Device Location: Internal Removable Media: Fixed Solid State: Yes Hardware AES Support: No Device Location: "Bay 1"

The values for "Volume UUID" and "Disk / Partition UUID" should be identical; copy that string (in this example, D5711839-E42A-4782-9172-E0DF14B21CDF).

Now, set your boot-args to include the following:

Code:

rd=uuid boot-uuid=The_UUID_you_just_copied

(using the diskutil output from above, our example would be rd=uuid boot-uuid=D5711839-E42A-4782-9172-E0DF14B21CDF). If you're running OpenCore, you probably need to edit config.plist and change boot-args there. (Remember to keep any debugging-relevant boot-args, such as -v or debug=0x100)

Once you have rd=uuid boot-uuid=Some_UUID in your boot-args, try booting Big Sur 11.3 and see if it makes any more progress than usual.

(For those who are interested: the first half or more of 11.3's IOFindBSDRoot() is identical to the binary of 11.1 and the source code for 11.2, but then it diverges. With limited time available, I'm hypothesizing that it's getting stuck trying to boot from either a RAMdisk or a network device, and by forcing it to use the correct disk partition, we might get past this particular hurdle. If setting the boot-uuid doesn't do it, there are still some other things to try.)

Thanks, and good luck. I should be able to check back in tomorrow.

IMPORTANT REMINDER: be sure you have a natively bootable partition available to you; if this (or any similar) experiment goes badly, you'll need to do a PRAM reset to get rid of the problematic boot-args, after which your OpenCore setup may or may not boot correctly.
(EDIT: even if this works, you'll still want to do a PRAM reset, since with rd=uuid boot-uuid=... in the boot-args, the only MacOS disk you'll be able to boot will be the BS 11.3 disk...)

I'd love to try that but as I am just an amateur, could you please guide me as to where/what/how to insert the volume uuid into oc config.plist?

Thanks!

Syncretic · May 6, 2021

Syncretic said:
(For those who are interested: the first half or more of 11.3's IOFindBSDRoot() is identical to the binary of 11.1 and the source code for 11.2, but then it diverges. With limited time available, I'm hypothesizing that it's getting stuck trying to boot from either a RAMdisk or a network device, and by forcing it to use the correct disk partition, we might get past this particular hurdle. If setting the boot-uuid doesn't do it, there are still some other things to try.)

While the boot-uuid test is still a valid one given the logs that have been reported, I must point out that the 11.3 IOFindBSDRoot() does not diverge from 11.1/11.2; I was sleep-deprived when making that inaccurate "observation."

eVasilis said:
I'd love to try that but as I am just an amateur, could you please guide me as to where/what/how to insert the volume uuid into oc config.plist?

Because this test could cause you some boot headaches if you can't reset boot-args and/or boot to something natively, I'll suggest that this experiment is not for "an amateur." I appreciate the offer, but if you need further instructions to do the experiment, I suspect you may have problems afterward, and neither of us really wants that (I won't be around much today to help you recover if you get stuck). Thanks, though.

(If no one manages to give this a try by this weekend, I'll do it after I reinstall and report back here.)

eVasilis · May 6, 2021

Syncretic said:
While the boot-uuid test is still a valid one given the logs that have been reported, I must point out that the 11.3 IOFindBSDRoot() does not diverge from 11.1/11.2; I was sleep-deprived when making that inaccurate "observation."

Because this test could cause you some boot headaches if you can't reset boot-args and/or boot to something natively, I'll suggest that this experiment is not for "an amateur." I appreciate the offer, but if you need further instructions to do the experiment, I suspect you may have problems afterward, and neither of us really wants that (I won't be around much today to help you recover if you get stuck). Thanks, though.

(If no one manages to give this a try by this weekend, I'll do it after I reinstall and report back here.)

Thanks for the concern but I am too curious not to try. I have two Mojave disks ready in case things go south: one in bay 4, the one I use to configure opencore, and one in a drawer waiting to go in bay one to reflash boot rom or start things over. Furthermore my EFI folder, the one that boots opencore, is backed up so if the worst comes to the worst I will only have to format my ssd and reinstall 11.2.3

Dayo · May 6, 2021

eVasilis said:
Thanks for the concern but I am too curious not to try.

As you have had the potential pitfalls explained and you still feel you will like to have stab at it, to implement via OC, look for <key>boot-args</key> in your config.plist and add rd=uuid boot-uuid=XXXXXXXX-XXXX-XXXX-XXXX-XXXXXXXXXXXX, where XXXXXXXX-XXXX-XXXX-XXXX-XXXXXXXXXXXX is your UUID, to whatever is there as a string value immediately below.

Make sure you have a tested and confirmed recovery strategy in place beforehand.

PS: Those using a RefindPlus chain-loading setup created with MyBootMgr can easily do this on one OpenCore instance and know they can always boot using another whatever happens.

The boot arg can also be set in RefindPlus if preferred (OpenCore better in this instance though). You basically have multiple paths and if one goes down, being mis-configured or whatever, you don't need to reset NVRAM and can just reboot and select another path way.

Macschrauber · May 6, 2021

I'll try the uuid thing this evening when I come home.

eVasilis · May 6, 2021

Dayo said:
As you have had the potential pitfalls explained and you still feel you will like to have stab at it, to implement via OC, look for <key>boot-args</key> in your config.plist and add rd=uuid boot-uuid=XXXXXXXX-XXXX-XXXX-XXXX-XXXXXXXXXXXX, where XXXXXXXX-XXXX-XXXX-XXXX-XXXXXXXXXXXX is your UUID, to whatever is there as a string value immediately below.

<key>boot-args</key> is not present in my config:

XML:

<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE plist PUBLIC "-//Apple//DTD PLIST 1.0//EN" "http://www.apple.com/DTDs/PropertyList-1.0.dtd">
<plist version="1.0">
<dict>
    <key>ACPI</key>
    <dict>
        <key>Add</key>
        <array/>
        <key>Delete</key>
        <array/>
        <key>Patch</key>
        <array>
            <dict>
                <key>Comment</key>
                <string>EHC1 to EH01</string>
                <key>Count</key>
                <integer>0</integer>
                <key>Enabled</key>
                <true/>
                <key>Find</key>
                <data>
                RUhDMQ==
                </data>
                <key>Limit</key>
                <integer>0</integer>
                <key>Mask</key>
                <data>
                </data>
                <key>OemTableId</key>
                <data>
                </data>
                <key>Replace</key>
                <data>
                RUgwMQ==
                </data>
                <key>ReplaceMask</key>
                <data>
                </data>
                <key>Skip</key>
                <integer>0</integer>
                <key>TableLength</key>
                <integer>0</integer>
                <key>TableSignature</key>
                <data>
                </data>
            </dict>
            <dict>
                <key>Comment</key>
                <string>EHC2 to EH02</string>
                <key>Count</key>
                <integer>0</integer>
                <key>Enabled</key>
                <true/>
                <key>Find</key>
                <data>
                RUhDMg==
                </data>
                <key>Limit</key>
                <integer>0</integer>
                <key>Mask</key>
                <data>
                </data>
                <key>OemTableId</key>
                <data>
                </data>
                <key>Replace</key>
                <data>
                RUgwMg==
                </data>
                <key>ReplaceMask</key>
                <data>
                </data>
                <key>Skip</key>
                <integer>0</integer>
                <key>TableLength</key>
                <integer>0</integer>
                <key>TableSignature</key>
                <data>
                </data>
            </dict>
        </array>
        <key>Quirks</key>
        <dict>
            <key>FadtEnableReset</key>
            <false/>
            <key>NormalizeHeaders</key>
            <false/>
            <key>RebaseRegions</key>
            <false/>
            <key>ResetHwSig</key>
            <false/>
            <key>ResetLogoStatus</key>
            <false/>
        </dict>
    </dict>
    <key>Booter</key>
    <dict>
        <key>MmioWhitelist</key>
        <array/>
        <key>Patch</key>
        <array/>
        <key>Quirks</key>
        <dict>
            <key>AllowRelocationBlock</key>
            <false/>
            <key>AvoidRuntimeDefrag</key>
            <false/>
            <key>DevirtualiseMmio</key>
            <false/>
            <key>DisableSingleUser</key>
            <false/>
            <key>DisableVariableWrite</key>
            <false/>
            <key>DiscardHibernateMap</key>
            <false/>
            <key>EnableSafeModeSlide</key>
            <false/>
            <key>EnableWriteUnprotector</key>
            <false/>
            <key>ForceBooterSignature</key>
            <false/>
            <key>ForceExitBootServices</key>
            <false/>
            <key>ProtectMemoryRegions</key>
            <false/>
            <key>ProtectSecureBoot</key>
            <true/>
            <key>ProtectUefiServices</key>
            <false/>
            <key>ProvideCustomSlide</key>
            <false/>
            <key>ProvideMaxSlide</key>
            <integer>0</integer>
            <key>RebuildAppleMemoryMap</key>
            <false/>
            <key>SetupVirtualMap</key>
            <false/>
            <key>SignalAppleOS</key>
            <false/>
            <key>SyncRuntimePermissions</key>
            <false/>
        </dict>
    </dict>
    <key>DeviceProperties</key>
    <dict>
        <key>Add</key>
        <dict>
            <key>PciRoot(0x0)/Pci(0x3,0x0)/Pci(0x0,0x0)</key>
            <dict>
                <key>agdpmod</key>
                <data>
                cGlrZXJhAA==
                </data>
                <key>rebuild-device-tree</key>
                <data>
                AA==
                </data>
                <key>shikigva</key>
                <data>
                UA==
                </data>
                <key>unfairgva</key>
                <data>
                AQAAAA==
                </data>
            </dict>
        </dict>
        <key>Delete</key>
        <dict/>
    </dict>
    <key>Kernel</key>
    <dict>
        <key>Add</key>
        <array>
            <dict>
                <key>Arch</key>
                <string>x86_64</string>
                <key>BundlePath</key>
                <string>Lilu.kext</string>
                <key>Comment</key>
                <string>Patch engine</string>
                <key>Enabled</key>
                <true/>
                <key>ExecutablePath</key>
                <string>Contents/MacOS/Lilu</string>
                <key>MaxKernel</key>
                <string></string>
                <key>MinKernel</key>
                <string></string>
                <key>PlistPath</key>
                <string>Contents/Info.plist</string>
            </dict>
            <dict>
                <key>Arch</key>
                <string>x86_64</string>
                <key>BundlePath</key>
                <string>WhateverGreen.kext</string>
                <key>Comment</key>
                <string>Video patches</string>
                <key>Enabled</key>
                <true/>
                <key>ExecutablePath</key>
                <string>Contents/MacOS/WhateverGreen</string>
                <key>MaxKernel</key>
                <string></string>
                <key>MinKernel</key>
                <string></string>
                <key>PlistPath</key>
                <string>Contents/Info.plist</string>
            </dict>
            <dict>
                <key>Arch</key>
                <string>x86_64</string>
                <key>BundlePath</key>
                <string>AppleMCEReporterDisabler.kext</string>
                <key>Comment</key>
                <string>Disable AppleMCEReporter</string>
                <key>Enabled</key>
                <true/>
                <key>ExecutablePath</key>
                <string></string>
                <key>MaxKernel</key>
                <string></string>
                <key>MinKernel</key>
                <string>19.0.0</string>
                <key>PlistPath</key>
                <string>Contents/Info.plist</string>
            </dict>
            <dict>
                <key>BundlePath</key>
                <string>RadeonBoost.kext</string>
                <key>Comment</key>
                <string></string>
                <key>Enabled</key>
                <true/>
                <key>ExecutablePath</key>
                <string></string>
                <key>MaxKernel</key>
                <string></string>
                <key>MinKernel</key>
                <string></string>
                <key>PlistPath</key>
                <string>Contents/Info.plist</string>
            </dict>
            <dict>
                <key>Arch</key>
                <string>x86_64</string>
                <key>BundlePath</key>
                <string>IO80211Mojave.kext</string>
                <key>Comment</key>
                <string>Broadcom Wifi Patch</string>
                <key>Enabled</key>
                <true/>
                <key>ExecutablePath</key>
                <string>Contents/MacOS/IO80211Mojave</string>
                <key>MaxKernel</key>
                <string></string>
                <key>MinKernel</key>
                <string>19.0.0</string>
                <key>PlistPath</key>
                <string>Contents/Info.plist</string>
            </dict>
            <dict>
                <key>BundlePath</key>
                <string>IO80211Mojave.kext/Contents/PlugIns/AirPortBrcm4331.kext</string>
                <key>Comment</key>
                <string>Broadcom Wifi Patch</string>
                <key>Enabled</key>
                <true/>
                <key>ExecutablePath</key>
                <string>Contents/MacOS/AirPortBrcm4331</string>
                <key>MaxKernel</key>
                <string></string>
                <key>MinKernel</key>
                <string>19.0.0</string>
                <key>PlistPath</key>
                <string>Contents/Info.plist</string>
            </dict>
            <dict>
                <key>Arch</key>
                <string>x86_64</string>
                <key>BundlePath</key>
                <string>USB-Map.kext</string>
                <key>Comment</key>
                <string>USB Map</string>
                <key>Enabled</key>
                <false/>
                <key>ExecutablePath</key>
                <string></string>
                <key>MaxKernel</key>
                <string></string>
                <key>MinKernel</key>
                <string></string>
                <key>PlistPath</key>
                <string>Contents/Info.plist</string>
            </dict>
        </array>
        <key>Block</key>
        <array/>
        <key>Emulate</key>
        <dict>
            <key>Cpuid1Data</key>
            <data>
            AAAAAAAAAAAAAAAAAAAAAA==
            </data>
            <key>Cpuid1Mask</key>
            <data>
            AAAAAAAAAAAAAAAAAAAAAA==
            </data>
            <key>DummyPowerManagement</key>
            <false/>
            <key>MaxKernel</key>
            <string></string>
            <key>MinKernel</key>
            <string></string>
        </dict>
        <key>Force</key>
        <array/>
        <key>Patch</key>
        <array/>
        <key>Quirks</key>
        <dict>
            <key>AppleCpuPmCfgLock</key>
            <false/>
            <key>AppleXcpmCfgLock</key>
            <false/>
            <key>AppleXcpmExtraMsrs</key>
            <false/>
            <key>AppleXcpmForceBoost</key>
            <false/>
            <key>CustomSMBIOSGuid</key>
            <false/>
            <key>DisableIoMapper</key>
            <false/>
            <key>DisableLinkeditJettison</key>
            <true/>
            <key>DisableRtcChecksum</key>
            <false/>
            <key>ExtendBTFeatureFlags</key>
            <false/>
            <key>ExternalDiskIcons</key>
            <false/>
            <key>ForceSecureBootScheme</key>
            <false/>
            <key>IncreasePciBarSize</key>
            <false/>
            <key>LapicKernelPanic</key>
            <false/>
            <key>LegacyCommpage</key>
            <false/>
            <key>PanicNoKextDump</key>
            <false/>
            <key>PowerTimeoutKernelPanic</key>
            <false/>
            <key>SetApfsTrimTimeout</key>
            <integer>9999999</integer>
            <key>ThirdPartyDrives</key>
            <false/>
            <key>XhciPortLimit</key>
            <false/>
        </dict>
        <key>Scheme</key>
        <dict>
            <key>FuzzyMatch</key>
            <false/>
            <key>KernelArch</key>
            <string>x86_64</string>
            <key>KernelCache</key>
            <string>Auto</string>
        </dict>
    </dict>
    <key>Misc</key>
    <dict>
        <key>BlessOverride</key>
        <array/>
        <key>Boot</key>
        <dict>
            <key>ConsoleAttributes</key>
            <integer>15</integer>
            <key>HibernateMode</key>
            <string>None</string>
            <key>HideAuxiliary</key>
            <true/>
            <key>LauncherOption</key>
            <string>Disabled</string>
            <key>LauncherPath</key>
            <string>Default</string>
            <key>PickerAttributes</key>
            <integer>16</integer>
            <key>PickerAudioAssist</key>
            <false/>
            <key>PickerMode</key>
            <string>External</string>
            <key>PickerVariant</key>
            <string>Modern</string>
            <key>PollAppleHotKeys</key>
            <true/>
            <key>ShowPicker</key>
            <true/>
            <key>TakeoffDelay</key>
            <integer>0</integer>
            <key>Timeout</key>
            <integer>10</integer>
        </dict>
        <key>Debug</key>
        <dict>
            <key>AppleDebug</key>
            <false/>
            <key>ApplePanic</key>
            <false/>
            <key>DisableWatchDog</key>
            <false/>
            <key>DisplayDelay</key>
            <integer>0</integer>
            <key>DisplayLevel</key>
            <integer>0</integer>
            <key>SerialInit</key>
            <false/>
            <key>SysReport</key>
            <false/>
            <key>Target</key>
            <integer>0</integer>
        </dict>
        <key>Entries</key>
        <array/>
        <key>Security</key>
        <dict>
            <key>AllowNvramReset</key>
            <false/>
            <key>AllowSetDefault</key>
            <true/>
            <key>ApECID</key>
            <integer>0</integer>
            <key>AuthRestart</key>
            <false/>
            <key>BlacklistAppleUpdate</key>
            <true/>
            <key>DmgLoading</key>
            <string>Signed</string>
            <key>EnablePassword</key>
            <false/>
            <key>ExposeSensitiveData</key>
            <integer>3</integer>
            <key>HaltLevel</key>
            <integer>2147483648</integer>
            <key>PasswordHash</key>
            <data>
            </data>
            <key>PasswordSalt</key>
            <data>
            </data>
            <key>ScanPolicy</key>
            <integer>0</integer>
            <key>SecureBootModel</key>
            <string>Disabled</string>
            <key>Vault</key>
            <string>Optional</string>
        </dict>
        <key>Tools</key>
        <array/>
    </dict>
    <key>NVRAM</key>
    <dict>
        <key>Add</key>
        <dict>
            <key>4D1EDE05-38C7-4A6A-9CC6-4BCCA8B38C14</key>
            <dict>
                <key>DefaultBackgroundColor</key>
                <data>
                AAAAAA==
                </data>
                <key>UIScale</key>
                <data>
                AQ==
                </data>
            </dict>
        </dict>
        <key>Delete</key>
        <dict>
            <key>4D1EDE05-38C7-4A6A-9CC6-4BCCA8B38C14</key>
            <array>
                <string>UIScale</string>
                <string>DefaultBackgroundColor</string>
            </array>
        </dict>
        <key>LegacyEnable</key>
        <false/>
        <key>LegacyOverwrite</key>
        <false/>
        <key>LegacySchema</key>
        <dict/>
        <key>WriteFlash</key>
        <false/>
    </dict>
    <key>PlatformInfo</key>
    <dict>
        <key>Automatic</key>
        <false/>
        <key>CustomMemory</key>
        <false/>
        <key>DataHub</key>
        <dict>
            <key>ARTFrequency</key>
            <integer>0</integer>
            <key>BoardProduct</key>
            <string></string>
            <key>BoardRevision</key>
            <data>
            </data>
            <key>DevicePathsSupported</key>
            <integer>0</integer>
            <key>FSBFrequency</key>
            <integer>0</integer>
            <key>InitialTSC</key>
            <integer>0</integer>
            <key>PlatformName</key>
            <string></string>
            <key>SmcBranch</key>
            <data>
            </data>
            <key>SmcPlatform</key>
            <data>
            </data>
            <key>SmcRevision</key>
            <data>
            </data>
            <key>StartupPowerEvents</key>
            <integer>0</integer>
            <key>SystemProductName</key>
            <string></string>
            <key>SystemSerialNumber</key>
            <string></string>
            <key>SystemUUID</key>
            <string></string>
        </dict>
        <key>Generic</key>
        <dict>
            <key>AdviseWindows</key>
            <false/>
            <key>MLB</key>
            <string></string>
            <key>MaxBIOSVersion</key>
            <false/>
            <key>ProcessorType</key>
            <integer>0</integer>
            <key>ROM</key>
            <data>
            </data>
            <key>SpoofVendor</key>
            <false/>
            <key>SystemMemoryStatus</key>
            <string>Auto</string>
            <key>SystemProductName</key>
            <string></string>
            <key>SystemSerialNumber</key>
            <string></string>
            <key>SystemUUID</key>
            <string></string>
        </dict>
        <key>PlatformNVRAM</key>
        <dict>
            <key>BID</key>
            <string></string>
            <key>FirmwareFeatures</key>
            <data>
            </data>
            <key>FirmwareFeaturesMask</key>
            <data>
            </data>
            <key>MLB</key>
            <string></string>
            <key>ROM</key>
            <data>
            </data>
            <key>SystemSerialNumber</key>
            <string></string>
            <key>SystemUUID</key>
            <string></string>
        </dict>
        <key>SMBIOS</key>
        <dict>
            <key>BIOSReleaseDate</key>
            <string></string>
            <key>BIOSVendor</key>
            <string></string>
            <key>BIOSVersion</key>
            <string>9999.0.0.0.0</string>
            <key>BoardAssetTag</key>
            <string></string>
            <key>BoardLocationInChassis</key>
            <string></string>
            <key>BoardManufacturer</key>
            <string></string>
            <key>BoardProduct</key>
            <string>Mac-7BA5B2D9E42DDD94</string>
            <key>BoardSerialNumber</key>
            <string></string>
            <key>BoardType</key>
            <integer>0</integer>
            <key>BoardVersion</key>
            <string></string>
            <key>ChassisAssetTag</key>
            <string></string>
            <key>ChassisManufacturer</key>
            <string></string>
            <key>ChassisSerialNumber</key>
            <string></string>
            <key>ChassisType</key>
            <integer>0</integer>
            <key>ChassisVersion</key>
            <string></string>
            <key>FirmwareFeatures</key>
            <data>
            </data>
            <key>FirmwareFeaturesMask</key>
            <data>
            </data>
            <key>PlatformFeature</key>
            <integer>-1</integer>
            <key>ProcessorType</key>
            <integer>0</integer>
            <key>SmcVersion</key>
            <data>
            </data>
            <key>SystemFamily</key>
            <string></string>
            <key>SystemManufacturer</key>
            <string></string>
            <key>SystemProductName</key>
            <string></string>
            <key>SystemSKUNumber</key>
            <string></string>
            <key>SystemSerialNumber</key>
            <string></string>
            <key>SystemUUID</key>
            <string></string>
            <key>SystemVersion</key>
            <string></string>
        </dict>
        <key>UpdateDataHub</key>
        <false/>
        <key>UpdateNVRAM</key>
        <false/>
        <key>UpdateSMBIOS</key>
        <true/>
        <key>UpdateSMBIOSMode</key>
        <string>Create</string>
        <key>UseRawUuidEncoding</key>
        <false/>
    </dict>
    <key>UEFI</key>
    <dict>
        <key>APFS</key>
        <dict>
            <key>EnableJumpstart</key>
            <false/>
            <key>GlobalConnect</key>
            <false/>
            <key>HideVerbose</key>
            <false/>
            <key>JumpstartHotPlug</key>
            <false/>
            <key>MinDate</key>
            <integer>0</integer>
            <key>MinVersion</key>
            <integer>0</integer>
        </dict>
        <key>AppleInput</key>
        <dict>
            <key>AppleEvent</key>
            <string>Builtin</string>
            <key>CustomDelays</key>
            <false/>
            <key>KeyInitialDelay</key>
            <integer>50</integer>
            <key>KeySubsequentDelay</key>
            <integer>5</integer>
            <key>PointerSpeedDiv</key>
            <integer>1</integer>
            <key>PointerSpeedMul</key>
            <integer>1</integer>
        </dict>
        <key>Audio</key>
        <dict>
            <key>AudioCodec</key>
            <integer>0</integer>
            <key>AudioDevice</key>
            <string></string>
            <key>AudioOut</key>
            <integer>0</integer>
            <key>AudioSupport</key>
            <false/>
            <key>MinimumVolume</key>
            <integer>0</integer>
            <key>PlayChime</key>
            <string>Disabled</string>
            <key>ResetTrafficClass</key>
            <false/>
            <key>SetupDelay</key>
            <integer>0</integer>
            <key>VolumeAmplifier</key>
            <integer>0</integer>
        </dict>
        <key>ConnectDrivers</key>
        <true/>
        <key>Drivers</key>
        <array>
            <string>OpenRuntime.efi</string>
            <string>OpenCanopy.efi</string>
        </array>
        <key>Input</key>
        <dict>
            <key>KeyFiltering</key>
            <false/>
            <key>KeyForgetThreshold</key>
            <integer>0</integer>
            <key>KeySupport</key>
            <false/>
            <key>KeySupportMode</key>
            <string>Auto</string>
            <key>KeySwap</key>
            <false/>
            <key>PointerSupport</key>
            <false/>
            <key>PointerSupportMode</key>
            <string></string>
            <key>TimerResolution</key>
            <integer>0</integer>
        </dict>
        <key>Output</key>
        <dict>
            <key>ClearScreenOnModeSwitch</key>
            <false/>
            <key>ConsoleMode</key>
            <string></string>
            <key>DirectGopRendering</key>
            <false/>
            <key>ForceResolution</key>
            <false/>
            <key>GopPassThrough</key>
            <false/>
            <key>IgnoreTextInGraphics</key>
            <false/>
            <key>ProvideConsoleGop</key>
            <true/>
            <key>ReconnectOnResChange</key>
            <false/>
            <key>ReplaceTabWithSpace</key>
            <false/>
            <key>Resolution</key>
            <string>Max</string>
            <key>SanitiseClearScreen</key>
            <false/>
            <key>TextRenderer</key>
            <string>BuiltinGraphics</string>
            <key>UgaPassThrough</key>
            <false/>
        </dict>
        <key>ProtocolOverrides</key>
        <dict>
            <key>AppleAudio</key>
            <false/>
            <key>AppleBootPolicy</key>
            <true/>
            <key>AppleDebugLog</key>
            <false/>
            <key>AppleFramebufferInfo</key>
            <false/>
            <key>AppleImageConversion</key>
            <false/>
            <key>AppleImg4Verification</key>
            <false/>
            <key>AppleKeyMap</key>
            <false/>
            <key>AppleRtcRam</key>
            <false/>
            <key>AppleSecureBoot</key>
            <false/>
            <key>AppleSmcIo</key>
            <false/>
            <key>AppleUserInterfaceTheme</key>
            <true/>
            <key>DataHub</key>
            <false/>
            <key>DeviceProperties</key>
            <false/>
            <key>FirmwareVolume</key>
            <false/>
            <key>HashServices</key>
            <false/>
            <key>OSInfo</key>
            <false/>
            <key>UnicodeCollation</key>
            <false/>
        </dict>
        <key>Quirks</key>
        <dict>
            <key>ActivateHpetSupport</key>
            <false/>
            <key>DisableSecurityPolicy</key>
            <false/>
            <key>EnableVectorAcceleration</key>
            <false/>
            <key>ExitBootServicesDelay</key>
            <integer>0</integer>
            <key>ForgeUefiSupport</key>
            <false/>
            <key>IgnoreInvalidFlexRatio</key>
            <false/>
            <key>ReleaseUsbOwnership</key>
            <false/>
            <key>ReloadOptionRoms</key>
            <false/>
            <key>RequestBootVarRouting</key>
            <true/>
            <key>TscSyncTimeout</key>
            <integer>0</integer>
            <key>UnblockFsConnect</key>
            <false/>
        </dict>
        <key>ReservedMemory</key>
        <array/>
    </dict>
</dict>
</plist>

Macschrauber · May 6, 2021

Syncretic said:
While the boot-uuid test is still a valid one given the logs that have been reported, I must point out that the 11.3 IOFindBSDRoot() does not diverge from 11.1/11.2; I was sleep-deprived when making that inaccurate "observation."

Because this test could cause you some boot headaches if you can't reset boot-args and/or boot to something natively, I'll suggest that this experiment is not for "an amateur." I appreciate the offer, but if you need further instructions to do the experiment, I suspect you may have problems afterward, and neither of us really wants that (I won't be around much today to help you recover if you get stuck). Thanks, though.

(If no one manages to give this a try by this weekend, I'll do it after I reinstall and report back here.)

set boot-args with the uuid and tried it

1. thru RefindPlus
2. vanilla, just thru the bootpicker

With both booting methods it got into a Kernel Panic what I could see with debug=0x100

without debug boot-arg it leads into a boot - kp - boot loop

what needed a single nvram reset to get out.

startergo · May 6, 2021

Macschrauber said:
set boot-args with the uuid and tried it

1. thru RefindPlus
2. vanilla, just thru the bootpicker

With both booting methods it got into a Kernel Panic what I could see with debug=0x100

without debug boot-arg it leads into a boot - kp - boot loop

what needed a single nvram reset to get out.

View attachment 1770755

Add keepsyms=1 to the boot arguments, because it is not seen where the crash occurs and the symbols are missing too

Macschrauber · May 6, 2021

startergo said:
Add keepsyms=1 to the boot arguments, because it is not seen where the crash occurs and the symbols are missing too

same with keepsyms=1
seems to look the same

Dayo · May 6, 2021

eVasilis said:
<key>boot-args</key> is not present in my config

Yes. You are not setup for this.

You need to look into the OC manual for where the boot-args key goes and insert.
This is however out of scope here.

Macschrauber · May 6, 2021

If I put this SSD into a sata-usb bridge than I just get an smc error (am on 4.1, btw).

SMC reset wouldnt change it.

Syncretic · May 6, 2021

Macschrauber said:
set boot-args with the uuid and tried it

1. thru RefindPlus
2. vanilla, just thru the bootpicker

With both booting methods it got into a Kernel Panic what I could see with debug=0x100

without debug boot-arg it leads into a boot - kp - boot loop

(I’m on my iPhone, trying to look at source code. I’m either obsessed or deranged, possibly both.)

I got it wrong, it’s the uuid from the “- Data” partition that’s needed, not the base partition. I’ll try to reinstall tonight so you folks don’t need to suffer from my mistakes.

Macschrauber · May 6, 2021

Syncretic said:
(I’m on my iPhone, trying to look at source code. I’m either obsessed or deranged, possibly both.)

I got it wrong, it’s the uuid from the “- Data” partition that’s needed, not the base partition. I’ll try to reinstall tonight so you folks don’t need to suffer from my mistakes.

Dont mind, I am prepared and will test it with the data uuid

and there it sits and keep hanging, no forbidden sign after a while.

khronokernel · May 6, 2021

Macschrauber said:
same with keepsyms=1
seems to look the same

View attachment 1770820

Please enable Kernel -> Quirks -> PanicNoKextDump
Lets you see the actual kexts and symbols that crashed (ofc still keep keepsyms=1)

Macschrauber · May 6, 2021

khronokernel said:
Please enable Kernel -> Quirks -> PanicNoKextDump
Lets you see the actual kexts and symbols that crashed (ofc still keep keepsyms=1)

did that, but as it only kp when the uuid of the SystemVolume was given it gives no information when the uuid of the DataVolume is set.

just sitting there as before in 4 lines of swcrypto_threadpool_worker_thread:1488

eVasilis · May 6, 2021

Syncretic said:
(I’m on my iPhone, trying to look at source code. I’m either obsessed or deranged, possibly both.)

I got it wrong, it’s the uuid from the “- Data” partition that’s needed, not the base partition. I’ll try to reinstall tonight so you folks don’t need to suffer from my mistakes.

No joy, be it the the base or the data partition I hangs with this:

eVasilis · May 6, 2021

Dayo said:
Yes. You are not setup for this.

You need to look into the OC manual for where the boot-args key goes and insert.
This is however out of scope here.

Thanks!

Syncretic · May 6, 2021

“Curiouser and curiouser!” cried Alice (she was so much surprised, that for the moment she quite forgot how to speak good English)

Regarding the 11.3 boot hangs, I have a list of things I want to try (boot-args and others), so I decided that sleep is overrated and I'll get back onto this tonight. I haven't gotten to try a single thing from my list, however, because events took me in another direction. I now offer a few more data points, although I'm not yet certain of their value.

First things first: my basic test setup is the same as before. I reinstalled Big Sur 11.3 from the same flash drive, to the same target drive, as I did the last time. The only hardware-related difference seems irrelevant, but I'll note it here for completeness: for reasons unrelated to this test, I had my Mac unplugged, with the CPU tray removed, for about 10 minutes prior to the events that follow (basically, a thorough SMC reset). No actual hardware changes were made. The software-related differences involve me fiddling with OpenCore and boot-args; for simplicity, I set WriteFlash to true and removed boot-args from both the Add and Delete lists. I also changed csr-active-config from to AAAAAA== (default "all off") to /w8AAA== (Big Sur "all off").

As before, for initial testing I used only two drives - the SATA SSD containing 11.3 and the NVMe drive (which happens to contain Mojave, but that shouldn't be relevant). The Sonnet Allegro was also installed for all tests. Right off the bat, I accidentally deleted the boot-args variable, so there were no debug messages - but it booted right up. I didn't expect that, so I rebooted again - and it worked. I did this 10 more times (total of 12 in a row), all with no boot-args whatsoever, no problems. OK, I thought, maybe the debug messages slow things down and cause the race - so I started experimenting with different boot-args. I couldn't make it fail. (This is in sharp contrast to my tests last weekend.)

From there, I started tinkering with the disk drives, and found something interesting. Normally, I have 7 drives in that system - 2 spinners, 4 SATA SSDs, and 1 NVMe. Tonight's testing (I'm up to 51 reboots so far - turns out that poweron-boot-login-shutdown takes ~79 seconds if I'm diligent) has shown me the following (as before, I can only make assertions about my own system; your mileage may vary):

With one SATA SSD (containing 11.3), one NVMe, and no other drives, I cannot reproduce the boot hang, regardless of (non-exotic) boot-args. Neither the NVMe slot nor the SATA port seem to make any difference, it just works.
With the 11.3 SATA SSD, one NVMe, and one or two more drives (up to a total of four, including the NVMe), I cannot reproduce the boot hang (other than under one condition, involving another Big Sur disk, which is noted below). The additional drives can be SSD or spinners, on any combination of ports; the bootability of the drives (I have both data and bootable drives in the mix) also appears to be irrelevant.
With the 11.3 SATA SSD, one NVMe, and three or more additional drives, the boot hang appears. SSD/spinner doesn't matter, nor does SATA port. I haven't done enough reboots under these conditions to make many assertions, but it's occurred in 100% of samples thus far, so it seems to be a high probability event.
Regardless of the number of drives, if one of the drives is another Big Sur installation (I have 11.1 on one of my SSDs), the boot hang appears certain to occur. I find this one particularly interesting, since we know that APFS on Big Sur is somewhat different from APFS on Catalina and earlier, so the time required to initialize the drive is likely different as well (which further supports the race condition theory). As with the "too many drives" scenario, I haven't done enough testing on this condition to make many assertions, but it appears to be a high probability event.

While that's all well and good, I think it describes symptoms more than causes. The addition of enough disk drives, or the addition of a second Big Sur drive, changes the timing of the boot sequence such that the hang occurs. In the coming days, I will spend what time I can trying to work through my list of arcane boot-args and other kernel tweaks that will hopefully point us in the right direction (or possibly even provide a solution). First, though, to sleep: perchance to dream...

startergo · May 6, 2021

Syncretic said:
With the 11.3 SATA SSD, one NVMe, and one or two more drives (up to a total of four, including the NVMe), I cannot reproduce the boot hang

I will try this to check for repeatability.

Syncretic said:
The additional drives can be SSD or spinners, on any combination of ports; the bootability of the drives (I have both data and bootable drives in the mix) also appears to be irrelevant.

I have 2 SSD's in a PCI Sonnet Tempo SSD Pro Plus. Will that be the same?

Syncretic · May 6, 2021

startergo said:
I have 2 SSD's in a PCI Sonnet Tempo SSD Pro Plus. Will that be the same?

I tend to doubt it, although I really don't know. The Tempo adds a SATA III controller into the mix, where I'm just using the Mac's backplane and ODD SATA connections. If the problem is PCIe-centric, which seems like a significant possibility at this point, the Tempo's controller could play a role in the race condition (in either direction, faster or slower). Similarly, if the problem is APFS-centric, the faster (but non-native) controller could swing things either way.

h9826790 · May 6, 2021

Syncretic said:
Syncretic said:

Regarding the 11.3 boot hangs, I have a list of things I want to try (boot-args and others), so I decided that sleep is overrated and I'll get back onto this tonight. I haven't gotten to try a single thing from my list, however, because events took me in another direction. I now offer a few more data points, although I'm not yet certain of their value.

First things first: my basic test setup is the same as before. I reinstalled Big Sur 11.3 from the same flash drive, to the same target drive, as I did the last time. The only hardware-related difference seems irrelevant, but I'll note it here for completeness: for reasons unrelated to this test, I had my Mac unplugged, with the CPU tray removed, for about 10 minutes prior to the events that follow (basically, a thorough SMC reset). No actual hardware changes were made. The software-related differences involve me fiddling with OpenCore and boot-args; for simplicity, I set WriteFlash to true and removed boot-args from both the Add and Delete lists. I also changed csr-active-config from to AAAAAA== (default "all off") to /w8AAA== (Big Sur "all off").

As before, for initial testing I used only two drives - the SATA SSD containing 11.3 and the NVMe drive (which happens to contain Mojave, but that shouldn't be relevant). The Sonnet Allegro was also installed for all tests. Right off the bat, I accidentally deleted the boot-args variable, so there were no debug messages - but it booted right up. I didn't expect that, so I rebooted again - and it worked. I did this 10 more times (total of 12 in a row), all with no boot-args whatsoever, no problems. OK, I thought, maybe the debug messages slow things down and cause the race - so I started experimenting with different boot-args. I couldn't make it fail. (This is in sharp contrast to my tests last weekend.)

From there, I started tinkering with the disk drives, and found something interesting. Normally, I have 7 drives in that system - 2 spinners, 4 SATA SSDs, and 1 NVMe. Tonight's testing (I'm up to 51 reboots so far - turns out that poweron-boot-login-shutdown takes ~79 seconds if I'm diligent) has shown me the following (as before, I can only make assertions about my own system; your mileage may vary):

With one SATA SSD (containing 11.3), one NVMe, and no other drives, I cannot reproduce the boot hang, regardless of (non-exotic) boot-args. Neither the NVMe slot nor the SATA port seem to make any difference, it just works.

With the 11.3 SATA SSD, one NVMe, and one or two more drives (up to a total of four, including the NVMe), I cannot reproduce the boot hang (other than under one condition, involving another Big Sur disk, which is noted below). The additional drives can be SSD or spinners, on any combination of ports; the bootability of the drives (I have both data and bootable drives in the mix) also appears to be irrelevant.

With the 11.3 SATA SSD, one NVMe, and three or more additional drives, the boot hang appears. SSD/spinner doesn't matter, nor does SATA port. I haven't done enough reboots under these conditions to make many assertions, but it's occurred in 100% of samples thus far, so it seems to be a high probability event.

Regardless of the number of drives, if one of the drives is another Big Sur installation (I have 11.1 on one of my SSDs), the boot hang appears certain to occur. I find this one particularly interesting, since we know that APFS on Big Sur is somewhat different from APFS on Catalina and earlier, so the time required to initialize the drive is likely different as well (which further supports the race condition theory). As with the "too many drives" scenario, I haven't done enough testing on this condition to make many assertions, but it appears to be a high probability event.

While that's all well and good, I think it describes symptoms more than causes. The addition of enough disk drives, or the addition of a second Big Sur drive, changes the timing of the boot sequence such that the hang occurs. In the coming days, I will spend what time I can trying to work through my list of arcane boot-args and other kernel tweaks that will hopefully point us in the right direction (or possibly even provide a solution). First, though, to sleep: perchance to dream...

Click to expand...

May I know if all your test drivers are in APFS? Or just the macOS drive is APFS, and the extra data drives may be in HFS+ or something else?

I wonder if "the number of hard drive" is the variable. Or, "the number of APFS hard drive (or even container)" is the variable to trigger the problem.

RLTechs1 · May 6, 2021

Ok so now that I have spent a ton of time catching up on this thread and a couple of others

...

My specs are in my sig, if you need screen shots I can't some and upload them, but I think there are plenty on here. I am using using Martin's 0.6.9 package, and I haven't modified it much yet, as I am reading through still the OpenCore configuration manual. I DO NOT have any NVMe devices, so I can't be much help on that issue.

The issues I am having currently are...

When booting from a powered off state, machine hangs with the progress bar not moving. I can at this point power off machine and reset NVRAM, this will cause a screen (after almost 3 minuets) with a circle and slash as well as a message to visit apple startup help page. Once I have that screen I can power off and it will boot and load to the login screen. Upon login it loads up ok, but I do get the "your computer was restarted because of an error" dialog box. I click cancel and it loads up, albeit quite a bit slower that 11.2 did running OC 0.6.6
I seem to get the spinning ball a lot when opening programs, or trying to connect to video sites, or even when saving documents from a program. When I am patient these eventually go away, but it is a continual issue.
If I do a restart, not shut down, the machine usually (80-90% of the time) reboots to the login screen successfully and upon login in I have the issues in #2 above. If it does not restart properly, I do a NVRAM reset and as in #1 above wait for the apple error screen, then power off and back on and it loads up.

Issues I did have that are now so far resolved...

The mouse was leaving trails and when moving a window it would move, however it was stuttering (don't know how else to explain it) and video was noticeably choppy. I had read on one of these threads that if you have an RX580 to disable the DirectGopRendering (set to false), so I changed this in my config and for the last 13 hours this problem has not seemed to resurface.
Last night, my USB drives kept randomly dropping and giving the "need to eject properly" message. Which made no sense to me as it showed up fine with no errors in system report. In addition about half the time my RAID would not show up. If I checked on the RAID set in disk utility, it showed a 'member missing'. I read up some more about the NVMe issue a lot of you are having, as well as checked some diagrams on the switching for PCIe slots 3 & 4. Originally my RX580 was in slot 1 with my usb card in slot 4. So opened up to move things around and now my Usb card is in slot 1 with my RX5880 in slot 2. My machine has been running all day with only a couple restarts and all my drives have continually showed up and are working as they did before in 11.2, including the RAID set. External Drives have been stable and functional all day so I think this one is fixed.

On a side note, my cMP at my office has a off brand USB3 card in slot 4 and seems to have no issues whatsoever with anything plugged into it. The only noticeable difference between the cards is the one at work requires a SATA power cable attached to it, and the Sonnet one does not. So I am wonder ing if maybe the issue in slots 3 and 4 are power issues. Maybe without the operational switch there is not enough voltage in those last two slots to power much of anything. Just a thought.

BTW a huge shout out to h9826790 for the easy packages. Yes I am still working on building an exact customized one for my machine, but I would not have any progress without Martin's packages for reference.

Next I will be trying to figure out the issues I still have. Tonight I am building an OC boot drive on USB stick to play with and make changes to. This way if I make something worse I can pull the USB stick and boot from my drives

JohnD · May 6, 2021

Interesting findings, for sure. I'll play with drives a bit more this weekend, but wanted to let everyone know my system config when I first started experiencing this issue with 11.3b3 (in my primary system, with bootable backup, and of course I rolled back to 11.2.3).

In my primary system, I have a dual SATA SSD PCIe card - the first SSD is Big Sur, and the other is partitioned into a volume for my virtual machines, and a volume for Time Machine. I have 4x 6TB HDD's in the drive bays, and 2x BD-R's in the optical bays. So, only one OS drive was in the system, but 2 APFS SSD's (the HDD's are SoftRAID-5 HFS+).

At the time, I also tested with a SATA SSD in sled bay 1 (removed all 4x HDD's), so that would have made 3x APFS SSD's, and naturally had issues so migrated testing to my test machine (where I've been since 11.3b3).

On the test system, I'll remove all drives from the drive bays, and leave the SATA SSD on PCIe (11.3.1), so it will be the only drive left in the system. Looking forward to the boot-args testing...

MP 1,1-5,1 Mac OS 11.3 has broken support for older Mac Pros

macrumors 603

macrumors 6502

macrumors 6502

macrumors 6502

macrumors 6502

macrumors 68020

macrumors 68030

macrumors 6502

macrumors 68030

macrumors 603

macrumors 68030

macrumors 68020

macrumors 68030

macrumors 6502

macrumors 68030

macrumors 6502

macrumors 68030

macrumors 6502

macrumors 6502

macrumors 6502

macrumors 603

macrumors 6502

macrumors P6

macrumors newbie

macrumors regular

Our Staff