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.

emulajavi Author

Level 1

10 points

BootCamp on SDD on system with Fusion Drive

Hi.

First, for those of you with iMacs or Mac minis with fusion drive, does your system always list:

SSD drive as disk0???

HDD drive as disk1???

My iMac originally listed them like that but after splitting the Fusion Drive, now SSD is listed randomly as disk1 or disk2 and HDD is always disk0.

I’d like to know if this random or not.

Now onto the reason behind that question: BootCamp

I have a late2015 Max with a 2TB fusion drive (120gb+2tb)

I want to install Windows on a partition of the SSD, something BootCamp Assistant doesn’t allow to because it can only create a new partition on the HDD, but Apple CoreStorage supports.

I have found that what seems to work to get Windows on the SSD is:

- Enter Internet Recovery

- Split the Fusion Drive

- Create on the SSD (for me disk1 or 2) two partitions: Macintosh HD (50GB) and BOOTCAMP (70GB)

- Create on the HDD (for me disk0) two partitions: Macintosh HD (990GB) and SHARED (1.1TB exFAT. Will be used for Windows Files permitting macOS r/w)

- Recreate the Fusion Drive with the two Macintosh HD partitions, to take advance of the magic of Fusion when in macOS

- Install macOS on the Macintosh HD Fusion Drive Volume.

- Create bootable USB with Windows 10 and BootCamp Drivers and install it on the BOOTCAMP partition of the SSD.

Everything works except the last step, where Windows installation gives me an error after selecting the BOOTCAMP partition (Disc 1 Partition 4), clicking on Format, and then on Next. A yellow warning appears saying ”we couldn’t create a new partition or locate an existing one”.

Seems that the error is because Windows likes to install on Drive 0 but not on Drive 1.

I don’t know how to make my system recognize the SSD as disk0 again.

Any clues?

Thank you

IMAC (RETINA 5K, 27-INCH, LATE 2015), macOS High Sierra (10.13.1)

Posted on Nov 22, 2017 9:54 AM

Top-ranking reply

emulajavi Author

Level 1

10 points

Posted on Nov 28, 2017 12:15 PM

So this is step by step how I managed to install Windows 10 (1709) on the SSD part of a 2TB Fusion Drive in my iMac 5K 27-inch (late 2015).

I don’t know if this will work to all types of stock Fusion Drive setups on Apple products. This is what I wanted:

iMac 5K 27-inch (late 2015) with 2TB Fusion Drive (120GB SSD + 2TB HDD)
macOS 10.13.1 High Sierra installed on a Fusion Drive of 800GB consisting of 45GB of the SSD and 755GB of the HDD.
Windows 10 (1709) installed on 75GB of the SSD
1,2TB on a separate exFAT partiton for sharing files between OSs.

Things to take into account (you can skip this. It’s only an explanation of why things are done in a specific order):

- YOU NEED TO ERASE ALL YOUR SYSTEM. PLEASE BACKUP.

- BEFORE DOING ANYTHING, DOWNLOAD WINDOWS COMPATIBILITY DRIVERS FROM BOOTCAMP ASSISTANT ON MACOS, AND SAVE THEM TO A USB DRIVE.

- macOS only permits to install Windows making a BOOTCAMP partition on the HDD.

- Windows doesn’t like macOS’s EFI partition structure

- Windows always tries to install on disk0 despite of you telling Windows to install on disk1.

- macOS doesn’t like the way Windows creates the EFI partition and refuses to install after Windows.

- Windows creates an EFI partition of 100MB but macOS needs 200MB minimum.

- Installing first macOS, separating a slice of the SDD from the Fusion Drive and trying to install Windows on it, doesn’t work because Windows doesn’t like macOS EFI partition.

- Spliting the Fusion Drive, erasing all disks, installing Windows normally, then reducing Window’s partition to make room for macOS and trying to install macOS doesn’t work because of the small Windows EFI partition.

- Of all the different tries I made, the only way I could manage to install Windows, was installing Windows first, without any operating system installed on my iMac.

Well, these are the STEPS that worked for me:

A. Split the Fusion Drive:

1.- Boot into Internet Recovery: Hold Command+Option+R till a spinning globe appears.

2.- Launch Utilities -> Terminal and type:

diskutil cs list

3.- Look for the Logical Volume Groupe ID (LVGID) at the top and Logical Volume ID (LVID) at the bottom part and type:

diskutil cs deleteVolume LVID

diskutil cs delete LVGID

Now you have your Fusion Drive splitted

B.- Boot into the Windows USB Installer.

1.- When the Windows Install Setup appears, press Shift+F10

2.- Type:

diskpart

list disk(check what drive is disk0 and what drive is disk 1. (For me: disk0 HDD, disk1 SSD)

select disk 0

clean (this deletes all the drive)

select disk 1

clean

3.- Now we are going to manually create the EFI partition that will solve all of our problems. Type:

select disk 1 (the SSD)

convert gpt

create partition efi size=200

format quick fs=FAT32 label=”EFI”

create partition msr size=128

exit

4.- Now proceed with Windows Setup, selecting custom install and on the partition selection window:

- delete (if any) all of the disk0 (HDD) partitions

- delete (if any) all of the disk1 (SDD) partitions except EFI and MSR so you will have:

- 2TB unallocated space on disk0 (HDD)

- EFI partition on the SSD

- MSR partition on the SSD

- 112GB of unallocated space on disk1 (SDD)

- select the 112GB of unallocated space and click next. Windows should install.

C.- Upon booting into Windows:

1.- Install Bootcamp Compatibility Drivers and reboot. You’ll see that C: drives has been magically renamed to BOOTCAMP.

2.- Delete the MSR partition. macOS doesn’t like it. Open a CMD as administrator and type:

diskpart

list disk (look for the SSD disk number. For me it was disk1)

select disk 1

list partition (look for a 128MB MSR partition. For me it was partition2)

select partition 2

delete override

3.- Shrink the BOOTCAMP partition. Using Windows Disk Management, reduce the BOOTCAMP volume to 44000MB.

4.- Create a new exFAT formatted volume (name doesn’t matter, it’s only a placeholder) on the newly freed space but leaving 128MB out of it. So substract 128 to the number that Windows suggests you. macOS needs those 128MB of unallocated space there.

D.- Installing macOS 10.13.1

1.- Boot into Internet Recovery.

2.- Using Disk Utility format the exFAT volume we’ve created before as HFS+ named Macintosh HD.

3.- Using Disk Utility format the HDD with a single Macintosh HD HFS+ partition.

4.- Recreate the Fusion Drive. Open terminal and type:

diskutil list (look what disk is disk0 and what disk is disk1. For me SSD was disk1 and HDD was disk0. Look also for the identifier of the SDD Macintosh HD partition which for me was disk1s4 I think)

diskutil cs create disk1s4 disk0 (first SSD partition, second whole HDD. It will do its stuff and report a large number Logical Volume Group ID -LVGID-)

diskutil cs createVolume LVGID jhfs+ Macintosh\ HD 100%

5.- Done. Fusion Drive created. Install macOS on Macintosh HD.

E.- Post macOS install:

1.- With Disk Utility, create a new exFAT partition on the Fusion Drive, size 1.2TB called WinMac that will be used to share files between OSs. The partition will be created out of the Fusion Drive and on the HDD.

An that’s all. That’s how I managed to get Windows installed on a portion of my SDD and keep the Fusion Drive for macOS, while also having a separate partition for file sharing.

All works correctly, but I have only experienced one ‘issue’:

- Bootcamp Control Panel on Windows shows three startup drives: MacOS X, disk1 Windows, and Microsoft Basic Data Windows

- macOS Startup Disk Preferences shows two: Macintosh HD - MacOS X, and BOOTCAMP-Windows.

- If you select MacOS X whether on Windows Bootcamp Control Panel or macOS Startup Disk Preferences, computer will always boot into macOS.

- In you select disk1 Windows on Bootcamp Control Panel on Windows, system will always boot into macOS.

- If you select Microsoft Basic Data Windows on Bootcamp control panel on Windows, system will always boot into Windows.

- If you select Windows on Startup disk on macOS, system will always boot into Windows, BUT Windows won’t recognize the HDD (and so the WinMac partitition) and show an error on a SATA/EHCI.

- Booting Windows using Alt-Option at startup always shows the HDD.

So to avoid the driver error and the HDD not being recognized I have to:

- If I have macOS set as default os: boot into Windows by pressing Alt-Option at startup. Selecting Windows on macOS and rebooting, means HDD won’t be recognized.

- If I want to set Windows as default os: I do it from Windows, selecting the ‘Microsoft Basic Data – Windows’ disk on Bootcamp Control Panel on Windows. After that, Windows will always boot recognizing the HDD.

View in context

44 replies

Loner T

Level 9

59,513 points

Nov 23, 2017 7:20 AM in response to emulajavi

Your 2015 Mac does not support legacy BIOS. A hybrid MBR is not really useful on your model. For EFI installation, you get a Protective MBR. Your SSD and HDD should have only a Protective MBR.

Post the output of

sudo fdisk /dev/disk0

sudo fdisk /dev/disk1

emulajavi Author

Level 1

10 points

Nov 23, 2017 7:38 AM in response to Loner T

I tried what I told you yesterday of making a 10MB 4th partition on the SSD so the Bootcamp would be the 5th, but nothing.

I'm trying now to record the Windows 10 image onto a disc and try to install it with a SuperDrive connected instead of a USB drive.

Also, I've managed to get some of the errors of the windows setup log. This is an extract of what I think refers to the SDD partition. I have the complete log also.

2017-11-23 13:23:32, Info [0x0606cc] IBS DiskInfo: ------ NT partition number [5] -------

2017-11-23 13:23:32, Info [0x0606cc] IBS DiskInfo: Offset (bytes) [46671069184 / 0xaddd00000]

2017-11-23 13:23:32, Info [0x0606cc] IBS DiskInfo: Size (bytes) [74660708352 / 0x1162200000]

2017-11-23 13:23:32, Info [0x0606cc] IBS DiskInfo: Simple index: [5]

2017-11-23 13:23:32, Info [0x0606cc] IBS DiskInfo: GPT partition type: [{EBD0A0A2-B9E5-4433-87C0-68B6B72699C7}] (recognized)

2017-11-23 13:23:32, Info [0x0606cc] IBS DiskInfo: DOS drive letter [C:]

2017-11-23 13:23:32, Info [0x0606cc] IBS DiskInfo: NT path: [\Device\HarddiskVolume8]

2017-11-23 13:23:32, Info [0x0606cc] IBS DiskInfo: File system type: [NTFS]

2017-11-23 13:23:32, Info [0x0606cc] IBS DiskInfo: File system version: [3:1]

2017-11-23 13:23:32, Info [0x0606cc] IBS DiskInfo: Volume flags = [0x98460]

2017-11-23 13:23:32, Info [0x0606cc] IBS DiskInfo: Volume free space (bytes) [74554843136]

2017-11-23 13:23:34, Info IBS Callback_ValidateInstallDrive:====== Does disk [1] offset [0xaddd00000] meet installation reqs? ======

2017-11-23 13:23:34, Info [0x0601ba] IBS DiskSpaceReqs: Windows image size (from metadata) = [8376922096] bytes

2017-11-23 13:23:34, Info [0x0601bb] IBS DiskSpaceReqs: Windows image size (after padding) = [10019920673] bytes

2017-11-23 13:23:34, Info IBS DiskSpaceReqs: Windows image contents: [10019920673] bytes

2017-11-23 13:23:34, Info IBS DiskSpaceReqs: ~BT volume (estimate): [0] bytes

2017-11-23 13:23:34, Info IBS DiskSpaceReqs: Install volume (estimate): [10019920673] bytes

2017-11-23 13:23:34, Info IBS DiskSpaceReqs: ~LS volume (estimate w/o padding): [0] bytes

2017-11-23 13:23:34, Info IBS CalculatingRecommendedSpaceForWindows: RequiredSize [10019920673] bytes

2017-11-23 13:23:34, Info IBS CalculatingRecommendedSpaceForWindows: Recommending [27304581921] bytes

2017-11-23 13:23:34, Info IBS Callback_ValidateInstallDrive:Install volume -- required free space = [10019920673] bytes

2017-11-23 13:23:34, Info IBS Callback_ValidateInstallDrive:Install volume -- recommended free space = [27304581921] bytes

2017-11-23 13:23:34, Info IBS Callback_ValidateInstallDrive:Summary - CCP check passed; able to calculate space reqs; able to find install location; location type meets installation reqs; size of location is not too small; location free space is enough; location free space meets the recommendation

2017-11-23 13:23:34, Info IBS Callback_ValidateInstallDrive:------------------------------------------------- ----------

2017-11-23 13:23:38, Info [0x0606cc] IBS GetSystemDiskNTPath: Unable to get required buffer size for system disk from BCD APIs; status = 0xc0000451

2017-11-23 13:23:38, Info IBS GetMachineInfo:Couldn't find any system volumes on this EFI-based computer

2017-11-23 13:23:38, Info IBSLIB CanBeSystemVolume: Volume at disk [1] offset [0xaddd00000] doesn't meet criteria for system volumes...

2017-11-23 13:23:38, Info IBSLIB DiskRegionSupportsCapability:Region on disk [1] (offset = [0xaddd00000]) is BLOCKED against capability [CanBeSystemVolume] for the following reasons...

2017-11-23 13:23:38, Info IBSLIB LogReasons: [BLOCKING reason for {disk 1 offset 0xaddd00000}: CanBeSystemVolume] El espacio en disco seleccionado no es del tipo ESP.

2017-11-23 13:25:25, Info IBSLIB Remedy was applied for said disk rule

2017-11-23 13:25:25, Info [0x0a0035] UI Allowing Page 'Tipo de instalaci?n' to be shown

About what you ask me: Yes. It seems that I have a protective MBR

iMac-de-Javier:~ javiergil$ sudo fdisk /dev/disk0

Password:

Disk: /dev/disk0 geometry: 14751/255/63 [236978176 sectors]

Signature: 0xAA55

Starting Ending

#: id cyl hd sec - cyl hd sec [ start - size]

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

1: EE 1023 254 63 - 1023 254 63 [ 1 - 236978175] <Unknown ID>

2: 00 0 0 0 - 0 0 0 [ 0 - 0] unused

3: 00 0 0 0 - 0 0 0 [ 0 - 0] unused

4: 00 0 0 0 - 0 0 0 [ 0 - 0] unused

iMac-de-Javier:~ javiergil$ sudo fdisk /dev/disk1

Disk: /dev/disk1 geometry: 243201/255/63 [3907029168 sectors]

Signature: 0xAA55

Starting Ending

#: id cyl hd sec - cyl hd sec [ start - size]

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

1: EE 1023 254 63 - 1023 254 63 [ 1 - 3907029167] <Unknown ID>

2: 00 0 0 0 - 0 0 0 [ 0 - 0] unused

3: 00 0 0 0 - 0 0 0 [ 0 - 0] unused

4: 00 0 0 0 - 0 0 0 [ 0 - 0] unused

Loner T

Level 9

59,513 points

Nov 23, 2017 8:14 AM in response to emulajavi

These are both protective MBRs. Can you erase the BOOTCAMP partition using the following command to Free Space and boot from the BCA-created USB Installer and manually select EFI Boot?

diskutil eraseVolume free free diskXsN

where X and N point to the Bootcamp slice on the SSD.

emulajavi Author

Level 1

10 points

Nov 23, 2017 9:42 AM in response to Loner T

Thank you. Since the 4th and 5th partition thing didn't work. I've erased all and recreated the full Fusion Drive and reinstalled OS X.

I did this:

diskutil cs resizeStack FusionVolumeID SSDId 2050g free free 0g

which I think made what you want me to do: Leave approximately 70GB of unallocated so Window Installer will try to manage.

Booted Windows install usb, got to the partitions window selected the unallocated space of the SSD drive and clicked next. It didn’t give the yellow warning and error, and seemed to start copying Windows files, but a second later an error window appeared, saying the setup had to stop and that I had to re-start it. Which I did. This time, on the partitions window I found that Windows installed had created some partitions on the step before (info taken with Diskutil):

- partition 4: 523.2mb Windows recovery

- partition 5: efi No Name 104.9mb

- partition 6: Microsoft Reserved 16.8mb

- partition 7: Microsoft basic data NTFS 74gb

When I clicked on the 7th and clic next, I got the same yellow warning with the same error.

Now I’m erasing all again and recreating the full Fusion Drive and reinstall OSX and going to try to install Windows with BootCamp to see what happens.

emulajavi Author

Level 1

10 points

Nov 24, 2017 1:33 PM in response to Loner T

Hi. Thank you.

Ok. I'll resizeStack again to get the 70GB Windows SSD partition, reset NVRAM and SMC, boot Windows USB and look at the diskpart output to see the differences.

I think that Windows might like to install itself on Disk 0 (which is the HDD). When installing the official way, as I showed you before, windows setup only can find the HDD and its partitions, and there's no sign of the SSD. BCA does something to hide the SSD to windows setup. It'd be great to temporarily 'hide' the HDD to the windows installer so it can only 'see' the SDD as disk 0, and probably will install without any problems.

emulajavi Author

Level 1

10 points

Nov 24, 2017 4:25 PM in response to Loner T

I also have some windows setup logs

2017-11-24 22:08:07, Info IBS InstallWindows:Successfully loaded resource language [es-es]

2017-11-24 22:08:07, Info [0x0601c1] IBS InstallWindows:Install Path = X:\Sources

2017-11-24 22:08:07, Info [0x0601c2] IBS InstallWindows:Setup Phase = 2

2017-11-24 22:08:07, Info [0x0606cc] IBS LogBootDeviceInfo:The firmware boot device ARC path is [multi(0)disk(0)rdisk(3)partition(1)] and NT path is [\Device\Harddisk2\Partition1].

2017-11-24 22:08:07, Info [0x0606cc] IBS LogBootDeviceInfo:The system boot device ARC path is [ramdisk(0)] and NT path is [\Device\Ramdisk{d9b257fc-684e-4dcb-ab79-03cfa2f6b750}].

2017-11-24 22:08:07, Info [0x0601e9] IBS CheckWinPEVersion:Compatible WinPE Version 10.0.16299 sp 0.0

2017-11-24 22:08:07, Info [0x0601c9] IBS InstallWindows:Starting a new install from WinPE

2017-11-24 22:08:07, Info IBS InstallWindows: Setup working directory = X:\windows\panther

2017-11-24 22:08:07, Info [0x0601ce] IBS Setup has started phase 2 at 2017-11-24 22:08:07

2017-11-24 22:08:07, Info [0x0601cf] IBS Install source is X:\Sources

2017-11-24 22:08:07, Info [0x0601d0] IBS Build version is 10.0.16299.15 (WinBuild.160101.0800)

2017-11-24 22:08:07, Info [0x06403f] IBSLIB CreateSetupBlackboard:Creating a new persistent blackboard. Path is [X:\windows\panther\SetupInfo] Setup phase is [2]

2017-11-24 22:08:07, Info [0x090008] PANTHR CBlackboard::Open: X:\windows\panther\SetupInfo succeeded.

2017-11-24 22:08:07, Info [0x064043] IBSLIB CreateSetupBlackboard:Successfully created/opened Setup black board path is [X:\windows\panther\SetupInfo]

2017-11-24 22:08:07, Info IBS InstallWindows:No UI language from a previous boot was found on the blackboard. Using selected language [es-es].

2017-11-24 22:08:07, Info IBS InstallWindows:Setup architecture is [x64]

2017-11-24 22:08:07, Info [0x0601d5] IBS InstallWindows:Starting with Empty Queue. Setup Phase = 2

2017-11-24 22:08:07, Info PANTHR InitializedCriticalSection for pExecQueue->csLock;