October 14, 20232 yr I've run a couple of parity checks over the last few weeks and the errors keep creeping in. Parity-Check 2023-10-13, 19:33:36 (Friday) 14 TB 1 day, 1 hr, 30 min, 29 sec152.5 MB/s OK 14 Parity-Check 2023-10-04, 10:07:22 (Wednesday) 14 TB 1 day, 1 hr, 22 min, 28 sec153.3 MB/s OK 12 Parity-Check 2023-10-02, 08:49:11 (Monday) 14 TB 1 day, 1 hr, 11 min154.4 MB/s OK 6 I'm using the Dynamix File Integrity plugin and just checked, and all files are not corrupted. I'm going to run another correcting check, and then to follow best practices after this is done I'll do another check without correction. Lets assume that the 2nd "verification" check still turns up parity errors. At which point in this operation would I collect diagnostics that would best help shed light on this situation?
October 15, 20232 yr Author OK, ran with correction and 12 errors were found. Attached are diagnostics post correction run. Starting a no correction run to see if anything was actually fixed. tower-diagnostics-20231015-1751.zip
October 16, 20232 yr Community Expert Solution Ryzen with overclocked RAM like you have is known to corrupt data, correct that and try again.
October 16, 20232 yr Author 3 hours ago, JorgeB said: Ryzen with overclocked RAM like you have is known to corrupt data, correct that and try again. Ah I swear I turned off ram overclocking. Well, I'll turn that off and start the cycle again.
October 17, 20232 yr Author OK, so the correction run found 6 errors, down from 12-15. I'm going to start the "verification" run without corrections. If any more errors are found I'll re-post diagnostics.
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.