A file system on volume needs repair

Viakoo says my files system is dirty. How do I fix it?

This means that something prevented a portion of in-memory state to not completely make it to the disk. For example, if there was a hard shutdown in the past and the system didn't have time to flush buffers to their appropriate drives. The most common cause of a dirty file system is a power failure. The second most common reason is communication to the drive volume was interrupted during a data write.

You will see this in the server's "Details" tab. The "Volumes" table will have an "Issues Detected" warning and rows associated with any of the storage partitions (for example, the "F:" drive) will have the following indicators:

The associated drive will have an ELEVATED status flag:


And the "Dirty Bit" field will be marked "Dirty" instead of "Not Dirty" or "n-a" (no data available). In the above example, the row for the "F:" drive would look like the following:


This means that the OS has determined your file system on the volume has errors it cannot fix on its own without administrator intervention.

To fix this issue, you need to go to your local machine, and perform the following from the Administrator account:

In Windows, run a process called check disk ("chkdsk"). In Linux the repair is done with a process called file system check ("fsck") on the associated drive.

  • To run a volume file system repair in windows you need to open an elevated command prompt and type the command: chkdsk [drive] /f
  • To run a partition file system repair in Linux or Mac OS you need to enter the follow command into the local console: fsck /dev/[drive]

In the above example, you need to run "chkdsk" on the "F:" drive. Therefore, you need to type following in the Windows console window:

C:\> chkdsk F: /f

If you do not understand how these features work in your server you may contact your onsite IT administrator or your Viakoo technical support for further information.


Have more questions? Submit a request


Powered by Zendesk