He wants to have two functioning systems on two separate volumes, how are you going to create a new volume for the new system without shrinking the existing volume?
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.
macOS 12 Monterey on Unsupported Macs Thread
- Thread starter khronokernel
- WikiPost WikiPost
- Start date
- Sort by reaction score
- Status
I use Disk Utilities. Have done it (creating and removing volumes) many times. That's provided that the disk is created as APFS. APFS supports creating new volumes automatically. All APFS volumes shares the disk space within a disk. Kind of cool actually.
As I've posted earlier, my 1 TB SSD disk has Monterey and High Sierra installed in their respective APFS volumes. In fact, my 1TB SSD has 3 volumes; named Macintosh HD (Monterey), High Sierra and Data. I can select to boot from Macintosh HD (into Monterey) or High Sierra from within OCLP boot disk picker. All 3 volumes shows the same amount of free disk space.
Have not ventured into macOS Ventura as there's no graphic acceleration yet(?) for pre-Haswell CPU running Kepler GTX768M GPU.
I have two 2012 MBPs that dual boot native Catalina and OCLP Monterey—exactly what you’re asking about, I believe. No problems to report. As I’ve said many times on this thread, my 2012 MBPs and my 2012 hackintosh all run Monterey with OCLP as well as my 2020 Intel MacBook Air.
On the 2012 MBPs, I can boot Catalina either through OCLP or without. I’ve noticed no problems with Catalina when booting through OCLP. Both OCLP Monterey and native Catalina are on the same SSD—no partition but different volumes.
”Order of install” may be important to get this to work well.
On a fresh SSD, first I installed Catalina natively. Then installed Monterey on a separate volume with OCLP.
I don’t know what happens / if it works when one installs Monterey with OCLP first,
and then Catalina natively second.
Last edited:
In my experience, I would argue that in @SPJones case, it is in fact best practice to dual boot native Catalina with an OCLP install for the machine in question. So, unfortunately I think that there’s some misinformation going around this thread right now.
If something goes sideways with the OCLP install, then SPJones will have Catalina to use as a back up. Catalina is also the last supported OS for the iMac in question. Further, @SPJones , have you ever installed Catalina on this iMac? All of the latest firmware updates for your machine are bundled with the Catalina security updates. OCLP will not work properly on your device until you have at least once installed Catalina and run the latest security updates.
If something goes sideways with the OCLP install, then SPJones will have Catalina to use as a back up. Catalina is also the last supported OS for the iMac in question. Further, @SPJones , have you ever installed Catalina on this iMac? All of the latest firmware updates for your machine are bundled with the Catalina security updates. OCLP will not work properly on your device until you have at least once installed Catalina and run the latest security updates.
I cant say as the concept is the same. The hidden EFI drive which helps in booting the Mac will be effected though. This issue is only if you have used DosDude's patching method for Catalina along with OCLP for Monterey. However, if you only use OCLP for say 2 different OS systems on the same SSD then there is no issue.
But thanks anyway! Do you think a Linux dual boot would work instead (alongside OCLP)?
Like some pointed out it also depends how the install goes and is subject to different configurations. I had Catalina patched with Dosdude's patcher and used for a long time. I thought of an upgrade and decided to go for Bigsur then using OCLP, so I created another Container Volume on my SSD and Installed it. It worked for sometime but then I started getting issues at boot level . Erased bigsur and my mac was back to normal.
Now as you can see in my signature I am on Ventura after clean wipe of my SSD. My hardware firmware is already up to date with past Catalina updates and as my machine is decade old I will not be going for any changes. Ventura works very fast, its smooth, and better than previous systems. Cheers
Last edited:
OK, either I don't get it or we are talking different things here.
Let's say I have my laptop with a 256GB GPT disk with the simplest setup: the whole disk (will be container, disk, volumes of the disk). So I got, like, 100GB used space and 156GB free space. My Macintosh HD indicates "156 GB free". If I created another volume ("Catalina") I will only by able to make it 156GB, as it will be placed within the free space. Therefore my Macintosh HD will indicate 0 free GBytes. Is it right?
You got it half right. Both volumes will now see 156GB of free disk space. As disk space gets used up by either volumes, both will show similar decrease. The free space are shared across all APFS volumes. Once you remove an existing volume, the disk space used by the removed volume gets returned back to the pool, and all volumes will then see an increase in disk space. That's what I thought cool about APFS volumes. Very different from HFS+ where it is rigid.
Edit: Replaced HPFS with HFS+. Got confused.
Watching the recent discussions about how OpenCore works reminds me of myself learning to play the guitar: I learned to play without learning to read music. I soon realized that my learning was limited until I learned to read music.
Read this to learn the OpenCore boot process
Guessing at answers about OpenCore is leading to a lot of misinformation. Would be best to refer to the documentation.
Read this to learn the OpenCore boot process
Guessing at answers about OpenCore is leading to a lot of misinformation. Would be best to refer to the documentation.
Unfortunately OC documentation is quite vague and since it is aimed at PCs, not Macs, I personally do not find it really useful for troubleshooting. Not to mention in some cases OC simply does not do what the documentation states it should do. YMMV of course.
Agreed that the documentation is good, but
it is not a guess if one is describing what works on comparable systems to @SPJones , and it has been working for nearly a year now. What I personally described in posts 8,530 and 8,531 is a fact, not a guess.
@SPJones , let us know what ends up working for you. Cheers.
Okay this fixed it for me:
Revert Root Patches
Reboot
Delete all old (pre 2023) extensions from /Library/Extensions
Reinstall Root Patches - no error this time
Reboot
Display patches now applied
I tried deleting the old extensions and just reinstalling root patches without without reverting root patches first but that still resulted in the error.
So glad this worked as otherwise a clean install was next on the cards.
Wait for release version. Until release it does not make a lot of sense to install, since Apple changes things back and forth.
Whats the best way to upgrade an unsupported Mac without wipe? (when no upgrade found in About this Mac)
Ive already tried a clean install test and it works on the 2011 Mac mini, but now I'm all sorted in Big Sur because graphics worked better, id rather not reinstall everything
Can I just boot off the Legacy patcher usb installer and upgrade that way?
Ive already tried a clean install test and it works on the 2011 Mac mini, but now I'm all sorted in Big Sur because graphics worked better, id rather not reinstall everything
Can I just boot off the Legacy patcher usb installer and upgrade that way?
Hi,
On my MBP 2011 -> no issue with 12.6.4 but big issue with Safari 16.4.
All pages are blank or not complete.
I tried to back to 16.3, but issues with loading the pages (nothing works).
I don't know how to get Safari without issues :
- go to Ventura (but known issue with the intel HD Graphics 3000)
- make a bootable USB with the full 12.6.4 to get a new Safari 16.3 (and never install 16.4)
On my MBP 2011 -> no issue with 12.6.4 but big issue with Safari 16.4.
All pages are blank or not complete.
I tried to back to 16.3, but issues with loading the pages (nothing works).
I don't know how to get Safari without issues :
- go to Ventura (but known issue with the intel HD Graphics 3000)
- make a bootable USB with the full 12.6.4 to get a new Safari 16.3 (and never install 16.4)
