Disk could not be partitioned (Bootcamp)

Question

Level 1

9 points

Disk could not be partitioned (Bootcamp)

Hello, in desperate need of help.

I used to install windows 8.0 (Trial version) in my macbook air and it works perfectly fine even its lacking some memory use. Heck i can even play League of Legends and Sims 4 there. But i recently wanted to upgrade to a windows 10. So i decided to do a new Bootcamp. To my suprised, it aint working. I have tried everything i could google on.

Clearing time machine backup and FV (never use them)
Run PRAM and SMC reset
Even tried manual downloading it (Making my own partition and usb flash stick) which pop up a new error (Windows cannot locate the disk and partition specified)

and at this point..im out of ideas. Could any1 lend a hand here. Appreciated it

PS: Additional info : What i found was, when i accessing disk utility..i cannot straight up partition a disk there to a format of ms-dot (FAT).

I was only able to partition during command + R restart at recovery mode. Even then, it was limited to 35 gb which is surprising to me since i wanted 40 gb and i had around 38 gb to spare for the partition. Kinda surprised there.

MacBook Air 13", macOS 10.14

Posted on Apr 2, 2019 7:20 AM

Reply

Answer 1

Loner T

Level 9

59,536 points

Apr 5, 2019 6:44 AM in response to Kaminosan

We need to address the partitioning issue, instead of using an alternative to BC Assistant. On your Desktop, you show W10 1809 (October) ISO, which has known issues. Have you tried to use W10 1803 (April), without using a USB installer?

Reply

Answer 2

Loner T

Level 9

59,536 points

Apr 10, 2019 1:34 AM in response to Kaminosan

Use W10 1803 (April) and run BCA and try to install Windows.

Reply

Answer 3

Loner T

Level 9

59,536 points

Apr 3, 2019 1:55 AM in response to Kaminosan

What is the year/model of your Mac (do not post the serial number)? The error message on the Windows installer screen indicates that you have external storage attached which is not required and is confusing the Windows Installer.

Reply

Answer 4

Loner T

Level 9

59,536 points

Apr 7, 2019 7:34 AM in response to Kaminosan

Start up your Mac in single-user mode or verbose mode - Apple Support and run

fsck_apfs -s -o -y /dev/rdisk1

If you get any errors, see the footnote under step 6. You will need to use Command+S during boot up to start Single User Mode.

Reply

Answer 5

Loner T

Level 9

59,536 points

Apr 10, 2019 11:36 AM in response to Kaminosan

Kaminosan wrote:

Wow..it worked. Thank you so much T.T .

Excellent.

May i at least know, whats up with the problem there ? A brief explanation for a newbie like me perhaps ?

We fixed

** Verifying allocated space.

warning: Overallocation Detected on Main device: (19923020+1) bitmap address (f450)

by running fsck_apfs in Single User Mode.

Reply

Answer 6

Kaminosan Author

Level 1

9 points

Apr 7, 2019 2:41 AM in response to Loner T

Here is what i got. I run it in the terminal (not sure what u mean by output there ) (as u can tell..not a mac expert)

** 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 diskmanagementd (945.220.38) and last modified by apfs_kext (945.250.134).

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

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

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

** 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: (19923020+1) bitmap address (f450)

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

Reply

Answer 7

Loner T

Level 9

59,536 points

Apr 6, 2019 6:39 AM in response to Kaminosan

Can you post the output of

sudo fsck_apfs -n -l /dev/rdisk1

Reply

Answer 8

Loner T

Level 9

59,536 points

Apr 10, 2019 1:22 AM in response to Kaminosan

One overallocation was corrected. Can you boot normally and post the output of

sudo fsck_apfs -n -l /dev/rdisk1

Reply

Answer 9

Kaminosan Author

Level 1

9 points

Apr 4, 2019 9:15 PM in response to Loner T

Mine is Air early 2015. The windows error is after i do a manual installation without bootcamp. And using flash disk as a bootstick for installing windows. But i cant use partitioning from bootcamp assistant like normal. Donno why.

Reply

Answer 10

Kaminosan Author

Level 1

9 points

Apr 10, 2019 1:32 AM in response to Loner T

** 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 diskmanagementd (945.220.38) and last modified by apfs_kext (945.250.134).

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

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

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

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

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

It seems the overallocation is fix..but still..im not sure what it means tho..hahahha sorry

Reply

Answer 11

sandios

Level 1

9 points

Apr 2, 2019 11:50 AM in response to Kaminosan

I don't think we have the same issue. You got Windows to run and are not having an error. I have never gotten it to run properly at all.

Reply

Answer 12

Kaminosan Author

Level 1

9 points

Apr 6, 2019 4:58 AM in response to Loner T

as per instruction, i use an older version of the windows iso (April 2018)..but still the same error

Reply

Answer 13

Kaminosan Author

Level 1

9 points

Apr 10, 2019 1:21 AM in response to Loner T

This is what i get when i use single user mode. But yeah, during recovery..there was an error. Something about afps cotainment (forgot to snap it)

Reply

Answer 14

Kaminosan Author

Level 1

9 points

Apr 10, 2019 7:17 AM in response to Loner T

Wow..it worked. Thank you so much T.T . May i at least know, whats up with the problem there ? A brief explanation for a newbie like me perhaps ?

Reply

Disk could not be partitioned (Bootcamp)

Similar questions