Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.

setul34

macrumors newbie
Original poster
May 28, 2020
6
2
Hello,

I feel like i'm missing about 200gb space on my macbook pro. Not sure if im correct or not.

This is what i got when i entered "diskutil list" in Terminal. To be honest i don't know whats going on here so i'm not exactly sure what im missing.
Code:
/dev/disk0 (internal, physical):
   #:                       TYPE NAME                    SIZE       IDENTIFIER
   0:      GUID_partition_scheme                        *500.1 GB   disk0
   1:                        EFI EFI                     209.7 MB   disk0s1
   2:                 Apple_APFS Container disk1         249.0 GB   disk0s2
   3:       Microsoft Basic Data                         50.0 GB    disk0s3

/dev/disk1 (synthesized):
   #:                       TYPE NAME                    SIZE       IDENTIFIER
   0:      APFS Container Scheme -                      +249.0 GB   disk1
                                 Physical Store disk0s2
   1:                APFS Volume Macintosh HD - Data     205.6 GB   disk1s1
   2:                APFS Volume Preboot                 58.1 MB    disk1s2
   3:                APFS Volume Recovery                1.0 GB     disk1s3
   4:                APFS Volume VM                      8.6 GB     disk1s4
   5:                APFS Volume Macintosh HD            11.1 GB    disk1s5


After checking Disk Utility. I noticed Main HDD says 500GB on the right hand side. And when i click on Container disk 1, it says 249GB on the right hand side. (Pictures below)


Screen Shot 2020-05-28 at 7.17.19 PM.png
Screen Shot 2020-05-28 at 7.17.03 PM.png


I was still confused, so i check DaisyDisk. And DaisyDisk was only able to find 249GB even with the full disk access (Picture below)


Screen Shot 2020-05-28 at 7.20.38 PM.png


So, now i really don't know whats going on, Search allover to see if i can get a hint. But still not luck. Can anyone help me?
 

Taz Mangus

macrumors 604
Mar 10, 2011
7,815
3,504
Boot into recovery mode (CMD-R) and run First Aid on the drive. See what that returns.
[automerge]1590724704[/automerge]
I would suggest doing a SMC reset as well. I have seen strange things with Disk Utility and a SMC reset seemed to fix it.

 
Last edited:
  • Like
Reactions: setul34

setul34

macrumors newbie
Original poster
May 28, 2020
6
2
Boot into recovery mode (CMD-R) and run First Aid on the drive. See what that returns.
[automerge]1590724704[/automerge]
I would suggest doing a SMC reset as well. I have seen strong things with Disk Utility and a SMC reset seemed to fix it.


Failed, same result on both.

Edit: when i run first aid on main apple HDD, it says operation successful

Edit 2: i'll try that SMC reset.
IMG_20200528_225933.jpg
 

Taz Mangus

macrumors 604
Mar 10, 2011
7,815
3,504
Make sure to restart the computer while pressing Command-R to get into recovery mode. Then execute the First Aid from Disk Utility while in recovery mode.
 
  • Like
Reactions: setul34

setul34

macrumors newbie
Original poster
May 28, 2020
6
2
Make sure to restart the computer while pressing Command-R to get into recovery mode. Then execute the First Aid from Disk Utility while in recovery mode.

Yes that's what i did. I was in macOS recovery to perform first aid. And i got that error above
[automerge]1590725515[/automerge]
After SMC reset, still same.
 

gilby101

macrumors 68030
Mar 17, 2010
2,952
1,635
Tasmania
However it happened (I assume something to do with how you created the Microsoft Basic Data partition), the good news is that your macOS is still working. It might easily not be with your non standard partition scheme.

I would also ask, why have a partition for VMware?

I suspect the only fix will be:
1. Backup your macOS and whatever is important from the 50 GB partition.
2. Boot into recovery mode, erase the whole disk (making sure that APFS file system is the full 500 GB) and reinstall macOS.
3. Restore your macOS apps, settings and data from your backup.
4. Create a new VMware virtual machine in your macOS file system and restore its data from backup.
5. Don't create extra partitions on your macOS boot disk unless you really know what you are doing, and accept the risks.
 
Last edited:

setul34

macrumors newbie
Original poster
May 28, 2020
6
2
Restart computer while pressing the D-key. Now run diagnostics and see what it returns.

After trying internet recovery it says No issue found. And im using mid 2012 macbook pro 13 in.
[automerge]1590799359[/automerge]
However it happened (I assume something to do with how you created the Microsoft Basic Data partition), the good news is that your macOS is still working. It might easily not be with your non standard partition scheme.

I would also ask, why have a partition for VMware?

I suspect the only fix will be:
1. Backup your macOS and whatever is important from the 50 GB partition.
2. Boot into recovery mode, erase the whole disk (making sure that APFS file system is the full 500 GB) and reinstall macOS.
3. Restore your macOS apps, settings and data from your backup.
4. Create a new VMware virtual machine in your macOS file system and restore its data from backup.
5. Don't create extra partitions on your macOS boot disk unless you really know what you are doing, and accept the risks.

Im planning to clean install the macos after backing up. It's just i wasn't sure if im missing the partition or not.
 

setul34

macrumors newbie
Original poster
May 28, 2020
6
2
I think your partition table is corrupt in some way (which I don't understand) so that the other 256GB is 'lost'. Just lucky that macOS will still boot!

So i erased the 2 partition and still it showed me 249gb is the only space i had. And after that i erased the whole drive. Beside macos installation. And it recovered all 500gb. And everything is good now after reinstalling.
[automerge]1590852670[/automerge]
Thank you for all your help @gilby101 @Taz Mangus
 
Register on MacRumors! This sidebar will go away, and you'll see fewer ads.