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

Artimus12

macrumors 6502a
Original poster
Nov 13, 2011
539
114
YooKay
After I updated from 10.10 to 10.10.1 (which I didn't have any issues with) I noticed my 512GB SSD took a huge hit and I somehow lost over 130GB of free space. I read earlier on here that someone had noticed a similar loss of space and they'd recovered it with a clean install instead of an update.

I decided to try it myself and it worked! I've gone from 320+ GB after the update, to 165GB after the format and clean install w\ TM recovery for settings and documents ...Apps were redownloaded from the App Store.

I just wondered if anyone else has found the Yosemite update has robbed them of space? Any thoughts on why?
 

iamMacPerson

macrumors 68040
Jun 12, 2011
3,488
1,927
AZ/10.0.1.1
Upgraded my rMBP (late-2013) and Mac Pro (2009) from 10.10 to 10.10.1 with no issue. To anyone else with this issue, I'd try running an app like DaisyDisk and see what's clogging up that space. Just a question, are you going by what Disk Utility or Finder says, or by the "About this Mac" dialog? The ATM dialog seems to be horribly inaccurate until Spotlight indexes.
 

Artimus12

macrumors 6502a
Original poster
Nov 13, 2011
539
114
YooKay
Another "I gained 130+Gb SSD space after clean install" thread

I used the built in disk utility to read the partition.

In the thread I read earlier the poster said they'd searched with different 3rd party utilities to find the root of the issue, but that it was listed as "other" and they could find no files of that size on disk, so they resorted to a clean install.

Can't find the thread right now, but will look in my browser history when I get back to the Mac.
 
Last edited:

Weaselboy

Moderator
Staff member
Jan 23, 2005
34,477
16,187
California
I used the built in disk utility to read the partition.

In the thread I read earlier the poster said they'd searched with different 3rd party utilities to find the root of the issue, but that it was listed as "other" and they could find no files of that size on disk, so they resorted to a clean install.

Can't find the thread right now, but will look in my browser history when I get back to the Mac.

I participated in that same thread, and gave the OP a Terminal command to get to the bottom of it, but unfortunately they wiped and reinstalled without running the commands to trouble shoot, so we will never know. Tough to do anything after the wipe.

Those apps mentioned don't show many system and hidden files, so are not of much use with issues like this.

Code:
sudo du -d 1 -x -c -g /

The command I mentioned is above. It will show you all base folders and size of each in GB, and it will include all system and hidden folders.
 

Artimus12

macrumors 6502a
Original poster
Nov 13, 2011
539
114
YooKay
I participated in that same thread, and gave the OP a Terminal command to get to the bottom of it, but unfortunately they wiped and reinstalled without running the commands to trouble shoot, so we will never know. Tough to do anything after the wipe.

Those apps mentioned don't show many system and hidden files, so are not of much use with issues like this.

Code:
sudo du -d 1 -x -c -g /

The command I mentioned is above. It will show you all base folders and size of each in GB, and it will include all system and hidden folders.
Thanks! If the same happens again - 10.10.2 maybe -I'll try that and post back here.

P.S: never did find that other thread again.
 
Register on MacRumors! This sidebar will go away, and you'll see fewer ads.