When resizing storage containers in Disk Utility, preparing a drive for external backup, or setting up Boot Camp Assistant on Intel-based Macs, users frequently encounter the error dialogue: ‘The disk couldn’t be partitioned. An error occurred while partitioning the disk.’ This failure commonly occurs alongside companion errors such as ‘Unable to resize APFS Container because the container is not empty’ or ‘Not enough free space.’ Even when macOS reports gigabytes of available storage, hidden APFS local snapshots, filesystem catalog inconsistencies, or fragmented container boundaries can prevent disk volume operations.
Underlying Causes of Partitioning Failures in macOS
Apple File System (APFS) manages storage dynamically using containers and shared space. When a partitioning request fails, it is usually due to one of the following factors:
- Accumulated Local APFS Snapshots: Time Machine generates silent local hourly snapshots on your primary drive. Disk Utility treats space occupied by these snapshots as locked, refusing to reallocate sectors.
- Corrupted APFS Container Metadata: Directory corruption, invalid extent records, or orphaned object maps within the APFS filesystem.
- FileVault Encryption In-Progress: Partitioning operations cannot execute while FileVault is actively encrypting, decrypting, or re-indexing your startup volume.
- Insufficient Contiguous Free Space: Legacy partition tables require physically contiguous blocks of unallocated storage, which heavily fragmented SSDs cannot allocate without defragmentation.
Step 1: Delete Local Time Machine APFS Snapshots
Local snapshots are the most common invisible roadblock during disk partitioning. Purging them frees up locked storage blocks instantly.
- Open the Terminal application on your Mac (located in Applications > Utilities).
- List all local APFS snapshots residing on your startup disk:
tmutil listlocalsnapshots / - If the output displays snapshots (formatted like
com.apple.TimeMachine.2026-11-14-120000.local), you can purge them all automatically using:tmutil thinlocalsnapshots / 10000000000 4 - Alternatively, delete individual snapshots manually using their specific datestamp identifier:
sudo tmutil deletelocalsnapshots 2026-11-14-120000 - Reopen Disk Utility and re-attempt the partition resize.
Step 2: Run First Aid on the Entire Drive Hierarchy
Filesystem errors inside container maps must be corrected before macOS will permit geometry modifications.
- Launch Disk Utility.
- Click the View button in the top toolbar and choose Show All Devices.
- Select your top-level physical internal drive (for example, APPLE SSD AP0512M).
- Click First Aid in the toolbar and click Run.
- Repeat the First Aid operation sequentially down the hierarchy: next select the Container, then the Macintosh HD – Data volume, and finally Macintosh HD.
Step 3: Perform Partitioning in macOS Recovery Mode
When running Disk Utility from within an active macOS session, the operating system cannot unmount locked system volumes. Running First Aid and partitioning from Recovery Mode removes OS locks.
- Shut down your Mac completely.
- On Apple Silicon Macs (M1, M2, M3, M4): Press and hold the power button until ‘Loading startup options’ appears, then select Options > Continue.
- On Intel Macs: Turn on your Mac and immediately press and hold Cmd + R until the Apple logo displays.
- Select Disk Utility from the macOS Recovery window.
- Run First Aid across the container and attempt to partition the drive while the startup volume is idle.
Step 4: Use APFS Volume Creation Instead of Physical Partitioning
Modern macOS rarely requires rigid, static disk partitioning. APFS volumes share storage dynamically from the same pool without dedicating fixed gigabytes.
- Open Disk Utility.
- Select your primary Container (e.g., Container disk1).
- Click the Add Volume (+) button rather than the Partition button.
- Assign the new volume a name (e.g., Secondary Storage or Beta Testing) and format it as APFS.
- Click Add. The volume will appear immediately in Finder and allocate storage dynamically on demand without risky disk boundary reallocations.