• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 1418
  • Last Modified:

SBS 2008 C: Drive Inexplicably Full

I have an SBS 2008 installation with a full C: drive.  The funny thing is that if I show hidden files/folders, highlight all contents of the C: drive and click properties, less than 40GB is shown as the size.  There seems to be something taking up storage somewhere...

I run an 80GB SSD for the OS, and have a 1TB RAID 1 for file storage. I was able to get some extra space for the moment by running the compcln.exe program to reduce the size of the winsxs file, but that only freed up 1.5 GB.

I run AVG av, I do not use sharepoint (it is installed though), and I do not use this server for email.  It is used primarily as a domain controller and server for Quickbooks point of sale.
0
Creeksidetech
Asked:
Creeksidetech
  • 7
  • 3
1 Solution
 
CreeksidetechAuthor Commented:
As an update, I am watching the free space get smaller pretty quickly, and cannot determine what files are growing...
0
 
CreeksidetechAuthor Commented:
I temporarily disabled AVG antivirus, and the space free keeps falling.  I am down to 1.19GB from 1.6GB free 30 minutes ago.
0
 
CreeksidetechAuthor Commented:
Another update - I installed Treesize, and it finds that the inetpub folder is HUGE (almost 30GB), but when I navigate to it in explorer, and click properties it is less than 1MB.  This might be my issue, but how do I fix it?
0
Concerto's Cloud Advisory Services

Want to avoid the missteps to gaining all the benefits of the cloud? Learn more about the different assessment options from our Cloud Advisory team.

 
CreeksidetechAuthor Commented:
I found that the reason behind not being able to see the size of the folder contents - it has to do with security settings.  In order to see the size, I had to open the folder first, and got the message that I would have to open with admin privileges.  After that, I was able to see the contents, and confirm that one log folder had over 28GB of logs.  I deleted all but the last one to fix my space problem.  Now, I need to figure out what causes this huge log file size.
0
 
David BrennanSenior Integration EngineerCommented:
Have you tried running CHKDSK C: /f      from the command prompt ?
sometimes this fixes incorrectly reported free space. It may require a reboot to lock the drive.

0
 
CreeksidetechAuthor Commented:
I have not tried that, but the overall free space was being reported correctly.  The problem with selecting several folders and right-click/properties, is that it apparently doesn't "run as administrator", so there could be files it isn't seeing.  I found this to be the case because I used Treesize (and ran as admin), and it found my inetpup folder was huge (30GB), although right-click/properties of inetpup was under 1MB.  If I drilled down into the folder inetpub/logs/logfiles, there were 5 folders.  Upon double-clicking those folders, the message "You don't currently have permission to access this folder, click Continue to get access" popped up.

Only then would right-click properties return the proper size for that particular folder.  I found huge log files under one of the folders, W3SVC1372222313 - that was the source of my space problem on C:.  

I still need to determine why the log files are so big...
0
 
David BrennanSenior Integration EngineerCommented:
Are the security permissions on the folder(s) set to include your own username or whatever username you're using (with full control)? I'm pretty sure that if you set the permissions correctly on the folder(s) that should help. or am I assuming too much here?
0
 
CreeksidetechAuthor Commented:
Well, the problem really was just finding what was taking up so much space on the server.  Using the standard right-click/properties method can no longer be deemed reliable in Server 2008 apparently because of a built in security block that keeps the data from being queried unless the user has confirmed administrator rights.  I want to clarify that I WAS logged in as the one and only administrator, but this is one of those new barriers that Windows uses.

The way that I found that issue was using a third party program, Treesize.  Treesize prompted me to run as admin, and it used those rights to look at the actual folder sizes.  That is when I found the inetpub log file discrepancy - Treesize said 30GB, right-click/properties said less than 1MB.
0
 
David BrennanSenior Integration EngineerCommented:
I'm glad you got it figured out. Just a note - Windirstat is another great alternative to Treesize.
0
 
CreeksidetechAuthor Commented:
After some stressful fast research, I was able to find my own solution.  Hopefully, someone else can benefit from this post.
0

Featured Post

Technology Partners: We Want Your Opinion!

We value your feedback.

Take our survey and automatically be enter to win anyone of the following:
Yeti Cooler, Amazon eGift Card, and Movie eGift Card!

  • 7
  • 3
Tackle projects and never again get stuck behind a technical roadblock.
Join Now