1

This question already has an answer here:

My Disk Utility is showing me some Weird Stuff.

My current startup partition is showing as 155 GB, with (I was shocked to discover) 344 GB of unpartitioned free space:

enter image description here

I can try to resize the first partition by removing the "Free space" section, then hit "Apply", but then I get this error:

enter image description here

Actually, if I try this a few times, I get variously different errors. Sometimes it even says it succeeds, but the partition size doesn't seem to have changed.

When I retry this same sequence after booting from my recovery partition, basically the same result happens, except that now I have two "Free space" partitions, both showing 344 GB, in addition to the 155 GB startup partition.

What's going on here, and how can I take advantage of my full 500 GB disk? Or do I not actually have a 500 GB disk??

Here's the Disk Utility info for the physical disk - notice that it says it's 500 GB, but the 155 GB partition takes up the whole blue bar:

enter image description here

I'm using High Sierra 10.13.6, on a Late 2011 MacBook Pro 13".

marked as duplicate by David Anderson, Nimesh Neema, Monomeeth May 20 at 4:49

This question has been asked before and already has an answer. If those answers do not fully address your question, please ask a new question.

  • Sorry, but your question/answer are over half a decade late in being posted. In other words, both your question and answer are duplicates of so may similar posts that I have stopped counting them. – David Anderson May 20 at 6:04
  • Actually I'm quite glad I didn't find that previous q/a, because the answer there is way more complicated than what I actually needed. Just reading the man page was the most helpful for me. Also, you're right, there are so many previous resizing questions that I couldn't find any relevant ones, probably because I didn't know my situation was about "core storage". – Ken Williams May 20 at 12:48
0

WELL, HOLY CRAP.

I did some digging around in the manual pages for the diskutil command-line utility. My volume was a CoreStorage Logical Volume, so I got some info on it:

$ diskutil cs list
CoreStorage logical volume groups (1 found)
|
+-- Logical Volume Group C8C10399-E3E0-4B52-A9EE-2F15AE56E992
    =========================================================
    Name:         Macintosh HD
    Status:       Online
    Size:         155701956608 B (155.7 GB)
    Free Space:   18960384 B (19.0 MB)
    |
    +-< Physical Volume 297002AD-AB9E-47CC-B31B-5B7C21BE0F7A
    |   ----------------------------------------------------
    |   Index:    0
    |   Disk:     disk0s2
    |   Status:   Online
    |   Size:     155701956608 B (155.7 GB)
    |
    +-> Logical Volume Family F134B1FE-CEC6-49F3-86E9-DF67D8530FF5
        ----------------------------------------------------------
        Encryption Type:         None
        |
        +-> Logical Volume F85FD6EB-0CF7-400E-960B-22572D96B498
            ---------------------------------------------------
            Disk:                  disk1
            Status:                Online
            Size (Total):          155330674688 B (155.3 GB)
            Revertible:            Yes (no decryption required)
            LV Name:               Macintosh HD
            Volume Name:           Macintosh HD
            Content Hint:          Apple_HFS

Then I held my breath and ran a resizeStack command, which makes everything very easy:

$ diskutil cs resizeStack F85FD6EB-0CF7-400E-960B-22572D96B498 0
The Core Storage Logical Volume UUID is F85FD6EB-0CF7-400E-960B-22572D96B498
Started CoreStorage operation
Checking prerequisites for resizing Logical-Physical volume stack
Growing Logical-Physical volume stack
Verifying file system
Volume could not be unmounted
Using live mode
Performing fsck_hfs -fn -l -x /dev/rdisk1
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
Restoring the original state found as mounted
Growing Core Storage Physical Volume from 155,701,956,608 to 499,248,103,424 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 499,248,103,424 bytes
Growing Logical Volume
Resizing Core Storage Logical Volume structures
Resized Core Storage Logical Volume to 498,876,821,504 bytes
Growing file system
Finished CoreStorage operation

Didn't even need sudo! Which is kind of strange!

Anyway, after this, my disk is now in fact a 500 GB disk:

enter image description here

This is like those dreams where you discover extra rooms in your house that you didn't know you had.

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