Bootcamp stuck on partitioning a disk

Question

Level 1

12 points

Bootcamp stuck on partitioning a disk

Hello there,

I've been using Bootcamp Windows since last April, just to play some Windows-supported games on my MacBook Pro (15-inch, 2019). Recently, I started to see some FPS drops and did tons of things on Windows, but none of them was helpful. That being said, I decided to delete BC Windows, and re-install it again. The thing is, it doesn't work. BC gets stuck on the partitioning disk and the system becomes unresponsive despite waiting for 3-4 hours. As I have done this process in early April 2020, I don't remember that I was waiting for this much to install Windows OS.

Followed your comments in this thread as well but couldn't find any solution. Would you be able to help me to figure out what's happening and why I cannot use BC to install windows?

My MacOS version is: Catalina 10.15.7

Thank you in advance!

MacBook Pro 15″, macOS 10.15

Posted on Feb 20, 2021 11:21 AM

Reply

Answer 1

eergun Author

Level 1

12 points

Feb 20, 2021 11:29 AM in response to Loner T

There you go:

** 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 - Data was formatted by newfs_apfs (945.200.129.100.1) and last modified by apfs_kext (1412.141.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.77.4) and last modified by apfs_kext (1412.141.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.77.4) and last modified by apfs_kext (1412.141.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 apfs.util (945.260.7) and last modified by apfs_kext (1412.141.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 Macintosh HD was formatted by diskmanagementd (1412.61.1) and last modified by apfs_kext (1412.141.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.

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

Reply

Answer 2

Loner T

Level 9

59,513 points

Feb 20, 2021 11:27 AM in response to eergun

From macOS Terminal, post the output of

sudo fsck_apfs -n -l /dev/rdisk1

Reply

Answer 3

Loner T

Level 9

59,513 points

Feb 20, 2021 11:46 AM in response to eergun

As a test, using Disk Utility, create a partition (not an APFS Volume), of the size you want Windows to be. Post the messages you see after you expand the Detail section.

Reply

Answer 4

eergun Author

Level 1

12 points

Feb 20, 2021 11:47 AM in response to Loner T

I have tried this as well, according to your comments in another thread. The system stuck again while doing the partition, so I had to restart the computer.

Reply