Boot camp error, disk cannot be partitioned

I ran into this same problem. It was a simple mistake on my part. When in the Disk Utility program, make sure to mount the main Mac partition volume, then run Disk Utility on the volume using the first aid function. I had been running it only on the disk, not the volume. Since my SSD was formatted in MacOS Journal with encryption, a password had to be entered to mount the volume. Once this was completed, it all worked.

I have the same issue.

iMac (27-inch, Late 2012)

I have done the following:

1. Disk Utility run first aid.

2. /Sbin/fsck -fy trick

3. Larger thumbdrive

4. Total clean re-install of OSX (10.12.4)

5. Called Apple

6. Tried with everything disconnected

Not sure what to try next......

The output is misaligned. Your diskutil list should look similar to the following.

diskutil list

/dev/disk0 (internal, physical):

#: TYPE NAME SIZE IDENTIFIER

0: GUID_partition_scheme *512.1 GB disk0

1: EFI EFI 209.7 MB disk0s1

2: Apple_HFS OSY-MBP13 380.3 GB disk0s2

3: Apple_Boot Recovery HD 650.0 MB disk0s3

4: Microsoft Basic Data BOOTCAMP 131.0 GB disk0s4

Last login: Wed Mar 29 18:26:37 on console

iMac:~ HBrown$ 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_CoreStorage Macintosh HD 121.0 GB disk0s2

3: Apple_Boot Boot OS X 134.2 MB disk0s3

/dev/disk1 (internal, physical):

#: TYPE NAME SIZE IDENTIFIER

0: GUID_partition_scheme *3.0 TB disk1

1: EFI EFI 209.7 MB disk1s1

2: Apple_CoreStorage Macintosh HD 3.0 TB disk1s2

3: Apple_Boot Recovery HD 650.1 MB disk1s3

/dev/disk2 (internal, virtual):

#: TYPE NAME SIZE IDENTIFIER

0: Apple_HFS Resident #1 +751.6 GB disk2

Logical Volume on disk0s2, disk1s2

365CC16D-8E03-46F6-9DA4-6BB4D2D3CE21

Unencrypted Fusion Drive

/dev/disk3 (external, physical):

#: TYPE NAME SIZE IDENTIFIER

0: FDisk_partition_scheme *31.0 GB disk3

1: DOS_FAT_32 WININSTALL 31.0 GB disk3s1

iMac:~ HBrown$ diskutil cs list

CoreStorage logical volume groups (1 found)

|

+-- Logical Volume Group DEC3A4E4-E127-4D79-AA3E-97F9C6444B16

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

Name: Macintosh HD

Status: Online

Size: 3120721960960 B (3.1 TB)

Free Space: 2354570723328 B (2.4 TB)

|

+-< Physical Volume 67ADECC5-D2CA-4890-A42C-0A8690848AD1

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

| Index: 0

| Disk: disk0s2

| Status: Online

| Size: 120988852224 B (121.0 GB)

|

+-< Physical Volume 99230153-D86B-4DBA-9B10-1D280F067415

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

| Index: 1

| Disk: disk1s2

| Status: Online

| Size: 2999733108736 B (3.0 TB)

|

+-> Logical Volume Family C101B7B2-199D-4E56-8942-0A7D1D5B859F

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

Encryption Type: None

|

+-> Logical Volume 365CC16D-8E03-46F6-9DA4-6BB4D2D3CE21

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

Disk: disk2

Status: Online

Size (Total): 751620849664 B (751.6 GB)

Revertible: No

LV Name: Resident #1

Volume Name: Resident #1

Content Hint: Apple_HFS

LVG Type: Fusion, Sparse

iMac:~ HBrown$

Good question. I never actually set up any partitions manually.

Part of my reasoning for a clean re-install of the system was to get rid of any partitions I made have made when using Parallels. Not sure when I would have made any manual partitions. Maybe when I brought back my data from TM some bad setting came along for the ride.

There was no intent to set it up this way.

diskutil cs resizeVolume 365CC16D-8E03-46F6-9DA4-6BB4D2D3CE21 0g

The Core Storage Logical Volume UUID is 365CC16D-8E03-46F6-9DA4-6BB4D2D3CE21

Started CoreStorage operation

Error: -69674: The provided Core Storage logical volume has an incorrect size; you should run whole-disk repair

Logical Volume Group DEC3A4E4-E127-4D79-AA3E-97F9C6444B16

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

Name: Macintosh HD

Status: Online

Size: 3120721960960 B (3.1 TB)

Free Space: 0 B (0 B)

|

+-< Physical Volume 67ADECC5-D2CA-4890-A42C-0A8690848AD1

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

| Index: 0

| Disk: disk0s2

| Status: Online

| Size: 120988852224 B (121.0 GB)

|

+-< Physical Volume 99230153-D86B-4DBA-9B10-1D280F067415

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

| Index: 1

| Disk: disk1s2

| Status: Online

| Size: 2999733108736 B (3.0 TB)

|

+-> Logical Volume Family C101B7B2-199D-4E56-8942-0A7D1D5B859F

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

Encryption Type: None

|

+-> Logical Volume 365CC16D-8E03-46F6-9DA4-6BB4D2D3CE21

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

Disk: disk2

Status: Online

Size (Total): 3106191572992 B (3.1 TB)

Revertible: No

LV Name: Resident #1

Volume Name: Resident #1

Content Hint: Apple_HFS

LVG Type: Fusion, Sparse

Can you post the output of

diskutil list

diskutil cs list

(Kicking will just hurt your foot. The Navy Jets probably need a kick to address mechanical issues, less so for software. 😉 ).

The new screen shot is much better than the previous errors and is a sign of progress.

F-14? Software? Firmware! A good bash would reseat the circuit boards after exposure to the marine environment (corrosion) and vicious catapult shots. But to be specific the equipment was never "kicked" and if there was kicking going on nobody kicked the entire jet.......

Last login: Thu Mar 30 07:44:51 on ttys000

iMac:~ HBrown$ 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_CoreStorage Macintosh HD 121.0 GB disk0s2

3: Apple_Boot Boot OS X 134.2 MB disk0s3

/dev/disk1 (internal, physical):

#: TYPE NAME SIZE IDENTIFIER

0: GUID_partition_scheme *3.0 TB disk1

1: EFI EFI 209.7 MB disk1s1

2: Apple_CoreStorage Macintosh HD 3.0 TB disk1s2

3: Apple_Boot Recovery HD 650.1 MB disk1s3

/dev/disk2 (internal, virtual):

#: TYPE NAME SIZE IDENTIFIER

0: Apple_HFS Resident #1 +3.1 TB disk2

Logical Volume on disk0s2, disk1s2

365CC16D-8E03-46F6-9DA4-6BB4D2D3CE21

Unencrypted Fusion Drive

/dev/disk3 (external, physical):

#: TYPE NAME SIZE IDENTIFIER

0: FDisk_partition_scheme *31.0 GB disk3

1: DOS_FAT_32 WININSTALL 31.0 GB disk3s1

/dev/disk4 (disk image):

#: TYPE NAME SIZE IDENTIFIER

0: GUID_partition_scheme +2.0 TB disk4

1: EFI EFI 209.7 MB disk4s1

2: Apple_HFS Time Machine Backups 2.0 TB disk4s2

iMac:~ HBrown$ diskutil cs list

CoreStorage logical volume groups (1 found)

|

+-- Logical Volume Group DEC3A4E4-E127-4D79-AA3E-97F9C6444B16

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

Name: Macintosh HD

Status: Online

Size: 3120721960960 B (3.1 TB)

Free Space: 0 B (0 B)

|

+-< Physical Volume 67ADECC5-D2CA-4890-A42C-0A8690848AD1

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

| Index: 0

| Disk: disk0s2

| Status: Online

| Size: 120988852224 B (121.0 GB)

|

+-< Physical Volume 99230153-D86B-4DBA-9B10-1D280F067415

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

| Index: 1

| Disk: disk1s2

| Status: Online

| Size: 2999733108736 B (3.0 TB)

|

+-> Logical Volume Family C101B7B2-199D-4E56-8942-0A7D1D5B859F

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

Encryption Type: None

|

+-> Logical Volume 365CC16D-8E03-46F6-9DA4-6BB4D2D3CE21

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

Disk: disk2

Status: Online

Size (Total): 3106191572992 B (3.1 TB)

Revertible: No

LV Name: Resident #1

Volume Name: Resident #1

Content Hint: Apple_HFS

LVG Type: Fusion, Sparse

What is the version of Windows you want to install?

Also, as a test can you create a FAT32 partition, and then remove it? BC Assistant also does the same for partitioning. If that works, there is a specific command - cs resizeStack - which can be used to partition the 3TB disk appropriately for Bootcamp to work properly.

Do you have a Time Machine (or any other tool) back up of OS X to an external disk?

All my stuff is backed up to TM.

Partition created and successfully removed.

Volume name : U

Volume type : Unknown

BSD device node : disk1s4

Mount point : /Volumes/U

File system : MS-DOS (FAT32)

Connection : SATA

Device tree path : IODeviceTree:/PCI0@0/SATA@1F,2/PRT0@0/PMP@0

Writable : Yes

Is case-sensitive : No

File system UUID : 65FBF238-52C8-34BC-9FAA-B803E8443B2E

Volume capacity : 19,215,667,200

Available space (Purgeable + Free) : 19,204,915,200

Purgeable space : 0

Free space : 19,204,915,200

Used space : 10,752,000

Owners enabled : No

Is encrypted : No

System Integrity Protection supported : No

Can be verified : Yes

Can be repaired : Yes

Bootable : No

Journaled : No

Disk number : 1

Partition number : 4

Media name :

Media type : Generic

Ejectable : No

Solid state : No

Parent disks : disk1

And removal:

Running operation 1 of 1…

Merging partitions

Checking prerequisites for resizing Logical-Physical volume stack

Growing Logical-Physical volume stack

Verifying file system.

Using live mode.

Performing live verification.

Checking Journaled HFS Plus volume.

Checking extents overflow file.

Checking catalog file.

Checking multi-linked files.

Checking catalog hierarchy.

Checking extended attributes file.

Checking volume bitmap.

Checking volume information.

The volume Resident #1 appears to be OK.

File system check exit code is 0.

Growing Core Storage Physical Volume from 2,980,383,223,808 to 2,999,733,108,736 bytes

Copying booter

Growing disk partition

Modifying partition map

Growing Core Storage data structures

Resizing Core Storage Physical Volume structures

Resized Core Storage Physical Volume to 2,999,733,108,736 bytes

Growing Logical Volume

Resizing Core Storage Logical Volume structures

Resized Core Storage Logical Volume to 3,106,191,441,920 bytes

Growing file system

Operation successful.

The following command will create a FAT32 partition in a 'sandwich' configuration for use by Bootcamp. This avoids the MBR 2Tb limitation. The following reduces the OS X partition to 1300g, creates a 500g Bootcamp and leaves the remainder of the 3TB (after Bootcamp) as REMAINDER which can be added back to the CS logical volume easily. Adjust the 1300g and 500g as desired. The two UUIDs are from from your diskutil cs list output. The 1300G number must be less than 2TB to create a valid layout.

diskutil cs resizestack 365CC16D-8E03-46F6-9DA4-6BB4D2D3CE21 99230153-D86B-4DBA-9B10-1D280F067415 1300g fat32 BOOTCAMP 500g jhfs+ REMAINDER 0g

iMac:~ HBrown$ diskutil cs resizestack 365CC16D-8E03-46F6-9DA4-6BB4D2D3CE21 99230153-D86B-4DBA-9B10-1D280F067415 1300g fat32 BOOTCAMP 500g jhfs+ REMAINDER 0g

The Core Storage Logical Volume UUID is 365CC16D-8E03-46F6-9DA4-6BB4D2D3CE21

Started CoreStorage operation

Checking prerequisites for resizing Logical-Physical volume stack

Shrinking Logical-Physical volume stack

Verifying file system

Using live mode

Performing live verification

Checking Journaled HFS Plus volume

Checking extents overflow file

Checking catalog file

Checking multi-linked files

Checking catalog hierarchy

Checking extended attributes file

Checking volume bitmap

Checking volume information

The volume Resident #1 appears to be OK

File system check exit code is 0

Shrinking file system

Shrinking Logical Volume

Resizing Core Storage Logical Volume structures

Resized Core Storage Logical Volume to 1,299,999,883,264 bytes

Shrinking Core Storage Physical Volume from 2,999,733,108,736 to 1,193,541,664,768 bytes

Shrinking Core Storage data structures

Resizing Core Storage Physical Volume structures

A problem occurred; undoing all changes

Growing Logical Volume

Resizing Core Storage Logical Volume structures

Resized Core Storage Logical Volume to 3,106,191,441,920 bytes

Growing file system

Error: -69733: A problem occurred while resizing Core Storage physical volume structures

CS bugs. 😠.

Use Disk Utility and create two partitions. Make the middle partition FAT32 and the remaining as Mac OS X Extended Journaled (JHFS+). Please ensure that the FAT32 partition starts within the first two TB of the Fusion drive.

Enable Show Details and post any error messages.