Menu

VC1.23 - How can I repair file systems?

2018-11-19
2018-11-19
  • Johannes Franke

    Johannes Franke - 2018-11-19

    Hi all,

    for some weeks, I am getting a message after the desktop loaded (all authentication passed). It's in German and rather long, but the essence is that one of the volumes may contain errors which may cause data loss, and I should repair the file system. The message can be confirmed with OK only, there is no way to dismiss it so it does not come back - and I would like to drill down to the reason that triggers this message rather than just ignore the problem.
    I ran chkdsk at the next boot time and it didn't find anything to correct. Took eternities however. In VeraCrypt's main window, I cannot find any option to repair a file system for a mounted volume. No menus, including the right-click context menu, are giving me any option that is even close to checking or repairing the selected volume.
    What am I missing?

    Thank you!

    Regards
    Joe

     
  • Johannes Franke

    Johannes Franke - 2018-11-19

    Found more info in the Application event log about the problem, a new entry of this type is added on each boot:

    Type: Error
    Event ID: 1
    Source: VeraCryptSystemFavorites
    Text: The filesystem of the volume mounted as F: was not cleanly dismounted and needs to be checked for errors.

    F: is a volume where virtual disk files for VMware are stored. It's a rather large partition of ~750GB on a Toshiba SATA SSD.
    Windows 7 System Maintenance just recommends me to check volumes for errors and will queue up another chkdsk for the next restart. Well, probably it won't solve it. My perception is that the volume stays tagged for having errors.
    So far, I did not experience any data loss or virtual machines that would no longer boot due to defective configuration or disk files.

     
  • Johannes Franke

    Johannes Franke - 2018-11-19

    Ok, consider it resolved. The F: drive reference in the event log was the final clue. Previous "chkdsk on startup" actions obiously verified only the system partition, not the others. Now that I have explicitly told chkdsk to verify and fix the F: partition, the message is gone.

     

Log in to post a comment.

MongoDB Logo MongoDB