Apple Intelligence is now available on iPhone, iPad, and Mac!
Hello, I have a question about Boot Camp. So I wanted to install windows, but Boot Camp Assistant gave an error: "Your disk could not be partitioned
An error occurred while partitioning the disk. Please run First Aid from within Disk Utility to check and fix the error". First aid said there weren't any problems. I am using macOS Big Sur 11.2.3.
I have had Windows installed earlier, and removed it, but now I want it back.
MacBook Air 13″, macOS 10.15
Can you upgrade to the latest version of macOS? See What's new in the updates for macOS Big Sur - Apple Support for reference.
If you have APFS corruption, from macOS Terminal, post the output of
sudo fsck_apfs -n -l /dev/rdisk1
If you have a Mac with a Fusion drive, then post the output of
sudo fsck_apfs -n -l /dev/rdisk2
Naut7 wrote:
https://discussions.apple.com/content/attachment/290a67c4-3058-4730-8c46-f83b9b499cdb
I am not sure, is the value of N still 1 here?
It is 2. Run
diskutil unmountDisk disk2
fsck_apfs -s -o -y /dev/rdisk2
Disk0s2 is the physical partition. Disk1 is the Container disk. In Internet Recovery, you will need to
Be aware that disk1 need to be the Container disk in Internet Recovery, since macOS can mount it anywhere. If the disk is diskN, you will need to find the value of N by running diskutil list internal or (diskutil list) command and checking the output.
I updated my macbook, ran the command, this is the output:
** Checking the container superblock.
Checking the checkpoint with transaction ID 3553472.
** 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.84) and last modified by apfs_kext (1677.120.9).
** Checking the object map.
** Checking the snapshot metadata tree.
** Checking the snapshot metadata.
** Checking the extent ref tree.
** Checking the fsroot tree.
warning: apfs_fs_alloc_count is not valid (expected 13531069, actual 13531453)
Fix apfs_fs_alloc_count(oid 0x402, xid 0x3638c0)? NO
** Checking volume.
** Checking the APFS volume superblock.
The volume Preboot was formatted by newfs_apfs (748.30.60) and last modified by apfs_kext (1677.120.9).
** 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.30.60) and last modified by apfs_kext (1677.120.9).
** 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.250.134) and last modified by apfs_kext (1677.120.9).
** 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 storagekitd (1677.81.1) and last modified by apfs_kext (1677.120.9).
** Checking the object map.
** Checking the snapshot metadata tree.
** Checking the snapshot metadata.
** Checking snapshot 1 of 1 (com.apple.os.update-F8CC686BD994CAC58E0A525C64B2C9D6329887202C9FA5AC86D15A7994507C67)
** Checking the extent ref tree.
** Checking the fsroot tree.
** Checking the file extent tree.
** Checking volume.
** Checking the APFS volume superblock.
The volume Update was formatted by com.apple.Mobile (1677.81.1) and last modified by apfs_kext (1677.120.9).
** 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: (0x2de9ddc+384) bitmap address (0x105ba)
Fix overallocation (0x2de9ddc+384) bitmap address (0x105ba)? NO
** The volume /dev/rdisk1 appears to be OK.
I don't know if it matters but my Macintosh HD APFS System Volume now says "System Snapshot Mounted" and is sort of grey.
Thanks for helping btw
So I booted my macbook in internet recovery mode by holding "cmd, alt / option (alt and option are the same as far as I know), and r" while booting up, and it worked. I ran the disk utility list before:
So the afps container was "disk0s2". The command I ran was "fsck_afps -s -o -y /dev/rdisk0s2" like you said. It gave me the output "error: container /dev/rdisk0s2 is mounted with write acces."
I tried running the command with sudo in front of it but it said "sudo isn't a command".
Did I use the wrong disk? Or is something else wrong?
This is my output:
** 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.84) and last modified by apfs_kext (1677.81.1).
** Checking the object map.
** Checking the snapshot metadata tree.
** Checking the snapshot metadata.
** Checking the extent ref tree.
** Checking the fsroot tree.
warning: apfs_fs_alloc_count is not valid (expected 14006898, actual 14007282)
Fix apfs_fs_alloc_count (oid 0x402, xid 0x363230)? NO
** Checking volume.
** Checking the APFS volume superblock.
** The volume Preboot was formatted by newfs_apfs (748.30.60) and last modified by apfs_kext (1677.81.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.30.60) and last modified by apfs_kext (1677.81.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.250.134) and last modified by apfs_kext (1677.81.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 storagekitd (1677.81.1) and last modified by apfs_kext (1677.81.1).
** Checking the object map.
** Checking the snapshot metadata tree.
** Checking the snapshot metadata.
** Checking snapshot 1 of 2 (com.apple.os.update-35C699ADD439C653A3B09EBD8A30FBD366881244EB7C82207A2E135362FCCB7F)
** Checking snapshot 2 of 2 (com.apple.os.update-MSUPrepareUpdate)
warning: snapshot fsroot/file key rolling tree corruptions are not repaired; they'll go away once the snapshot is deleted
** Checking the extent ref tree.
** Checking the fsroot tree.
** Checking the file extent tree.
** Checking volume.
** Checking the APFS volume superblock.
** The volume Update was formatted by com.apple.Mobile (1677.81.1) and last modified by apfs_kext (1677.81.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: (0x2de9ddc+384) bitmap address (0x105ba)
Fix overallocation (0x2de9ddc+384) bitmap address (0x105ba)? NO
** The volume /dev/rdisk1 appears to be OK.
I'll update to the latest version of macOS later today.
The fsck_apfs command is running in diagnostic mode, when macOS is booted normally. To address corruption issues, we need to boot the Mac in Internet Recovery (not Local recovery) and in Utilities -> Terminal, run
fsck_apfs -s -o -y /dev/rdiskN
N should point to the APFS Container. Its value can be found by running diskutil list command.
Can you run the fsck_apfs command once more? The 'YES' output should no longer be there.
I am not sure, is the value of N still 1 here?
I ran the commands, this is my output:
The YES is indeed gone as shown below:
Does this mean it is now fixed? Or is there more to do?
Yes! It worked! Thanks a lot for helping me!
After you update macOS, re-run the fsck_apfs and we can check if any repairs are necessary.
Good! Please retry BC Assistant, and post back if you still issues during partitioning. If partitioning is successful, but you are still running into issues, please post back.
Excellent!
Windows bootcamp not working
