Your disk could not be partitioned

ddennedy wrote:

The subject is the error I get running BCA on a new 2018 MacBook Pro with High Sierra with APFS but without encrypted volumes. Here is the partition list after running BCA and the failed partitioning:

/dev/disk0 (internal):

#: TYPE NAME SIZE IDENTIFIER

0: GUID_partition_scheme 1.0 TB disk0

1: EFI EFI 314.6 MB disk0s1

2: Apple_APFS Container disk1 504.0 GB disk0s2

3: Microsoft Basic Data OSXRESERVED 8.0 GB disk0s6

4: Microsoft Basic Data BOOTCAMP 488.1 GB disk0s4

5: Apple_Boot Boot OS X 134.2 MB disk0s3

/dev/disk1 (synthesized):

#: TYPE NAME SIZE IDENTIFIER

0: APFS Container Scheme - +504.0 GB disk1

Physical Store disk0s2

1: APFS Volume Macintosh HD 107.0 GB disk1s1

2: APFS Volume Preboot 22.6 MB disk1s2

3: APFS Volume Recovery 515.8 MB disk1s3

4: APFS Volume VM 1.1 GB disk1s4

/dev/disk2 (disk image):

#: TYPE NAME SIZE IDENTIFIER

0: CCCOMA_X64FRE_EN-US... +4.7 GB disk2

The order of disk slices seems to indicate failures. Can you reboot and post the output of

diskutil list

What is the current macOS version?

ddennedy wrote:

Another thread said to try to create a FAT partition and report any errors. It reports failure with these messages:

Running operation 1 of 2: Add “test” by splitting “Macintosh HD”…

Aligning shrink delta to 8,077,725,696 bytes and targeting a new physical store size of 495,922,274,304 bytes

Determined the minimum size for the targeted physical store of this APFS Container to be 112,473,837,568 bytes

Resizing APFS Container designated by APFS Container Reference disk1

The specific APFS Physical Store being resized is disk0s2

Verifying storage system

Using live mode.

Performing fsck_apfs -n -x -l /dev/disk0s2

Checking volume.

Checking the container superblock.

Checking the EFI jumpstart record.

Checking the space manager.

Checking the object map.

Checking the APFS volume superblock.

Checking the object map.

Checking the fsroot tree.

warning: crypto_val: object (oid 0x4): invalid state.major_version (0)

warning: crypto_val: object (oid 0x4): invalid state.key_os_version (0x0)

warning: crypto_val: object (oid 0x4): invalid state.key_revision (0)

Checking the snapshot metadata tree.

Checking the extent ref tree.

Checking the snapshots.

Checking the APFS volume superblock.

Checking the object map.

Checking the fsroot tree.

Checking the snapshot metadata tree.

Checking the extent ref tree.

Checking the snapshots.

Checking the APFS volume superblock.

Checking the object map.

Checking the fsroot tree.

Checking the snapshot metadata tree.

Checking the extent ref tree.

Checking the snapshots.

Checking the APFS volume superblock.

Checking the object map.

Checking the fsroot tree.

Checking the snapshot metadata tree.

Checking the extent ref tree.

Checking the snapshots.

Verifying allocated space.

The volume /dev/disk0s2 appears to be OK.

Storage system check exit code is 0.

Shrinking APFS Physical Store disk0s2 from 504,000,000,000 to 495,922,274,304 bytes

Shrinking APFS data structures

Shrinking partition

Modifying partition map

Initialized /dev/rdisk0s7 as a 7 GB case-insensitive HFS Plus volume with a 8192k journal

Mounting disk

Creating a new empty APFS Container

Unmounting Volumes

Switching disk0s7 to APFS

Creating APFS Container

Created new APFS Container disk3

Preparing to add APFS Volume to APFS Container disk3

Creating APFS Volume

Created new APFS Volume disk3s1

Mounting APFS Volume

Setting volume permissions

Running operation 2 of 2: Erase “test”…

Deleting APFS Container with all of its APFS Volumes

Unmounting Volumes

Unmounting Volume “test” on disk3s1

Deleting Volumes

Deleting Container

Wiping former APFS disks

Switching content types

Name invalid.

Operation failed…

This is not good. We should first clean up the current partitions, before you attempt BC Assistant steps again.

This disk layout is clean and standard on APFS-based file systems.