I'm running a MacPro 5,1 on MacOS 10.14.6 with a 500gb Samsung SSD as my boot/host drive. I recently ran out of space on my 500gb ssd so I speced an identical 1tb ssd.
A clean reinstall is not an option for me so I used clonezilla to do a block copy to the new drive (using newb settings, all defaults). Once the copy was finished and I booted from the new 1tb drive, Disk Utility showed the full 1tb of the physical disk but the APFS container and volume were still both sized at 500gb, completely negating my upgrade =(
This is where it gets weird. I fooled around with this a couple months ago, so I don't remember what I did or where I found documentation for this but somehow, I managed to resize the container to 1tb but the APFS volume size never changed, as I'm still out of usable disk space at 500gb. If it helps, I feel like I vaguely remember using a function of GParted to accomplish this but I don't remember anything outside of that.
How do I fix this? For context, my boot drive is disk2, with the APFS container's physical store located at disk2s2. I've attempted to do a resizeContainer disk2s2 0
hoping it'd somehow realize the mismatch and fix the APFS volume size but with no success. I've also tried a resizeContainer disk2s2 500g
with the intention of shrinking the container to 500gb and then retrying the resizeContainer disk2s2 0
to again and properly reclaim the unused 500gb on the drive. I'll show the output of both of those as well as diskutil list
, diskutil apfs list
(abbreviated, I have alot of other drives lol), and what I'm seeing in Disk Utility.
Any insight is greatly appreciated as I'm in over my head here. Thanks!
$ diskutil list
/dev/disk2 (internal, physical):
#: TYPE NAME SIZE IDENTIFIER
0: GUID_partition_scheme *1.0 TB disk2
1: EFI EFI 209.7 MB disk2s1
2: Apple_APFS Container disk3 1000.0 GB disk2s2
/dev/disk3 (synthesized):
#: TYPE NAME SIZE IDENTIFIER
0: APFS Container Scheme - +499.9 GB disk3
Physical Store disk2s2
1: APFS Volume JBax Mac Pro 484.6 GB disk3s1
2: APFS Volume Preboot 44.5 MB disk3s2
3: APFS Volume Recovery 1.0 GB disk3s3
4: APFS Volume VM 3.2 GB disk3s4
$ diskutil apfs list
APFS Container (1 found)
|
+-- Container disk3 C2500AD1-3713-42B3-847F-663C77A85C86
====================================================
APFS Container Reference: disk3
Size (Capacity Ceiling): 499898105856 B (499.9 GB)
Capacity In Use By Volumes: 489041268736 B (489.0 GB) (97.8% used)
Capacity Not Allocated: 10856837120 B (10.9 GB) (2.2% free)
|
+-< Physical Store disk2s2 D63FD546-5CC2-4EB7-B5E7-8DA660BA026B
| -----------------------------------------------------------
| APFS Physical Store Disk: disk2s2
| Size: 999995133440 B (1000.0 GB)
|
+-> Volume disk3s1 66E7E184-D546-4493-854D-92632DF1A94D
| ---------------------------------------------------
| APFS Volume Disk (Role): disk3s1 (No specific role)
| Name: JBax Mac Pro (Case-insensitive)
| Mount Point: /
| Capacity Consumed: 484590370816 B (484.6 GB)
| FileVault: No
|
+-> Volume disk3s2 42F434F9-B33D-423F-99C1-F7B04B2EE0C1
| ---------------------------------------------------
| APFS Volume Disk (Role): disk3s2 (Preboot)
| Name: Preboot (Case-insensitive)
| Mount Point: Not Mounted
| Capacity Consumed: 44486656 B (44.5 MB)
| FileVault: No
|
+-> Volume disk3s3 26827351-189E-4ECB-983F-738A825FAD80
| ---------------------------------------------------
| APFS Volume Disk (Role): disk3s3 (Recovery)
| Name: Recovery (Case-insensitive)
| Mount Point: /Volumes/Recovery 1
| Capacity Consumed: 1023565824 B (1.0 GB)
| FileVault: No
|
+-> Volume disk3s4 C571DD11-615E-43CF-BFC0-7FBEC0321EA7
---------------------------------------------------
APFS Volume Disk (Role): disk3s4 (VM)
Name: VM (Case-insensitive)
Mount Point: /private/var/vm
Capacity Consumed: 3221385216 B (3.2 GB)
FileVault: No
Screenshots from Disk Utility: 1. Disk Utility- Physical Drive 2. Disk Utility- Container
Now here's what happens when trying to manipulate the size of the container:
$ sudo diskutil apfs resizeContainer disk2s2 0
Password:
Started APFS operation
Error: -69519: The target disk is too small for this operation, or a gap is required in your partition map which is missing or too small, which is often caused by an attempt to grow a partition beyond the beginning of another partition or beyond the end of partition map usable space
And here's the second method I tried, attempting to shrink then reclaim:
$ sudo diskutil apfs resizeContainer disk2s2 500g
Started APFS operation
Aligning shrink delta to 499,995,135,488 bytes and targeting a new physical store size of 499,999,997,952 bytes
Determined the minimum size for the targeted physical store of this APFS Container to be 499,898,105,856 bytes
Error: -69605: There is not enough free space in the APFS Container for this operation