I have a Win2k server that sat idle for a year and then I
booted it up about a week ago. It has a 60GB HD evenly
divided into C: (NTFS) & E: (FAT32), plus a 2.5GB setup
with only system files on it (e.g., Active Directory).
It ran fine for 96 hours after startup, but then AD just
died. I can't get it back up because it says its having
problem with th AD files.
When I try to run "chkdsk /f", it aborts within a few
seconds with an "unspecified error" message. If I try to
run it with the "/I /F" option it makes it almost all the
way through its 5 phases, but it reports such errors as:
.. Insufficent space to correct errors in index $SII in
file 9
.. Insufficent space to fix security descriptor data stream
.. Insufficent space to correct attribute definition table.
Since this is a tiny 5-user system, I put all the system
files (e.g., Active Directory) on the separate, small
2.5GB drive. This drive had, and still does have, 2.1 GB
of free space left over, but "chkdsk" keeps saying it
does have enough space to fix the disk.
Does the NTFS file systems (and AD) need a larger disk?
Is there a way to tell "chkdsk" to fix the D: drive, but
use the C: drive (which has 30gb free) for its working
files?
Is there a way to expand the NTFS tables/files?
Or is my disk fried and I have to get another one (and
lose all of AD)?
Any help would be appreciated.
|
Similar Threads
