Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.

Stefdar

macrumors regular
Original poster
Feb 4, 2012
139
163
Is it possible to install Monterey on a separate (internal) partition and dual boot with Big Sur? (I am thinking not but thought I 'd ask).
 
  • Like
Reactions: !!!
Same as Intel. Create a new APFS volume and install it there.
I'm strongly considering doing this as an easy way to test my workflow before committing to installing it on my primary volume.
 
Create a new APFS volume and install it there.
Not a VOLUME, that is highly risky. Create a new APFS container/partition and install it there. Better on external disk.

Is it possible to install Monterey on a separate (internal) partition and dual boot with Big Sur?
Possibly. But it is risky unless you know that Monterey and Big Sur have compatible Recovery and other boot partitions. Let someone else do it first. I don't think any of the previous responses are based on direct experience.

And don't yet unless you are a developer and need to test under macOS 12. Wait for a public beta, which will be much more stable.
 
Not a VOLUME, that is highly risky. Create a new APFS container/partition and install it there. Better on external disk.

what i mean is that to create a new container you have to click on the + sign next to Volume in disk utility.
 
what i mean is that to create a new container you have to click on the + sign next to Volume in disk utility.
That creates a new volume within the existing container. To create new container/partition you need to boot to recovery mode and use Disk Utility, then select the device and click partition.

Anyway, I suspect this is moot as far as this thread (M1, not Intel) goes. Other threads suggest that changing from Monterey to BS requires DFU mode.
 
That creates a new volume within the existing container. To create new container/partition you need to boot to recovery mode and use Disk Utility, then select the device and click partition.

Anyway, I suspect this is moot as far as this thread (M1, not Intel) goes. Other threads suggest that changing from Monterey to BS requires DFU mode.
That's what I am afraid of. With Intel Macs it was easy, you could create just a volume on the internal disk and install, and delete it in case you didn't like it, even though the recovery partition remained from the new betas. In M1's case I am not so sure if you can dual boot Big Sur afterwards.
 
That's what I am afraid of. With Intel Macs it was easy, you could create just a volume on the internal disk and install, and delete it in case you didn't like it, even though the recovery partition remained from the new betas. In M1's case I am not so sure if you can dual boot Big Sur afterwards.
I’m dual booting Monterey and Big Sur. All I did was add a new volume, default choices, two clicks. Installed Monty there and boot into it. When the GM is released I just delete that volume and upgrade Big Sur.
 
I’m dual booting Monterey and Big Sur. All I did was add a new volume, default choices, two clicks. Installed Monty there and boot into it. When the GM is released I just delete that volume and upgrade Big Sur.
Are you on an M1?
 
I was afraid to install on my internal drive on my M1 mac mini. Instead installed on 2TB Thunderbolt 3 external SSD. Dual boot works great by changing startup diisk in system preferences. So far so good, but I know as updates arrive the "fun" will start
 
I was afraid to install on my internal drive on my M1 mac mini. Instead installed on 2TB Thunderbolt 3 external SSD. Dual boot works great by changing startup diisk in system preferences. So far so good, but I know as updates arrive the "fun" will start

I did the same. It will not work on a USB-C only drive - it has to be Thunderbolt. I am using a 2TB Envoy Pro FX from OWC. It works fine with my M1 Mac Mini. You must format the drive as APFS.
 
  • Like
Reactions: ArPe
That's what I am afraid of. With Intel Macs it was easy, you could create just a volume on the internal disk and install, and delete it in case you didn't like it, even though the recovery partition remained from the new betas. In M1's case I am not so sure if you can dual boot Big Sur afterwards.
Duel booting DOES work on M1 Macs.
 
I created a new container on my M1 MacBook Pro for Monterey, and installed it Monday afternoon. Works fine at first glance, but I had issues with charging and the Touch Bar after soft-rebooting back into Big Sur using Startup Disk.
A full power down avoids these problems.
 
Can anyone of you with dual boot on M1 go into their System Profiler and see if the Firmware and OS Loader versions are matching (while booted under Big Sur). Thanks
 
Can anyone of you with dual boot on M1 go into their System Profiler and see if the Firmware and OS Loader versions are matching (while booted under Big Sur). Thanks
My two-container, fresh-boot M1 MacBook Pro Big Sur System Profiler says:
Code:
System Firmware Version:    7429.0.72.0.3
OS Loader Version:    6723.120.36
(is that what you're asking for?)

EDIT: ooh, so iBoot firmware gets irreversibly updated with OS betas, much like EFI did for Intel Macs. sounds like fun :)
 
My two-container, fresh-boot M1 MacBook Pro Big Sur System Profiler says:
Code:
System Firmware Version:    7429.0.72.0.3
OS Loader Version:    6723.120.36
(is that what you're asking for?)

EDIT: ooh, so iBoot firmware gets irreversibly updated with OS betas, much like EFI did for Intel Macs. sounds like fun :)
This firmware can only be restored with another Mac with usb c with apple configurator as far as I know.
The thing is. I don’t know if any incompatibility issues can arise from mismatched firmware versions. Especially since one of them is from
Monterey.
 
  • Like
Reactions: TimmuJapan
Register on MacRumors! This sidebar will go away, and you'll see fewer ads.