9

this is a somewhat similar post to this one (Can't create partition on free space with Disk Utility) but not quite...

It started with me creating a BootCamp partition (around 145 GB) for Windows 8 quite some time ago.

Everything was working fine until I decided to upgrade to 8.1 from the Windows store - the installation went fine but Windows never managed to boot again. I managed to fix the iMac into booting OSX and forgot about it until today (oh why?!)

I decided I will give 8.1 another go - as the partition was there and so I wanted to use it by trying to install over it again. I chose the EFI install and went for it, but the installer informed me that it will not install, because the partition has MBR instead of GPT.

So instead of running the installer again in normal mode - I logged back into OSX deleted the BOOTCAMP partition (or so I then thought), ran the installer again in EFI and told it to create a partition for itself in the free space and install Windows.

The installer created 3 partition - 1 large one and 2 small ones. I didn't like that so went back to OS X tried to delete those partitions, but that of course didn't work and my drive became messier and messier. By that time I knew I was not very smart about it and tried to delete all the partitions I thought I didn't need from the Windows Installer.

I messed up even more... OSX stopped booting. I then read and performed steps from the above mentioned thread. But all along my diskutil list showed 2 physical volumes instead of 1.

So I followed all the steps from the above thread and this is the effect at the moment:

Disk Utility - No hidden partitions

Disk Utility - No hidden partitions

Disk Utility - hidden partitions shown

Disk Utility - hidden partitions shown

Diskutility - partition scheme

Diskutility - partition scheme

Information from the Terminal:

-bash-3.2# 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                     *1.0 TB   disk1
    1:                         EFI EFI                209.7 MB   disk1s1
    2:           Apple_CoreStorage                    852.7 GB   disk1s2
    3:                  Apple_Boot Recovery HD        650.1 MB   disk1s3
    4:                         EFI NO NAME            104.9 MB   disk1s4
 /dev/disk2
    #:                        TYPE NAME               SIZE       IDENTIFIER
    0:      Apple_partition_scheme                     *1.3 GB   disk2
    1:         Apple_partition_map                     30.7 KB   disk2s1
    2:                   Apple_HFS OS X Base System     1.3 GB   disk2s2
 /dev/disk3
    #:                        TYPE NAME               SIZE       IDENTIFIER
    0:                   Apple_HFS Macintosh HD       967.8 GB   disk3
                                   Logical Volume on disk1s2, disk0s2
                                   D237FFDC-70A4-41D7-AC13-4CC7E5E8C0A0
                                   Unencrypted Fusion Drive
/dev/disk4
    #:                        TYPE NAME               SIZE       IDENTIFIER
    0:                             untitled           *5.2 MB    disk4
/dcv/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         *524.3 KB    disk7
/dev/disk8
    #:                        TYPE NAME               SIZE       IDENTIFIER
    0:                             untitled         *524.3 KB    disk8
/dev/disk9
    #:                        TYPE NAME               SIZE       IDENTIFIER
    0:                             untitled         *524.3 KB    disk9
/dev/disk10
    #:                        TYPE NAME               SIZE       IDENTIFIER
    0:                             untitled           *6.3 MB    disk10
/dev/disk11
    #:                        TYPE NAME               SIZE       IDENTIFIER
    0:                             untitled           *2.1 MB    disk11
/dev/disk12
    #:                        TYPE NAME               SIZE       IDENTIFIER
    0:                             untitled           *1.0 MB    disk12
/dev/disk13
    #:                        TYPE NAME               SIZE       IDENTIFIER
    0:                             untitled         *524.3 KB    disk13
/dev/disk14
    #:                        TYPE NAME               SIZE       IDENTIFIER
    0:                             untitled         *524.3 KB    disk14
/dev/disk15
    #:                        TYPE NAME               SIZE       IDENTIFIER
    0:                             untitled           *1.0 MB    disk15
/dev/disk16
    #:                        TYPE NAME               SIZE       IDENTIFIER
    0:                             untitled           *6.3 MB    disk16
-bash-3.2#
-bash-3.2# diskutil cs list
CoreStorage logical volume groups (1 found)
|
+-- Logical Volume Group 1EFE58BC-3613-44C4-86EE-D816F3B66E3E
    =========================================================
    Name:   Macintosh HD
    Status: Online
    Size:   973655252992 B (973.7 G8)
    Free Space: 0 B (0 B)
    |
    +-- Physical Volume 93892BE8-2B7F-4ABD-A4C3-984495DCD98D
    |   ----------------------------------------------------
    |
    |   Index:  0                     
    |   Disk:   disk1s2    
    |   Status: Online
    |   Size:   852666400768 B (852.7 GB)
    |                                                               
    +-- Physical Volume 4BF0E99A-8D5F-4B1E-B6C5-31B705455EDF                          
    |   ----------------------------------------------------
    |
    |   Index:  1                                                       
    |   Disk:   disk0s2                                                      
    |   Status: Online                                                     
    |   Size:   120988852224 B (121.0 GB)
    |     
    +-- Logical Volume Family 3C62D09F-E2B7-47E2-8106-76EDB58F32F7
        ----------------------------------------------------------
        Encryption Status:      Unlocked
        Encryption Type:        None
        Conversion Status:      NoConversion
        Conversion Direction:   -none-
        Has Encrypted Extents:  No
        Fully Secure:           No
        Passphrase Required:    No
        |
        +-- Logical Volume D237FFDC-7DA4-41D7-AC13-4CC7E5E8C0A0  
            ---------------------------------------------------
            Disk:                 disk3                                                        
            Status:               Online                                                     
            Size (Total):         967799996416 B (967.8 GB) 
            Conversion Progress:  -none-                    
            Revertible:           No 
            LV Name:              Macintosh HD    
            Volume Name:          Macintosh HD         
            Content Hint:         Apple_HFS

Result of gpt -r -vvv show /dev/disk0:

-bash-3.2# gpt -r -vvv show /dev/disk0
gpt show: /dev/disk0: mediasize=121332826112; sectorsize=512; blocks=236978176
gpt show: /dev/disk0: PMBR at sector 0
gpt show: /dev/disk0: Pri GPT at sector 1
gpt show: /dev/disk0: GPT partition: type=C12A7328-F81F-11D2-BA48-00A0C93EC93B, start=40, size=409600
gpt show: /dev/disk0: GPT partition: type=53746F72-6167-11AA-AA11-00306543ECAC, start=409640, size=236306352
gpt show: /dev/disk0: GPT partition: type=426F6F74-0000-11AA-AA11-00306543ECAC, start=236715992, size=262144
gpt show: /dev/disk0: Sec GPT at sector 236978175
    start      size index contents
        0         1       PMBR
        1         1       Pri GPT header
        2        32       Pri GPT table
       34         6
       40    409600     1 GPT part - C12A7328-F81F-11D2-BA4B-00A0C93EC93B
   409640 236306352     2 GPT part - 53746F72-6167-11AA-AA11-00306543ECAC
236715992    262144     3 GPT part - 426F6F74-0000-11AA-AA11-00306543ECAC
236978136         7
236978143        32       Sec GPT table
236978175         1       Sec GPT header

Result of gpt -r -vvv show /dev/disk1:

-bash-3.2# gpt -r -vvv show /dev/disk1
gpt show: /dev/disk1: mediasize=1000204886016; sectorsize=512; blocks=1953525168
gpt show: /dev/disk1: PMBR at sector 0
gpt show: /dev/disk1: Pri GPT at sector 1
gpt show: /dev/disk1: GPT partition: type=C12A7328-F81F-11D2-BA4B-00A0C93EC93B, start=40, size=409600
gpt show: /dev/disk1: GPT partition: type=53746F72-6167-11AA-AA11-00306543ECAC, start=409640, size=1671210848
gpt show: /dev/disk1: GPT partition: type=426F6F74-0000-11AA-AA11-00306543ECAC, start=1671620488, size=1269760
gpt show: /dev/disk1: GPT partition: type=C12A7328-F81F-11D2-BA4B-00A0C93EC93B, start=1672890368, size=204800
gpt show: /dev/disk1: Sec GPT at sector 1953525167                               
     start          size  index contents                                        
         0             1        PMBR                                            
         1             1        Pri GPT header                                  
         2            32        Pri GPT table                                   
        34             6
        40        409600      1 GPT part - C12A7328-F81F-11D2-BA4B-00A0C93EC93B
    409640    1671210848      2 GPT part - 53746F72-6167-11AA-AA11-00306543ECAC
1671620488       1269760      3 GPT part - 426F6F74-0000-11AA-AA11-00306543ECAC
1672890248           120   
1672890368        204800      4 GPT part - C12A7328-F81F-11D2-BA4B-00A0C93EC93B
1673095168     280429967
1953525135            32        Sec GPT table
1953525167             1        Sec GPT header

I don't know where to go from here? Why are there 2 physical volumes and what to do with them? If anyone could help I would greatly appreciate it.

  • Do you have a backup of your volume 'Macintosh HD'? Is any important data on your Mac or could you delete all volumes and start from scratch? – klanomath Jan 24 '15 at 0:26
  • Sorry just noticed this comment now - I am ready to go from scratch. And of course thanks very much for your help on this. I will be online now... – dalogrus Jan 24 '15 at 7:41
  • Please add pictures of gpt -r -vvv show /dev/disk0 and gpt ... /dev/disk1 executed in Terminal to your question. I will convert them with an OCR app afterwards. – klanomath Jan 24 '15 at 8:36
  • Done. I added them after the first 3. – dalogrus Jan 24 '15 at 9:11
  • Index NO.4 partition of disk1 must be created by windows installer. I would like to suggest your the remove it if you don't care about windows partition. – nelson Jan 24 '15 at 9:24
15

Theoretically everything is fine with your Fusion Drive. Fusion Drives look like this. Disk0 is your SSD with 121 GB and disk1 is your HDD with ~1 TB (~1.121 TB summed up).

The larger parts of your SSD (disk0s2) and your HDD (disk1s2) are pooled to a CoreStorage LVG (Fusion Drive: disk3) with a size of 967.8 GB. The rest is reserved for EFIs, a Recovery HD (alltogether ~1.3 GB) and your old Windows partition - now probably free space (~152 GB).

The logical volume 'Macintosh HD' (967.8 GB) spans disk0s2 and disk1s2. This is the first 'Macintosh HD' in picture 1. The volume 'Macintosh HD' - it's the one visible on the desktop - should ideally also have about 967.8 GB. This is the second 'Macintosh HD' in picture 1.
In fact it has only 852.67 GB (see picture 3).

In the second picture the logical volume 'Macintosh HD' is the first listed in black, the volume 'Macintosh HD' is the second listed in black, the other two 'Macintosh HD's listed in grey are the parts of your SSD and HDD dedicated to the logical volume 'Macintosh HD'.

In my opinion something went wrong after deleting various partitions with the Bootcamp Assistant/Disk Utility or in Windows.

Preparation:

  • Detach any external drive (especially your external Time Machine backup drive)
  • Restart to Internet Recovery Mode by pressing alt cmd R at startup.
    The prerequisites are the latest firmware update installed, either ethernet or WLAN (WPA/WPA2) and a router with DHCP activated.
    On a 50 Mbps-line it takes about 4 min (presenting a small animated globe) to boot into a recovery netboot image which usually is loaded from an apple/akamai server.

    I recommend ethernet because it's more reliable. If you are restricted to WIFI and the boot process fails, just restart your Mac until you succeed booting.

    Alternatively you may start from a bootable installer thumb drive (preferably Mavericks or Yosemite) or a thumb drive containing a full system (preferably Mavericks or Yosemite).

Now you may either repair CoreStorage or rebuild your Fusion Drive:

'Repair CoreStorage' (not recommended):

  • First i would try to check the volume 'Macintosh HD' with Disk Utility. If the volume is corrupted consider a reinstall of Mac OS X.

  • If the volume is ok quit Disk Utility

  • Open Terminal and enter diskutil unmountDisk /dev/LVIdentifier and both diskutil unmountDisk /dev/DiskContainingApple_CoreStorageIdentifier
    In your case: first diskutil unmountDisk /dev/disk3 then diskutil unmountDisk /dev/disk0 and diskutil unmountDisk /dev/disk1
  • remove the EFI NO NAME partition with gpt remove -i IndexNumberOfEFINoName DiskIdentifier:
    gpt remove -i 4 disk1
  • Remount the CoreStorage disks and then the Logical Volume:
    In your case: first diskutil mountDisk /dev/disk0 and diskutil mountDisk /dev/disk1 and then diskutil mount /dev/disk3.
  • enter gpt -r -vvv show /dev/diskIdentfierOfApple_CoreStorage to get infos of your HDD CoreStorage disk.
    In your case: gpt -r -vvv show /dev/disk1
    It should look like this:

    -bash-3.2# gpt -r -vvv show /dev/disk1
    gpt show: /dev/disk1: mediasize=1000204886016; sectorsize=512;         blocks=1953525168
    gpt show: /dev/disk1: PMBR at sector 0
    gpt show: /dev/disk1: Pri GPT at sector 1
    gpt show: /dev/disk1: GPT partition: type=C12A7328-F81F-11D2-BA4B-00A0C93EC93B, start=40, size=409600
    gpt show: /dev/disk1: GPT partition: type=53746F72-6167-11AA-AA11-00306543ECAC, start=409640, size=1671210848
    gpt show: /dev/disk1: GPT partition: type=426F6F74-0000-11AA-AA11-00306543ECAC, start=1671620488, size=1269760
    gpt show: /dev/disk1: Sec GPT at sector 1953525167                               
         start          size  index contents                                        
             0             1        PMBR                                            
             1             1        Pri GPT header                                  
             2            32        Pri GPT table                                   
            34             6
            40        409600      1 GPT part - C12A7328-F81F-11D2-BA4B-00A0C93EC93B
        409640    1671210848      2 GPT part - 53746F72-6167-11AA-AA11-00306543ECAC
    1671620488       1269760      3 GPT part - 426F6F74-0000-11AA-AA11-00306543ECAC
    1672890248     280634887
    1953525135            32        Sec GPT table
    1953525167             1        Sec GPT header
    
  • The free space on your HDD has 280634887 blocks. Please calculate the biggest block number dividable through 8. That's 280634880 blocks (á 512 bytes) which equals 143685058560 B or ~143.7 GB. Add the size of your HDD CoreStorage Physical Volume (852666400768 B) The result is 143685058560 B + 852666400768 B = 996351459328 B

  • Resize your HDD CoreStorage physical volume with diskutil cs resizeDisk HDDPVUUID newsize
    In your case: diskutil cs resizeDisk 93892BE8-2B7F-4ABD-A4C3-984495DCD98D 996351459328b
  • Calculate the maximal size of your CoreStorage Logical Volume in diskutil cs list: (size disk0s2) + (size disk1s2) In your case that's 120988852224 B + 996351459328 B = 1117340311552 B. That should be the size of your refreshed Logical Volume Group.
  • Resize your Logical Volume with diskutil cs resizeVolume LVUUID LVGSize-128 MB In your case that's diskutil cs resizeVolume D237FFDC-7DA4-41D7-AC13-4CC7E5E8C0A0 1117212311552b. If you get an error (There is not enough free space...) choose a smaller size like 1117148311552b.
  • Quit Terminal and open Disk Utility.
  • Check your expanded CoreStorage Volume for errors.
  • Quit Disk Utility, choose your CS volume as startup disk and restart your Mac

'Rebuild Fusion Drive' (recommended if you have a Time Machine backup)

  • Booted to Internet Recovery Mode open Utilities → Terminal in the menubar and enter:
    diskutil cs list to get the CoreStorage listing.
  • Copy the Logical Volume UUID, it's the fifth listed.
  • Now delete the Logical Volume with diskutil cs deleteVolume LVUUID.
    In your case: diskutil cs deleteVolume D237FFDC-7DA4-41D7-AC13-4CC7E5E8C0A0.
  • Copy the Logical Volume Group UUID, it's the first listed in the listing of diskutil cs list.
  • Then delete the Logical Volume Group with diskutil cs delete LVGUUID.
    In your case: diskutil cs delete 1EFE58BC-3613-44C4-86EE-D816F3B66E3E
  • Enter exit and quit 'Terminal'
  • Open 'Disk Utility'. Enter 'Ignore' if you are asked to fix the drives.
  • Choose your SSD and partition it: 1 Partition Mac OS X Extended (Journaled), hit the Options button and choose GUID Partiton table and hit OK and Apply.
    Please check that the size is ~121 GB

    Example:

    ssd

  • Choose your HDD and partition it: 1 Partition Mac OS X Extended (Journaled), hit the Options button and choose GUID Partiton table and hit OK and Apply.
    Please check that the size is ~1 TB

    Example:

    hdd

  • Quit Disk Utility and open Terminal

  • Enter diskutil list

    Example (your disk identifiers and sizes are different of course: Your volume SSD probably has the Identifier disk0s2 and the size 121 GB and your volume HDD probably has the Identifier disk1s2 and the size 1.0 TB):

    diskutil

  • Enter diskutil cs create "Name" IdentifierSSD IdentifierHDD
    In your case probably diskutil cs create "Macintosh HD" disk0s2 disk1s2.

    Copy the resulting LVGUUID

    Example:

    cscreate

  • Enter diskutil cs CreateVolume LVGUUID jhfs+ "Macintosh HD" 100%.

    Example:

    lvcreate

  • Enter diskutil cs list
    Check the size of your Logical Volume. It should have the size ~1.121 TB

    Example:

    diskcslist

  • Quit Terminal

  • Open 'Disk Utility' and check your newly created volume for errors
  • Quit 'Disk Utility'
  • Attach your external Time Machine backup drive or check this answer if you use NAS or another network share.
  • Open 'Restore from Time Machine Backup'
  • Choose the appropriate Time Machine backup and restore your system
  • Reboot to your restored system.
  • Unmount and detach your Time Machine backup drive
  • Open 'Terminal' and enter 'diskutil list'
  • Check if your 'Recovery HD' is listed.
  • If your 'Recovery HD' is missing, usually reinstalling your current system with the latest available system installer (e.g. 'Install OS X Mavericks (10.9.5)' if Mavericks is currently installed) will recreate it without loosing any data. AFAIK Recovery Partition Creator 3.8 will NOT create a Recovery HD on CoreStorage volumes.
  • After reinstalling the system with the latest available system installer open App Store and install the latest security fixes.
  • Comments are not for extended discussion; this conversation has been moved to chat. – bmike Jan 24 '15 at 16:58
  • For those with the Time Machine on a network drive like me and wanting to restore without bootable OS X - there is a step-by-step walkthrough here: (ialsowent.com/2012/08/13/recovering-from-time-machine-on-nas) . – dalogrus Jan 24 '15 at 17:18
  • @klanomath Got you about the Time Machine solution, unfortunately I can't actively participate in chat rooms yet, hence my answer here. FYI - I restored from the NAS and everything works great! Thank you again and let me know where to send the beers? ;) – dalogrus Jan 25 '15 at 22:10
  • @dalogrus I prefer Wodka ;-). Hmm regarding the chat: I think an admin increasesd your 'temporary chat points' to 50 so that you can participate in this little chatroom. At least your account has shown 50 points there... – klanomath Jan 25 '15 at 22:17
  • Ok got the chat to work, will try to reach you on it tomorrow... – dalogrus Jan 25 '15 at 22:36
0

Where did you fail? Where ever you could.

The disks are GPT. Windows thinks they are MBR. Apple/Microsoft set it up this way. This means you can not use anything from Microsoft to change the partitions on the disks. If changes are going to be made to the partitions, the software used must come from Apple. The only exception is windows can format partitions. Now while the Disk Utility and the Terminal can be used to change partitions, there is no reason to do so. You should be using Bootcamp to create or destroy the windows Bootcamp partition. Bootcamp knows what it is doing, you don't.

If you wish to know what MBR partition scheme windows views, enter the following commands in a terminal window:

fdisk /dev/disk0
fdisk /dev/disk1

Your OS X HFS+ core storage partitions should have an id of AC. Windows partitions are type 07. The efi partition is type EE and the OS X recovery partition is type AB.

I am not using core storage. I would tell you do to do the same, except with a fusion drive you have no choice. I have found, the OS X partition can not be resize unless it is done while OS X is running. This is the opposite of what I would have expected. Using the disk utility to resize the OS X boot partition while booted to a recovery partition for me has resulted in failure. However, resizing is possible for both Windows and OS X, if you remove them from their partitions, resize the partitions and then restore them back to their partitions.

FYI, here is some info on Fusion drives: Mac mini (Late 2012 and later), iMac (Late 2012 and later): About Fusion Drive

  • I made the mistake with the 2 disk1s2. Previously the OP published some huge pics and i ran them through OCR and used the text output. Probably i missed that error. – klanomath Jan 24 '15 at 7:29
  • @DavidAnderson Yes I think you are right - there is something wrong with the partitions and naming of the volumes thats why I am ready to start with setting this up from scratch and then restoring from a Time Machine copy... Also thanks for having a look into my case. – dalogrus Jan 24 '15 at 7:45
0

I had the same problem after an attempt to install Windows 8.1 on my fusion drive. That wouldn't work since windows refused to use the MBR type partition created by bootcamp. Yosemite was running ok, there was just a 300Gb unmovable free space block. I could have left it as it was, but I decided to reinstall Yosemite booting from a USB install drive. It took about 2 hours, after that everything was working again. No free space, no extra little partitions (there were 13 of them), and the recovery partition was present once more. I made a fresh time machine backup just in case, but I ended up not even have to use it. This is consistent with report that the installer is cable of repairing fusion drive issues.

-3

Since you are using El Capitan you can now do this:

From the terminal execute

diskutil coreStorage delete lvgUUID

Then exit terminal.

Start disk utility.

When it prompts you to fix the drive, say yes. It will automatically rebuild the Fusion drive.

  • 1
    This does not rebuild your Fusion drive volume, it DELETES it. – Allan Aug 21 '16 at 11:54
  • Can anyone verify whether this works as an alternative to klanomath’s answer assuming you have a time machine backup to restore from afterwards? – Patrick L Nov 9 '17 at 19:57

You must log in to answer this question.

protected by Community Dec 20 '17 at 15:33

Thank you for your interest in this question. Because it has attracted low-quality or spam answers that had to be removed, posting an answer now requires 10 reputation on this site (the association bonus does not count).

Would you like to answer one of these unanswered questions instead?

Not the answer you're looking for? Browse other questions tagged .