Note
Access to this page requires authorization. You can try signing in or changing directories.
Access to this page requires authorization. You can try changing directories.
Question
Thursday, September 20, 2018 4:27 PM
I was looking through the event logs and discovered that Data Deduplication had been disable and it had found 2 corruptions. The file that it mentioned is not important and I can restore that file from backup.
How do I clear the deduplication error so I can re-enable Data Deduplication?
I have already ran a deep scrub full and that did not fix the corruption. I have also run check disk and no errors were found. This is an 8 TB share that has 5 TB of data deduplicated. I do not have the extra storage capacity laying around to copy all of the data off of the volume to reformat it, I would have to purchase additional hardware.
Log Name: Microsoft-Windows-Deduplication/Scrubbing
Source: Microsoft-Windows-Deduplication
Date: 9/1/2018 4:28:53 AM
Event ID: 12805
Task Category: Data Deduplication Scrubbing Task
Level: Error
Keywords: Reporting
User: SYSTEM
Computer: <hostname>
Description:
Data Deduplication service found 2 corruption(s) on volume D:\ 0 corruption(s) are fixed. 1 user file(s) are corrupted. 0 user file(s) are fixed. For the corrupted file list, see the Microsoft/Windows/Deduplication/Scrubbing events.
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
<System>
<Provider Name="Microsoft-Windows-Deduplication" Guid="{F9FE3908-44B8-48D9-9A32-5A763FF5ED79}" />
<EventID>12805</EventID>
<Version>0</Version>
<Level>2</Level>
<Task>3</Task>
<Opcode>0</Opcode>
<Keywords>0x4000000000000001</Keywords>
<TimeCreated SystemTime="2018-09-01T11:28:53.198851800Z" />
<EventRecordID>394</EventRecordID>
<Correlation />
<Execution ProcessID="11964" ThreadID="5396" />
<Channel>Microsoft-Windows-Deduplication/Scrubbing</Channel>
<Computer><hostname></Computer>
<Security UserID=<userid> />
</System>
<EventData>
<Data Name="JobInstanceId">{0055960B-DF10-42FD-BA48-79DF66BA5592}</Data>
<Data Name="VolumeGuidPath">\?\Volume{6db5369a-4d88-4132-acf1-a8e9e0a84d9f}\/Data>
<Data Name="VolumeDisplayName">D:\/Data>
<Data Name="DetectedCorruptionCount">2</Data>
<Data Name="FixedCorruptionCount">0</Data>
<Data Name="CorruptedUserFileCount">1</Data>
<Data Name="FixedUserFileCount">0</Data>
<Data Name="ErrorCode">0</Data>
<Data Name="ErrorMessage">NULL</Data>
<Data Name="ReadOnlyMode">false</Data>
</EventData>
</Event>
All replies (11)
Thursday, September 20, 2018 4:39 PM
Hi,
You could try to locate and then delete the corrupted file (as you have backup of it), I believe you can find where the file is by looking in the Microsoft-Windows-Deduplication\Scrubbing log.
After removing the corrupted file you could try enabling data deduplication again.
Best regards,
Leon
Blog: https://thesystemcenterblog.com LinkedIn:
Thursday, September 20, 2018 4:48 PM
Thanks Leon. I deleted the corrupted file and re-ran a regular scrubbing job and it shows this error.
I'm wondering if I should try to run a deep scrub again or just re-enable deduplication again and see what happens...
Log Name: Microsoft-Windows-Deduplication/Scrubbing
Source: Microsoft-Windows-Deduplication
Date: 9/20/2018 9:15:11 AM
Event ID: 12805
Task Category: Data Deduplication Scrubbing Task
Level: Error
Keywords: Reporting
User: SYSTEM
Computer: <hostname>
Description:
Data Deduplication service found 2 corruption(s) on volume D:\ 0 corruption(s) are fixed. 0 user file(s) are corrupted. 0 user file(s) are fixed. For the corrupted file list, see the Microsoft/Windows/Deduplication/Scrubbing events.
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
<System>
<Provider Name="Microsoft-Windows-Deduplication" Guid="{F9FE3908-44B8-48D9-9A32-5A763FF5ED79}" />
<EventID>12805</EventID>
<Version>0</Version>
<Level>2</Level>
<Task>3</Task>
<Opcode>0</Opcode>
<Keywords>0x4000000000000001</Keywords>
<TimeCreated SystemTime="2018-09-20T16:15:11.647648600Z" />
<EventRecordID>413</EventRecordID>
<Correlation />
<Execution ProcessID="14280" ThreadID="16136" />
<Channel>Microsoft-Windows-Deduplication/Scrubbing</Channel>
<Computer><hostname></Computer>
<Security UserID="<userid>" />
</System>
<EventData>
<Data Name="JobInstanceId">{308A75DB-1352-4A4B-B5F5-252B496778AA}</Data>
<Data Name="VolumeGuidPath">\?\Volume{6db5369a-4d88-4132-acf1-a8e9e0a84d9f}\/Data>
<Data Name="VolumeDisplayName">D:\/Data>
<Data Name="DetectedCorruptionCount">2</Data>
<Data Name="FixedCorruptionCount">0</Data>
<Data Name="CorruptedUserFileCount">0</Data>
<Data Name="FixedUserFileCount">0</Data>
<Data Name="ErrorCode">0</Data>
<Data Name="ErrorMessage">NULL</Data>
<Data Name="ReadOnlyMode">false</Data>
</EventData>
</Event>
Thursday, September 20, 2018 4:51 PM
Ok, at least it looks slightly better :-)
Try running the scrubbing task if that doesn't work then try re-enabling. A reboot may also help.
Blog: https://thesystemcenterblog.com LinkedIn:
Thursday, September 20, 2018 4:57 PM
Agreed, "slightly better"... haha
I'm running the deep scrub now to see what happens. I think it took about 6 hours or so last time so we'll see later if anything has changed.
Thanks again!
Thursday, September 20, 2018 11:39 PM
Ok Deep scrubbing ran again and still seeing four similar events in the operational event logs, but still no corruption in CorruptionLogEntryCount. I guess I will try to re-enable deduplication but I think it will stop again.
PS C:\Windows\system32> Get-DedupMetadata | fl
Volume : D:
VolumeId : \?\Volume{6db5369a-4d88-4132-acf1-a8e9e0a84d9f}\
StoreId : {7EEE4E1C-CD67-466B-AE22-77E5319743DD}
DataChunkCount : 60413615
DataContainerCount : 3434
DataChunkAverageSize : 59.5 KB
DataChunkMedianSize : 0 B
DataStoreUncompactedFreespace : 0 B
StreamMapChunkCount : 656781
StreamMapContainerCount : 55
StreamMapAverageDataChunkCount :
StreamMapMedianDataChunkCount :
StreamMapMaxDataChunkCount :
HotspotChunkCount : 9225
HotspotContainerCount : 1
HotspotMedianReferenceCount :
CorruptionLogEntryCount : 0
TotalChunkStoreSize : 3.36 TB
Log Name: Microsoft-Windows-Deduplication/Operational
Source: Microsoft-Windows-Deduplication
Date: 9/20/2018 4:35:48 PM
Event ID: 4134
Task Category: None
Level: Warning
Keywords:
User: SYSTEM
Computer: <hostname>
Description:
The data is invalid.
Error-specific details:
Error: The actual file size is less than the ValidDataLength in the header: actual size 1073709056, ValidDataLength 1073729536, \?\Volume{6db5369a-4d88-4132-acf1-a8e9e0a84d9f}\System Volume Information\Dedup\ChunkStore\7EEE4E1C-CD67-466B-AE22-77E5319743DD}.ddp\Data\00000843.00000001.ccc, 0x8056531d, The data is invalid.
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
<System>
<Provider Name="Microsoft-Windows-Deduplication" Guid="{F9FE3908-44B8-48D9-9A32-5A763FF5ED79}" />
<EventID>4134</EventID>
<Version>0</Version>
<Level>3</Level>
<Task>0</Task>
<Opcode>0</Opcode>
<Keywords>0x8000000000000000</Keywords>
<TimeCreated SystemTime="2018-09-20T23:35:48.551776700Z" />
<EventRecordID>125509</EventRecordID>
<Correlation />
<Execution ProcessID="11860" ThreadID="14760" />
<Channel>Microsoft-Windows-Deduplication/Operational</Channel>
<Computer><hostname></Computer>
<Security UserID="<userid>" />
</System>
<EventData>
<Data Name="Context">
Error-specific details:
Error: The actual file size is less than the ValidDataLength in the header: actual size 1073709056, ValidDataLength 1073729536, \?\Volume{6db5369a-4d88-4132-acf1-a8e9e0a84d9f}\System Volume Information\Dedup\ChunkStore\7EEE4E1C-CD67-466B-AE22-77E5319743DD}.ddp\Data\00000843.00000001.ccc, 0x8056531d, The data is invalid.
</Data>
<Data Name="DebugInfo">Code: CCSTCTNR.00003800; Call: CCSTCTNR.00003547; CMD: C:\Windows\system32\svchost -k ddpsvc ; User: Name: NT AUTHORITY\SYSTEM, SID:S-1-5-18 </Data>
</EventData>
</Event>
Friday, September 21, 2018 1:59 PM
Let us know the result after trying to re-enable deduplication.
Blog: https://thesystemcenterblog.com LinkedIn:
Friday, September 21, 2018 4:23 PM
Deduplication did not disable itself but I see this event in the Operational Log repeating every hour or so.."Initializing" then "Uninitializing".
No further errors reported so far in the Diagnostic or Scrubbing log.
I'll try to run a regular scrub then a deep scrub to see if it will generate further event logs.
The CorruptionLogEntryCount is still 0 when running Get-DedupMetadata | fl
_________________________________________________________________
The data is invalid.
Operation:
Initializing chunk store.
Running the deduplication job.
Context:
Volume name: \?\Volume{6db5369a-4d88-4132-acf1-a8e9e0a84d9f}\
Volume name: D: (\?\Volume{6db5369a-4d88-4132-acf1-a8e9e0a84d9f}\
Error-specific details:
Error: The actual file size is less than the ValidDataLength in the header: actual size 1073709056, ValidDataLength 1073729536, \?\Volume{6db5369a-4d88-4132-acf1-a8e9e0a84d9f}\System Volume Information\Dedup\ChunkStore\7EEE4E1C-CD67-466B-AE22-77E5319743DD}.ddp\Data\00000843.00000001.ccc, 0x8056531d, The data is invalid.
___________________________________________________________________________
The data is invalid.
Operation:
Uninitializing chunk store.
Running the deduplication job.
Context:
Volume name: D: (\?\Volume{6db5369a-4d88-4132-acf1-a8e9e0a84d9f}\
Error-specific details:
Error: The actual file size is less than the ValidDataLength in the header: actual size 1073709056, ValidDataLength 1073729536, \?\Volume{6db5369a-4d88-4132-acf1-a8e9e0a84d9f}\System Volume Information\Dedup\ChunkStore\7EEE4E1C-CD67-466B-AE22-77E5319743DD}.ddp\Data\00000843.00000001.ccc, 0x8056531d, The data is invalid.
Friday, September 21, 2018 4:51 PM
Ok while running a normal scrub it has disable deduplication again.
Any other ideas before we have to figure out how to migrate all the data to a new volume?
Data Deduplication has disabled the volume \?\Volume{6db5369a-4d88-4132-acf1-a8e9e0a84d9f}\ because there are missing or corrupt containers. Please run deep scrubbing on the volume.
Operation:
Running the deduplication scrubbing job.
Context:
Volume name: D: (\?\Volume{6db5369a-4d88-4132-acf1-a8e9e0a84d9f}\
Sunday, September 23, 2018 1:46 PM
Hmm, running low on ideas actually. Did you try running another checkdisk after that the corrupted files are gone?
Blog: https://thesystemcenterblog.com LinkedIn:
Tuesday, September 25, 2018 8:37 PM
I ended up just adding a new volume and migrating the data.
Thanks for your help!
Wednesday, March 4, 2020 4:27 AM
Has anyone found a solution to this?
I'm experiencing the same scenario:
Event ID: 4171
Description:
Data Deduplication has disabled the volume \?\Volume{2db9fd48-a547-4435-ba94-4cb5ce7b969c}\ because there are missing or corrupt containers. Please run deep scrubbing on the volume.
and:
Event ID: 4134
Error-specific details:
Error: The actual file size is less than the ValidDataLength in the header: actual size 852062208, ValidDataLength 852443136, \?\Volume{2db9fd48-a547-4435-ba94-4cb5ce7b969c}\System Volume Information\Dedup\ChunkStore\F7CBE2B0-60F1-4DF0-9765-706A0ECE7151}.ddp\Data\0000a1e7.00040000.ccc, 0x8056531d, The data is invalid.
I deleted all files reported as broken (even though most of them were actually not broken, as I was able to copy them and open from other disk).
No matter how many times I run Deep Scrubbing, I keep getting the same errors, resulting in disabled Deduplication.
How to deal with that? My volume is 50TB and I have no space elsewhere to copy all files over.