I am just replying to poke CG into coming and correcting me. (S).
anything in the event logs?
chkdsk /f reported no problems?
MS sez many things can cause this, here is an excerpt from the article
How to Locate and Correct Disk Space Problems on NTFS Volumes
http://support.microsoft.com/kb/814594/en-us
This article discusses how to check an NTFS file system's disk space allocation to discover offending files and folders or look for volume corruption in Windows Server 2003-based computers.
NTFS supports many volume and file-level features that may lead to what appear to be lost or incorrectly reported free disk space. For example, an NTFS volume may suddenly appear to become very full for no reason, and an administrator cannot find the cause or locate the offending folders and files. This may occur if malicious or unauthorized access to an NTFS volume where very large files or a high quantity of small files are secretly copied has occurred. These files then have their NTFS permissions removed or restricted. This behavior may also occur after a computer malfunction or power outage occurs that cause volume corruption.
The disk space allocation of an NTFS volume may appear to be misreported for any of the following reasons: ? The NTFS volume's cluster size is too large for the average-sized files that are stored there.
? File attributes or NTFS permissions prevent Windows Explorer or a Windows command prompt from displaying or accessing files or folders.
? The folder path exceeds 255 characters.
? Folders or files contain invalid or reserved file names.
? NTFS metafiles (such as the Master File Table) have grown, and you cannot de-allocate them.
? Files or folders contain alternate data streams.
? NTFS corruption causes free space to be reported as in use.
? Other NTFS features may cause file-allocation confusion.
can you dupe this drive in another box?
no raid?