November 4, 20196 yr Howdy folks, Just wanted to say hi and introduce myself to this wonderful community! Been loving UnRaid and everything that goes with it! Yesterday the monthly parity check ran and came up with 15 sync errors. From everything I've read and deciphered so far it seems this can be normal if there have been any dirty shutdowns, and I believe there may have been 1 or 2 during a couple bad storms we had. (on a side note if anyone could recommend a good UPS for my system lol). The thing I could find in the logs that looked related was this bit Quote Nov 3 00:30:01 TowerX2 kernel: md: recovery thread: check P Q ... Nov 3 00:30:01 TowerX2 kernel: md: using 1536k window, over a total of 9766436812 blocks. Nov 3 00:30:16 TowerX2 kernel: md: recovery thread: P corrected, sector=5554344 Nov 3 00:30:16 TowerX2 kernel: md: recovery thread: P corrected, sector=5554352 Nov 3 00:30:16 TowerX2 kernel: md: recovery thread: P corrected, sector=5554360 Nov 3 00:30:16 TowerX2 kernel: md: recovery thread: P corrected, sector=5554368 Nov 3 00:30:16 TowerX2 kernel: md: recovery thread: P corrected, sector=5554488 Nov 3 00:30:16 TowerX2 kernel: md: recovery thread: P corrected, sector=5554496 Nov 3 00:30:16 TowerX2 kernel: md: recovery thread: P corrected, sector=5554616 Nov 3 00:30:16 TowerX2 kernel: md: recovery thread: P corrected, sector=5554680 Nov 3 00:30:16 TowerX2 kernel: md: recovery thread: P corrected, sector=5554720 Nov 3 00:30:16 TowerX2 kernel: md: recovery thread: P corrected, sector=5554728 Nov 3 00:30:17 TowerX2 kernel: md: recovery thread: P corrected, sector=5688120 Nov 3 00:30:18 TowerX2 kernel: md: recovery thread: P corrected, sector=6293496 Nov 3 00:30:18 TowerX2 kernel: md: recovery thread: P corrected, sector=6293504 Nov 3 04:15:41 TowerX2 kernel: md: recovery thread: PQ corrected, sector=4593406928 Nov 3 05:52:54 TowerX2 kernel: md: recovery thread: PQ corrected, sector=5942149320 I thought I should maybe post the logs here and see what you guys thought as I have no idea really and am still learning the ropes. Thank you kindly for any and all help you may be able to provide. towerx2-diagnostics-20191104-1137.zip
November 4, 20196 yr Community Expert If you have had an unclean shutdown then it is normal to expect a few parity sync errors as the system would have not been able to complete housekeeping and tidily unmount the drives. Typically such errors occur near the start of the parity sync process.
November 4, 20196 yr Author Thank you kindly for the quick reply. That seems to correlate to what I see. The Check starts to run at 12:30 and 13/15 of those errors were within 18 seconds of that and the other 2/15 were within 6 hours of a 23 hour run. I will likely run another check and see what comes up the second time to be safe.
Archived
This topic is now archived and is closed to further replies.