I’m trying to install Windows bootcamp again, because I tried to delete it to add more storage, and I’m stuck at the “Partitioning disk...” part. The first time and second time I have downloaded bootcamp it worked like a charm, but my recent tries have been really irritating. Any solutions?
iMac Pro
Uniblizz wrote:
(After 2nd try for Windows Install)
/dev/disk0 (internal, physical):
#: TYPE NAME SIZE IDENTIFIER
0: GUID_partition_scheme *1.0 TB disk0
1: EFI 209.7 MB disk0s1
2: Apple_APFS Container disk1 750.0 GB disk0s2
3: Microsoft Reserved 16.8 MB disk0s3
4: Microsoft Basic Data 250.0 GB disk0s4
If this is your current partition layout, run
diskutil eraseVolume jhfs+ BC1 disk0s3
diskutil eraseVolume jhfs+ BC2 disk0s4
diskutil mergePartitions jhfs+ BCMP disk0s3 disk0s4
If you these commands complete without any errors, then
diskutil eraseVolume fat32 BOOTCAMP disk0s3
and now run BCA and click on Remove/Restore.
Once you have your full disk space in macOS, re-run BCA and try to install Windows. You can skip the Create+Download steps.
If the download was successful, let the process continue.
Is the lid closed or open? If the display is asleep, but the Mac is awake, it should continue.
Nice. Is 250G enough storage? If yes, do you have a USB2 installer created by BC Assistant?
Take a look at Bootcamp User Interface - Apple Community. Do you have the Create and Download options when you run BC Assistant?
As expected. If the error message was different, we would have to try a different path. Click on OK, and click on Format, which should enable the Next button.
Beautiful. Now select EFI Boot and try.
This shows the issues related to the Kingston USB, which would not show up. 😉
If you do clean on the disk, you will also lose macOS. Do you have an MSR and MSD partition?
Does Shift+F10 open a CMD Window?
List disk:
list volume:
List partitions (If I type in list partition without the “s”, it says: “There is no disk selected to list partitions. Select a disk and try again.”
Run BCA and try to use the Install Option.
/dev/disk0 (internal, physical):
#: TYPE NAME SIZE IDENTIFIER
0: GUID_partition_scheme *1.0 TB disk0
1: EFI 209.7 MB disk0s1
2: Apple_APFS Container disk1 749.0 GB disk0s2
3: Windows Recovery 505.4 MB disk0s3
Finished erase on disk0
Started APFS operation
Aligning grow delta to 250,995,130,368 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 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 M5 was formatted by hfs_convert (945.230.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 Preboot was formatted by hfs_convert (945.230.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 diskmanagementd (945.230.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 apfs.util (945.230.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/disk0s2 appears to be OK
Storage system check exit code is 0
Growing APFS Physical Store disk0s2 from 748,999,999,488 to 999,995,129,856 bytes
Modifying partition map
Growing APFS data structures
Finished APFS operation
Sorry for the inconvenience, but I have to continue this tomorrow because I have school and it is late where I am. But thank you for helping so far ^_^
Uniblizz wrote:
Growing APFS Physical Store disk0s2 from 748,999,999,488 to 999,995,129,856 bytes
Modifying partition map
Growing APFS data structures
Finished APFS operation
Looks good.
Sorry for the inconvenience, but I have to continue this tomorrow because I have school and it is late where I am. But thank you for helping so far ^_^
Post back when you are ready.
It has been currently around 2 hours since it has been trying to partition the disk, I have decided to leave it to partition over night, because I will go to sleep right now. I’ll tell you when I’m ready to check why it’s taking this long.
Started APFS operation
Aligning shrink delta to 249,995,132,928 bytes and targeting a new physical store size of 749,999,996,928 bytes
Determined the minimum size for the targeted physical store of this APFS Container to be 612,001,173,504 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 M5 was formatted by hfs_convert (945.230.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 Preboot was formatted by hfs_convert (945.230.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 diskmanagementd (945.230.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 apfs.util (945.230.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/disk0s2 appears to be OK
Storage system check exit code is 0
Shrinking APFS Physical Store disk0s2 from 999,995,129,856 to 749,999,996,928 bytes
Shrinking APFS data structures
Shrinking partition
Modifying partition map
4096 bytes per physical sector
/dev/rdisk0s3: 488150592 sectors in 7627353 FAT32 clusters (32768 bytes/cluster)
bps=512 spc=64 res=32 nft=2 mid=0xf8 spt=32 hds=255 hid=1465253888 drv=0x80 bsec=488269824 bspf=59592 rdcl=2 infs=1 bkbs=6
Mounting disk
1 new disk created or changed due to APFS operation
Disk from APFS operation: disk0s3
Finished APFS operation
Partitioning disk taking too long
