Macintosh HD and Macintosh HD Data, why there are two volumes
Finder shows one disk. Disk Utility shows two, sometimes more. Only one of those pictures is a simplification.
Since Catalina the startup disk has been two volumes rather than one. Macintosh HD holds macOS and takes no changes. Macintosh HD Data holds everything you own. Finder joins them so convincingly that most people never learn there are two. Then they open Disk Utility one day and assume something has gone wrong.
Nothing has. What follows is what each one is for and how to tell an ordinary pair from a genuine mess.
What each volume holds
| Volume | Holds | Writable |
|---|---|---|
| Macintosh HD | macOS itself, plus the applications that ship with it | No |
| Macintosh HD Data | Your home folder, the software you installed, settings and a handful of system parts that have to be writable | Yes |
The second row matters more than it looks. The Data volume is not simply your files. Parts of macOS that have to change while the Mac runs live there too. That rules out treating it as an optional extra.
Read more: The hidden Library folder on a Mac and what lives in it.
Why the split exists
Apple fixes everything on the system volume at the moment it builds the release. Nothing running on the Mac alters it afterwards, including anything that arrives uninvited.
Before Catalina the two shared one writable volume. Anything with enough privilege could rewrite parts of macOS. Separating them removes the possibility rather than defending against it.
You are not running from Macintosh HD. Big Sur went further and sealed the system volume cryptographically. What starts up is a read-only snapshot of that volume rather than the volume itself. Snapshots also decide whether a deleted file can still be recovered. Even the copy in use sits one step away from anything that could change it.
Why the Data volume is the older one
This is the part that reads backwards. It explains the naming.
When a Mac upgraded to Catalina, the installer did not create a new volume for your files. It took the volume you already had, renamed it to Macintosh HD Data and changed its role. Then it created a fresh volume alongside for the operating system.
So the volume with Data in the name is the original startup disk, carrying everything from before the upgrade. The one named plainly is the newcomer. Anyone reasoning from the names alone gets the history exactly the wrong way round.
What holds the two together
Two volumes appearing as one takes a mechanism. Apple built one for the purpose.
Firmlinks join specific folders across the volume boundary. A path starting on the read-only volume continues onto the writable one with no visible transition. Applications, Users and Library all work this way, so the result behaves like a single file system while remaining two.
macOS also groups them. That is why Disk Utility indents one under the other. It is also why erasing one on its own tends to go wrong.
Why neither volume has a size
Look for the capacity of either one and you will not find a useful number.
APFS puts both volumes inside a container. Every volume in a container draws from the same free space. That container is the layer HFS+ never had, explained in full in the way the Mac file system is laid out. Nothing gets allocated in advance. The system volume takes what macOS needs and the Data volume takes the rest, with the boundary moving on its own.
Partitioning worked the other way. Each slice had a fixed size. Filling one meant repartitioning the lot. The words look similar and the behaviour is not.
When a third volume is a problem
One System and one Data volume is correct. More than that is worth looking at.
Normal
Leave it alone
- Macintosh HD and Macintosh HD Data
- Entries marked as snapshots
- A Recovery volume
- Preboot and VM volumes
Something went wrong
Worth investigating
- Two volumes named Macintosh HD
- Anything called Macintosh HD Data Data
- Two Data volumes, one of them empty
The right column comes from an incomplete erase before a reinstall. Erasing only the volume named Macintosh HD leaves the old Data volume in place. The installer then makes a fresh one beside it. The Mac still starts, which is why this goes unnoticed for months.
The answer is to work one level up. Turn on Show All Devices from Disk Utility's View menu, then erase the drive itself rather than a volume inside it. That clears the whole container in one action.
Relocated Items, the folder left behind
Some Macs carry a folder called Relocated Items, most commonly in the Shared folder. It is a leftover from the same change.
The Catalina upgrade had to move anything sitting in a location about to become read only. Rather than delete those files it collected them there, with a note explaining what happened.
Nothing has gone into it since that upgrade. A Mac bought recently never had one. A folder sitting untouched for years deserves the same review as anything else.
Common questions
Can I delete the Macintosh HD Data volume?
Only if you intend to erase the Mac. It holds your home folder, your applications and your settings. Removing it takes all of that. The system volume left behind boots to a setup screen with nothing on it.
Why does Finder show one disk when Disk Utility shows two?
Finder shows the arrangement macOS wants you to work with. Disk Utility shows what sits on the drive. Neither is wrong. Links between the two volumes make them behave as one.
Do the two volumes have fixed sizes?
No. Both draw from the same pool of free space and grow as they need to, which is why neither shows a capacity of its own that you can adjust. To read the bar that reports that pool, see which categories the storage bar is counting.
What is the Data folder under System Volumes?
That path is where macOS mounts the Data volume, so it reaches the same storage by another route rather than holding a second copy.
What is Relocated Items?
A folder the Catalina upgrade created for files sitting in places the new arrangement made read only. Nothing goes into it after that upgrade, so a recent Mac will not have one at all.
Should I worry about seeing snapshots listed too?
No. Entries marked as snapshots are recovery points macOS keeps rather than extra copies of the disk. They lengthen the list in Disk Utility and occupy far less room than their labels suggest.
Sources
Every date, version number and path above is taken from these pages rather than from memory.