- Jul 13, 2013
- Gigabyte Z490 Vision D
- AMD RX 580
- Classic Mac
- Mobile Phone
When we install Big Sur or Monterey, macOS creates a System volume and a Data volume. Because these two volumes are part of a single installation, they are placed together into an APFS Volume Group.
If we take either the Data or System volumes out of that group and put either one into a different volume group, then they are no longer paired together.
There may be ways to handle this situation, but in general we should avoid doing so. We should not separate the two volumes that are joined together in a single group.
In order to clone a Big Sur or Monterey disk to a larger SSD, we should clone the entire volume group. This can be done by Carbon Copy Cloner. The procedure is described in Step 11 here:
CaseySJ's Intel Alder Lake i5-12600K: Gigabyte Z690 Aero G + Intel i5-12600K + AMD RX 6800 XT Please do not quote this guide in its entirety. Post a link instead. 10 Dec 2021: All P-cores, E-cores, and Hyper Threads now working!! This guide is made possible by the wonderful teamwork on...www.tonymacx86.com
OK, my volume names are causing confusion -- I haven't separated the boot drive's volume group at all...it is still made up of the System and Data volumes as shown below on the Sabrent Media SSD (boot drive is named "macOS"). The separate hard drive (ST18000) has a single APFS container with a single volume within it named "Data". This naming scheme has never caused any issues for me before, but admittedly it used to be formatted as an HFS+ volume if I remembered correctly, so the OS could be getting confused. But my understanding of the boot drive behavior is that for a given boot volume group name of "FUBAR" it would have a pair of separate volumes within the group -- "FUBAR" for System and "FUBAR - Data" for Data.
Also of interest -- this hard drive was cloned and re-installed into an existing, working deployment of Catalina. And the separate Data volume did show on the Desktop fine for a week or two -- it has disappeared somewhere in the last week if I remember correctly. I don't reboot this system much, so frankly I don't recall the specifics of timing.
With that explanation, any other ideas?