You can make a difference in the Apple Support Community!

When you sign up with your Apple Account, you can provide valuable feedback to other community members by upvoting helpful replies and User Tips.

Looks like no one’s replied in a while. To start the conversation again, simply ask a new question.

User profile for user: Nigel_Sim
Nigel_Sim Author
User level: Level 1
8 points

bootcamp problem - partition error! I swear I've tried it all!

So I've tried everything in previous posts, and I'm stumped!


I've done the single user start up fix.

I've done disk utility

I've turned off time machine

I've deleted snapshots

I've made sure FileVault was off

I've tried 40gb, all the way to 100gb in 10gb increments for install.

I've been so desperate as to wipe my entire MacBook and start from scratch!


I cannot get past the disk partition error!


Please someone save me!


Im working with:

MacBook (Retina, 12-inch, 2017)

Processor: 1.2 GHz Intel Core m3

Memory: 8 GB 1867 MHz LPDDR3

Graphics: Intel HD Graphics 615 1536 MB


Running Latest MacOS Mojave

MacBook

Posted on Jan 18, 2019 3:07 PM

Reply
Question marked as Top-ranking reply
User profile for user: Loner T
Loner T
User level: Level 9
59,513 points

Posted on Jan 18, 2019 6:31 PM


** Verifying allocated space.

warning: Overallocation Detected on Main device: (40777241+1) bitmap address (f307)

warning: Overallocation Detected on Main device: (60862312+1) bitmap address (f337)

This is not good. Start up your Mac in single-user mode or verbose mode - Apple Support and run


fsck_apfs -s -o -y /dev/rdisk1


You will need to post a photograph. Please see the note after step 6.

View in context

Similar questions

12 replies
Question marked as Top-ranking reply
User profile for user: Loner T
Loner T
User level: Level 9
59,513 points

Jan 18, 2019 6:31 PM in response to Nigel_Sim


** Verifying allocated space.

warning: Overallocation Detected on Main device: (40777241+1) bitmap address (f307)

warning: Overallocation Detected on Main device: (60862312+1) bitmap address (f337)

This is not good. Start up your Mac in single-user mode or verbose mode - Apple Support and run


fsck_apfs -s -o -y /dev/rdisk1


You will need to post a photograph. Please see the note after step 6.

Reply
User profile for user: Nigel_Sim
Nigel_Sim Author
User level: Level 1
8 points

Jan 18, 2019 4:08 PM in response to Loner T

** 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 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 Preboot was formatted by newfs_apfs (748.30.60) 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 newfs_apfs (748.30.60) 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 newfs_apfs (748.57.19) 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.


warning: Overallocation Detected on Main device: (40777241+1) bitmap address (f307)


warning: Overallocation Detected on Main device: (60862312+1) bitmap address (f337)


** Performing deferred repairs.


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



I am on Mojave 10.14.2 if that helps

Reply
User profile for user: Nigel_Sim
Nigel_Sim Author
User level: Level 1
8 points

Jan 19, 2019 11:45 AM in response to Loner T

I will snap a photo as soon as I wrap up this bootcamp install! HAHAHA jumped the gun I’m sorry! But what you did worked!!! I cannot thank you enough, I was racking my brain and getting ready to frisbee this beautiful computer out the window!


Thank you thank you thank you!!!


im also very behind on homework since I needed windows to complete an assignment.


What all did you ask me to do? No idea what all those command prompts were.

Reply
User profile for user: Loner T
Loner T
User level: Level 9
59,513 points

Jan 19, 2019 11:53 AM in response to Nigel_Sim

I will snap a photo as soon as I wrap up this bootcamp install! HAHAHA jumped the gun I’m sorry! But what you did worked!!! I cannot thank you enough, I was racking my brain and getting ready to frisbee this beautiful computer out the window!

Look under your Window(s) for an outstretched pair of hands waiting to catch that 'frisbee'.

Thank you thank you thank you!!!

Excellent.

im also very behind on homework since I needed windows to complete an assignment.

You can not use the-computer-ate-my-homework excuse any more.

What all did you ask me to do? No idea what all those command prompts were.

Fsck tries to correct file system issues. In your case, it worked.

Reply
User profile for user: Nigel_Sim
Nigel_Sim Author
User level: Level 1
8 points

Jan 19, 2019 2:40 PM in response to Loner T

** 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 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 Preboot was formatted by newfs_apfs (748.30.60) 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 newfs_apfs (748.30.60) 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 newfs_apfs (748.57.19) 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/rdisk1 appears to be OK.


Nigels-MacBook:~ nigelsim$ 



There is the output! THANK YOU AGAIN!

Reply

bootcamp problem - partition error! I swear I've tried it all!

Welcome to Apple Support Community
A forum where Apple customers help each other with their products. Get started with your Apple Account.
Learn more Sign up