1

I have my SSD partitioned into two 128 GB disks. I was managing my disk space and decided to shrink one of my partitions (the one with Mavericks) because it had more free disk space, in order to transfer this space into my main drive (the one with El Capitan).

As I couldn't just transfer space from Mavericks to El Capitan I shrank my Mavericks partition, but then my total disk space was reduced. I did everything I could without success.

Macbook Pro Retina Late 2013 13" (256 GB SSD)

Thanks!

enter image description here

M. Pater
  • 65

1 Answers1

0

Try this:

  1. Reboot Into recoverymode
  2. Select disk utility
  3. First try to use first aid on your drive
  4. And then use first aid on each partition.
Harcker
  • 2,734
  • Already tried it, but it says that everything's ok. – M. Pater Oct 17 '16 at 01:23
  • Can't edit last comment.

    I also tried this solution without success.

    http://apple.stackexchange.com/questions/148473/reclaim-delete-freespace-partition-after-yosemite-removal

    Thanks btw!

     – M. Pater Oct 17 '16 at 01:25
  • 1
    Try to create a new partition by splitting up one, did you do step 3? Do you have a Time Machine backup? – Harcker Oct 17 '16 at 05:32
  • I don't think that it'll work, and I may end up losing more disk space. I do have a Time Machine backup, maybe I should do a clean Sierra install. – M. Pater Oct 18 '16 at 04:05
  • I read that what you're telling me to do may work, some people said that they just splitted one partition and the new partition became bigger (letting them use all their disk space). Do you recommend me to do this on Recovery Mode? – M. Pater Oct 21 '16 at 13:50
  • Yeah, do it in recovery mode, backup before you start! – Harcker Oct 21 '16 at 13:53
  • After losing almost all my space on my main disk, I entered on my Mavericks partition and resized my disks. The one with Mavericks finally could be resized to half my SSD, and the one with El Capitan couldn't be resized to half my SSD, BUT it could be to almost (I left 0.5 GB). I can't say that it's solved, but almost. Thanks for your help! – M. Pater Oct 22 '16 at 00:05
  • The .5 is because of corestorage – Harcker Oct 22 '16 at 06:21