October 17, 201213 yr I intended to upgrade my unraid from 4.5-beta8 to 4.7. Before I started I thought a parity check might be a good idea, considering that the last one was done over a years ago. It showed one sync error right from the beginning. I looked in the syslog, expecting to see which sector was invalid but found nothing. All there was, was: Oct 17 19:49:45 Kanga kernel: mdcmd (8 ): check Oct 17 19:49:45 Kanga kernel: md: recovery thread woken up ... Oct 17 19:49:45 Kanga kernel: md: recovery thread checking parity... Oct 17 19:49:45 Kanga kernel: md: using 1152k window, over a total of 1953514552 blocks. Shouldn't the sector with invalid parity be logged? Any options I missed? If it matters, I started the check from the main page of the standard webui. Regards, myce
October 18, 201213 yr I intended to upgrade my unraid from 4.5-beta8 to 4.7. Before I started I thought a parity check might be a good idea, considering that the last one was done over a years ago. It showed one sync error right from the beginning. I looked in the syslog, expecting to see which sector was invalid but found nothing. All there was, was: Oct 17 19:49:45 Kanga kernel: mdcmd (8 ): check Oct 17 19:49:45 Kanga kernel: md: recovery thread woken up ... Oct 17 19:49:45 Kanga kernel: md: recovery thread checking parity... Oct 17 19:49:45 Kanga kernel: md: using 1152k window, over a total of 1953514552 blocks. Shouldn't the sector with invalid parity be logged? Any options I missed? If it matters, I started the check from the main page of the standard webui. Regards, myce older versions of unRAID did not log the block with the parity error. Newer versions log ONLY the first 20 or so errors. Joe L.
Archived
This topic is now archived and is closed to further replies.