Kbase P104938: chkdsk reports "unallocated cluster" errors on NTFS file system
| Autor |
Progress Software Corporation - Progress |
| Acesso |
Público |
| Publicação |
29/01/2009 |
|
Status: Verified
SYMPTOM(s):
chkdsk reports "unallocated cluster" errors on NTFS file system
chkdsk terminates with errors
chkdsk run while database in use
FACT(s) (Environment):
Windows
Progress 9.x
OpenEdge 10.x
CAUSE:
chkdsk is run in read-only mode if the volumes aren't locked. Microsoft Knowledge Base Article Q314835 says:
? In read-only mode, CHKDSK quits before it completes all three phases if it encounters errors in earlier phases, and CHKDSK is prone to falsely reporting errors. For example, CHKDSK may report disk corruption if NTFS happens to modify areas of a disk while CHKDSK is examining the disk. For correct verification, a volume must be static, and the only way to guarantee a static state is to lock the volume. CHKDSK locks the volume only if you specify the /F switch (or the /R switch, which implies /F). You may need to run CHKDSK more than once to get CHKDSK to complete all its passes in read-only mode.
FIX:
Run "chkdsk /f" or "chkdsk /r". This means chkdsk will be run in safe-mode, with locked volumes, after the next reboot.