Can't rescue original disk size (Sierra)

Discussion in 'Mac Basics and Help' started by Wowzera, Sep 13, 2017.

  1. Wowzera macrumors 6502a

    Joined:
    Oct 14, 2008
    Location:
    Brazil
    #1
    Hello,

    I recently deleted a bootcamp partition in my drive, but I can not rescue the size of my drive.
    I have a MPB 2015 128GB. But it is currently showing only 83GB of disk space.
    Can anyone help me? I have no clue what happened here.
     

    Attached Files:

  2. Kissmyne macrumors 6502

    Kissmyne

    Joined:
    Apr 21, 2015
    #2
    Run "First Aid" on the volume group using Disk Utility, you may also need to force Spotlight to reindex as well...
     
  3. Wowzera thread starter macrumors 6502a

    Joined:
    Oct 14, 2008
    Location:
    Brazil
    #3
    Ok, just did it and didnt change a thing. Disk utility showed that my disk is ok, nothing wrong.
     
  4. Bruno09, Sep 14, 2017
    Last edited: Sep 14, 2017

    Bruno09 macrumors 68020

    Joined:
    Aug 24, 2013
    Location:
    Far from here
    #4
    You need to use the Terminal to solve this issue.

    First, make sure to have a full backup of your machine (Time machine, clone)

    Then in Terminal, paste this :

    diskutil cs resizeStack F753BED7-78F3-43D4-9A8F-3920722FB6E2 0b

    Hit Enter.

    This command ask to extend the core storage to the maximum space available (0b left).

    You should see this in the Terminal :

    MacBook-Pro-de-Matheus:~ matheus$ diskutil cs resizeStack F753BED7-78F3-43D4-9A8F-3920722FB6E2 0b


    The Core Storage Logical Volume UUID is F753BED7-78F3-43D4-9A8F-3920722FB6E2


    Started CoreStorage operation


    Checking prerequisites for resizing Logical-Physical volume stack


    Growing Logical-Physical volume stack


    Verifying file system


    Using live mode


    Performing live verification


    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


    File system check exit code is 0


    Growing Core Storage Physical Volume from 83 364 976 128 to 120 473 067 520 bytes


    Copying booter


    Growing disk partition


    Modifying partition map


    Growing Core Storage data structures


    Resizing Core Storage Physical Volume structures


    Resized Core Storage Physical Volume to 120 473 067 520 bytes


    Growing Logical Volume


    Resizing Core Storage Logical Volume structures


    Resized Core Storage Logical Volume to 120 108 089 344 bytes


    Growing file system


    Finished CoreStorage operation


    MacBook-Pro-de-Matheus:~ matheus$

    Then run diskutil list again to check the result.
     
  5. Wowzera thread starter macrumors 6502a

    Joined:
    Oct 14, 2008
    Location:
    Brazil
    #5
    Thanks for your help, but it didn't solve the issue. Any clue? This is driving me crazy.



    Code:
    MacBook-Pro-de-Matheus:~ matheus$ diskutil cs resizeStack F753BED7-78F3-43D4-9A8F-3920722FB6E2 0b
    
    The Core Storage Logical Volume UUID is F753BED7-78F3-43D4-9A8F-3920722FB6E2
    
    Started CoreStorage operation
    
    Checking prerequisites for resizing Logical-Physical volume stack
    
    Error: -69743: The new size must be different than the existing size
    
    MacBook-Pro-de-Matheus:~ matheus$
     

    Attached Files:

  6. Bruno09 macrumors 68020

    Joined:
    Aug 24, 2013
    Location:
    Far from here
    #6
    The command failed because of the Apple_KernelCoreDump partition : there is no "free" space available "underneath" the Recovery partition.

    Do you know why you have this partition ?
    Is your Mac a corporate machine, or did you get help from Apple assistance, or other reason ?
     
  7. Wowzera thread starter macrumors 6502a

    Joined:
    Oct 14, 2008
    Location:
    Brazil
    #7
    No, I dont know.
    My mac is a personal machine and I didnt get help from Apple or another reason.
    All I did was remove the Bootcamp Partition, but the disk space didnt return to my main drive and neither is listed as available in Disk Utility, its simple "gone".
     
  8. Bruno09, Sep 15, 2017
    Last edited: Sep 15, 2017

    Bruno09 macrumors 68020

    Joined:
    Aug 24, 2013
    Location:
    Far from here
    #8
    The command resizeStack is the right one to solve your issue, however it will only work if there is "nothing" underneath the Recovery partition.

    I think there are three ways to solve your problem :

    1. delete the Apple_KernelCoreDump partition, then use the resizeStack command

    or

    2. revert the core storage, then use Disk Utility to delete the Apple_KernelCoreDump partition and expand the Macintosh HD partition to the maximum space available.

    or

    3. clone your Macintosh HD partition to an external hard drive (Carbon Copy Cloner, 30 days free demo)
    Boot from this clone, erase your internal disk, then clone your clone to the internal drive.
    (good solution without using the Terminal)

    I am not a Terminal guru by any way, therefore I would prefer if someone else with good knowledge came to help you on this...

    Please post the output of this command : diskutil cs list
     
  9. Wowzera thread starter macrumors 6502a

    Joined:
    Oct 14, 2008
    Location:
    Brazil
    #9
    Isn't kernel core dump taking only 655MB?

    Code:
     
    MacBook-Pro-de-Matheus:~ matheus$ diskutil cs list
    
    CoreStorage logical volume groups (1 found)
    
    |
    
    +-- Logical Volume Group F03CBE82-21B5-47B4-9667-D66502836A67
    
        =========================================================
    
        Name:         Macintosh HD
    
        Status:       Online
    
        Size:         83716304896 B (83.7 GB)
    
        Free Space:   0 B (0 B)
    
        |
    
        +-< Physical Volume D5D47530-B706-4964-8F19-6419A8FB5F9B
    
        |   ----------------------------------------------------
    
        |   Index:    0
    
        |   Disk:     disk0s2
    
        |   Status:   Online
    
        |   Size:     83716304896 B (83.7 GB)
    
        |
    
        +-> Logical Volume Family FE60EDDC-D7F8-4E72-9139-2C1D389F2665
    
            ----------------------------------------------------------
    
            Encryption Type:         None
    
            |
    
            +-> Logical Volume F753BED7-78F3-43D4-9A8F-3920722FB6E2
    
                ---------------------------------------------------
    
                Disk:                  disk1
    
                Status:                Online
    
                Size (Total):          83349209088 B (83.3 GB)
    
                Revertible:            Yes (no decryption required)
    
                LV Name:               Macintosh HD
    
                Volume Name:           Macintosh HD
    
                Content Hint:          Apple_HFS
     
  10. Bruno09 macrumors 68020

    Joined:
    Aug 24, 2013
    Location:
    Far from here
    #10
    Yes, but the resizeStack command can only work if there is nothing underneath the Recovery partition in the output of the diskutil list command.

    If you want to solve the problem without using the Terminal, use the #3. option (clone, format the internal drive, clone back).
     
  11. Audit13, Sep 15, 2017
    Last edited: Sep 15, 2017

    Audit13 macrumors 601

    Audit13

    Joined:
    Apr 19, 2017
    Location:
    Toronto, Ontario, Canada
    #11
    On a PC, the windows installation process creates a recovery partition that is protected and difficult to remove. The same appears to have happened on your Mac and the simplest way to get all of the space back would be to delete all partitions and reinstall the os or restore a time machine backup.
     
  12. Wowzera thread starter macrumors 6502a

    Joined:
    Oct 14, 2008
    Location:
    Brazil
    #12
    I have no problem using terminal. But I don't know the commands. I cant remove it using Disk Utility (the core dump partition). Do you know how what I have to do?
     
  13. Bruno09 macrumors 68020

    Joined:
    Aug 24, 2013
    Location:
    Far from here
    #13
    I don't know them either.

    I personally would use the #3 solution.
     
  14. Fishrrman macrumors P6

    Fishrrman

    Joined:
    Feb 20, 2009
    #14
    OP:

    Look at choice #3 in Bruno's post 8 above.

    THIS is your answer.

    It involves a little time, but it WILL do the job and do it right.
     
  15. Wowzera thread starter macrumors 6502a

    Joined:
    Oct 14, 2008
    Location:
    Brazil
    #15
    I did the choice 3 and it solved the problem. Thanks!!
     

Share This Page

14 September 13, 2017