Oct 2 11:29:43 vildkatt kernel: md: recovery thread: P corrected, sector=1064
Oct 2 11:29:43 vildkatt kernel: md: recovery thread: P corrected, sector=13304
Oct 2 11:29:43 vildkatt kernel: md: recovery thread: P corrected, sector=30712
Oct 2 11:29:43 vildkatt kernel: md: recovery thread: P corrected, sector=44016
Oct 2 11:29:43 vildkatt kernel: md: recovery thread: P corrected, sector=58344
Oct 2 11:29:43 vildkatt kernel: md: recovery thread: P corrected, sector=69616
Oct 2 11:29:43 vildkatt kernel: md: recovery thread: P corrected, sector=81896
Oct 2 11:29:43 vildkatt kernel: md: recovery thread: P corrected, sector=92136
Oct 2 11:29:43 vildkatt kernel: md: recovery thread: P corrected, sector=103400
Oct 4 20:40:57 vildkatt kernel: md: recovery thread: P incorrect, sector=1064
Oct 4 20:40:57 vildkatt kernel: md: recovery thread: P incorrect, sector=13304
Oct 4 20:40:57 vildkatt kernel: md: recovery thread: P incorrect, sector=30712
Oct 4 20:40:57 vildkatt kernel: md: recovery thread: P incorrect, sector=44016
Oct 4 20:40:57 vildkatt kernel: md: recovery thread: P incorrect, sector=58344
Oct 4 20:40:57 vildkatt kernel: md: recovery thread: P incorrect, sector=69616
Oct 4 20:40:57 vildkatt kernel: md: recovery thread: P incorrect, sector=81896
Oct 4 20:40:57 vildkatt kernel: md: recovery thread: P incorrect, sector=92136
Oct 4 20:40:57 vildkatt kernel: md: recovery thread: P incorrect, sector=103400
Didn't check them all but at least the first ones are exactly the same sectors as before, that could indicate that they were previously wrongly updated, due to some hardware issue, run a correcting check and then a non correcting one right after.