~ aa$ diskutil ap resizeContainer disk2 0b ; diskutil list
Started APFS operation
Aligning grow delta to 187 993 624 576 bytes and targeting a new physical store size of 999 995 129 856 bytes
Determined the maximum size for the targeted physical store of this APFS Container to be 999 994 101 760 bytes
Resizing APFS Container designated by APFS Container Reference disk2
The specific APFS Physical Store being resized is disk0s2
Verifying storage system
Using live mode
Performing fsck_apfs -n -x -l -S /dev/disk1s2
Checking the container superblock
Checking the fusion superblock
Checking the EFI jumpstart record
Checking the space manager
Checking the space manager free queue trees
Checking the object map
Checking the Fusion data structures
Checking volume
Checking the APFS volume superblock
The volume Macintosh HD was formatted by hfs_convert (945.200.129) and last modified by apfs_kext (945.275.7)
Checking the object map
Checking the snapshot metadata tree
Checking the snapshot metadata
Checking the extent ref tree
Checking the fsroot tree
Checking volume
Checking the APFS volume superblock
The volume Preboot was formatted by hfs_convert (945.200.129) and last modified by apfs_kext (945.275.7)
Checking the object map
Checking the snapshot metadata tree
Checking the snapshot metadata
Checking the extent ref tree
Checking the fsroot tree
Checking volume
Checking the APFS volume superblock
The volume Recovery was formatted by diskmanagementd (945.200.129) and last modified by apfs_kext (945.275.7)
Checking the object map
Checking the snapshot metadata tree
Checking the snapshot metadata
Checking the extent ref tree
Checking the fsroot tree
Checking volume
Checking the APFS volume superblock
The volume VM was formatted by apfs.util (945.200.129) and last modified by apfs_kext (945.275.7)
Checking the object map
Checking the snapshot metadata tree
Checking the snapshot metadata
Checking the extent ref tree
Checking the fsroot tree
Verifying allocated space
warning: Overallocation Detected on Main device: (90362+1) bitmap address (1f9d9)
warning: Overallocation Detected on Main device: (90364+1) bitmap address (1f9d9)
warning: Overallocation Detected on Main device: (90366+1) bitmap address (1f9d9)
warning: Overallocation Detected on Main device: (90369+1) bitmap address (1f9d9)
warning: Overallocation Detected on Main device: (90372+1) bitmap address (1f9d9)
warning: Overallocation Detected on Main device: (90374+1) bitmap address (1f9d9)
warning: Overallocation Detected on Main device: (90383+1) bitmap address (1f9d9)
warning: Overallocation Detected on Main device: (90385+1) bitmap address (1f9d9)
warning: Overallocation Detected on Main device: (90387+1) bitmap address (1f9d9)
warning: Overallocation Detected on Main device: (90394+1) bitmap address (1f9d9)
warning: Overallocation Detected on Main device: (90398+1) bitmap address (1f9d9)
warning: Overallocation Detected on Main device: (90401+1) bitmap address (1f9d9)
warning: Overallocation Detected on Main device: (90408+1) bitmap address (1f9d9)
warning: Overallocation Detected on Main device: (90411+1) bitmap address (1f9d9)
warning: Overallocation Detected on Main device: (90414+2) bitmap address (1f9d9)
warning: Overallocation Detected on Main device: (90418+3) bitmap address (1f9d9)
warning: Overallocation Detected on Main device: (90423+1) bitmap address (1f9d9)
warning: Overallocation Detected on Main device: (90426+1) bitmap address (1f9d9)
warning: Overallocation Detected on Main device: (90428+1) bitmap address (1f9d9)
warning: Overallocation Detected on Main device: (90430+1) bitmap address (1f9d9)
warning: Overallocation Detected on Main device: (90433+1) bitmap address (1f9d9)
warning: Overallocation Detected on Main device: (90435+1) bitmap address (1f9d9)
warning: Overallocation Detected on Main device: (90437+3) bitmap address (1f9d9)
warning: Overallocation Detected on Main device: (90441+1) bitmap address (1f9d9)
warning: Overallocation Detected on Main device: (90449+1) bitmap address (1f9d9)
warning: Overallocation Detected on Main device: (139390+1) bitmap address (1f9f4)
warning: Overallocation Detected on Main device: (139392+3) bitmap address (1f9f4)
warning: Overallocation Detected on Main device: (139398+1) bitmap address (1f9f4)
warning: Overallocation Detected on Main device: (139400+2) bitmap address (1f9f4)
warning: Overallocation Detected on Main device: (139404+4) bitmap address (1f9f4)
warning: Overallocation Detected on Main device: (139409+2) bitmap address (1f9f4)
warning: Overallocation Detected on Main device: (139414+1) bitmap address (1f9f4)
warning: Overallocation Detected on Main device: (139421+1) bitmap address (1f9f4)
warning: Overallocation Detected on Main device: (139425+2) bitmap address (1f9f4)
warning: Overallocation Detected on Main device: (139430+3) bitmap address (1f9f4)
warning: Overallocation Detected on Main device: (139435+1) bitmap address (1f9f4)
warning: Overallocation Detected on Main device: (139437+1) bitmap address (1f9f4)
warning: Overallocation Detected on Main device: (139442+1) bitmap address (1f9f4)
warning: Overallocation Detected on Main device: (139448+1) bitmap address (1f9f4)
warning: Overallocation Detected on Main device: (139453+1) bitmap address (1f9f4)
warning: Overallocation Detected on Main device: (139457+1) bitmap address (1f9f4)
warning: Overallocation Detected on Main device: (139460+1) bitmap address (1f9f4)
warning: Overallocation Detected on Main device: (139462+1) bitmap address (1f9f4)
warning: Overallocation Detected on Main device: (139464+1) bitmap address (1f9f4)
warning: Overallocation Detected on Main device: (139466+1) bitmap address (1f9f4)
warning: Overallocation Detected on Main device: (139469+1) bitmap address (1f9f4)
warning: Overallocation Detected on Main device: (139476+2) bitmap address (1f9f4)
warning: Overallocation Detected on Main device: (139479+2) bitmap address (1f9f4)
warning: Overallocation Detected on Main device: (139485+2) bitmap address (1f9f4)
warning: Overallocation Detected on Main device: (139490+1) bitmap address (1f9f4)
too many warnings generated; suppressing subsequent ones
The volume /dev/disk1s2 appears to be OK
Storage system check exit code is 0
Growing APFS Physical Store disk0s2 from 812 001 505 280 to 999 995 129 856 bytes
Modifying partition map
Growing APFS data structures
Finished APFS operation
/dev/disk0 (internal, physical):
#: TYPE NAME SIZE IDENTIFIER
0: GUID_partition_scheme *1.0 TB disk0
1: EFI EFI 209.7 MB disk0s1
2: Apple_APFS Container disk2 1000.0 GB disk0s2
/dev/disk1 (internal):
#: TYPE NAME SIZE IDENTIFIER
0: GUID_partition_scheme 24.0 GB disk1
1: EFI EFI 314.6 MB disk1s1
2: Apple_APFS Container disk2 23.7 GB disk1s2
/dev/disk2 (synthesized):
#: TYPE NAME SIZE IDENTIFIER
0: APFS Container Scheme - +1.0 TB disk2
Physical Stores disk1s2, disk0s2
1: APFS Volume Macintosh HD 559.7 GB disk2s1
2: APFS Volume Preboot 44.6 MB disk2s2
3: APFS Volume Recovery 510.4 MB disk2s3
4: APFS Volume VM 20.5 KB disk2s4