bootcamp "your disk cannot be paritioned"

Question

Level 1

8 points

bootcamp "your disk cannot be paritioned"

I am currently having issues with bootcamp where i get the error message "your disk cannot be paritioned". ive tried using first aid numerous times, ive tried using first aid in safe mode, turning off time machine, and turning off filevault. Nothing has seemed to work so far. I've tried looking throughout the forums for an answer but i cant seem to find one.

I am currently on a MBP 15-inch mid 2015 running catalina 10.15.4

Loner T, if you're out there please help this poor soul.

MacBook Pro 15", macOS 10.15

Posted on Apr 10, 2020 8:09 PM

Reply

Answer 1

Loner T

Level 9

59,526 points

Apr 11, 2020 8:42 PM in response to hnlwoozy

Type 'exit' (without the quotes) at the '#' prompt, which will boot the Mac normally. Try to create a FAT32 (MSDOS-FAT) partition of the size you want Windows to be. See Partition a physical disk in Disk Utility on Mac - Apple Support for reference.

Reply

Answer 2

hnlwoozy Author

Level 1

8 points

Apr 11, 2020 3:56 PM in response to Loner T

i have no external peripherals connected to my mac. Put the command through terminal and this is what i got.

** 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 woozy - Data was formatted by diskmanagementd (945.230.6) and last modified by apfs_kext (1412.101.1).

** 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.41.3) and last modified by apfs_kext (1412.101.1).

** 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.41.3) and last modified by apfs_kext (1412.101.1).

** 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.41.3) and last modified by apfs_kext (1412.101.1).

** 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 woozy was formatted by diskmanagementd (1412.81.1) and last modified by apfs_kext (1412.101.1).

** 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: (0x30e0374+1) bitmap address (0x6d4c)

Fix overallocation (0x30e0374+1) bitmap address (0x6d4c)? NO

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

Reply

Answer 3

Loner T

Level 9

59,526 points

Apr 11, 2020 5:57 PM in response to hnlwoozy

Reboot and hold Command+S, which will put you in Single-User Mode. In the black-and-white console, at the '#' prompt, run

fsck_apfs -s -o -y /dev/rdisk1

and post the output. If you get an error about it being mounted read-write, then we need to install Catalina on an external disk and boot from it to address the issue.

Reply

Answer 4

hnlwoozy Author

Level 1

8 points

Apr 11, 2020 8:48 PM in response to Loner T

this is the error message im getting when partitioning

Partitioning disk “APPLE SSD SM0256G Media” (disk0)

Resizing the startup volume will cause this computer to stop responding.

Running operation 1 of 2: Add “Untitled” 75.03 GB by shrinking container disk1 “woozy” (disk0s2) from 250.79 GB to 175.76 GB…

Aligning shrink delta to 75,027,746,816 bytes and targeting a new physical store size of 175,762,690,048 bytes

Determined the minimum size for the targeted physical store of this APFS Container to be 82,158,026,752 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 -S /dev/disk0s2

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 woozy - Data was formatted by diskmanagementd (945.230.6) and last modified by apfs_kext (1412.101.1).

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.41.3) and last modified by apfs_kext (1412.101.1).

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.41.3) and last modified by apfs_kext (1412.101.1).

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.41.3) and last modified by apfs_kext (1412.101.1).

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 woozy was formatted by diskmanagementd (1412.81.1) and last modified by apfs_kext (1412.101.1).

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: (0x30e0374+1) bitmap address (0x6d4c)

The volume /dev/disk0s2 appears to be OK.

Storage system check exit code is 0.

Shrinking APFS Physical Store disk0s2 from 250,790,436,864 to 175,762,690,048 bytes

Shrinking APFS data structures

APFS Container Resize error code is 49187

A problem occurred while resizing APFS Container structures. : (-69606)

Operation failed…

Reply

Answer 5

Loner T

Level 9

59,526 points

Apr 11, 2020 9:19 PM in response to hnlwoozy

hnlwoozy wrote:

this is the error message im getting when partitioning

Verifying allocated space.

warning: overallocation detected on Main device: (0x30e0374+1) bitmap address (0x6d4c)

The volume /dev/disk0s2 appears to be OK.

Storage system check exit code is 0.

Shrinking APFS Physical Store disk0s2 from 250,790,436,864 to 175,762,690,048 bytes

Shrinking APFS data structures

APFS Container Resize error code is 49187

A problem occurred while resizing APFS Container structures. : (-69606)

Operation failed…

This is what we are trying to fix in Single-User Mode.

Do you have a Time Machine backup of macOS?

Reply

Answer 6

Loner T

Level 9

59,526 points

Apr 12, 2020 7:01 AM in response to hnlwoozy

You may want to erase the whole internal disk (not just Macintosh HD) and restoring your backup. Also, run a SMC and NVRAM reset before your next attempt at installing Windows.

Reply

Answer 7

Loner T

Level 9

59,526 points

Apr 11, 2020 5:49 AM in response to hnlwoozy

Do you have any external peripherals connected to the Mac?

From macOS Terminal, post the output of

sudo fsck_apfs -n -l /dev/rdisk1

The command can freeze the Mac temporarily.

Reply

Answer 8

hnlwoozy Author

Level 1

8 points

Apr 11, 2020 6:01 PM in response to Loner T

put the command through terminal and this is what i got.

hnlwoozy@henrys-MacBook-Pro ~ % fsck_apfs -s -o -y /dev/rdisk1

error: container /dev/rdisk1 is mounted with write access.

Reply

Answer 9

Loner T

Level 9

59,526 points

Apr 11, 2020 6:57 PM in response to hnlwoozy

This is a known bug in Catalina. Do you have an external disk of 64+GB, which can be wiped and Catalina installed on it?

Reply

Answer 10

hnlwoozy Author

Level 1

8 points

Apr 11, 2020 7:00 PM in response to Loner T

no i dont at the moment

Reply

Answer 11

hnlwoozy Author

Level 1

8 points

Apr 11, 2020 9:22 PM in response to Loner T

yes i have a current time machine backup

Reply

Answer 12

hnlwoozy Author

Level 1

8 points

Apr 12, 2020 1:51 PM in response to Loner T

will i have to change the format of the disk? or will i still use APFS

Reply

Answer 13

Loner T

Level 9

59,526 points

Apr 12, 2020 4:55 PM in response to hnlwoozy

High Sierra/Mojave/Catalina will use APFS. Unless you want to downgrade to Sierra, you will need to use APFS. Since you are restoring the 'full' system, it will be APFS.

Reply

Answer 14

hnlwoozy Author

Level 1

8 points

Apr 13, 2020 11:15 PM in response to Loner T

ended up erasing my disk completely and reinstalling catalina. reset the SMC and NVRAM and everything seems to work flawlessly now. thank you so much Loner T.

Reply

Answer 15

Loner T

Level 9

59,526 points

Apr 14, 2020 4:23 AM in response to hnlwoozy

Excellent!

Reply

bootcamp "your disk cannot be paritioned"

Similar questions