last months parity check was done with no errors...today i have started new is at 20% and already has found 117 sync errors...when it finishes it will show which drive it is? or how to procedure ?

running unraid 4.7 with no plugins only rsync

 

regards

finished...Parity updated  107  times to address sync errors what this means?

finished...Parity updated  107  times to address sync errors what this means?

It depends.  Was this the monthly un-correcting parity check you scheduled? Or a correcting check?

 

If an un-correcting check there are 117 errors in parity...  They were not fixed. (that's the whole idea of un-correcting)

 

Re-run another un-correcting check.  You should still get 117 errors.  Then, the challenge is to determine what, if anything they affect.

It could be absolutely any drive, or drives.  The error addresses will be in the syslog.  (Or at least the first bunch of them)

 

You'll need to search for how others have diagnosed the drives with the issues using repeated "dd" reads of ranges of sectors and checksums.

i havent runned this from unmenu but from the default menu of unraid 4.7 by pressing check(there is no other option)I have just copied the result from unmenu page.

I re-run parity check now and havent write anything to the server since the last one with the erros to see....

If i have the same erros what is means? if they arefixed,again what this means ?some files where corrupt anf been fixed? generally can i trust my data?i have run also smart test to all drives and all passed.

i havent runned this from unmenu but from the default menu of unraid 4.7 by pressing check(there is no other option)I have just copied the result from unmenu page.

I re-run parity check now and havent write anything to the server since the last one with the erros to see....

If i have the same erros what is means? if they arefixed,again what this means ?some files where corrupt anf been fixed? generally can i trust my data?i have run also smart test to all drives and all passed.

 

Then you ran a Correcting parity check, and so the Parity should now be correct.  you should either get unMenu or go to the console and type

 

/root/mdcmd check NOCORRECT 1>/dev/null 2>&1

 

If more errors show up, you have an issue you need to look further into.

 

You should only run the command from the unraid menu (Correcting) when you are sure there are no data integrity issues.

 

There are tons of posts on here about setting up monthly automatic runs of the above command from crond.

i run now this also mdcmd check NOCORRECT 1>/dev/null 2>&1

so here is the sys.log with the errors and after i with no errors....So if i have understood it correct parity check should been runned without correcting errors? and when do errors appear,how to proceed?

 

regards

syslog-2012-03-04.txt

syslog-2012-03-05.txt