February 21, 201313 yr I ran a parity check, no real reason other than it hadn't happened in a while. Came back the next day to: Feb 19 13:57:02 Tower kernel: mdcmd (23): check CORRECT (unRAID engine) Feb 19 13:57:02 Tower kernel: md: recovery thread woken up ... (unRAID engine) Feb 19 13:57:02 Tower kernel: md: recovery thread checking parity... (unRAID engine) Feb 19 13:57:02 Tower kernel: md: using 1536k window, over a total of 1953514552 blocks. (unRAID engine) Feb 19 19:49:37 Tower kernel: md: parity incorrect: 3490241256 (Errors) Feb 19 20:36:27 Tower kernel: md: sync done. time=23965sec (unRAID engine) Feb 19 20:36:27 Tower kernel: md: recovery thread sync completion status: 0 (unRAID engine) Is this normal? I have 3x 2TD WD black drives, whole system is under 2 months old.
February 21, 201313 yr I ran a parity check, no real reason other than it hadn't happened in a while. Came back the next day to: Feb 19 13:57:02 Tower kernel: mdcmd (23): check CORRECT (unRAID engine) Feb 19 13:57:02 Tower kernel: md: recovery thread woken up ... (unRAID engine) Feb 19 13:57:02 Tower kernel: md: recovery thread checking parity... (unRAID engine) Feb 19 13:57:02 Tower kernel: md: using 1536k window, over a total of 1953514552 blocks. (unRAID engine) Feb 19 19:49:37 Tower kernel: md: parity incorrect: 3490241256 (Errors) Feb 19 20:36:27 Tower kernel: md: sync done. time=23965sec (unRAID engine) Feb 19 20:36:27 Tower kernel: md: recovery thread sync completion status: 0 (unRAID engine) Is this normal? I have 3x 2TD WD black drives, whole system is under 2 months old. not normal unless the array was not shut down cleanly.
Archived
This topic is now archived and is closed to further replies.