A dirty bit set in damaged file systems (a.k.a. dirty file systems), means that the file system's state is inconsistent. For example, the dirty bit is set if there are outstanding modifications to the volume pending and the server is restarted before these modifications were saved. If a dirty bit is set, the checkdisk utility runs after each restart. In order to check and repair the file system, you must prevent checkdisk from starting automatically. After the server has been booted to rescue mode, you can then repair the file system. Proceed as follows:
You have created a backup of your server.
You have selected the desired keyboard language.
To check whether a dirty bit has been set in the file system, enter the following command in the Administrator: X:\WINDOWS\system32\cmd.exe window:
To prevent checkdisk from starting automatically during the next reboot, enter the following command:
C:\>chkntfs C: /x
Boot the server to the Windows rescue system.
Select the desired keyboard language.
Click Microsoft ® Diagnostics and Recovery.
Click Windows Server 2012 R2 or Windows Server 2016.
To check and repair the file system, enter the following command in the Administrator: X\WINDOWS\system32\cmd.exe window.
C:\>chkdsk C: /F
After repairing the file system, check whether the dirty bit was removed. If so, the following message will be displayed:
The type of the file system is NTFS.
C: is not dirty.