Link to home
Start Free TrialLog in
Avatar of nflynn85
nflynn85

asked on

Low Disk Space on Server2008R2

What's the best way to track down the culprit of what's eating up my disk space? I have two servers that are dangerously low on C: and I want to get to the bottom of this.
SOLUTION
Avatar of Lee W, MVP
Lee W, MVP
Flag of United States of America image

Link to home
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Start Free Trial
+1 for Tree Size. I use this and it is one of the best to root out space usage.
ASKER CERTIFIED SOLUTION
Link to home
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Start Free Trial
You should not muck with winsxs. On systems newer than 2008, Disk Cleanup will clean it up properly. But do not delete it on your own. Find other places to save space or you may need to provide more space.
How large is your C: drive?  How large is your Hard Drive?
Avatar of nflynn85
nflynn85

ASKER

John I don't see why you "shouldn't muck" with the winsxs, when MSFT has provided a KB for a way to resolve the issue when that particular folder is too large and needs to be cleaned up - https://support.microsoft.com/en-us/kb/2852386

Lee that particular drive is 30GB - this server is a VM in hyper-v and the drive is a .vhdx
SOLUTION
Link to home
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Start Free Trial
It is a bare bones server that does not do much :) It's a "compute" server for an application we have but doesn't need a ton of power to do what it needs to do.

The article I posted above points to disk cleanup for 2008 via an update to reduce winsxs

Thanks for the clarification
Try the article (Disk Cleanup) and see if it works.
Disk Cleanup got me about 8gigs back on the 2008 server

The other server is running Windows Server Enterprise without Hyper-V, disk cleanup didn't pick up the directories for cleanup like the previous one did.

In both instances, my predecessor configured C and D on the same disk0 so I can expand D but cannot expand C without deleting D

Any thoughts on how to proceed?
Using the WinDirStat pointed me to the real culprit - the winsxs folder.

I chose my answer as the best because not only did it outline what the real culprit was, but I also linked to how to resolve an issue when your winsxs folder is too large and needs to be cleaned up, nobody else provided that nor seemed to read it nor did they seem to know that it was possible to clean that up with an update from msft