Bootcamp cannot partition on a clean mojave install

Question

Level 1

13 points

Bootcamp cannot partition on a clean mojave install

hi,

i have fresh installed Mojave and now wanted to install windows 10... cant seem to get bootcamp to work!

i have no local screenshots, no time machine, nothing fancy.... i am 99% sure its just a problem with APFS file system and how my volumes/ containers are held.

here is the result of "diskutil apfs list"

APFS Container (1 found)

|

+-- Container disk1 B4B1ED26-E559-4C02-B07E-71B5DA2C1495

    ====================================================

    APFS Container Reference:     disk1

    Size (Capacity Ceiling):      121123069952 B (121.1 GB)

    Capacity In Use By Volumes:   44424155136 B (44.4 GB) (36.7% used)

    Capacity Not Allocated:       76698914816 B (76.7 GB) (63.3% free)

    |

    +-< Physical Store disk0s2 9653DCA7-4815-404A-BA4F-EA28BBBD76DA

    |   -----------------------------------------------------------

    |   APFS Physical Store Disk:   disk0s2

    |   Size:                       121123069952 B (121.1 GB)

    |

    +-> Volume disk1s1 8A3AC255-B74C-402C-B69C-72DF17A62F74

    |   ---------------------------------------------------

    |   APFS Volume Disk (Role):   disk1s1 (No specific role)

    |   Name:                      Macintosh (Case-insensitive)

    |   Mount Point:               /

    |   Capacity Consumed:         42120503296 B (42.1 GB)

    |   FileVault:                 No

    |

    +-> Volume disk1s2 64824D4D-D7EA-4852-BB67-BD0256DB83EF

    |   ---------------------------------------------------

    |   APFS Volume Disk (Role):   disk1s2 (Preboot)

    |   Name:                      Preboot (Case-insensitive)

    |   Mount Point:               Not Mounted

    |   Capacity Consumed:         72953856 B (73.0 MB)

    |   FileVault:                 No

    |

    +-> Volume disk1s3 AE0276D3-CB12-4750-A99B-CF7D257DEC46

    |   ---------------------------------------------------

    |   APFS Volume Disk (Role):   disk1s3 (Recovery)

    |   Name:                      Recovery (Case-insensitive)

    |   Mount Point:               Not Mounted

    |   Capacity Consumed:         1030520832 B (1.0 GB)

    |   FileVault:                 No

    |

    +-> Volume disk1s4 F3561C7B-F0E8-497C-AA5E-0E41B4F22392

        ---------------------------------------------------

        APFS Volume Disk (Role):   disk1s4 (VM)

        Name:                      VM (Case-insensitive)

        Mount Point:               /Volumes/VM

        Capacity Consumed:         1073766400 B (1.1 GB)

        FileVault:                 No

Any help Highly appriciated !

i see someone has helped with apfs here --> https://discussions.apple.com/thread/8437314 , looking for someone to guide me like this.

MacBook Air

Posted on Dec 13, 2018 8:20 PM

Reply

Answer 1

Dec 14, 2018 5:55 AM in response to BooAndBoo

Looks like I got similiar problem.

https://discussions.apple.com/thread/250021042

Funny thing I've installed Windows with Bootcamp week ago, today I erased it with BCA, and now I can't even create a FAT partition :(

Reply

Answer 2

BooAndBoo Author

Level 1

13 points

Dec 13, 2018 9:40 PM in response to BooAndBoo

just for reference , heres the output of "diskutil list"

/dev/disk0 (internal, physical):

   #:                       TYPE NAME                    SIZE       IDENTIFIER

   0:      GUID_partition_scheme                        *121.3 GB   disk0

   1:                        EFI EFI                     209.7 MB   disk0s1

   2:                 Apple_APFS Container disk1         121.1 GB   disk0s2



/dev/disk1 (synthesized):

   #:                       TYPE NAME                    SIZE       IDENTIFIER

   0:      APFS Container Scheme -                      +121.1 GB   disk1

                                 Physical Store disk0s2

   1:                APFS Volume Macintosh               42.2 GB    disk1s1

   2:                APFS Volume Preboot                 73.0 MB    disk1s2

   3:                APFS Volume Recovery                1.0 GB     disk1s3

   4:                APFS Volume VM                      1.1 GB     disk1s4

Reply

Answer 3

Loner T

Level 9

59,471 points

Dec 14, 2018 1:48 AM in response to BooAndBoo

You do not have the same issue as the linked discussion that you are referring to. As a test, try to create a FAT partition (not an APFS volume) using Disk Utility, of the size you want Windows to be, and report any errors.

Reply

Answer 4

BooAndBoo Author

Level 1

13 points

Dec 14, 2018 2:56 AM in response to Loner T

Partitioning disk “APPLE SSD SD0128F Media” (disk0)

Running operation 1 of 2: Add “Windoz” 60.56 GB by splitting “Macintosh” (disk0s2) from 121.12 GB to 60.56 GB…
Aligning shrink delta to 60,56,15,34,976 bytes and targeting a new physical store size of 60,56,15,34,976 bytes
Determined the minimum size for the targeted physical store of this APFS Container to be 47,58,11,67,616 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 Macintosh was formatted by diskmanagementd (945.200.129) and last modified by apfs_kext (945.220.38).
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 (apfs-687.0.0.1.7) and last modified by apfs_kext (945.220.38).
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 (apfs-687.0.0.1.7) and last modified by apfs_kext (945.220.38).
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 (apfs-687.0.0.1.7) and last modified by apfs_kext (945.220.38).
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: (7067409+1) bitmap address (e5a9)
warning: Overallocation Detected on Main device: (25960708+1) bitmap address (e7ea)
Performing deferred repairs.
The volume /dev/disk0s2 appears to be OK.
Storage system check exit code is 0.
Shrinking APFS Physical Store disk0s2 from 1,21,12,30,69,952 to 60,56,15,34,976 bytes
Shrinking APFS data structures
APFS Container Resize error code is 49187
A problem occurred while resizing APFS Container structures.

Operation failed…

yeah... the operation failed.. no idea why.

and thank you for taking so much interest in this :D ... you are literally doing something which was basically Apples responsibility!

Reply

Answer 5

BooAndBoo Author

Level 1

13 points

Dec 14, 2018 7:42 PM in response to Loner T

i guess, i could clean my external hard drive.... format it with apfs and turn on the TM backup....

but how would that help?

if you have some solution involving total loss of data/ FORMATting drive .... i am totally fine with that, i dont have any sensitive data in the laptop... i have them backed up.

Reply

Answer 6

Loner T

Level 9

59,471 points

Dec 14, 2018 8:05 PM in response to BooAndBoo

i guess, i could clean my external hard drive.... format it with apfs and turn on the TM backup....

No, you do not need to.

if you have some solution involving total loss of data/ FORMATting drive .... i am totally fine with that, i dont have any sensitive data in the laptop... i have them backed up.

Before we nuke-and-pave, you can boot into Single-User Mode, and try to run fsck_apfs to correct the over-allocation. If we cannot (Mojave does not always do this), then we can erase the whole internal disk and try Bootcamp.

What is the year/model of your Mac (do not post the serial number)? Also (depending on you model), one option to consider, if possible, is to install Sierra, install Windows, and then upgrade to Mojave. The 120GB disk seems indicate that it is a MacBook Air.

Reply

Answer 7

BooAndBoo Author

Level 1

13 points

Dec 18, 2018 9:00 AM in response to Loner T

hey... can you help me with another laptop please?

same problem I think... idk...

heres the result of "disk"util list"

/dev/disk0 (internal, physical):
   #:                       TYPE NAME                    SIZE       IDENTIFIER
   0:      GUID_partition_scheme                        *121.3 GB   disk0
   1:                        EFI EFI                     209.7 MB   disk0s1
   2:          Apple_CoreStorage Macintosh HD            120.5 GB   disk0s2
   3:                 Apple_Boot Recovery HD             650.0 MB   disk0s3

/dev/disk1 (internal, virtual):
   #:                       TYPE NAME                    SIZE       IDENTIFIER
   0:                  Apple_HFS Macintosh HD           +120.1 GB   disk1
                                 Logical Volume on disk0s2
                                 36D0CC20-636F-4680-A367-8FEA28EBE7C8
                                 Unencrypted

this is my brothers laptop, he recently formatted it and installed Sierra ... its in HFS format, and possibly has that OVER-allocation problem...

Reply