I have an urgent problem on a Windows Server 2003 Domain Controller
(Production Server).
The server has four seperate NTFS Partitions in this layout:
C - (NTFS) - System Volume
X - (NTFS + Compression) - File Server
Y - (NTFS + Compression) - Personal Storage
Z - (NTFS) - Network Database
Recently, Z Drive was getting a bit short of space, so as a short term
solution I enabled Compression on the Volume. The compression went fairly
smoothly with only one hitch. McAfee Enterprise VirusScan through up a
warning of a possible 'unwanted program' (the program in question was a mIRC
Plugin Installer a seperate administrator put on the drive for temporary
storage). This resulted in this single executable not being compressed but
the rest of the volume was compressed successfully. However, a serious
problem manifested itself.
In Windows Explorer the 'Total Size' and 'Free Space' of ALL four partitions
is entirely inaccurate. Drive C is listed as having 100MB Total Size (in fact
10GB) and 0 bytes Free Space (in fact 3.5GB). Drive's X Y Z all have similar
inacurate values ranging from 100 to 1GB Total Size and 0 to 99MB Free Space.
This is as you can imagine wreaking havoc with the system applications but
the server still boots fine! However, a look at the Disk Management snap-in
for MMC shows the correct Drive Capacity and Free Space. The Disk
Defragmenter snap-in for MMC shows the incorrect Drive Capacity but the
correct Free Space!! If I right-click on a partition - hardware tab - and
check the properties of the device driver for the hard-disk and choose to
display volumes - i also get the correct information.
I completed a chkdsk on all volumes (and a vrfydsk before that) and chkdsk
reports no errors and returns the correct total capacity and free space in
the summary. I am at a total loss as to how to correct this problem and how
compressing a drive could wreak so much havoc (i am having a lot of badluck
this week). The server is a production machine with a lot of important data
and a reinstall is NOT an option. Thank-you for any and all correspondence in
advance addressing this maddening problem.
Yours hopefully,
Ralish