Bootcamp gets stuck in the middle of Partitioning disk

** 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 newfs_apfs (945.200.84) and last modified by apfs_kext (945.260.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 asr (945.250.109.100.1) and last modified by apfs_kext (945.260.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 asr (945.250.109.100.1) and last modified by apfs_kext (945.260.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.250.134) and last modified by apfs_kext (945.260.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: (7737900+1) bitmap address (2542e3)

** The volume /dev/rdisk2 appears to be OK.** 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 newfs_apfs (945.200.84) and last modified by apfs_kext (945.260.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 asr (945.250.109.100.1) and last modified by apfs_kext (945.260.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 asr (945.250.109.100.1) and last modified by apfs_kext (945.260.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.250.134) and last modified by apfs_kext (945.260.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: (7737900+1) bitmap address (2542e3)

** The volume /dev/rdisk2 appears to be OK.

** Verifying allocated space.

warning: Overallocation Detected on Main device: (3276429+1) bitmap address (280cb0)

warning: Overallocation Detected on Main device: (7737900+1) bitmap address (27ef06)

** The volume /dev/rdisk2 appears to be OK.

$ diskutil list

/dev/disk0 (internal):

   #:                       TYPE NAME                    SIZE       IDENTIFIER

   0:      GUID_partition_scheme                         121.3 GB   disk0

   1:                        EFI EFI                     314.6 MB   disk0s1

   2:                 Apple_APFS Container disk2         120.9 GB   disk0s2

/dev/disk1 (internal, physical):

   #:                       TYPE NAME                    SIZE       IDENTIFIER

   0:      GUID_partition_scheme                        *2.0 TB     disk1

   1:                        EFI EFI                     209.7 MB   disk1s1

   2:                 Apple_APFS Container disk2         2.0 TB     disk1s2

/dev/disk2 (synthesized):

   #:                       TYPE NAME                    SIZE       IDENTIFIER

   0:      APFS Container Scheme -                      +2.1 TB     disk2

                                 Physical Stores disk0s2, disk1s2

   1:                APFS Volume Macintosh HD            19.2 GB    disk2s1

   2:                APFS Volume Preboot                 45.4 MB    disk2s2

   3:                APFS Volume Recovery                509.7 MB   disk2s3

   4:                APFS Volume VM                      2.1 GB     disk2s4

It appears like this

Hey Loner! yes I have the 2019 iMac.

This post is only to tell you that even though "fsck_apfs -s -o -y /dev/rdisk2" threw an error, it appears it did the trick. After that I tried the Bootcamp procedure again and it worked!

Now I am running Windows 10 with no problems at all. You are a life saver!! Thanks!

Hi Loner,

I have run the SMC and NVRAM Reset already and I dont have any external storage connected to my computer

The name of W10 ISO is: Win10_1903_V1_English_x64

Thanks!

Loner, I tried to do that but got the following error:

error: container /dev/rdisk3 is mounted with write access

when I run that, it gives me the next error:

error: Device does not contain a valid AFPS container.

hehehe... thanks a lot for the quick responses by the way