November 1, 20169 yr monthly check completed with four sync errors found. From Log: Nov 1 00:00:01 Tower kernel: mdcmd (263): check NOCORRECT Nov 1 00:00:01 Tower kernel: md: recovery thread: check P Q ... Nov 1 00:00:01 Tower kernel: md: using 1536k window, over a total of 3907018532 blocks. Nov 1 00:00:10 Tower kernel: md: recovery thread: PQ incorrect, sector=0 Nov 1 07:09:38 Tower kernel: md: recovery thread: PQ incorrect, sector=3907050624 Nov 1 07:09:39 Tower kernel: md: recovery thread: PQ incorrect, sector=3907122776 Nov 1 07:09:39 Tower kernel: md: recovery thread: PQ incorrect, sector=3907261496 Nov 1 13:26:27 Tower kernel: md: sync done. time=48386sec Nov 1 13:26:27 Tower kernel: md: recovery thread: completion status: 0 After searching around the forum and reading what I could find I have concluded all I can do is run another check, but with option to CORRECT parity enabled. Just wanted to check with the forum experts before proceeding. Thank You.
November 1, 20169 yr Community Expert Then after correcting check again to make sure it comes back with zero after everything was corrected.
November 1, 20169 yr Author Just curious if it is acceptable to stop parity che k once (if) sync errors are corrected, then start a fresh check to verify? Or is it more beneficial to complete, then recheck? Sent from my HTC One M9 using Tapatalk
November 2, 20169 yr Community Expert Let it finish. You want to see that everything is stable and parity is correct. Then when you run that second parity check, you are certain that it should have zero errors. (With your parity checks taking 13.5 hours, I can understand why you want to terminate early but if something is wrong, you don't want to have to run a third check! Plus the fact you will only be saving about half of the total time.)
November 3, 20169 yr Author correcting run and errors were indeed corrected. second run to verify confirmed no errors.
Archived
This topic is now archived and is closed to further replies.