So I've got the dreaded checksum mismatch. I backed up what files I had patience for, waited to see if this would work itself out but 75,000 errors later it seems like it's an issue. So I followed the advice on the forums which said to "ignore chunk verification" and run "chkdsk f: /x /r" in the windows powershell admin which is hopefully the correct command. Unfortunately it looks like my chkdsk is going to take an eternity. 999+ hours I've made it through 50, of 700,000 chunks in a day and a half. What can I do? My drive is 6TB and my local cache is a meager 10GB's.
Quote
Stage 2: Examining file name linkage ...
275 reparse records processed.
913692 index entries processed.
Index verification completed.
Phase duration (Index verification): 10.16 hours.
0 unindexed files scanned.
Phase duration (Orphan reconnection): 1.08 seconds.
0 unindexed files recovered to lost and found.
Phase duration (Orphan recovery to lost and found): 1.16 milliseconds.
275 reparse records processed.
Phase duration (Reparse point and Object ID verification): 5.20 milliseconds.
Question
DataDummy
So I've got the dreaded checksum mismatch. I backed up what files I had patience for, waited to see if this would work itself out but 75,000 errors later it seems like it's an issue. So I followed the advice on the forums which said to "ignore chunk verification" and run "chkdsk f: /x /r" in the windows powershell admin which is hopefully the correct command. Unfortunately it looks like my chkdsk is going to take an eternity. 999+ hours I've made it through 50, of 700,000 chunks in a day and a half. What can I do? My drive is 6TB and my local cache is a meager 10GB's.
Link to comment
Share on other sites
0 answers to this question
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.