CulturalFish81234

Hi All, On Sept 1, 2025, a scheduled parity check reported a large number of errors, despite previous checks being clean. The parity check history shows the affected entry with an incorrect timestamp (month displayed as 5 / May instead of 9 / September). Screenshot attached. System state prior to incident: System uptime ~2 weeks. Array was recently migrated to encryption following the procedure recommended by Spaceinvader One: each disk was individually emptied, removed, reformatted as encrypted, and re-added. This was repeated for all 3 array disks. No parity check was performed immediately after the migration. After the incident: A correcting parity check was run. System was rebooted. A non-correcting parity check is currently in progress. Unclear whether the parity errors originated from the encryption migration procedure or another cause, but the incorrect timestamp in the history log indicates a possible bug.