V
VincentRob
I have Windows 10 Pro for Workstation installed with an REFS volume that uses 2x 10TB disk in a mirror configuration. I have also enabled the file integrity feature using "Set-FileIntegrity D:\ -Enable $True" in PowerShell. I can run "PS C:\> Get-FileIntegrity 'D:\'" to confirm that file integrity is working. I can also run a the Crystal Disk Benchmark and I can tell that file integrity is enabled, because the performance is different. So up to now everything is find as I want it.
The problem comes what I want to scrub the disk (which is configured by default by windows to run every 4 weeks using a schedule tasked) the scrub fails and I get the following two Windows Events
Event 57, DataIntegrityScan
Volume metadata scrub operation failed.
Volume name: D:
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.
Event 24, DataIntegrityScan
Files were skipped during the volume scan.
Files skipped: 134489
Volume name: D:\ (\??\Volume{4279e221-4b3b-11e8-9c70-5404a6b9b8a6}\)
First skipped file name: D:
HResult: The specified copy of the requested data could not be read.
Also, if I start a PowerShell in administrator and type test the repair command I get the following:
PS C:\WINDOWS\system32> Repair-FileIntegrity -FileName 'D:test.txt'
Repair-FileIntegrity : The specified copy of the requested data could not be read.
At line:1 char:1
+ Repair-FileIntegrity -FileName 'D:test.txt'
+ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+ CategoryInfo : NotSpecified: (MSFT_FileIntegrity:ROOT/Microsoft/...T_FileIntegrity) [Repair-FileIntegrity], CimException
+ FullyQualifiedErrorId : HRESULT 0x80070151,Repair-FileIntegrity
PS C:\WINDOWS\system32>
On a final note, the scrub and the repair-fileintegrity command works on Windows Server 2016 without a problem, but not on Windows 10 pro for Workstation.
Does anyone know why? Thank you.
Continue reading...
The problem comes what I want to scrub the disk (which is configured by default by windows to run every 4 weeks using a schedule tasked) the scrub fails and I get the following two Windows Events
Event 57, DataIntegrityScan
Volume metadata scrub operation failed.
Volume name: D:
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.
Event 24, DataIntegrityScan
Files were skipped during the volume scan.
Files skipped: 134489
Volume name: D:\ (\??\Volume{4279e221-4b3b-11e8-9c70-5404a6b9b8a6}\)
First skipped file name: D:
HResult: The specified copy of the requested data could not be read.
Also, if I start a PowerShell in administrator and type test the repair command I get the following:
PS C:\WINDOWS\system32> Repair-FileIntegrity -FileName 'D:test.txt'
Repair-FileIntegrity : The specified copy of the requested data could not be read.
At line:1 char:1
+ Repair-FileIntegrity -FileName 'D:test.txt'
+ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+ CategoryInfo : NotSpecified: (MSFT_FileIntegrity:ROOT/Microsoft/...T_FileIntegrity) [Repair-FileIntegrity], CimException
+ FullyQualifiedErrorId : HRESULT 0x80070151,Repair-FileIntegrity
PS C:\WINDOWS\system32>
On a final note, the scrub and the repair-fileintegrity command works on Windows Server 2016 without a problem, but not on Windows 10 pro for Workstation.
Does anyone know why? Thank you.
Continue reading...