chkdsk.exe

Check Disk - check and repair disk problems

Syntax
      CHKDSK [drive:][[path]filename] [/F] [/V] [/R] [/L[:size]] 

Key
   [drive:]   Specify the drive to check. 
   
   filename   Specify the file(s) to check for fragmentation (FAT only). 
   
   /F         Automatically Fix file system errors on the disk.

   /X         Fix file system errors on the disk, (Win2003 and above)
              dismounts the volume first, closing all open file handles.
   
   /R         Scan for and attempt Recovery of bad sectors.
   
   /V         Display the full path and name of every file on the disk. 
   
   /L:size    NTFS only: change the log file size to the specified number of kilobytes. 
              If size is not specified, displays the current log size and the drive type
              (FAT or NTFS).

   /C         Skip directory corruption checks. 

   /I         Skip corruption checks that compare directory entries to the
              file record segment (FRS) in the volume's master file table (MFT)

For example:

CHKDSK c: /F

Fixing Errors /F

If the drive is the boot partition, you will be prompted to run the check during the next boot

To issue chkdsk on a hard drive you must be a member of the Administrators group.

If you specify the /f switch, chkdsk will show an error if open files are found on the disk.

Chkdsk /f will lock the volume, making data unavailable until chkdsk is finished.

If you use chkdsk /f on a very large disk or a disk with a very large number of files (millions), chkdsk may take a long time to complete. The computer will not be available during this time, as chkdsk does not relinquish control until it is done.

Scan only (without /f switch)

If a file needs to be fixed chkdsk will alert you with a message but will not fix the error(s).

chkdsk may report lost allocation units on the disk - it will produce this report even if the files are in-use (open). If corruption is found, consider closing all files and repairing the disk with /F.

Running chkdsk on a data volume that is in use by another program or process may incorrectly report errors when none are present. To avoid this, close all programs or processes that have open handles to the volume.

As a rule, run chkdsk only on volumes that are known to be corrupt.

On computers running Windows 2003 SP1, chkdsk automatically creates a shadow copy, so you can check volumes that are 'in use' by another program or process. This enables an accurate report against a live file server. On earlier versions of Windows, chkdsk would always lock the volume, making data unavailable.

Run at Bootup

Use the chkntfs or the FSUTIL dirty commands to set or query the volume's dirty bit (indicating corruption) so that Windows runs chkdsk when the computer is restarted.
On volumes marked as "dirty," Windows automatically runs chkdsk when the computer is restarted. Prior to Win2003 SP1, running at bootup is often the easiest way to close all open file handles.

Event Logs

Chkdsk will log error messages in the Event Viewer - System Log.
Chkdsk /f removes ACLs that are no longer used and reports this in the Event Viewer - Application Log.

Cluster (or block) Size

CHKDSK produces a report that shows the the block /cluster size
typically: "4096 bytes in each allocation unit."
When the cluster size is greater than 4 KB on an NTFS volume, none of the NTFS compression functions are available.

Exit codes

0 No errors were found
1 Errors were found and fixed.
2 Could not check the disk, did not or could not fix errors.

Notes:
Consider the time required to run Chkdsk to repair any errors that occur. Chkdsk times are determined by the number of files on the volume and by the number of files in the largest folder. Chkdsk performance under Windows 2003 is around 30% faster than previous versions.

When CHKDSK is set to run at boot-up there is a delay to allow the check to be cancelled - this can be configured in the registry:

HKLM\System\CurrentControlSet\Control\Session Manager
REG_DWORD:AutoChkTimeOutData
The value is the time in seconds that you want CHKDSK to wait (0 = no delay) default is 10 seconds.

The file system structure on the disk is corrupt and unusable.

If you have disk corruption, run the drive manufacturers diagnostics:
fujitsu | ibm | maxtor | seagate | western digital

Also: memtest.org and ubcd.sourceforge.net

Chkdsk is also available from the Recovery Console (with different parameters.)

"I either want less corruption, or more chance to participate in it" - Ashleigh Brilliant

Related commands:

CHKNTFS - schedule CHKDSK to run at boot time.
FSUTIL dirty query C: - Is the drive dirty
Cleanmgr.exe - Windows 2000 disk cleanup
Q187941 - New /C and /I Switches
Q283340 - Windows XP does not detect corruption
Q303079 - Locate and correct NTFS problems.
Q310747 - System File Checker (Sfc.exe)
Q327009 - Chkdsk Finds Incorrect Security IDs
Q329394 - Long Delays Occur When You Run Chkdsk.exe
Q873437 - Windows 2000 incorrectly identifies security descriptors
JSIFAQ - Cleaning unused security descriptors

Equivalent Linux BASH commands:

cksum - Print CRC checksum and byte counts
fsck - filesystem consistency check and interactive repair