HT201468: How to install Windows using Boot Camp

Learn about How to install Windows using Boot Camp
bentonfromzelenograd

Q: Hello, how do it possible to create FAT32 BOOTCAMP partition over CoreStorage via command line interface?

Hello, how do it possible to create FAT32 BOOTCAMP partition over CoreStorage via command line interface?

 

I mean "diskutil cs *" and so on...

Mac mini, OS X Yosemite (10.10.5), SSD

Posted on Aug 19, 2016 3:53 AM

Close

Q: Hello, how do it possible to create FAT32 BOOTCAMP partition over CoreStorage via command line interface?

  • All replies
  • Helpful answers

  • by Loner T,

    Loner T Loner T Aug 19, 2016 4:10 AM in response to bentonfromzelenograd
    Level 7 (23,613 points)
    Safari
    Aug 19, 2016 4:10 AM in response to bentonfromzelenograd

    Yes, you need to use the resizeStack command. Please see Re: How to fix Bootcamp's "Your disk could not be partitioned.." fsck not working as an example.

  • by bentonfromzelenograd,

    bentonfromzelenograd bentonfromzelenograd Aug 19, 2016 5:02 AM in response to Loner T
    Level 1 (8 points)
    Windows Software
    Aug 19, 2016 5:02 AM in response to Loner T

    I suspect you mean this line

    "4. >> Running diskutil cs resizeStack 3CDA64B4-C946-48FD-ABC9-1B2011FE809E 293A06F5-6E17-4415-81DD-832A8F42792C 2600g free BOOTCAMP 0g"

    but what is 2600G and 0G? I do not understand the disk related to this sizes,

     

    also this steps finished by host restarts and partitions unmount and removing - is it really mandatory actions?

     

    p.s.

    For my point of view - this steps do not look like valid steps to get FAT32 partition over coreStorage via command line only

  • by Loner T,Solvedanswer

    Loner T Loner T Aug 19, 2016 5:55 AM in response to bentonfromzelenograd
    Level 7 (23,613 points)
    Safari
    Aug 19, 2016 5:55 AM in response to bentonfromzelenograd

    bentonfromzelenograd wrote:

     

    I suspect you mean this line

    "4. >> Running diskutil cs resizeStack 3CDA64B4-C946-48FD-ABC9-1B2011FE809E 293A06F5-6E17-4415-81DD-832A8F42792C 2600g free BOOTCAMP 0g"

    but what is 2600G and 0G? I do not understand the disk related to this sizes,

     

    LVUUID = 3CDA64B4-C946-48FD-ABC9-1B2011FE809E

    PVUUID (Optional) = 293A06F5-6E17-4415-81DD-832A8F42792C

     

    Reduce the LVUUID to 2600G (on a 3 TB Fusion drive), and create a Free Space partition on the HDD (the PVUUID) using the now available free space. Instead of Free, you can also use FAT32. If you are using EFI Boot, use Free, otherwise use FAT32 for legacy BIOS/MBR partitioning.

     

    The syntax is

     

    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

     

    bentonfromzelenograd wrote:

     

    also this steps finished by host restarts and partitions unmount and removing - is it really mandatory actions?

    The host does not restart. This just creates a partition. You still need to run the installer.

     

    For my point of view - this steps do not look like valid steps to get FAT32 partition over coreStorage via command line only

    Please see the previous explanation. For a non-Fusion drive Mac, you can omit the PVUUID, since you only have a single disk. BC Assistant uses the same method, but uses distinct steps.

  • by bentonfromzelenograd,

    bentonfromzelenograd bentonfromzelenograd Aug 19, 2016 5:56 AM in response to Loner T
    Level 1 (8 points)
    Windows Software
    Aug 19, 2016 5:56 AM in response to Loner T

    Thank you very much for the detailed answer!!

  • by Loner T,

    Loner T Loner T Aug 19, 2016 6:01 AM in response to bentonfromzelenograd
    Level 7 (23,613 points)
    Safari
    Aug 19, 2016 6:01 AM in response to bentonfromzelenograd

    If you want to try this, please post back if you run into any issues.

     

    A single-disk Mac is much better managed by BC Assistant. You should not need this.

  • by bentonfromzelenograd,

    bentonfromzelenograd bentonfromzelenograd Aug 19, 2016 6:29 AM in response to Loner T
    Level 1 (8 points)
    Windows Software
    Aug 19, 2016 6:29 AM in response to Loner T

    I tried and your solution helps!

     

    p.s.

    We have two disks: SSD+HDD in macmini and FusionDrive above them.

  • by Loner T,

    Loner T Loner T Aug 19, 2016 7:08 AM in response to bentonfromzelenograd
    Level 7 (23,613 points)
    Safari
    Aug 19, 2016 7:08 AM in response to bentonfromzelenograd

    Can you post the output of

     

    diskutil list

    diskutil cs list

     

    and I can check.

  • by bentonfromzelenograd,

    bentonfromzelenograd bentonfromzelenograd Aug 19, 2016 7:26 AM in response to Loner T
    Level 1 (8 points)
    Windows Software
    Aug 19, 2016 7:26 AM in response to Loner T

    Yep, but with one little exception:0

    I had added two 6GB BOOTCAMP partitions during my experiment and can't to remove them,

    after this experiments my diskutil cs list looks "different" than original (when partitions has been added)

     

    $ diskutil cs list

    CoreStorage logical volume groups (1 found)

    |

    +-- Logical Volume Group 4EDE10D7-5790-4B58-989F-850B6619DDFA

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

        Name:         Macintosh HD

        Status:       Online

        Size:         922539798528 B (922.5 GB)

        Free Space:   828684636160 B (828.7 GB)

        |

        +-< Physical Volume C25464AF-745E-4804-A332-AF70B345828B

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

        |   Index:    0

        |   Disk:     disk1s2

        |   Status:   Online

        |   Size:     120988852224 B (121.0 GB)

        |

        +-< Physical Volume 59E53ACF-C895-4BD8-B3C2-16BF6FB3BFCC

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

        |   Index:    1

        |   Disk:     disk0s2

        |   Status:   Online

        |   Size:     801550946304 B (801.6 GB)

        |

        +-> Logical Volume Family D7ACCA81-DADF-4B29-A06C-0B86A3ABF301

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

            Encryption Status:       Unlocked

            Encryption Type:         None

            Conversion Status:       NoConversion

            Conversion Direction:    -none-

            Has Encrypted Extents:   No

            Fully Secure:            No

            Passphrase Required:     No

            |

            +-> Logical Volume 72F29770-E4BC-4B34-A9D7-E8E29E2F3322

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

                Disk:                  disk2

                Status:                Online

                Size (Total):          87999905792 B (88.0 GB)

                Conversion Progress:   -none-

                Revertible:            No

                LV Name:               Auto Testing

                Volume Name:           Auto Testing

                Content Hint:          Apple_HFS

    $ diskutil list

    /dev/disk0

       #:                       TYPE NAME                    SIZE       IDENTIFIER

       0:      GUID_partition_scheme                        *1.0 TB     disk0

       1:                        EFI EFI                     209.7 MB   disk0s1

       2:          Apple_CoreStorage                         801.6 GB   disk0s2

       3:                 Apple_Boot Recovery HD             650.0 MB   disk0s7

       4:       Microsoft Basic Data BOOTCAMP                6.0 GB     disk0s8

       5:       Microsoft Basic Data BOOTCAMP                6.0 GB     disk0s4

       6:                  Apple_HFS Deploy HD               185.7 GB   disk0s5

    /dev/disk1

       #:                       TYPE NAME                    SIZE       IDENTIFIER

       0:      GUID_partition_scheme                        *121.3 GB   disk1

       1:                        EFI EFI                     209.7 MB   disk1s1

       2:          Apple_CoreStorage                         121.0 GB   disk1s2

       3:                 Apple_Boot Boot OS X               134.2 MB   disk1s3

    /dev/disk2

       #:                       TYPE NAME                    SIZE       IDENTIFIER

       0:                  Apple_HFS Auto Testing           *88.0 GB    disk2

                                     Logical Volume on disk1s2, disk0s2

                                     72F29770-E4BC-4B34-A9D7-E8E29E2F3322

                                     Unencrypted Fusion Drive

  • by Loner T,

    Loner T Loner T Aug 19, 2016 7:59 AM in response to bentonfromzelenograd
    Level 7 (23,613 points)
    Safari
    Aug 19, 2016 7:59 AM in response to bentonfromzelenograd

    You have a 1.1 TB Fusion drive. You have 828GB Free Space out of 922GB . The difference is the 88GB LV - "Macintosh HD". We can merge disk0s4,5,8 into a single FAT32 partition, if needed.

  • by bentonfromzelenograd,

    bentonfromzelenograd bentonfromzelenograd Aug 19, 2016 8:13 AM in response to Loner T
    Level 1 (8 points)
    Windows Software
    Aug 19, 2016 8:13 AM in response to Loner T

    Such idea sounds reasonable! Thanks one more time!:)

  • by Loner T,Helpful

    Loner T Loner T Aug 19, 2016 9:14 AM in response to bentonfromzelenograd
    Level 7 (23,613 points)
    Safari
    Aug 19, 2016 9:14 AM in response to bentonfromzelenograd

    A. Convert the two FAT32 6GB partitions to JHFS+, since FAT file systems cannot be merged.

     

    1. diskutil eraseVolume jhfs+ Part1 disk0s4

    2. diskutil eraseVolume jhfs+ Part2 disk0s8

     

    B. Merge disk0s4, disk0s5 and disk0s8 into a single disk0s4.

     

    diskutil mergePartitions jhfs+ BCMP disk0s4 disk0s8

     

    C. Convert the new/merged disk0s4 back to FAT32.

     

    diskutil eraseVolume  fat32 BOOTCAMP disk0s4

  • by bentonfromzelenograd,

    bentonfromzelenograd bentonfromzelenograd Aug 22, 2016 3:30 AM in response to Loner T
    Level 1 (8 points)
    Windows Software
    Aug 22, 2016 3:30 AM in response to Loner T

    Hello, Loner!

     

    I had splited this partitions (disk0s4, disk0s8) but skipped disk0s5 because it our deploy partition.

     

    I still not understand two points:

    1. How it possible to remove FAT32 partition to return disk map to original state? Should i use resizeStack again?

    2. How it possible to return disk2 size to 800+ GB? //It has been decreased during resizing to two partitions, but second partition has ben removed. I tried just resize  by command "$ diskutil cs resizeStack 72F29770-E4BC-4B34-A9D7-E8E29E2F3322 800G" but got error "Error: -69771: The target disk is too small for this operation"

  • by Loner T,

    Loner T Loner T Aug 22, 2016 4:22 AM in response to bentonfromzelenograd
    Level 7 (23,613 points)
    Safari
    Aug 22, 2016 4:22 AM in response to bentonfromzelenograd

    bentonfromzelenograd wrote:

     

    I had splited this partitions (disk0s4, disk0s8) but skipped disk0s5 because it our deploy partition.

    I assume disk0s4 and disk0s8 are merged into a single HFS+ partition. How is disk0s5 (Deploy) used?

     

    1. How it possible to remove FAT32 partition to return disk map to original state? Should i use resizeStack again?

    No. You cannot use resizeStack. The simpler method is backup/erase/restore using Time Machine. The method used by BCA involves converting the BOOTCAMP part to Free Space and then using resizeVolume to extend the CS to cover the Free Space.

     

    2. How it possible to return disk2 size to 800+ GB? //It has been decreased during resizing to two partitions, but second partition has ben removed. I tried just resize  by command "$ diskutil cs resizeStack 72F29770-E4BC-4B34-A9D7-E8E29E2F3322 800G" but got error "Error: -69771: The target disk is too small for this operation"

    Use resizeVolume. If you need exact syntax, let me know.