Um. I'm not really sure what to do here.

 

I logged into my server this morning, and did a parity sync. I did it manually via the unraid gui, and it looks like correct is the default option when not running the script.

 

I then saw this:

 

STARTED, 6 disks in array.    Parity is Valid:.   Last parity check < 1 day ago .   Parity updated  14908  times to address sync errors.  

 

And, from the syslog:

 

[color=red]Jun 13 03:18:36 Shiva login[23274]: ROOT LOGIN  on `pts/0' from `192.168.1.145' (Logins)
Jun 13 03:20:42 Shiva kernel: mdcmd (70): check CORRECT (unRAID engine)
Jun 13 03:20:42 Shiva kernel: md: recovery thread woken up ... (unRAID engine)
Jun 13 03:20:42 Shiva kernel: md: recovery thread checking parity... (unRAID engine)
Jun 13 03:20:42 Shiva kernel: md: using 1152k window, over a total of 1953514552 blocks. (unRAID engine)
Jun 13 03:20:53 Shiva kernel: md: parity incorrect: 128 (Errors)
Jun 13 03:20:53 Shiva kernel: md: parity incorrect: 136 (Errors)
Jun 13 03:20:54 Shiva kernel: md: parity incorrect: 65680 (Errors)
Jun 13 03:20:54 Shiva kernel: md: parity incorrect: 65688 (Errors)
Jun 13 03:20:55 Shiva kernel: md: parity incorrect: 262144 (Errors)
Jun 13 03:20:57 Shiva kernel: md: parity incorrect: 524288 (Errors)
Jun 13 03:20:58 Shiva kernel: md: parity incorrect: 786432 (Errors)
Jun 13 03:20:59 Shiva kernel: md: parity incorrect: 1048576 (Errors)
Jun 13 03:21:01 Shiva kernel: md: parity incorrect: 1310720 (Errors)
Jun 13 03:21:02 Shiva kernel: md: parity incorrect: 1572864 (Errors)
Jun 13 03:21:04 Shiva kernel: md: parity incorrect: 1835008 (Errors)
Jun 13 03:21:05 Shiva kernel: md: parity incorrect: 2097152 (Errors)
Jun 13 03:21:06 Shiva kernel: md: parity incorrect: 2359296 (Errors)
Jun 13 03:21:08 Shiva kernel: md: parity incorrect: 2621440 (Errors)
Jun 13 03:21:10 Shiva kernel: md: parity incorrect: 2883584 (Errors)
Jun 13 03:21:11 Shiva kernel: md: parity incorrect: 3145728 (Errors)
Jun 13 03:21:13 Shiva kernel: md: parity incorrect: 3407872 (Errors)
Jun 13 03:21:14 Shiva kernel: md: parity incorrect: 3670016 (Errors)
Jun 13 03:21:15 Shiva kernel: md: parity incorrect: 3932160 (Errors)
Jun 13 03:21:17 Shiva kernel: md: parity incorrect: 4194304 (Errors)
Jun 13 03:24:04 Shiva emhttp: shcmd (39): cp /var/spool/cron/crontabs/root- /var/spool/cron/crontabs/root (Other emhttp)
Jun 13 03:24:04 Shiva emhttp: shcmd (40): echo '# Generated mover schedule:' >>/var/spool/cron/crontabs/root (Other emhttp)
Jun 13 03:24:04 Shiva emhttp: shcmd (41): echo '40 3 * * * /usr/local/sbin/mover 2>$stuff$1 | logger' >>/var/spool/cron/crontabs/root (Other emhttp)
Jun 13 03:24:04 Shiva emhttp: shcmd (42): crontab /var/spool/cron/crontabs/root (Other emhttp)
Jun 13 03:24:04 Shiva emhttp: shcmd (43): rm /etc/samba/smb-shares.conf >/dev/null 2>$stuff$1 (Other emhttp)
Jun 13 03:24:04 Shiva emhttp: shcmd (44): cp /etc/exports- /etc/exports (Other emhttp)
Jun 13 03:24:04 Shiva emhttp: shcmd (45): killall -HUP smbd (Minor Issues)
Jun 13 03:24:04 Shiva emhttp: shcmd (46): /etc/rc.d/rc.nfsd restart | logger (Other emhttp)
Jun 13 03:47:04 Shiva sSMTP[10079]: Creating SSL connection to host
Jun 13 03:47:04 Shiva sSMTP[10079]: SSL connection using RC4-SHA
Jun 13 03:47:08 Shiva sSMTP[10079]: Sent mail for root@myemailaddress (221 2.0.0 closing connection r1sm3709667icz.2) uid=0 username=root outbytes=1407
Jun 13 04:47:04 Shiva sSMTP[22354]: Creating SSL connection to host
Jun 13 04:47:05 Shiva sSMTP[22354]: SSL connection using RC4-SHA
Jun 13 04:47:09 Shiva sSMTP[22354]: Sent mail for root@myemailaddress (221 2.0.0 closing connection fw9sm2713312ibb.30) uid=0 username=root outbytes=1408
Jun 13 05:47:04 Shiva sSMTP[852]: Creating SSL connection to host
Jun 13 05:47:04 Shiva sSMTP[852]: SSL connection using RC4-SHA
Jun 13 05:47:08 Shiva sSMTP[852]: Sent mail for root@myemailaddress (221 2.0.0 closing connection vn4sm4655819icb.19) uid=0 username=root outbytes=1408
Jun 13 06:47:04 Shiva sSMTP[8766]: Creating SSL connection to host
Jun 13 06:47:05 Shiva sSMTP[8766]: SSL connection using RC4-SHA
Jun 13 06:47:08 Shiva sSMTP[8766]: Sent mail for root@myemailaddress (221 2.0.0 closing connection s9sm2746914ibe.61) uid=0 username=root outbytes=1408
Jun 13 07:47:05 Shiva sSMTP[17927]: Creating SSL connection to host
Jun 13 07:47:05 Shiva sSMTP[17927]: SSL connection using RC4-SHA
Jun 13 07:47:09 Shiva sSMTP[17927]: Sent mail for root@myemailaddress (221 2.0.0 closing connection hw7sm4728131icc.15) uid=0 username=root outbytes=1408
Jun 13 08:47:04 Shiva sSMTP[24402]: Creating SSL connection to host
Jun 13 08:47:04 Shiva sSMTP[24402]: SSL connection using RC4-SHA
Jun 13 08:47:08 Shiva sSMTP[24402]: Sent mail for root@myemailaddress (221 2.0.0 closing connection y1sm4765904ica.16) uid=0 username=root outbytes=1408
Jun 13 09:47:04 Shiva sSMTP[28649]: Creating SSL connection to host
Jun 13 09:47:05 Shiva sSMTP[28649]: SSL connection using RC4-SHA
Jun 13 09:47:09 Shiva sSMTP[28649]: Sent mail for root@myemailaddress (221 2.0.0 closing connection 4sm2813495ibc.59) uid=0 username=root outbytes=1407
Jun 13 10:47:05 Shiva sSMTP[2574]: Creating SSL connection to host
Jun 13 10:47:05 Shiva sSMTP[2574]: SSL connection using RC4-SHA
Jun 13 10:47:09 Shiva sSMTP[2574]: Sent mail for root@myemailaddress (221 2.0.0 closing connection hw7sm4860038icc.3) uid=0 username=root outbytes=1406
Jun 13 10:48:33 Shiva kernel: md: sync done. time=26870sec rate=72702K/sec (unRAID engine)
Jun 13 10:48:33 Shiva kernel: md: recovery thread sync completion status: 0 (unRAID engine)[/color]

 

So now I don't know what to do. (Or if there is anything to do, since I guess they were corrected?). What could have caused this? And how does Unraid know if the errors are actually with the parity, vs being with the actual data?  

 

Unraid Pro, 4.7.

Post SMART reports for all the drives. unRAID assumes the mistake is in parity but it could be wrong. The md5deep package available in the unMenu package manager can help to determine if the error is on a data disk and which file.

Ok, I hope this is what you're referring to (and not the long tests?)

 

Too long to post, attached it.

 

smart_tests.txt

The SMART reports don't indicate a problem. Attach the full syslog.

ok, here is the running one.  Thanks for looking. I have a few more going back some; the time between parity checks was about 25 days or so.

syslog-2011-06-13.txt

Have you run an overnight memory test?

You mean like Memtest x86 or similar? Not yet, no... should I? I certainly could.

You mean like Memtest x86 or similar? Not yet, no... should I? I certainly could.

 

Bad memory can often be the cause of sync errors.  Reboot the server (cleanly!) - at start-up, you can choose between booting into UnRaid, and running Memtest.  Choose the latter and let us know the results

ok, running 16 hours, 30 passes, zero errors. Memory looks OK. Any other ideas what it could be?

 

Also, it's possible I had a power outage after the last parity check 25-odd days ago, and before I finally got a UPS in place around 3 weeks ago. Would that have potentially caused it? I'm not really even 100% clear on what a sync error is. Does it mean my files are corrupt, or what? Cause 14k would mean essentially everything.