2008 R2 HD space missing

Discussion in 'Windows Server' started by Curtis Vaughan, Aug 13, 2013.

  1. Remote Desktop users noted that the D: drive on a 2008 R2 server had only around 5 GB left. But that HD has about 250 GB of space. After having gone through checking all the directories (including hidden ones) all files take up only about 30-40 GB. So where are the other 200+ GB?

    I noted on another forum that someone found Semantec as the problem. But we're using Security Essentials.

    Here's the output of CHKDSK:

    The type of the file system is NTFS.
    Volume label is DATAPART1.

    WARNING! F parameter not specified.
    Running CHKDSK in read-only mode.

    CHKDSK is verifying files (stage 1 of 3)...
    18176 file records processed.
    File verification completed.
    3 large file records processed.
    0 bad file records processed.
    0 EA records processed.
    80 reparse records processed.
    CHKDSK is verifying indexes (stage 2 of 3)...
    24692 index entries processed.
    Index verification completed.
    0 unindexed files scanned.
    0 unindexed files recovered.
    CHKDSK is verifying security descriptors (stage 3 of 3)...
    18176 file SDs/SIDs processed.
    Security descriptor verification completed.
    3258 data files processed.
    Windows has checked the file system and found no problems.

    247289855 KB total disk space.
    241916156 KB in 10647 files.
    5292 KB in 3260 indexes.
    0 KB in bad sectors.
    91715 KB in use by the system.
    65536 KB occupied by the log file.
    5276692 KB available on disk.

    4096 bytes in each allocation unit.
    61822463 total allocation units on disk.
    1319173 allocation units available on disk.
    Curtis Vaughan, Aug 13, 2013
    1. Advertisements

  2. Ok, using a utility called TreeSize Free, I determined that about 200 GB are being stored in the System Volume Information folder.
    I am using the built-in backup tool to backup to a dedicated G: drive.
    Full VSS is on.

    But why is it taking up so much room on the D: drive? And how do I get rid of it?
    Curtis Vaughan, Aug 13, 2013
    1. Advertisements

  3. OK, issuing a command something like vssadmin and basically resizing the shadow copy to not exceed 10 GB worked. Is there any reason I should not have done that? Or should consider a different size?
    Curtis Vaughan, Aug 13, 2013
    1. Advertisements

Ask a Question

Want to reply to this thread or ask your own question?

You'll need to choose a username for the site, which only take a couple of moments (here). After that, you can post your question and our members will help you out.