Apple Event: May 7th at 7 am PT

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

Level 1

8 points

Cannot install Windows on Bootcamp after replacing 3TB FusionDrive with 1TB SSD

3TB Fusion Drive was replaced by 1TB SSD drive. When reinstalling OS X i see that the 128GB of Fusion drive is still available as a harddrive, stopping me from installing OS X or Windows (Bootcamp) on the SSD.

I've been testing quite a few ways of installing:

OSX on SSD (Internet Recovery Mode, deleting all partitions and repartitioning SSD)
The installation fails when trying to install
OSX on FusionDrive (128GB), Bootcamp on SSD
OSX installs fine, Bootcamp does not. First time (Windows 10) i got an error message with I/O failure and winload.exe, second time (Windows 8.1) a dos message with "Failed to load operating system, press CTRL+ALT+DELETE". Done this part a few times.
OSX on FusionDrive (128GB), Bootcamp on the same drive
Working, but limited to 128GB for both OSX and Bootcamp
Making Logical Volume (fusiondrive) with both 128GB and 1TB
OSX Working, but cannot give me more than 64GB to my Bootcamp. Bootcamp at 64GB ok.
OSX on FusionDrive (128GB), Bootcamp on FusionDrive - moving to SSD with Winclone
Clean Windows 8.1 install, sysprepped. Everything seems ok in Winclone. When trying to restart i get a message similar to "failed to load operating system

I would like at least 800GB on my Bootcamp. Does anyone know how to make this work?

iMac late 2012, 1TB Samsung EVO replaced the 3TB drive (installed at certified Mac service partner).

iMac (27-inch, Late 2012)

Posted on Apr 17, 2016 11:55 PM

44 replies

vifurnes Author

Level 1

8 points

Apr 20, 2016 2:15 PM in response to Loner T

CoreStorage logical volume groups (1 found)

+-- Logical Volume Group CA87B7DB-0062-4737-A8DD-563870724124

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

Name: OSX-Macintosh-LVG

Status: Online

Size: 1119818194944 B (1.1 TB)

Free Space: 90112 B (90.1 KB)

+-< Physical Volume C1BF991A-494F-4700-B6E1-DC78EAF8158F

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

| Index: 0

| Disk: disk0s2

| Status: Online

| Size: 120473067520 B (120.5 GB)

+-< Physical Volume 4D38DC4A-F39C-434F-ABE9-FA0FFD84EF3E

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

| Index: 1

| Disk: disk1s2

| Status: Online

| Size: 999345127424 B (999.3 GB)

+-> Logical Volume Family BFA1C720-24E7-42DE-A1EF-5F46A732380C

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

Encryption Status: Unlocked

Encryption Type: None

Conversion Status: NoConversion

Conversion Direction: -none-

Has Encrypted Extents: No

Fully Secure: No

Passphrase Required: No

+-> Logical Volume 88F32EC2-8C91-4CFB-84A4-461EB17D53EF

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

Disk: disk2

Status: Online

Size (Total): 1115874377728 B (1.1 TB)

Size (Converted): -none-

Revertible: No

LV Name: Macintosh HD

Volume Name: Macintosh HD

Content Hint: Apple_HFS

Loner T

Level 9

59,471 points

May 1, 2016 3:47 AM in response to vifurnes

There is command that Bootcamp uses to create the partition. Let us run the same command and see what we get.

diskutil cs resizeStack 88F32EC2-8C91-4CFB-84A4-461EB17D53EF 4D38DC4A-F39C-434F-ABE9-FA0FFD84EF3E 900g fat32 BOOTCAMP 0g

This command will reduce the Macintosh HD to 900g and create a FAT32 partition on the available free space (~200g).

The first long string is the OSX UUID, the second is the UUID assigned to the 1 TB SSD.

Here is the help syntax for reference.

diskutil cs resizestack

Usage: diskutil coreStorage resizeStack

lvUUID|MountPoint|DiskIdentifier|DeviceNode [pvUUID] size

[part1Format part1Name part1Size part2Format part2Name part2Size

part3Format part3Name part3Size ...]

Resize both a logical volume and one of its underlying physical volumes in a

single operation. A single physical volume is always chosen for the underlying

shrink or grow, even if the logical volume's logical volume group is backed by

more than one physical volume. If you do not specify a particular physical

volume, then one is chosen for you. Note that if this is a grow operation,

this verb is limited by the physical volume's partition's room to grow.

Specifying zero as the size asks for an "automatic" grow-to-fill operation.

If this is a shrink operation, you can optionally request that new partitions

be created in the newly-formed free space gap in the partition map.

Again, note that this only resizes one of the underlying physical volumes; if

you need more sophistication in managing your topology, you should use the

separate physical and logical volume resize verbs.

Example: diskutil coreStorage resizeStack

11111111-2222-3333-4444-555555555555 10g JHFS+ New 1g

vifurnes Author

Level 1

8 points

Apr 20, 2016 2:54 PM in response to Loner T

-bash-3.2# diskutil cs resizeStack 88F32EC2-8C91-4CFB-84A4-461EB17D53EF 4D38DC4A-F39C-434F-ABE9-FA0FFD84EF3E 900g fat32 BOOTCAMP 0g

Started CoreStorage operation

Checking prerequisites for resizing Logical-Physical volume stack

Shrinking Logical-Physical volume stack

Checking file system

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 Macintosh HD appears to be OK

Shrinking file system

Shrinking Logical Volume

Resizing Core Storage Logical Volume structures

Resized Core Storage Logical Volume to 899999997952 bytes

Shrinking Core Storage Physical Volume from 999345127424 to 783470747648 bytes

Shrinking Core Storage data structures

Resizing Core Storage Physical Volume structures

Resized Core Storage Physical Volume to 783470747648 bytes

Copying booter

A problem occurred; undoing all changes

Growing Core Storage data structures

A problem occurred; undoing all changes

Growing Logical Volume

Resizing Core Storage Logical Volume structures

Resized Core Storage Logical Volume to 1115874377728 bytes

Growing file system

Error: 5: POSIX reports: Input/output error

Loner T

Level 9

59,471 points

Apr 20, 2016 3:17 PM in response to vifurnes

Let us try the same thing with the 120GB SSD.

diskutil cs resizeStack 88F32EC2-8C91-4CFB-84A4-461EB17D53EFC1BF991A-494F-4700-B6E1-DC78EAF8158F 980g fat32 BOOTCAMP 0g

This will create a ~20G partition on the smaller SSD.

vifurnes Author

Level 1

8 points

Apr 20, 2016 9:28 PM in response to Loner T

-bash-3.2# diskutil cs resizeStack 88F32EC2-8C91-4CFB-84A4-461EB17D53EF C1BF991A-494F-4700-B6E1-DC78EAF8158F 980g fat32 BOOTCAMP 0g

Started CoreStorage operation

Checking prerequisites for resizing Logical-Physical volume stack

Shrinking Logical-Physical volume stack

Checking file system

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 Macintosh HD appears to be OK

Shrinking file system

Shrinking Logical Volume

Resizing Core Storage Logical Volume structures

Resized Core Storage Logical Volume to 979999997952 bytes

Shrinking Core Storage Physical Volume from 120473067520 to 18446744058308239360 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 1115874377728 bytes

Growing file system

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

-bash-3.2#

Loner T

Level 9

59,471 points

Apr 21, 2016 6:21 AM in response to vifurnes

It fails on both disks which eliminates the possibility of hardware issues to a very large extent (95%).

1. In Internet Recovery, run

diskutil repairDisk disk0

diskutil repairDisk disk1

Test partitioning manually, before we try BC Assistant.

2. Rename the CS LVG and test

diskutil cs rename OSX-Macintosh-LVG OSXLVG

diskutil cs rename

Usage: diskutil coreStorage rename lvgUUID|lvgName newName

Rename a CoreStorage logical volume group. Do not confuse this with LV names.

Ownership of the affected disks is required.

This may not work in Internet Recovery. If it fails, please run

diskutil cs rename CA87B7DB-0062-4737-A8DD-563870724124 OSXLVG

vifurnes Author

Level 1

8 points

Apr 21, 2016 12:03 PM in response to Loner T

Step 1 ok, step 2 not possible - rename is not an option in diskutil.

Did a few things on my own:

Booted Windows Installation on usb-stick
Removed every partition on both disks using diskpart
Booted to IR mode, partitioned both disks with one partition
Followed Your instructions to create CS

Now the resize stack function is working. Reinstalling OS X now.

Loner T

Level 9

59,471 points

Apr 21, 2016 12:10 PM in response to vifurnes

Can you post the output of diskutil list ? We should check the EFI partition on each disk is valid for OSX. Diskpart behaves a bit differently. Good to know your resizeStack is working.

vifurnes Author

Level 1

8 points

Apr 21, 2016 12:14 PM in response to Loner T

Will do in about 1 hour when the installation is finished. Deleted everything using diskpart, even the EFI partitions. Disk Utility recreated the EFI when partitioning each of the drives.

Loner T

Level 9

59,471 points

Apr 21, 2016 12:23 PM in response to vifurnes

If DU created the EFI, we should confirm with diskutil list when you have time. It is not that critical yet.

vifurnes Author

Level 1

8 points

Apr 21, 2016 12:54 PM in response to Loner T

diskutil list

/dev/disk0

#: TYPE NAME SIZE IDENTIFIER

0: GUID_partition_scheme *1.0 TB disk0

1: EFI 209.7 MB disk0s1

2: Apple_CoreStorage 183.0 GB disk0s2

3: Apple_Boot Boot OS X 134.2 MB disk0s3

4: Microsoft Basic Data BOOTCAMP 816.9 GB disk0s4

/dev/disk1

#: TYPE NAME SIZE IDENTIFIER

0: GUID_partition_scheme *121.3 GB disk1

1: EFI 209.7 MB disk1s1

2: Apple_CoreStorage 120.5 GB disk1s2

3: Apple_Boot Boot OS X 650.0 MB disk1s3

/dev/disk2

#: TYPE NAME SIZE IDENTIFIER

0: Apple_HFS Macintosh HD *299.5 GB disk2

Loner T

Level 9

59,471 points

Apr 21, 2016 1:19 PM in response to vifurnes

This is clean. Good to see it working so far.

vifurnes Author

Level 1

8 points

Apr 21, 2016 2:01 PM in response to Loner T

Tried to install Windows.
Fist 8.1 from bootcamp configured USB-stick; installation ok, booting first time no luck - took about 5 minutes before the Windows logo appeared - followed by ntoskrnl.exe error.
Tried to overwrite the Windows 8.1 installation with Windows 10 from clean Windows 10 image on USB stick. Unexpected I/O error. Winload.exe 0xc00000e9

vifurnes Author

Level 1

8 points

Apr 21, 2016 2:16 PM in response to vifurnes

Had to format the Bootcamp partition when installing Windows, would not be able to press "next" if not.

Should i try to reconfigure once more, without resizeStack, reinstall, upgrade to El Capitan and let Bootcamp resize the disk and prepare a new Windows 10 drive?

Loner T

Level 9

59,471 points

Apr 21, 2016 2:20 PM in response to vifurnes

Yes, please.

Cannot install Windows on Bootcamp after replacing 3TB FusionDrive with 1TB SSD