Hi Shalika,

Do you see any events in the Application Event Log for those Volumes on the MA Server?

Have you run chkdsk on the Mountpoints for these Mount Paths? - You can get the Volume guid from mountvol, then run a chkdsk against that volume GUID.

Regards,

Michael

Hi MichaelCapon,

I’m checking on that.

Regards,

Shalika

If NTFS detects issues with the file system it turns on the “dirty” bit which forces a check disk operation next reboot. Commvault detects this as we don’t want to write to a potentially damaged volume and unknowingly put data at risk. You can see more info about the dirty bit and how to turn it ‘off’ here: https://docs.microsoft.com/en-us/windows-server/administration/windows-commands/fsutil-dirty

• A volume's dirty bit indicates that the file system may be in an inconsistent state. The dirty bit can be set because:

  • The volume is online and it has outstanding changes.

  • Changes were made to the volume and the computer was shut down before the changes were committed to the disk.

  • Corruption was detected on the volume.

• If the dirty bit is set when the computer restarts, chkdsk runs to verify the file system integrity and to attempt to fix any issues with the volume.

description: Export / Mount failed for mount path [K:/E29HAA_04.16.2022_09.11/CV_MAGNETIC], please check if the mount path is accessible on Data Server [MHSDC-BKP-SRV3.MAHAGOV.LOCAL]. Check the logs for detailed error. what does it mean

@101c3e , log into MHSDC-BKP-SRV3.MAHAGOV.LOCAL and confirm that K:/E29HAA_04.16.2022_09.11/CV_MAGNETIC is accessible.  the error indicates it is not (or was not at the time of the error).