I just recently (a few days ago) upgraded this server from 4.5 to 5.0b6a.  I performed a parity check before upgrading and it returned 0 errors.  I have unMenu installed and via unMenut I installed the monthly parity check and have it set to not correct errors.  Last night a parity check ran as expected and it found 4 errors (not expected) and unMenu says "Parity updated 4 times to address sync errors.".  My questions:

 

1. Why was parity updated if the monthly parity check package was set to "NOCORRECT"?

2. I'm going to run another parity check shortly, but any ideas or suggestions/ideas what might have caused the errors?  I've had no unexpected shutdowns and like I said, parity was good right before the upgrade.

3. On an unrelated note, there a lot of of repeating lines in my log that say:

 

Apr 30 02:08:23 Tower2 unmenu[1641]: bad method -     3664   345504  2792009    56290        9        3       96      100        0    50610    563803664-^M

 

what does it mean?

 

 

Here is my log: http://pastebin.com/TBvwL9FJ

I just recently (a few days ago) upgraded this server from 4.5 to 5.0b6a.  I performed a parity check before upgrading and it returned 0 errors.  I have unMenu installed and via unMenut I installed the monthly parity check and have it set to not correct errors.  Last night a parity check ran as expected and it found 4 errors (not expected) and unMenu says "Parity updated 4 times to address sync errors.".  My questions:

 

1. Why was parity updated if the monthly parity check package was set to "NOCORRECT"?

2. I'm going to run another parity check shortly, but any ideas or suggestions/ideas what might have caused the errors?  I've had no unexpected shutdowns and like I said, parity was good right before the upgrade.

3. On an unrelated note, there a lot of of repeating lines in my log that say:

 

Apr 30 02:08:23 Tower2 unmenu[1641]: bad method -     3664   345504  2792009    56290        9        3       96      100        0    50610    563803664-^M

 

what does it mean?

 

 

Here is my log: http://pastebin.com/TBvwL9FJ

The user interface is not using the right description.  It will always say "updated" even though it was in NOCORRECT mode.

 

It did not update.  If you run it again in NOCORRECT mode, it will find the same errors again.

 

JOE L.

I see.  Then shouldn't unRaid be saying that parity is not valid?  Both the stock GUI and unMenu say parity is valid.

 

EDIT:  Should I just let unRaid go ahead and repair these errors?