Moonraker

Q: Issue trying to clean install Windows 10 on Fusion Drive. el Capitan.

Issue: Trying a clean install of Windows 10 via Boot Camp Assistant on an iMac 27 inch (Late2013) with 10.11.4 results in the installation taking hours (over 8 hours) and then unable to install Boot Camp updates. Basically installation taking much longer than normal and unable to install the Apple software updates or create normally booting Windows 10 Boot Camp.

 

Background: After slowdown issues after upgrading to 10.11.4 (with Bootcamp upgraded Windows 10) which had previously worked fine for 10 months, to the point of a hour to boot to OS X, I decided to do a clean install of my iMac with 3TB Fusion Drive.

 

As I was unable to remove the Boot Camp partition via BCA due to it taking forever to even load, I used Internet Recovery and reinitialised the Fusion Drive. This then required me to repair the Fusion Drive partition via DU 'fix' option which appeared to work fine. And reinstalled OS X 10.11.4 which works fine now (no delays etc.)

 

On trying to use BCA to create a new Boot Camp partition and a clean Windows 10 install, after downloading a W10 disk image direct from Microsoft (Win10_1511_1_English_x64), BCA downloading the software updates and selecting the desired partition, it commenced reboot and initialise the install. However the whole process was very slow, each stage taking much longer than usual, to progress. Leaving it for hours still left a blank screen or one with a rotating circle.

 

I tried with another USB 3 stick and also a USB 2 stick but neither made a difference.

 

On the last attempt I left it running over night and after 8-9 hours it eventually reached the Windows 10 desk top and the Apple Bootcamp Update launching to load the updates. However it just hung and even after 2 hours nothing had happened. Rebooting and trying again was the same.

 

After this I tried creating a Windows 8.0 install via BCA however it just gives a GPT error when trying to select the drive (due to el Capitan I assume?)

 

After four days of efforts I am at a lose as to how to get the Windows 10 onto the Boot Camp partition. I am unable even to install W8 and upgrade due to GPT error.

 

Any help or suggestions how to proceed with diagnosing/resolving the issue would be appreciated.

 

Details:

System: iMac (27-inch, Late 2013), 3,4 GHz Intel Core i5, 16 GB 1600 MHz DDR3, NVIDIA GeForce GTX 780M 4096 MB, OS X 10.11.4.

  • Nothing other than keyboard and mouse attached via USB ports, along with the BCA USB stick. No other devices attached.
  • Reset NVRAM, SMC and ran Disk Utility a number of times. No issue reported.  Ran NVRAM reset before each attempt.
  • Ran EtreCheck report which appeared OK.
  • Ran Diagnostic check which returned no issue.

One detail I noticed after fixing the Fusion Drive there are now two Macintosh HD images when using option boot. Only one previously. The are named 'Macintosh HD' and 'Macintosh HD2'. I remember there being three at one time in Yosemite but that was fixed in an update.

Also, there appears to be no Recovery partition. Cmd+R launches Internet Recovery.

 

Distil results (Boot Camp partition removed):

 

/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 Internal Drive          121.0 GB   disk0s2

   3:                 Apple_Boot Boot OS X               134.2 MB   disk0s3

/dev/disk2 (internal, physical):

   #:                       TYPE NAME                    SIZE       IDENTIFIER

   0:      GUID_partition_scheme                        *3.0 TB     disk2

   1:                        EFI NO NAME                 209.7 MB   disk2s1

   2:          Apple_CoreStorage Internal Drive          3.0 TB     disk2s2

   3:                 Apple_Boot Boot OS X               134.2 MB   disk2s4

/dev/disk3 (internal, virtual):

   #:                       TYPE NAME                    SIZE       IDENTIFIER

   0:                  Apple_HFS Macintosh HD           +3.1 TB     disk3

                                 Logical Volume on disk0s2, disk2s2

                                 7BE1F343-ACBE-4144-BF86-C838BE1E49D4

                                 Unencrypted Fusion Drive

imac---simon:~ simon$ diskutil cs list

CoreStorage logical volume groups (1 found)

|

+-- Logical Volume Group CA0B8D0A-6315-4E85-B313-52AB509473F2

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

    Name:         Internal Drive

    Status:       Online

    Size:         3121237860352 B (3.1 TB)

    Free Space:   0 B (0 B)

    |

    +-< Physical Volume 5E75EE74-EE1F-4FCB-A0C5-9ED5517FEB93

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

    |   Index:    0

    |   Disk:     disk0s2

    |   Status:   Online

    |   Size:     120988852224 B (121.0 GB)

    |

    +-< Physical Volume 91D639D6-634E-47C1-AFE5-616CE12E71E0

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

    |   Index:    1

    |   Disk:     disk2s2

    |   Status:   Online

    |   Size:     3000249008128 B (3.0 TB)

    |

    +-> Logical Volume Family EE9934AC-F3CB-4101-ADB6-576F4371B4B9

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

        Encryption Type:         None

        |

        +-> Logical Volume 7BE1F343-ACBE-4144-BF86-C838BE1E49D4

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

            Disk:                  disk3

            Status:                Online

            Size (Total):          3106705375232 B (3.1 TB)

            Revertible:            No

            LV Name:               Macintosh HD

            Volume Name:           Macintosh HD

            Content Hint:          Apple_HFS

            LVG Type:              Fusion, Sparse

iMac (27-inch, Late 2013), OS X El Capitan (10.11.4), null

Posted on Apr 28, 2016 8:39 AM

Close

Q: Issue trying to clean install Windows 10 on Fusion Drive. el Capitan.

  • All replies
  • Helpful answers

first Previous Page 3 of 6 last Next
  • by Loner T,

    Loner T Loner T May 2, 2016 9:45 AM in response to Moonraker
    Level 7 (23,493 points)
    Safari
    May 2, 2016 9:45 AM in response to Moonraker

    Moonraker wrote:

     

    Reinstalled OS X 10.10 Yosemite. Updated to 10.10.5 with BCA 5.1.4. Reset NVRAM. Disconnected wired connection. Used existing WININSTALL W10 USB2 via BCA to create new Boot Camp partition . Rebooted, confirmed initial settings and commenced install process. Time much the same as previously posted.

     

    Eventually reached W10 desktop but same very slow responses, BC Setup.exe opens and starts 'Enumerating....' small green bar but then does not progress after 1 hour. Rebooted took 25 minutes to reach desktop again. Everything takes minutes rot respond.

     

     

    What is your Windows Computer language setting? Some language selections are known to cause this problem.

     

    Moonraker wrote:

     

    Tried setting selective boot in mschonfig for basic boot but still the same delays. Inserted USB2 install and tried to run Setup.exe but got error 'This version of Boot Camp is not intended for this computer model' so not able to even try and install BC drivers and updates.

     

    Using DU in OS X shows no issues.

     

    Basically looks like it has not resolved the slow install booted in Windows issue preventing install of BC drivers.

     

    What is the Product Version in Bootcamp.xml on this W10 USB?

     

    Moonraker wrote:

     

    Not sure what to do next. I have downloaded the W10 media install iso twice. Not sure how to check hash sum for any issue with that.

    Not sure why I am getting that BD error on trying to run Setup.exe given it is created and we checked previously via BCA 5.1.4.

     

    I can't seem to be able to boot W10 via Safe Boot but guess it is same as msconfig with Selective boot and restart.

     

     

    We are going to try something a bit more radical next - install a minimal W10 on the SSD.

     

    1. Remove W10 using BC Assistant.

    2. Run the following command to create a 60GB FAT32 partition.

     

    diskutil coreStorage resizeStack 5073B838-BBC1-4931-85A1-55558687D58F 6641A8D4-B739-4E86-843E-5C686A8DF4DE 60g fat32 BOOTCAMP

     

    3. Boot from W10 Installer USB and choose the ~60GB partition on the SSD and install W10 and capture timing.

     

    Help for the resizeStack command

    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

  • by Moonraker,

    Moonraker Moonraker May 2, 2016 9:56 AM in response to Loner T
    Level 1 (9 points)
    Windows Software
    May 2, 2016 9:56 AM in response to Loner T

    Windows 10 is set to ENG UK. Same as I had previously. Same for Keyboard.

     

    The error message from Setup.exe was most likely due to having used mschonfig to boot to Safe mode. As it didn't help I reset to default mode, rebooted and Setup.exe launched OK. Still stuck at Enumerating green bar at around 5% as previously. Will check product version once this attempt to get drivers on W10 ends.

     

    Will try this next.

  • by Loner T,

    Loner T Loner T May 2, 2016 10:12 AM in response to Moonraker
    Level 7 (23,493 points)
    Safari
    May 2, 2016 10:12 AM in response to Moonraker

    Try English US as the language for the BC setup.exe.

  • by Moonraker,

    Moonraker Moonraker May 2, 2016 10:27 AM in response to Loner T
    Level 1 (9 points)
    Windows Software
    May 2, 2016 10:27 AM in response to Loner T

    I initially downloaded an W10 English iso which is US and used that with US language, keyboard but results have been the same. I downloaded an ENG International W10 media iso which I have used since and left it at the UK language/ keyboard which it defaults to in initial settings. This was trying a second iso download; I still can't find a way to check the hash checksum to be sure there is no corruption in download. Apparently each download has a unique hash.

     

    I can try US English though guess I would better download the US English install if doing that?

  • by Loner T,

    Loner T Loner T May 2, 2016 11:47 AM in response to Moonraker
    Level 7 (23,493 points)
    Safari
    May 2, 2016 11:47 AM in response to Moonraker

    This is what I currently have. What are the ISO filename(s) that you are currently using?

    ls -lhg

    total 84256616

     

    -rw-r--r--@ 1 staff   4.1G Feb 21 13:51 Win10_1511_1_English_x64.iso

    -rw-r--r--@ 1 staff   3.7G Oct 31  2015 Win10_1511_EnglishInternational_x64.iso

    -rw-r--r--@ 1 staff   3.7G Oct 31  2015 Win10_1511_English_x64.iso

    -rw-r--r--@ 1 staff   3.7G Nov 22 22:26 Win10_1511_French_x64.iso

    -rw-r--r--@ 1 staff   3.7G Jan  8 14:50 Win10_1511_SingleLang_EnglishInternational_x64.iso

    -rw-r--r--@ 1 staff   3.6G Nov 22 22:30 Win10_1511_SingleLang_French_x64.iso

    -rw-r--r--@ 1 staff   4.0G Jul  2  2015 Win8.1_Dutch_x64.iso

    -rw-r--r--@ 1 staff   4.0G Dec  5  2014 Win8.1_English_x64.iso

    -rw-r--r--  1 staff   2.7G Jul 26  2014 Windows8.1-32bit.cdr

    -rw-r--r--  1 staff   3.6G Jul 26  2014 Windows8.1-64bit.cdr

     

    $ openssl md5 Win10_1511_1_English_x64.iso

    MD5(Win10_1511_1_English_x64.iso)= a4fde74732557d75ffc5354d0271832e

    $ openssl md5 Win10_1511_EnglishInternational_x64.iso

    MD5(Win10_1511_EnglishInternational_x64.iso)= 3c45cb361bf29098c2536e14a2be6f1c

  • by Moonraker,

    Moonraker Moonraker May 2, 2016 1:25 PM in response to Loner T
    Level 1 (9 points)
    Windows Software
    May 2, 2016 1:25 PM in response to Loner T

    openssl md5 /Users/simon/Desktop/Win10_1511_1_EnglishInternational_x64.iso

    MD5(/Users/simon/Desktop/Win10_1511_1_EnglishInternational_x64.iso)= b4140f914b656783c531871b2629c6a5

     

    openssl md5 /Users/simon/Desktop/Windows\ 8.1\ Install.iso

    MD5(/Users/simon/Desktop/Windows 8.1 Install.iso)= edfc9c76a7e859102e5164ec02384989

     

    Currently using the W10 International English version downloaded a few days ago. I believe the checksum varies as the MS web site creates a new .iso each time?

     

    I'll progress the last test now with the SSD partition.

     

    For info, I managed to eventually get the BC drivers installed onto W10 by copying the folders to the desktop and waiting a long time. On reboot the usual delay so it doesn't look like it is down to a lack of the BC driver updates.

  • by Moonraker,

    Moonraker Moonraker May 2, 2016 2:20 PM in response to Loner T
    Level 1 (9 points)
    Windows Software
    May 2, 2016 2:20 PM in response to Loner T

    Entering this command resulted in an error. Not sure from Help what is wrong if you have a suggestion please.

     

    diskutil coreStorage resizeStack 5073B838-BBC1-4931-85A1-55558687D58F 6641A8D4-B739-4E86-843E-5C686A8DF4DE 60g fat32 BOOTCAMP

    Incorrect number of arguments

     

    or info;

     

    imac---simon:~ simon$ diskutil list

    /dev/disk0

      #:                      TYPE NAME                    SIZE      IDENTIFIER

      0:      GUID_partition_scheme                        *121.3 GB  disk0

      1:                        EFI EFI                    209.7 MB  disk0s1

      2:          Apple_CoreStorage                        121.0 GB  disk0s2

      3:                Apple_Boot Boot OS X              134.2 MB  disk0s3

    /dev/disk1

      #:                      TYPE NAME                    SIZE      IDENTIFIER

      0:      GUID_partition_scheme                        *3.0 TB    disk1

      1:                        EFI EFI                    209.7 MB  disk1s1

      2:          Apple_CoreStorage                        3.0 TB    disk1s2

      3:                Apple_Boot Recovery HD            650.1 MB  disk1s3

    /dev/disk2

      #:                      TYPE NAME                    SIZE      IDENTIFIER

      0:                  Apple_HFS Macintosh HD          *3.1 TB    disk2

                                    Logical Volume on disk0s2, disk1s2

                                    5073B838-BBC1-4931-85A1-55558687D58F

                                    Unencrypted Fusion Drive

    imac---simon:~ simon$ diskutil cs list

    CoreStorage logical volume groups (1 found)

    |

    +-- Logical Volume Group 325DB18C-74DF-4E97-9E20-43E32159069D

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

        Name:        OSX-LVG

        Status:      Online

        Size:        3120721960960 B (3.1 TB)

        Free Space:  0 B (0 B)

        |

        +-< Physical Volume 6641A8D4-B739-4E86-843E-5C686A8DF4DE

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

        |  Index:    0

        |  Disk:    disk0s2

        |  Status:  Online

        |  Size:    120988852224 B (121.0 GB)

        |

        +-< Physical Volume 52281275-3F5C-4434-903B-2F7BEA53600D

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

        |  Index:    1

        |  Disk:    disk1s2

        |  Status:  Online

        |  Size:    2999733108736 B (3.0 TB)

        |

        +-> Logical Volume Family 86480997-C77F-4C38-8CF0-D601FB0213B1

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

            Encryption Status:      Unlocked

            Encryption Type:        None

            Conversion Status:      NoConversion

            Conversion Direction:    -none-

            Has Encrypted Extents:  No

            Fully Secure:            No

            Passphrase Required:    No

            |

            +-> Logical Volume 5073B838-BBC1-4931-85A1-55558687D58F

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

                Disk:                  disk2

                Status:                Online

                Size (Total):          3106189475840 B (3.1 TB)

                Conversion Progress:  -none-

                Revertible:            No

                LV Name:              Macintosh HD

                Volume Name:          Macintosh HD

                Content Hint:          Apple_HFS

  • by Loner T,

    Loner T Loner T May 2, 2016 2:57 PM in response to Moonraker
    Level 7 (23,493 points)
    Safari
    May 2, 2016 2:57 PM in response to Moonraker

    Please try the following command on a single line.

    diskutil coreStorage resizeStack 5073B838-BBC1-4931-85A1-55558687D58F 6641A8D4-B739-4E86-843E-5C686A8DF4DE 60g fat32 BOOTCAMP 0g
  • by Moonraker,

    Moonraker Moonraker May 2, 2016 3:05 PM in response to Loner T
    Level 1 (9 points)
    Windows Software
    May 2, 2016 3:05 PM in response to Loner T

    Result of the command entered onto one line.

     

    diskutil coreStorage resizeStack 5073B838-BBC1-4931-85A1-55558687D58F 6641A8D4-B739-4E86-843E-5C686A8DF4DE 60g fat32 BOOTCAMP 0g

    The Core Storage Logical Volume UUID is 5073B838-BBC1-4931-85A1-55558687D58F

    Started CoreStorage operation

    Checking prerequisites for resizing Logical-Physical volume stack

    Error: -69669: The request would shrink one of your Core Storage physical volumes to a size of zero; try a more modest change in size

  • by Loner T,

    Loner T Loner T May 2, 2016 3:11 PM in response to Moonraker
    Level 7 (23,493 points)
    Safari
    May 2, 2016 3:11 PM in response to Moonraker

    Try with 90g and 0g respectively.

  • by Moonraker,

    Moonraker Moonraker May 2, 2016 3:14 PM in response to Loner T
    Level 1 (9 points)
    Windows Software
    May 2, 2016 3:14 PM in response to Loner T

    Same error message, hopefully entered as requested;

     

    diskutil coreStorage resizeStack 5073B838-BBC1-4931-85A1-55558687D58F 6641A8D4-B739-4E86-843E-5C686A8DF4DE 90g fat32 BOOTCAMP 0g

    The Core Storage Logical Volume UUID is 5073B838-BBC1-4931-85A1-55558687D58F

    Started CoreStorage operation

    Checking prerequisites for resizing Logical-Physical volume stack

    Error: -69669: The request would shrink one of your Core Storage physical volumes to a size of zero; try a more modest change in size

  • by Loner T,Helpful

    Loner T Loner T May 2, 2016 6:14 PM in response to Moonraker
    Level 7 (23,493 points)
    Safari
    May 2, 2016 6:14 PM in response to Moonraker

    This is a bit more work then you wanted, but does the same command work properly in Internet Recovery. If you still get the same error in Internet Recovery, then we may need to rebuild the CS after the splitting the SSD in half first and then using the half SSD and the full HDD as OSX CS. Let me know if you need detailed steps.

  • by Moonraker,

    Moonraker Moonraker May 2, 2016 3:42 PM in response to Loner T
    Level 1 (9 points)
    Windows Software
    May 2, 2016 3:42 PM in response to Loner T

    Just loading Internet Recovery now to try again with the same commands in order. Will report back.

     

    I will need detailed steps to do as you asked please, if required.

  • by Loner T,

    Loner T Loner T May 2, 2016 3:52 PM in response to Moonraker
    Level 7 (23,493 points)
    Safari
    May 2, 2016 3:52 PM in response to Moonraker

    You have the steps on who to create the CS LV/LVG. The only difference is after step 4 where you erase the SSD.

     

    You will partition the SSD in half before you run step 6 using the following command.

     

    diskutil partitiondisk disk0 2 GPT jhfs+ SSD 60g fat32 BOOTCAMP R

     

    This should give you disk0s1 (EF), disk0s2 (JHFS+), disk0s3 (BOOTCAMP)

     

    Here is the help for the partitionDisk verb

    diskutil partitionDisk

    Usage:  diskutil partitionDisk MountPoint|DiskIdentifier|DeviceNode

            [numberOfPartitions] [APM[Format]|MBR[Format]|GPT[Format]]

            [part1Format part1Name part1Size part2Format part2Name part2Size

             part3Format part3Name part3Size ...]

     

    (Re)Partition an existing disk.  All volumes on this disk will be destroyed.

    Ownership of the affected disk is required.

     

    For the partition scheme parameter:

       APM specifies that an Apple Partition Map scheme be created.

       MBR specifies that a DOS-compatible format scheme be created.

       GPT specifies that a GUID Partitioning scheme be created.

    APMFormat and APMScheme are synonyms for APM; the same applies to the others.

     

    For each partition triplet:

       Format is normally the file system personality used to set the

          partition type and to choose the initialization (newfs) program.

          "diskutil listFilesystems" shows a list of supported personalities.

          Alternatively, you can specify "Free Space" to leave a gap.

          Or you can explicitly specify the partition type (either as a human-

          readable string or as a GPT UUID constant) surrounded by "%".

          Explicitly specifying the type or Free Space implies %noformat% (below).

       Name is the initial volume name (subject to file system-specific naming

          restrictions).  You can also specify %noformat% to skip initialization

          (newfs).  If the format (above) is "Free Space" or an explicit partition

          type, the name is ignored, but it must still be present.

       Size is the length of the partition (slice); the exact resulting size may

          be somewhat larger or smaller as necessary in certain cases.

     

    Valid sizes are floating-point numbers with a suffix of B(ytes), S(512-byte-

    blocks), K(ilobytes), M(egabytes), G(igabytes), T(erabytes), P(etabytes),

    or (%)percentage of the total size of the whole disk; also, at most 1 triplet

    can specify a size of "R" (without a preceding number) to specify the remainder

    left on the whole disk after considering the other sizes.

     

    The last partition will be lengthened to the end of the disk; to specify an

    exact size for the last usable partition, specify an additional partition

    of type "Free Space".

  • by Moonraker,

    Moonraker Moonraker May 2, 2016 3:57 PM in response to Loner T
    Level 1 (9 points)
    Windows Software
    May 2, 2016 3:57 PM in response to Loner T

    Results from trying commands via Internet Recovery. More verbose but ultimately the same errors. Will try the next instruction. Thanks for these.

     

    -bash-3.2# diskutil list

    /dev/disk0

       #:                       TYPE NAME                    SIZE       IDENTIFIER

       0:     Apple_partition_scheme                        *1.2 GB     disk0

       1:        Apple_partition_map                         30.7 KB    disk0s1

       2:                  Apple_HFS Mac OS X Base System    1.2 GB     disk0s2

    /dev/disk1

       #:                       TYPE NAME                    SIZE       IDENTIFIER

       0:      GUID_partition_scheme                        *121.3 GB   disk1

       1:                        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:                            untitled               *524.3 KB   disk2

    /dev/disk3

       #:                       TYPE NAME                    SIZE       IDENTIFIER

       0:                            untitled               *524.3 KB   disk3

    /dev/disk4

       #:                       TYPE NAME                    SIZE       IDENTIFIER

       0:                            untitled               *524.3 KB   disk4

    /dev/disk5

       #:                       TYPE NAME                    SIZE       IDENTIFIER

       0:                            untitled               *524.3 KB   disk5

    /dev/disk6

       #:                       TYPE NAME                    SIZE       IDENTIFIER

       0:                            untitled               *524.3 KB   disk6

    /dev/disk7

       #:                       TYPE NAME                    SIZE       IDENTIFIER

       0:                            untitled               *6.3 MB     disk7

    /dev/disk8

       #:                       TYPE NAME                    SIZE       IDENTIFIER

       0:                            untitled               *2.1 MB     disk8

    /dev/disk9

       #:                       TYPE NAME                    SIZE       IDENTIFIER

       0:                            untitled               *1.0 MB     disk9

    /dev/disk10

       #:                       TYPE NAME                    SIZE       IDENTIFIER

       0:                            untitled               *524.3 KB   disk10

    /dev/disk11

       #:                       TYPE NAME                    SIZE       IDENTIFIER

       0:                            untitled               *524.3 KB   disk11

    /dev/disk12

       #:                       TYPE NAME                    SIZE       IDENTIFIER

       0:                            untitled               *1.0 MB     disk12

    /dev/disk13

       #:                       TYPE NAME                    SIZE       IDENTIFIER

       0:     FDisk_partition_scheme                        *7.9 GB     disk13

       1:                 DOS_FAT_32 WININSTALL              7.9 GB     disk13s1

    /dev/disk14

       #:                       TYPE NAME                    SIZE       IDENTIFIER

       0:      GUID_partition_scheme                        *3.0 TB     disk14

       1:                        EFI                         209.7 MB   disk14s1

       2:          Apple_CoreStorage                         3.0 TB     disk14s2

       3:                 Apple_Boot Recovery HD             650.1 MB   disk14s3

    /dev/disk15

       #:                       TYPE NAME                    SIZE       IDENTIFIER

       0:                  Apple_HFS Macintosh HD           *3.1 TB     disk15

    -bash-3.2# diskutil cs list

    CoreStorage logical volume groups (1 found)

    |

    +-- Logical Volume Group 325DB18C-74DF-4E97-9E20-43E32159069D

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

        Name:         OSX-LVG

        Status:       Online

        Size:         3120721960960 B (3.1 TB)

        Free Space:   0 B (0 B)

        |

        +-< Physical Volume 6641A8D4-B739-4E86-843E-5C686A8DF4DE

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

        |   Index:    0

        |   Disk:     disk1s2

        |   Status:   Online

        |   Size:     120988852224 B (121.0 GB)

        |

        +-< Physical Volume 52281275-3F5C-4434-903B-2F7BEA53600D

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

        |   Index:    1

        |   Disk:     disk14s2

        |   Status:   Online

        |   Size:     2999733108736 B (3.0 TB)

        |

        +-> Logical Volume Family 86480997-C77F-4C38-8CF0-D601FB0213B1

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

            Encryption Status:       Unlocked

            Encryption Type:         None

            Conversion Status:       NoConversion

            Conversion Direction:    -none-

            Has Encrypted Extents:   No

            Fully Secure:            No

            Passphrase Required:     No

            |

            +-> Logical Volume 5073B838-BBC1-4931-85A1-55558687D58F

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

                Disk:               disk15

                Status:             Online

                Size (Total):       3106189475840 B (3.1 TB)

                Size (Converted):   -none-

                Revertible:         No

                LV Name:            Macintosh HD

                Volume Name:        Macintosh HD

                Content Hint:       Apple_HFS

    -bash-3.2# diskutil coreStorage resizeStack 5073B838-BBC1-4931-85A1-55558687D58F 6641A8D4-B739-4E86-843E-5C686A8DF4DE 60g fat32 BOOTCAMP

    Incorrect number of arguments

    -bash-3.2# diskutil coreStorage resizeStack 5073B838-BBC1-4931-85A1-55558687D58F 6641A8D4-B739-4E86-843E-5C686A8DF4DE 60g 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 59999997952 bytes

    Shrinking Core Storage Physical Volume from 120988852224 to 18446741148508925952 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 3106189475840 bytes

    Growing file system

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

    -bash-3.2# diskutil coreStorage resizeStack 5073B838-BBC1-4931-85A1-55558687D58F 6641A8D4-B739-4E86-843E-5C686A8DF4DE 60g 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 59999997952 bytes

    Shrinking Core Storage Physical Volume from 120988852224 to 18446741148508925952 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 3106189475840 bytes

    Growing file system

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

    -bash-3.2# diskutil coreStorage resizeStack 5073B838-BBC1-4931-85A1-55558687D58F 6641A8D4-B739-4E86-843E-5C686A8DF4DE 90g 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 89999998976 bytes

    Shrinking Core Storage Physical Volume from 120988852224 to 18446741178508926976 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 3106189475840 bytes

    Growing file system

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

first Previous Page 3 of 6 last Next