I had a problem with my watercooling pump which caused the processor to overheat and the server to reboot. So parity didn't complete a couple of times before I noticed it.

I've tried to complete parity a few times now but it keeps aborting. When I last looked it was at 98% then told me later it had aborted. Am I looking at the parity log wrong?

I've attached my syslog file. It looks like a parity tuning plugin issue, where I'm running it from.

 

Quote

2021-02-01, 00:00:06UnavailableUnavailableAborted0Unknown1Unknown

2021-02-01, 21:43:0821 hr, 43 min, 2 sec179.1 MB/sOK0UnknownUnavailable

2021-01-30, 19:39:0116 secUnavailableCanceled0UnknownUnavailable

2021-01-30, 18:59:169 hr, 16 min, 17 secUnavailableCanceled0UnknownUnavailable

2021-01-29, 08:28:01UnavailableUnavailableAborted0Unknown1Unknown

2021-01-28, 16:49:01UnavailableUnavailableAborted0Unknown1Unknown

2021-01-28, 16:51:284 min, 58 secUnavailableCanceled0UnknownUnavailable

1 day, 4 hr, 27 min, 45 sec7OKUnknownUnavailable

2021-01-28, 08:50:3223 hr, 18 min, 2 sec166.9MB/sCanceled1UnknownUnavailable

2021-01-26, 18:07:01UnavailableUnavailableAborted0Unknown1Unknown

2021-01-26, 18:31:3727 min, 10 secUnavailableCanceled0UnknownUnavailable

2021-01-26, 12:07:071 hr, 3 min, 43 sec3.7GB/sAborted03 hr, 3 min, 36 sec3Unknown

2021-01-25, 13:42:061 hr, 2 min, 49 sec3.7GB/sAborted020 hr, 34 min, 44 sec3Unknown

2021-01-24, 19:22:161 min, 15 secUnavailableCanceled0UnknownUnavailable

2021-01-24, 13:42:0723 hr, 25 min, 50 sec166.0MB/sAborted01 day, 22 hr, 7 min, 24 sec9Unknown

2021-01-16, 13:42:3719 hr, 39 min, 8 sec197.9 MB/sOK0UnknownUnavailable

2021-01-16, 12:42:3719 hr, 39 min, 8 sec197.9MB/sOK019 hr, 39 min, 8 sec1Correcting

2021-01-15, 16:55:472 min, 33 secUnavailableCanceled0UnknownUnavailable

2021-01-15, 16:52:2754 secUnavailableCanceled0UnknownUnavailable

2021-01-15, 16:45:531 min, 8 secUnavailableCanceled0UnknownUnavailable

2021-01-13, 19:36:077 min, 47 secUnavailableCanceled0UnknownUnavailable

2021-01-06, 20:16:3821 hr, 44 min, 21 sec178.9MB/sOK021 hr, 44 min, 21 sec1Correcting

2020-11-04, 03:30:263 hr, 48 sec1.3 GB/sOK03 hr, 48 sec1Non-Correcting

2020-10-10, 09:26:3312 min, 4 sec19.3 GB/sCanceled012 min, 4 sec1Non-Correcting

2020-10-04, 23:04:4011 min, 20 sec20.6 GB/sCanceled011 min, 20 sec1Non-Correcting

2020-10-04, 22:06:331 min, 51 secUnavailableCanceled0UnknownUnavailable

2020-09-30, 23:10:4820 hr, 5 min, 4 sec193.6 MB/sCanceled020 hr, 5 min, 4 sec1Correcting

2020-09-28, 21:43:191 hr, 22 min, 50 sec2.8 GB/sCanceled01 hr, 22 min, 50 sec1Non-Correcting

2020-09-01, 00:36:162 hr, 38 min, 20 sec1.5 GB/sOK02 hr, 38 min, 20 sec1Non-Correcting

2020-08-22, 00:12:2151 min, 42 sec4.5 GB/sOK051 min, 42 sec1Non-Correcting

2020-08-13, 13:53:291 day, 3 hr, 13 min, 10 sec142.9 MB/sCanceled01 day, 3 hr, 13 min, 10 sec1Non-Correcting

2020-08-02, 23:57:541 min, 18 sec179.5 GB/sCanceled01 min, 18 sec1Non-Correcting

2020-07-31, 06:16:4621 hr, 16 min, 45 secUnavailableOK0UnknownUnavailable

2020-07-31, 23:16:461 day, 18 hr, 33 min, 30 sec91.4 MB/sOK01 day, 18 hr, 33 min, 30 sec1Non-Correcting

2020-07-28, 16:45:095 hr, 47 min, 14 sec672.0 MB/sOK05 hr, 47 min, 14 sec1Non-Correcting

2020-07-04, 07:44:251 day, 14 hr, 13 min, 16 sec101.8 MB/sOK01 day, 14 hr, 13 min, 16 sec1Non-Correcting

2020-06-30, 20:29:515 min, 10 secUnavailableCanceled0

2020-06-03, 12:29:352 hr, 58 min, 33 sec1.3 GB/sOK0

2020-05-03, 10:41:272 hr, 2 min, 37 sec1.9 GB/sOK0

2020-04-04, 16:00:302 hr, 6 min, 39 sec1.8 GB/sOK0

2020-03-26, 04:03:583 hr, 44 min, 11 sec1.0 GB/sOK0

2020-03-02, 03:09:085 hr, 1 min, 22 sec774.3 MB/sOK0

2020-01-31, 21:06:2419 hr, 6 min, 23 sec203.5 MB/sOK0

2019-12-31, 21:38:2519 hr, 38 min, 24 sec198.0 MB/sOK0

2019-12-15, 12:20:0912 hr, 20 min, 8 secUnavailableCanceled0

2019-12-10, 17:29:1639 secUnavailableCanceled0

2019-12-10, 17:28:2845 secUnavailableCanceled0

2019-12-10, 16:53:0322 hr, 3 min176.4 MB/sOK0

 

syslog.txt

Edited February 1, 20215 yr by Geck0

Not sure what your problem is, but the plugin would not be automatically starting or aborting the parity check - it is just reporting what it thinks has happened.   According to the syslog the parity check was manually cancelled.

Is this because its a non-correcting parity check?

 

 

1 minute ago, Geck0 said:

Is this because its a non-correcting parity check?

 

 

A non-correcting check will not be a reason for aborting.   It would just mean that the same errors will show up each time you run the check until you have successfully run a correcting check.

Hiya,

I haven't cancelled it, I've tried this multiple times. I've uninstalled the plugin and started this manually. I thought maybe it was aborting because it was a non-correcting parity check and was set up to get to the end and abort so nothing got written as it says 0 errors.????

 

Quote

Jan 30 19:02:28 Nexus parity.check.tuning.php: Unclean shutdown detected
Jan 30 19:02:29 Nexus parity.check.tuning.php: Send notification: Automatic Unraid parity check will be started: Unclean shutdown detected

Quote

Feb  1 21:49:02 Nexus parity.check.tuning.php: Send notification: Correcting Parity Check aborted (0 errors)  0% completed : Elapsed Time Unavailable, Runtime Unavailable, Increments 1, Average Speed nanB/s

 

Okay, I'm running a correcting check now. I guess I'll find out tomorrow. 

Thanks for your input.

Hi,

Correting parity check worked first time from the 'Main' page. No errors.

Literally, when I ran it through the plugin it aborted 5 times and always at completion. I've uninstalled the plugin for now, not that I have any evidence it was causing the issue.

 

Thanks for your help itimpi.

2 hours ago, Geck0 said:

Literally, when I ran it through the plugin it aborted 5 times and always at completion. I've uninstalled the plugin for now, not that I have any evidence it was causing the issue.

 

The thing is the plugin never "runs" the parity check - it can only pause/resume one that Unraid is running.   Maybe there is something wrong about the completion message suggesting it has aborted when in fact it has not?  What does the Parity History for those runs say happened?