I have over 80 GBs of space left on my SSD, but boot camp assistant keeps saying I don't have enough and that I need 42 GBs of space. I even created a blank FAT partition of 50 GBs, just to test it out, and when I rerun Boot Camp Assistant, it wants to remove the "Windows partition," even though it is NOT a windows partition. I'm on a 15" Macbook Pro from 2018, running Catalina 10.15.6.
MacBook Pro 15”, macOS 10.15
But if it is an issue with the current setup, wouldn't restoring a backup of the current setup just recreate the problem? I know for sure a clean/fresh reinstall will work, but I REALLY don't want to lose all my apps (not worried about the data, as everything is in the cloud).
Sounds good. So I should go into macOS Recovery mode using Command-R and selecting Restore From Time Machine Backup? I guess I’ll do that tonight, and get back to you tomorrow. Thank you so much for sticking with me thus far!
Ok, so I went ahead and did that, and I think the file system got even more messed up. Whereas before I had over 80 GBs of space free, now it says I have only 7 GBs of space free... how can this be the case? My "Other Volumes in the Container" has ballooned to over 84 GBs, but there are no other volumes...
Actually, it doesn’t seem to have mattered. I tried that command for both, and it gave the same output.
I did have it turned on. I turned it off, and it still gave the same error about not being able to partition the disk.
Yes, I do.
Back to square 1: The startup disk does not have enough space to be partitioned.
It won't let me partition the drive, saying, "This container can’t be split, because the resulting containers would be too small."
So the first 3 are the same as before: disk0 is the internal, physical, disk1 is the one that has the HFS macOS Base System on it, and disk2 is the (synthesized) APFS Container that has a 5 of Volumes for preboot, recovery, VM, Macintosh HD, and Macintosh HD - Data, each with identifiers ranging from disk2, to disk2s5. Just to be certain, I should put disk2, right, not disk0s2, which is the Apple Container volume of disk0?
EDIT: Apologies, the output isn’t exactly the same as before. Because I can’t copy/paste, I recreated it manually below:
/dev/disk0 (internal, physical):
#: TYPE NAME. SIZE IDENTIFIER
0: GUID_partition_scheme. *251.0 GB disk0
1: EFI EFI. 314.6 MB disk0s1
2: Apple_APFS Container disk2. 250.7 GB. disk0s2
/dev/disk1 (disk image):
#: TYPE NAME. SIZE IDENTIFIER
0: GUID_partition_scheme. *2.1 GB disk1
1: Apple_HFS macOS Base System 250.7 GB. disk1s1
/dev/disk2 (synthesized):
#: TYPE NAME. SIZE IDENTIFIER
0: APFS Container Scheme - Physical Store disk0s2 +250.7 GB disk2
1: APFS Volume Macintosh HD - Data 87.3 GB disk2s1
2: APFS Volume Preboot 86.4 MB disk2s2
3: APFS Volume Recovery 528.9 MB disk2s3
4: APFS Volume VM 1.1 GB disk2s4
5: APFS Volume Macintosh HD 11.4 GB disk2s5
HovikGaspar wrote:
But if it is an issue with the current setup, wouldn't restoring a backup of the current setup just recreate the problem?
No. You are rebuilding the entire file system, one file at a time, as the files are restored.
I know for sure a clean/fresh reinstall will work, but I REALLY don't want to lose all my apps (not worried about the data, as everything is in the cloud).
Erasing the disk(s) and rebuilding the file system acts like a fsck, but it is much slower than one.
/dev/disk0 (internal, physical):
#: TYPE NAME SIZE IDENTIFIER
0: GUID_partition_scheme *251.0 GB disk0
1: EFI EFI 314.6 MB disk0s1
2: Apple_APFS Container disk1 250.7 GB disk0s2
/dev/disk1 (synthesized):
#: TYPE NAME SIZE IDENTIFIER
0: APFS Container Scheme - +250.7 GB disk1
Physical Store disk0s2
1: APFS Volume Macintosh HD - Data 137.7 GB disk1s1
2: APFS Volume Preboot 86.3 MB disk1s2
3: APFS Volume Recovery 525.7 MB disk1s3
4: APFS Volume VM 3.2 GB disk1s4
5: APFS Volume Macintosh HD 11.1 GB disk1s5
Since you have a TM backup, erase the whole disk, install a clean copy of the same version of macOS, without any other software, install Windows and test and verify. If Windows works, then restore your TM backup and test and verify (again!).
I guess it is a size issue? I tried it again, with a smaller partition size (46 GBs) and it went through... here is the full output from that:
Do you have a Time Machine backup? If not, can you create one now?
You want to erase the whole internal disk in Internet Recovery, not Local Recovery. Then restore the TM backup and retry BC Assistant.
Boot Camp Assistant Says Not Enough Space When There is Plenty of Space