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.

Partition BootCap on DD 3To Fusion Drive: A methode

In continuation of another post above a bootcamp disk problem, i ask to now how to crate a Bootcamp partition on a 3To. Fusion drive using command on terminal like:


diskutil list

diskutil cs list

sudo gpt -vv -r show /dev/disk0

sudo gpt -vv -r show /dev/disk1

sudo fdisk /dev/disk0

sudo fdisk /dev/disk1


The end of the first thread:

Can't format former Boot Camp partition


Thanks.

iMac, OS X Yosemite (10.10)

Posted on Nov 10, 2014 7:15 AM

Reply
Question marked as Top-ranking reply

Posted on Nov 11, 2014 3:47 AM

Sorry, did not get a chance to post on this before.


There are two options,


1. Use diskutil cs resizeStack, or,

2. Re-install Yosemite by using the steps from the previous thread, but this time create a Bootcamp-suitable volume also.

50 replies

Nov 11, 2014 7:39 AM in response to Baron MARTo

Please let me know if you see any error messages.


diskutil cs resizeStack 7D2AB070-B558-4788-BD0F-ECD835245C2C 3DDE5754-7274-4D58-AED2-EF28CC6A28AF 2200g fat32 BOOTCAMP 300g jhfs+ OSX-Remainder 1900g


Here is the syntax/help and you can see what is being done.


part1Format = fat32

part1Name = BOOTCAMP

part1Size = 300g


part2Format = jhfs+

part2Name = OSX-Remainder

part2size = 1900g


lvUUID = 7D2AB070-B558-4788-BD0F-ECD835245C2C (This is "Macintosh HD")

pvUUID = 3DDE5754-7274-4D58-AED2-EF28CC6A28AF (This is disk1s2)


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

Nov 11, 2014 10:45 AM in response to Loner T

It's complicated because i dont understand clearly what you want me to do, i dont understand why only 1900 Go for the OSX disk, why i have to format it (do i have to lost everything again?!), why i dont understand better your explanations (My english show its limits) and why the BootCamp program doesn't work normally with a 3 To Fusion drive? This disk sale out two years ago, i really dont understand. 😢

Nov 11, 2014 10:57 AM in response to Baron MARTo

1. You have a two-disk logical volume with the SSD and HDD.

2. The resizeStack command does not change the SSD at all. The pvUUID I have used is disk1s2, which is a part of your HDD. The goal is to recreate a disk1s3 of 300G which will be your BC Windows partition, an fit is being formatted as FAT. The Windows installer will reformat it to NTFS during the installation process.

3. The command is resizing the disk1s2 part into two parts, a Bootcamp 300G partition and a remainder part which is 1900G out of the disk1s2 slice which is 2.2TB right now.

4. The order specified in the command puts the 300g partition at the beginning of the 2.2TB disk1s2 to allow FAT to address the 300G partition.

5. This will provide the partitions, but the Hybrid MBR still needs to be created.

6. BCA messed up when it did not create disk1s3 and disk1s4. You can see these are missing in your diskutil output.

Nov 11, 2014 11:17 AM in response to Loner T

Ok thanks, i understand better now (still dont understand why BootCamp was not updated).


Still dont understand the space of the different disk but ok, i dont try any more.

So, i just have to enter :

diskutil cs resizeStack 7D2AB070-B558-4788-BD0F-ECD835245C2C3DDE5754-7274-4D58-AED2-EF28CC6A28AF 2200g fat32 BOOTCAMP 250g jhfs+ OSX-Remainder 1950g

I change for 250 Gigas for Windows, i quite a lot for what i'am doing whit it.

I dont lost anything of my OS X partition doing this?


I am working tonight with the Mac, i try this tomorrow if your ok.


Dont understand this:

"5. This will provide the partitions, but the Hybrid MBR still needs to be created."


Sorry for my thin patience, i quit cigarettes four day ago and i am very bad today. 😝

Nov 11, 2014 11:35 AM in response to Baron MARTo

1. Bootcamp failed because it requires a FAT partition which needs to reside within the first 2TB of the disk blocks, but it did not create disk1s3/disk1s4 in correct locations.

2. Part1 will be the first 250GB right after the EFI entry on your HDD.

3. The OSX partition should be untouched.

4. You can try it when you have time and want to work on this.


Bootcamp uses GPT for OSX and MBR for Windows. The output of Fdisk needs to created after the disk are partitioned. Here is an example

GPT is


sudo gpt -vv -r show /dev/disk0

Password:


gpt show: /dev/disk0: mediasize=1000555581440; sectorsize=512; blocks=1954210120

gpt show: /dev/disk0: Suspicious MBR at sector 0

gpt show: /dev/disk0: Pri GPT at sector 1

gpt show: /dev/disk0: Sec GPT at sector 1954210119

start size index contents

0 1 MBR

1 1 Pri GPT header

2 32 Pri GPT table

34 6

40 409600 1 GPT part - C12A7328-F81F-11D2-BA4B-00A0C93EC93B

409640 1448624648 2 GPT part - 48465300-0000-11AA-AA11-00306543ECAC

1449034288 1269536 3 GPT part - 426F6F74-0000-11AA-AA11-00306543ECAC

1450303824 1712

1450305536 503904256 4 GPT part - EBD0A0A2-B9E5-4433-87C0-68B6B72699C7

1954209792 295

1954210087 32 Sec GPT table

1954210119 1 Sec GPT header




MBR is


sudo fdisk /dev/disk0

Disk: /dev/disk0 geometry: 121643/255/63 [1954210120 sectors]

Signature: 0xAA55

Starting Ending

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

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

1: EE 0 0 2 - 25 127 14 [ 1 - 409639] <Unknown ID>

2: AF 25 127 15 - 1023 54 16 [ 409640 - 1448624648] HFS+

3: AB 1023 54 17 - 1023 60 39 [1449034288 - 1269536] Darwin Boot

*4: 07 1023 87 51 - 1023 238 3 [1450305536 - 503904256] HPFS/QNX/AUX


Baron MARTo wrote:



Sorry for my thin patience, i quit cigarettes four day ago and i am very bad today. 😝

I do not want you to go back to 'bad' cigarettes. 😉. I can wait till you are ready.

Partition BootCap on DD 3To Fusion Drive: A methode

Welcome to Apple Support Community
A forum where Apple customers help each other with their products. Get started with your Apple Account.