Your disk could not be partitioned

Question

Level 1

8 points

Your disk could not be partitioned

I'm trying to install Windows 10 with Bootcamp. I did it a week ago and it worked well. But partition that I created was too small for me so I run BCA today and deleted partition with Windows to install it again.

Unfortunately when I try to install Windows again with BCA I got error after few minutes "your disc could not be partitioned."

I already used DiskUtility, checked disk with CMD+R, reset PRAM SMC etc. I even tried to create partition by my own and I got same error at the end APFS: 49187.

diskutil list

/dev/disk0 (internal):
   #:                       TYPE NAME                    SIZE       IDENTIFIER
   0:      GUID_partition_scheme                         1.0 TB     disk0
   1:                        EFI EFI                     314.6 MB   disk0s1
   2:                 Apple_APFS Container disk1         1.0 TB     disk0s2

/dev/disk1 (synthesized):
   #:                       TYPE NAME                    SIZE       IDENTIFIER
   0:      APFS Container Scheme -                      +1.0 TB     disk1
                                 Physical Store disk0s2
   1:                APFS Volume Macintosh HD            390.5 GB   disk1s1
   2:                APFS Volume Preboot                 148.0 MB   disk1s2
   3:                APFS Volume Recovery                2.6 GB     disk1s3
   4:                APFS Volume VM                      2.1 GB     disk1s4

Any ideas?

iMac 27 5K i7 1TB SSD 2017 with Mojave 10.14.1

Posted on Dec 14, 2018 2:40 AM

Reply

Answer 1

p.czechowski Author

Level 1

8 points

Dec 14, 2018 5:52 AM in response to Loner T

I tried one more time to create FAT partition, but no luck again.

Sorry it's in polish but I think you will get what it says:

problems with overlocation
APFS error 49187
There was a problem with changing size of container APFS
Operation didn't succeed.

Wykonuję operację 1 z 2: Dodaj „Bez nazwy” 301,16 GB, dzieląc „Macintosh HD” (disk0s2) z 1 TB na 699,08 GB…
Zrównuję zmniejszenie do 301 156 298 752 B i próbuję osiągnąć nową docelową wielkość dysku fizycznego (699 084 664 832 B)
Ustalona minimalna wielkość docelowego dysku fizycznego tego kontenera APFS to 443 924 824 064 B
Zmieniam wielkość kontenera APFS wyznaczonego przez odwołanie kontenera APFS disk1
Wskazany dysk fizyczny APFS, którego wielkość jest zmieniana, to disk0s2
Weryfikuję system pamięci masowej
Używam trybu aktywnego.
Wykonuję 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 HD was formatted by newfs_apfs (748.57.19) 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 (748.1.46) 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 (748.1.46) 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 (748.1.46) 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: (6084008+1) bitmap address (17a46)
warning: Overallocation Detected on Main device: (145141476+1) bitmap address (18166)
warning: Overallocation Detected on Main device: (196466012+1) bitmap address (18dff)
warning: Overallocation Detected on Main device: (196825951+1) bitmap address (18e09)
Performing deferred repairs.
The volume /dev/disk0s2 appears to be OK.
Kod wyjściowy sprawdzania systemu pamięci masowej: 0.
Pomniejszam dysk APFS disk0s2 z 1 000 240 963 584 do 699 084 664 832 bajtów
Pomniejszam struktury danych APFS
Kod błędu zmiany wielkości kontenera APFS: 49187
Wystąpił problem podczas zmiany wielkości struktur kontenera APFS.

Operacja nie powiodła się…

Reply

Answer 2

p.czechowski Author

Level 1

8 points

Dec 14, 2018 5:43 AM 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 newfs_apfs (748.57.19) 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 (748.1.46) 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 (748.1.46) 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 (748.1.46) 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: (6084008+1) bitmap address (17a46)
warning: Overallocation Detected on Main device: (145141476+1) bitmap address (18166)
warning: Overallocation Detected on Main device: (196466012+1) bitmap address (18dff)
warning: Overallocation Detected on Main device: (196825951+1) bitmap address (18e09)
** Performing deferred repairs.
** The volume /dev/rdisk1 appears to be OK.

Reply

Answer 3

p.czechowski Author

Level 1

8 points

Dec 14, 2018 11:45 AM in response to p.czechowski

So I decided to check if I can create any other size of FAT partition but not the I need. It worked when I set size to 189GB - it didn't work with 195GB or more.. How can I change that 'cause I want 300GB partition not 189GB ? :) I got enough free space on SSD.

Reply

Answer 4

p.czechowski Author

Level 1

8 points

Dec 14, 2018 12:15 PM in response to p.czechowski

So even I can create FAT32 partition I can not install Windows (after erasing partition that I've created earlier). I tried for few times.

Every time I'm setting partition size in BCA smaller and smaller (now it's 149GB) it starts to download something, then starts to create partition and .... error. Can not create partition ............. but partition is visible in DiskUtil. I need to remove it before next try with BCA ..... looks like I'm not able to install Windows.

From what I can see on this discussion board every day many people ask the same question - how to install Windows or create partition!? Is Apple serious with this???? It looks like quite big problem with MacOS software or SSD.

Reply

Answer 5

p.czechowski Author

Level 1

8 points

Dec 14, 2018 1:23 PM in response to Loner T

Right now I'm without any OS on my internal SSD ... and lack of empty external drives ;)

I bought my iMac with Sierra on board so it shows me I can go back to Sierra - but apparently I can't. Do I have to reinstall Mojave or I can use Sierra install?

Here where I live its 10pm so shops are closed. If I buy external SSD tomorrow will I be able to install Windows with BCA on it?

Reply

Answer 6

p.czechowski Author

Level 1

8 points

Dec 14, 2018 2:00 PM in response to Loner T

So I managed finally to install Sierra on my internal 1TB SSD. Then I used BootCampAssist to install Windows 10 - it created partition with size that I wanted which is 300GB.

Now I'm planing to upgrade Sierra to Mojave and not deleting Windows partition - will this work? :)

Reply

Answer 7

p.czechowski Author

Level 1

8 points

Dec 14, 2018 3:20 AM in response to p.czechowski

PS. I don't use Time Machine or FileVault encryption - they are disabled.

Reply

Answer 8

Loner T

Level 9

59,471 points

Dec 14, 2018 5:07 AM in response to p.czechowski

Post the output of

sudo fsck_apfs -n -l /dev/rdisk1

Reply

Answer 9

Loner T

Level 9

59,471 points

Dec 14, 2018 12:57 PM in response to p.czechowski

Can you post the output of

diskutil apfs list

Reply

Answer 10

p.czechowski Author

Level 1

8 points

Dec 14, 2018 1:14 PM in response to Loner T

At the moment I'm trying to install Sierra with Shift+Option+Cmd+R ... I erased SSD, started installation. It downloaded system but after a while it gives me icon O with / across.

Reply