August 26, 20169 yr The last couple of parity checks on my server keep identifying an error but I'm having a hard time identifying anything wrong with the server. I've attached the diagnostics for my server, any help would be greatly appreciated. tower-diagnostics-20160826-1052.zip
August 26, 20169 yr Community Expert Aug 25 07:40:43 Tower kernel: mdcmd (68): check CORRECT Aug 25 07:40:43 Tower kernel: md: recovery thread woken up ... Aug 25 07:40:43 Tower kernel: md: recovery thread checking parity... Aug 25 07:40:43 Tower kernel: md: using 1536k window, over a total of 3907018532 blocks. Aug 25 12:32:23 Tower kernel: mdcmd (69): spindown 2 Aug 25 12:32:23 Tower kernel: mdcmd (70): spindown 3 Aug 25 12:32:24 Tower kernel: mdcmd (71): spindown 4 Aug 25 15:32:51 Tower kernel: mdcmd (72): spindown 6 Aug 25 17:36:22 Tower kernel: md: correcting parity, sector=6517111144 Is it the same sector each time?
August 26, 20169 yr Author Aug 25 07:40:43 Tower kernel: mdcmd (68): check CORRECT Aug 25 07:40:43 Tower kernel: md: recovery thread woken up ... Aug 25 07:40:43 Tower kernel: md: recovery thread checking parity... Aug 25 07:40:43 Tower kernel: md: using 1536k window, over a total of 3907018532 blocks. Aug 25 12:32:23 Tower kernel: mdcmd (69): spindown 2 Aug 25 12:32:23 Tower kernel: mdcmd (70): spindown 3 Aug 25 12:32:24 Tower kernel: mdcmd (71): spindown 4 Aug 25 15:32:51 Tower kernel: mdcmd (72): spindown 6 Aug 25 17:36:22 Tower kernel: md: correcting parity, sector=6517111144 Is it the same sector each time? Thanks for taking a look. That's a great question, it didn't even phase me to check that. I'm going to run another check tonight and will update tomorrow morning. Unfortunately it seems I removed the diagnostics files I saved from after the last check I completed on the 15th.
Archived
This topic is now archived and is closed to further replies.