Cannot Remove Windows 10 previously installed with Boot Camp Assistant

Run

diskutil eraseVolume jhfs+ BC1 disk0s3

diskutil eraseVolume jhfs+ BC2 disk0s4

diskutil mergePartitions jhfs+ BCMP disk0s3 disk0s4

diskutil list

If you only see disk0s3 as the last partition on disk0, then

diskutil eraseVolume fat32 BOOTCAMP disk0s3

and now run BC Assistant and try to Remove/Restore.

I have a iMac with the following specifications that I tried to uninstall Bootcamp running Windows 10 and the restore failed using Bootcamp Assistant. I got the error that it could not be installed.

I ran diskutil list and received the output below which does not indicate any BOOTCAMP partition at all. I have not rebooted the iMac yet. I would like to get the ~200 GB of disk space back on my 1 TB Fusion Drive.

Any thoughts on where to go from here?

I owe you a cold one. I now have all the space available with the drive. I am going to restart this computer and see how that panes out but looks good based on output below. Thanks.

> apfs resizeContainer disk2 0g

Started APFS operation

Aligning grow delta to 223,979,704,320 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.220.38)

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.220.38)

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.220.38)

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.220.38)

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: (123618+1) bitmap address (1d16a)

warning: Overallocation Detected on Main device: (123628+1) bitmap address (1d16a)

warning: Overallocation Detected on Main device: (123686+1) bitmap address (1d16a)

warning: Overallocation Detected on Main device: (123775+1) bitmap address (1d16a)

warning: Overallocation Detected on Main device: (123833+1) bitmap address (1d16a)

warning: Overallocation Detected on Main device: (123845+1) bitmap address (1d16a)

warning: Overallocation Detected on Main device: (123859+1) bitmap address (1d16a)

warning: Overallocation Detected on Main device: (123868+1) bitmap address (1d16a)

warning: Overallocation Detected on Main device: (123877+1) bitmap address (1d16a)

warning: Overallocation Detected on Main device: (123898+1) bitmap address (1d16a)

warning: Overallocation Detected on Main device: (123917+1) bitmap address (1d16a)

warning: Overallocation Detected on Main device: (123923+1) bitmap address (1d16a)

warning: Overallocation Detected on Main device: (123956+1) bitmap address (1d16a)

warning: Overallocation Detected on Main device: (123961+1) bitmap address (1d16a)

warning: Overallocation Detected on Main device: (124049+1) bitmap address (1d16a)

warning: Overallocation Detected on Main device: (124055+1) bitmap address (1d16a)

warning: Overallocation Detected on Main device: (124213+1) bitmap address (1d16a)

warning: Overallocation Detected on Main device: (124245+1) bitmap address (1d16a)

warning: Overallocation Detected on Main device: (124294+1) bitmap address (1d16a)

warning: Overallocation Detected on Main device: (124330+1) bitmap address (1d16a)

warning: Overallocation Detected on Main device: (124333+1) bitmap address (1d16a)

warning: Overallocation Detected on Main device: (124380+1) bitmap address (1d16a)

warning: Overallocation Detected on Main device: (124423+1) bitmap address (1d16a)

warning: Overallocation Detected on Main device: (124434+1) bitmap address (1d16a)

warning: Overallocation Detected on Main device: (124452+1) bitmap address (1d16a)

warning: Overallocation Detected on Main device: (124484+1) bitmap address (1d16a)

warning: Overallocation Detected on Main device: (124539+1) bitmap address (1d16a)

warning: Overallocation Detected on Main device: (124563+1) bitmap address (1d16a)

warning: Overallocation Detected on Main device: (124644+1) bitmap address (1d16a)

warning: Overallocation Detected on Main device: (124672+1) bitmap address (1d16a)

warning: Overallocation Detected on Main device: (124682+1) bitmap address (1d16a)

warning: Overallocation Detected on Main device: (124686+1) bitmap address (1d16a)

warning: Overallocation Detected on Main device: (124709+1) bitmap address (1d16a)

warning: Overallocation Detected on Main device: (124744+1) bitmap address (1d16a)

warning: Overallocation Detected on Main device: (124767+1) bitmap address (1d16a)

warning: Overallocation Detected on Main device: (124776+1) bitmap address (1d16a)

warning: Overallocation Detected on Main device: (124792+1) bitmap address (1d16a)

warning: Overallocation Detected on Main device: (124795+1) bitmap address (1d16a)

warning: Overallocation Detected on Main device: (124810+1) bitmap address (1d16a)

warning: Overallocation Detected on Main device: (124860+1) bitmap address (1d16a)

warning: Overallocation Detected on Main device: (124940+1) bitmap address (1d16a)

warning: Overallocation Detected on Main device: (124993+1) bitmap address (1d16a)

warning: Overallocation Detected on Main device: (125014+1) bitmap address (1d16a)

warning: Overallocation Detected on Main device: (125018+1) bitmap address (1d16a)

warning: Overallocation Detected on Main device: (125023+1) bitmap address (1d16a)

warning: Overallocation Detected on Main device: (125040+1) bitmap address (1d16a)

warning: Overallocation Detected on Main device: (125093+1) bitmap address (1d16a)

warning: Overallocation Detected on Main device: (125095+1) bitmap address (1d16a)

warning: Overallocation Detected on Main device: (125118+1) bitmap address (1d16a)

warning: Overallocation Detected on Main device: (125143+1) bitmap address (1d16a)

too many warnings generated; suppressing subsequent ones

Performing deferred repairs

The volume /dev/disk1s2 appears to be OK

Storage system check exit code is 0

Growing APFS Physical Store disk0s2 from 776,015,425,536 to 999,995,129,856 bytes

Modifying partition map

Growing APFS data structures

Finished APFS operation

Scotts-iMac:~ rsdavis$ diskutil list

/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 28.0 GB disk1

1: EFI EFI 314.6 MB disk1s1

2: Apple_APFS Container disk2 27.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 516.3 GB disk2s1

2: APFS Volume Preboot 45.3 MB disk2s2

3: APFS Volume Recovery 512.8 MB disk2s3

4: APFS Volume VM 1.1 GB disk2s4

/dev/disk3 (disk image):

#: TYPE NAME SIZE IDENTIFIER

0: GUID_partition_scheme +3.2 TB disk3

1: EFI EFI 209.7 MB disk3s1

2: Apple_HFS Time Machine Backups 3.2 TB disk3s2

> diskutil list

/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 28.0 GB disk1

1: EFI EFI 314.6 MB disk1s1

2: Apple_APFS Container disk2 27.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 516.3 GB disk2s1

2: APFS Volume Preboot 45.3 MB disk2s2

3: APFS Volume Recovery 512.8 MB disk2s3

4: APFS Volume VM 1.1 GB disk2s4

/dev/disk3 (disk image):

#: TYPE NAME SIZE IDENTIFIER

0: GUID_partition_scheme +3.2 TB disk3

1: EFI EFI 209.7 MB disk3s1

2: Apple_HFS Time Machine Backups 3.2 TB disk3s2

Hard Drive Info after running the above commands:

It does seem like a 1 TB drive should not have a full 1TB of available space since I would think the overhead of the filesystem itself would use some space but perhaps there is more than 1 TB to cover the additional space to begin with.

Should I run a verify with diskutil or something to check integrity of filesystem?

So far no issues with drive. It restarted fine.

rsdavis wrote:

It does seem like a 1 TB drive should not have a full 1TB of available space since I would think the overhead of the filesystem itself would use some space but perhaps there is more than 1 TB to cover the additional space to begin with.

The Fusion APFS is a single file system across the two underlying physical disks. If you run

diskutil apfs list

it will show you the details of space management. The 1TB disk is not exactly 1TiB, due to differences between the two space calculation methods - powers of 2 vs powers of 10.

rsdavis wrote:

Should I run a verify with diskutil or something to check integrity of filesystem?

So far no issues with drive. It restarted fine.

The 'grow' operation on the Container does check the file system as you posted earlier.

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

I suggest you leave it alone, till you see an issue. I also highly recommend Time Machine backups, for your own safety.

Excellent.

Run

diskutil apfs resizeContainer disk2 0g

diskutil list

and post the output.

Excellent. The 'Overallocation' errors bother me. Please post back, if you run into any new issues.