RE: chkdsk on a mounted disk

FWIW, 9 months later, it turns out that this would have been the cause of this problem -

Very nasty when trying to diagnose the cause of a database corruption, and whether there is a problem with the hardware, your drivers, or MSSQL, and every time you do a dbcc checkdb you suddenly find that your filesystem is also corrupt (as incorrectly reported by chkdsk!).


-----Original Message-----
From: [mailto:bounce-472719-] On Behalf Of James Harper
Sent: Wednesday, 31 August 2011 10:20 AM
To: Windows System Software Devs Interest List
Subject: [ntdev] chkdsk on a mounted disk

Is a chkdsk on a mounted disk (which I think is done on a VSS snapshot)
‘reliable’? Can it show errors that don’t exist?

I’m doing ‘chkdsk c:’ and it is coming up with errors:

C:\>chkdsk c:
The type of the file system is NTFS.
Volume label is SYSTEM.

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

CHKDSK is verifying files (stage 1 of 3)…
95744 file records processed.
File verification completed.
8559 large file records processed.
0 bad file records processed.
0 EA records processed.
6 reparse records processed.
CHKDSK is verifying indexes (stage 2 of 3)…
331279 index entries processed.
Index verification completed.

Errors found. CHKDSK cannot continue in read-only mode.

but maybe that’s not to be trusted and a chkdsk done at reboot would be


NTDEV is sponsored by OSR

For our schedule of WDF, WDM, debugging and other seminars visit:

To unsubscribe, visit the List Server section of OSR Online at