When I run the Data Integrity Scan manually within the Task Scheduler, it runs and completes immediately without doing anything even though I know there are corrupt files in the volume. The following are the event log entries. Notice that most of my files are skipped. Why doesn't the scan attempt to fix corrupted files?
Integrity is both enabled and enforced for all of the several hundred files. The ReFS storage space is a two-way mirror. Both drives are attached via SATA and the motherboard BIOS SATA Configuration is AHCI.
Information:
Started checking data integrity.
Information:
Disk scan started on \\?\PhysicalDrive9 (\\?\Disk{ecb98218-784e-47d5-b316-941ae9595eb4})
Error:
Volume metadata scrub operation failed.
Volume name: I:
Metadata reference: 0x204
Range offset: 0x0
Range length (in bytes): 0x0
Bytes repaired: 0x0
Bytes not repaired: 0x3000
Status: The specified copy of the requested data could not be read.
Error:
Files were skipped during the volume scan.
Files skipped: 310
Volume name: I:\ (\??\Volume{53d99c4e-9ad6-11e8-8448-0cc47ad896dd}\)
First skipped file name: I:
HResult: The specified copy of the requested data could not be read.
Information:
Volume scan completed on I:\ (\??\Volume{53d99c4e-9ad6-11e8-8448-0cc47ad896dd}\)
Bytes repaired: 0x0
Bytes not repaired: 0x3000
HResult: The operation completed successfully.
Information:
Disk scan completed on \\?\PhysicalDrive9 (\\?\Disk{ecb98218-784e-47d5-b316-941ae9595eb4})
Information:
Completed data integrity check.