January 5, 20251 yr Hello, tonight the Parity-Check ran, and it finished with 0 errors. But why I have these entries in my log? Jan 5 04:46:08 SauerRaid kernel: md: recovery thread: P incorrect, sector=1565565768 Jan 5 04:46:08 SauerRaid kernel: md: recovery thread: P incorrect, sector=1565565776 Jan 5 04:46:08 SauerRaid kernel: md: recovery thread: P incorrect, sector=1565565784 Jan 5 04:46:08 SauerRaid kernel: md: recovery thread: P incorrect, sector=1565565792 Jan 5 04:46:08 SauerRaid kernel: md: recovery thread: P incorrect, sector=1565565800 Jan 5 05:26:05 SauerRaid emhttpd: spinning down /dev/sdb Jan 5 09:16:56 SauerRaid kernel: md: sync done. time=22615sec Jan 5 09:16:56 SauerRaid kernel: md: recovery thread: exit status: 0 Unraid Parity-Check: 05-01-2025 03:01 Notice [SAUERRAID] - Parity-Check started Size: 3 TB Unraid Parity-Check: 05-01-2025 09:17 Notice [SAUERRAID] - Parity-Check finished (0 errors) Duration: 5 hours, 46 minutes, 42 seconds. Average speed: 144.2 MB/s
January 5, 20251 yr Community Expert If those are notifications they can be wrong, post a screenshot from the bottom of the main page
January 5, 20251 yr Author Oh, yes… On the main page, 5 errors found. Why I need these notifications, when they can be wrong? And what should I do now? EDIT: Could it be because I connected an HDD from the array to my SATA PCIE ASM1166 card for a day or so? To see if the controller is working? It was about a week ago. So now the HDD is connected normally. Edited January 5, 20251 yr by RichardIstSauer
January 5, 20251 yr Community Expert 20 minutes ago, RichardIstSauer said: Why I need these notifications, when they can be wrong? It's a bug, should be fixed for v7. 21 minutes ago, RichardIstSauer said: Could it be because I connected an HDD from the array to my SATA PCIE ASM1166 card for a day or so? Some controllers, possibly in conjunction with some devices, have been known to cause the same 5 sync errors after a reboot,
January 5, 20251 yr Author So should I reboot and do the check again? Or is it enough to do the check again without rebooting? Do these 5 errors cause data loss or wrong written data?
January 5, 20251 yr Community Expert Solution Run a correcting check now, then run another one without rebooting, and if no errors are detected, reboot and run another one.
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.