I've been having a problem where my High Sierra installation seems to be corrupting my Big Sur installation. I have each operating system installed on a separate SSD, and I am using the latest version of OCLP. I tried updating my Big Sur installation from 11.2.3 to 11.3, but the process kept getting hung-up partway through. When booting into Big Sur, I would often see the gray "prohibited" symbol show up, or the loading bar would just hang halfway through. I was reading the OCLP GitHub issues and found something useful, though: https://github.com/dortania/OpenCore-Legacy-Patcher/issues/157
It sounds like I was experiencing a problem where High Sierra was corrupting the SecureBoot image of Big Sur each time I booted between my two drives. This would explain why when I was in High Sierra, the Big Sur Drive appeared as several different and inaccessible partitions (the normal 11.3 drive with"- Data" appended to it, and another called "Update").
My solution to fix this, which seems to be working so far (I am writing this from my Big Sur drive) was to first prevent all of the Big Sur volumes from auto-mounting at startup on High Sierra. This was accomplished by adding each volume UUID to a blocklist in High Sierra: https://discussions.apple.com/docs/DOC-7942
I then needed to reset the PRAM and SMC ---rebooting into High Sierra after resetting the PRAM, of course, the Big Sur disks weren't mounted by the OS (yay!). I was able to select my Catalina Loader SD card within the High Sierra System Preferences, and boot into OCLP automatically. After selecting Big Sur as my primary boot disk in OCLP, the computer loaded up the Big Sur SSD and finished the 11.3 delta update that it had been working on the day before. (I should also mention that I had to restart my computer about a dozen times throughout this process before things started behaving.)
I hope that this will prove to be a good long-term solution, and I will update this post if things stop working again. I did not disable SecureBoot as suggested in the OCLP GitHub Issue, but the 11.3 updates worked, so hopefully, I'm in the clear. I know that I could sort of fix things by only using one OS (Big Sur), but sometimes I like running legacy programs on my computer, as well as using target disk mode, so I want 10.13 installed. Not to mention the fact that High Sierra is also useful for repairing things when I corrupt Big Sur by mistake...
It sounds like I was experiencing a problem where High Sierra was corrupting the SecureBoot image of Big Sur each time I booted between my two drives. This would explain why when I was in High Sierra, the Big Sur Drive appeared as several different and inaccessible partitions (the normal 11.3 drive with"- Data" appended to it, and another called "Update").
My solution to fix this, which seems to be working so far (I am writing this from my Big Sur drive) was to first prevent all of the Big Sur volumes from auto-mounting at startup on High Sierra. This was accomplished by adding each volume UUID to a blocklist in High Sierra: https://discussions.apple.com/docs/DOC-7942
I then needed to reset the PRAM and SMC ---rebooting into High Sierra after resetting the PRAM, of course, the Big Sur disks weren't mounted by the OS (yay!). I was able to select my Catalina Loader SD card within the High Sierra System Preferences, and boot into OCLP automatically. After selecting Big Sur as my primary boot disk in OCLP, the computer loaded up the Big Sur SSD and finished the 11.3 delta update that it had been working on the day before. (I should also mention that I had to restart my computer about a dozen times throughout this process before things started behaving.)
I hope that this will prove to be a good long-term solution, and I will update this post if things stop working again. I did not disable SecureBoot as suggested in the OCLP GitHub Issue, but the 11.3 updates worked, so hopefully, I'm in the clear. I know that I could sort of fix things by only using one OS (Big Sur), but sometimes I like running legacy programs on my computer, as well as using target disk mode, so I want 10.13 installed. Not to mention the fact that High Sierra is also useful for repairing things when I corrupt Big Sur by mistake...