You can make a difference in the Apple Support Community!

When you sign up with your Apple Account, you can provide valuable feedback to other community members by upvoting helpful replies and User Tips.

Looks like no one’s replied in a while. To start the conversation again, simply ask a new question.

Windows Bootcamp

I'm trying to reinstall windows 10 through bootcamp, but I keep getting "An error occurred while partitioning the disk. Please run Disk Utility to check and fix the error." I made sure I had enough space to attempt this, but here were my results


I have ran disk utility, came up with nothing

I have used command+s to go into single user mode and used fsck -fy, didn't help my case either

I have completely reinstalled Mac OSX, still nothing

Turned off filevault to install, didn't do anything either

resetting PRAM did nothing

Verified my disk, that didn't help

Manually setting a partition didn't help

and cleaning out my previous time machine snapshots was a waste of time


Which is odd, because I haven't had to go this far before, and I just want to bloody install it, but it seems everytime I have to, it takes an additional 10 steps to do it. Can somebody please give me a straight answer to how to fix it? Because at this point, I am starting to lose patients.

Posted on Jan 26, 2019 2:17 PM

Reply

Similar questions

23 replies

Feb 1, 2019 8:22 PM in response to kameronfromrochester

The current layout will not work, even if you called Apple Technical Support. The following steps will give you a unified macOS partition. This should be done before Windows installer will work correctly. Use April 1803 ISO unless there are other issues that we find after the cleanup.


  • Step 1


In your specific case, given the current state, try


diskutil eraseVolume jhfs+ BC1 disk0s3

diskutil eraseVolume jhfs+ BC2 disk0s4

diskutil eraseVolume jhfs+ BC2 disk0s5


diskutil mergePartitions jhfs+ BCMP disk0s3 disk0s5

diskutil list


  • Step 2


If you see only disk0s3 as the last entry under disk0, then run


diskutil eraseVolume fat32 BOOTCAMP disk0s3


and retry removing the partition using BC Assistant only.

Jan 30, 2019 2:57 PM in response to kameronfromrochester

Two more things.


1: every-time I attempt to boot up the .iso file in bootcamp, it says that the time for installation is usually one or two minutes, following with a message that tells me that "An error occurred while partitioning the disk. Please run Disk Utility to check and fix the error."


2: I'm not sure if this helps, but when I go into Disk Utility, it shows it as if it was a bootable drive. I'm not sure what this even means.

Feb 1, 2019 10:17 AM in response to Loner T

It could make the FAT Partition, and I kept the FAT Partition when I did bootcamp assistant, but when it got to when I can load the partition and partition the space, it was completely blank. I went through it anyways, and it still said I could not partition the disk.



Edit: Okay, I've made a new development. I deleted the FAT partition and remade my OSX partition. I ran bootcamp this time and this popped up. It does recognize bootcamp, but it still comes up with "An error occurred while partitioning the disk. Please run Disk Utility to check and fix the error."

Feb 1, 2019 7:06 PM in response to Loner T

Here it is, It has changed a bit, which I will explain, and I will even post a screenshot of the terminal to prove that this is the output result:

/dev/disk0 (internal):


   #:                       TYPE NAME                    SIZE       IDENTIFIER


   0:      GUID_partition_scheme                         500.3 GB   disk0


   1:                        EFI EFI                     314.6 MB   disk0s1


   2:                 Apple_APFS Container disk1         291.0 GB   disk0s2


   3:       Microsoft Basic Data OSXRESERVED             8.0 GB     disk0s3


   4:       Microsoft Basic Data BOOTCAMP                200.8 GB   disk0s4


   5:                 Apple_Boot Boot OS X               134.2 MB   disk0s5




/dev/disk1 (synthesized):


   #:                       TYPE NAME                    SIZE       IDENTIFIER


   0:      APFS Container Scheme -                      +291.0 GB   disk1


                                 Physical Store disk0s2


   1:                APFS Volume Macintosh HD            170.6 GB   disk1s1


   2:                APFS Volume Preboot                 104.7 MB   disk1s2


   3:                APFS Volume Recovery                2.1 GB     disk1s3


   4:                APFS Volume VM                      1.1 GB     disk1s4


I've also contacted Apple support and tried walking it through with them, and I still got no results. Apparently, the October 2018 release has been problematic so they suggested I try the April 2018 release then upgrade to October's release. I tried to use the April ISO and I still got the same bloody result. It won't partition for the life of it. And at this point, I cannot even fathom why this keeps happening, but hey, I'm gonna have to work for my results.


Jan 26, 2019 3:21 PM in response to Loner T

Password:


dev_init:590: Using /private/var/folders/zz/zyxvpxvq6csfxvn_n0000000000000/T/fsck_apfs.6687.1/apfs and /private/var/folders/zz/zyxvpxvq6csfxvn_n0000000000000/T/fsck_apfs.6687.1/nx for device-io.


** Checking the container superblock.


** Checking the EFI jumpstart record.


** Checking the space manager.


** Checking the space manager free queue trees.


** Checking the object map.


** Checking volume.


** Checking the APFS volume superblock.


** The volume Macintosh HD was formatted by newfs_apfs (748.77.8) and last modified by apfs_kext (945.230.6).


** Checking the object map.


** Checking the snapshot metadata tree.


** Checking the snapshot metadata.


** Checking snapshot 1 of 1.


warning: inode_val: object (oid 0x111c938): invalid bsd_flags (0x10)


** Checking the extent ref tree.


** Checking the fsroot tree.


warning: inode_val: object (oid 0x111c938): invalid bsd_flags (0x10)


** Checking volume.


** Checking the APFS volume superblock.


** The volume Preboot was formatted by newfs_apfs (748.21.6) and last modified by apfs_kext (945.230.6).


** 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 newfs_apfs (748.21.6) and last modified by apfs_kext (945.230.6).


** 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 newfs_apfs (748.21.6) and last modified by apfs_kext (945.230.6).


** 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.


** Performing deferred repairs.


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


Kamerons-MacBook-Pro:~ kameronpersonal$ 

Jan 30, 2019 2:46 PM in response to Loner T

dev_init:590: Using /private/var/folders/zz/zyxvpxvq6csfxvn_n0000000000000/T/fsck_apfs.827.1/apfs and /private/var/folders/zz/zyxvpxvq6csfxvn_n0000000000000/T/fsck_apfs.827.1/nx for device-io.


** Checking the container superblock.


** Checking the EFI jumpstart record.


** Checking the space manager.


** Checking the space manager free queue trees.


** Checking the object map.


** Checking volume.


** Checking the APFS volume superblock.


** The volume Macintosh HD was formatted by newfs_apfs (748.77.8) and last modified by apfs_kext (945.230.6).


** Checking the object map.


** Checking the snapshot metadata tree.


** Checking the snapshot metadata.


** Checking the extent ref tree.


** Checking the fsroot tree.


warning: inode_val: object (oid 0x111c938): invalid bsd_flags (0x10)


** Checking volume.


** Checking the APFS volume superblock.


** The volume Preboot was formatted by newfs_apfs (748.21.6) and last modified by apfs_kext (945.230.6).


** 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 newfs_apfs (748.21.6) and last modified by apfs_kext (945.230.6).


** 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 newfs_apfs (748.21.6) and last modified by apfs_kext (945.230.6).


** 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.


** Performing deferred repairs.


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


Kamerons-MacBook-Pro:~ kameronpersonal$ 

Jan 31, 2019 9:03 PM in response to kameronfromrochester

Its not letting me change the partiion from APFS to FAT when I go and partition my drive.

Edit: I figured it out, set it to the appropriate size, and gonna go and try bootcamp now

The test was to check if a FAT partition can be created by Disk Utility.


Edit 2: Same error reoccured. "An error occurred while partitioning the disk. Please run Disk Utility to check and fix the error."

Did you remove the FAT partition before you retried BC Assistant again?

Feb 1, 2019 11:12 AM in response to kameronfromrochester

And just did sudo fsck_apfs -n -l /dev/rdisk1, here is the output results.


dev_init:590: Using /private/var/folders/zz/zyxvpxvq6csfxvn_n0000000000000/T/fsck_apfs.1571.1/apfs and /private/var/folders/zz/zyxvpxvq6csfxvn_n0000000000000/T/fsck_apfs.1571.1/nx for device-io.


** Checking the container superblock.


** Checking the EFI jumpstart record.


** Checking the space manager.


** Checking the space manager free queue trees.


** Checking the object map.


** Checking volume.


** Checking the APFS volume superblock.


** The volume Macintosh HD was formatted by newfs_apfs (748.77.8) and last modified by apfs_kext (945.241.4).


** Checking the object map.


** Checking the snapshot metadata tree.


** Checking the snapshot metadata.


** Checking the extent ref tree.


** Checking the fsroot tree.


warning: inode_val: object (oid 0x111c938): invalid bsd_flags (0x10)


** Checking volume.


** Checking the APFS volume superblock.


** The volume Preboot was formatted by newfs_apfs (748.21.6) and last modified by apfs_kext (945.241.4).


** 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 newfs_apfs (748.21.6) and last modified by apfs_kext (945.241.4).


** 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 newfs_apfs (748.21.6) and last modified by apfs_kext (945.241.4).


** 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.


** Performing deferred repairs.


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


Kamerons-MacBook-Pro:~ kameronpersonal$ 


Also, as a fun fact, warning: inode_val: object (oid 0x111c938): invalid bsd_flags (0x10) is an error code for OneDrive Sync Folder which has been occurring from Mojave 10.14.2 and the latest OneDrive version 18.240.1202.0004. And Since that is an update issue, that lays the blame on the recent update.

Feb 1, 2019 12:46 PM in response to Loner T

Here is it with OSXRESERVED and BOOTCAMP removed:


Kamerons-MacBook-Pro:~ kameronpersonal$ diskutil list


/dev/disk0 (internal):


   #:                       TYPE NAME                    SIZE       IDENTIFIER


   0:      GUID_partition_scheme                         500.3 GB   disk0


   1:                        EFI EFI                     314.6 MB   disk0s1


   2:                 Apple_APFS Container disk1         499.8 GB   disk0s2


   3:                 Apple_Boot Boot OS X               134.2 MB   disk0s3




/dev/disk1 (synthesized):


   #:                       TYPE NAME                    SIZE       IDENTIFIER


   0:      APFS Container Scheme -                      +499.8 GB   disk1


                                 Physical Store disk0s2


   1:                APFS Volume Macintosh HD            165.9 GB   disk1s1


   2:                APFS Volume Preboot                 104.7 MB   disk1s2


   3:                APFS Volume Recovery                2.1 GB     disk1s3


   4:                APFS Volume VM                      1.1 GB     disk1s4




Kamerons-MacBook-Pro:~ kameronpersonal$ 



And here is one with them:Kamerons-MacBook-Pro:~ kameronpersonal$ diskutil list


/dev/disk0 (internal):


   #:                       TYPE NAME                    SIZE       IDENTIFIER


   0:      GUID_partition_scheme                         500.3 GB   disk0


   1:                        EFI EFI                     314.6 MB   disk0s1


   2:                 Apple_APFS Container disk1         291.0 GB   disk0s2


   3:       Microsoft Basic Data OSXRESERVED             8.0 GB     disk0s6


   4:       Microsoft Basic Data BOOTCAMP                200.8 GB   disk0s4


   5:                 Apple_Boot Boot OS X               134.2 MB   disk0s3




/dev/disk1 (synthesized):


   #:                       TYPE NAME                    SIZE       IDENTIFIER


   0:      APFS Container Scheme -                      +291.0 GB   disk1


                                 Physical Store disk0s2


   1:                APFS Volume Macintosh HD            165.8 GB   disk1s1


   2:                APFS Volume Preboot                 104.7 MB   disk1s2


   3:                APFS Volume Recovery                2.1 GB     disk1s3


   4:                APFS Volume VM                      1.1 GB     disk1s4




/dev/disk2 (disk image):


   #:                       TYPE NAME                    SIZE       IDENTIFIER


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


Feb 1, 2019 6:09 PM in response to kameronfromrochester


And here is one with them:Kamerons-MacBook-Pro:~ kameronpersonal$ diskutil list

/dev/disk0 (internal):

   #:                       TYPE NAME                    SIZE       IDENTIFIER

   0:      GUID_partition_scheme                         500.3 GB   disk0

   1:                        EFI EFI                     314.6 MB   disk0s1

   2:                 Apple_APFS Container disk1         291.0 GB   disk0s2

   3:       Microsoft Basic Data OSXRESERVED             8.0 GB     disk0s6

   4:       Microsoft Basic Data BOOTCAMP                200.8 GB   disk0s4

   5:                 Apple_Boot Boot OS X               134.2 MB   disk0s3

This layout is not valid. Can you reboot and post the output of


diskutil list


so the the disk parts are correctly ordered?

Windows Bootcamp

Welcome to Apple Support Community
A forum where Apple customers help each other with their products. Get started with your Apple Account.