Persistent 1378 Parity Errors After Drive Replacement & Unclean Shutdown (Unraid 7.2.3)

Hey everyone,

I’m stuck in a loop with persistent parity errors and could use some help.

My Unraid server (running version 7.2.3) just finished its scheduled parity check and came back with exactly 1378 errors. The problem is, this is the third time it’s done this, and the error count is identical every single time. I’ve ran the check twice now with the "Write corrections to parity" box checked, but it just keeps coming back with the exact same 1378 errors.

Some context on the server:

  • Recent Drive Replacement: I recently had a data drive develop bad sectors that I physically replaced and rebuilt, which I assume has something to do with why these errors started popping up.
  • Healthy SMART Reports: I’ve already pulled and verified the SMART logs for my parity and data drives (a mix of 16TB WD and 12TB Seagates). Every single drive is reporting PASSED with 0 current pending sectors, reallocated sectors, or UDMA CRC errors. The hardware looks solid.

The Errors: In my system log, the lines look like this during the sync process: Jul 9 18:26:42 HOME-NAS kernel: md: recovery thread: P corrected, sector=30570733776 ... up until it hits the 1378 count and stops logging.

Since my hardware diagnostics look perfect, I'm assuming this is a logical or filesystem metadata mismatch trapped in the parity calculation from the drive rebuild or the improper shutdown.

How do I actually get rid of these errors and force the array back into a truly clean sync? Should I stop running correcting checks and try running a filesystem repair on the data disks in Maintenance Mode first?

Thanks in advance for the help!

Posted Jul 10, 2026, 7:28 PM UTC

73
Loading comments…