An idea for a feature:

"Skip next scheduled check"

Sure you can manually disable it and then enable it after it would start, but a single checkbox (self cleared after a single use), would greatly help people that for some reason want to skip a scheduled parity check "just once".
For example, I just swapped an array disk, so that disk got rebuilt from parity, so there is no point to do the scheduled monthly check (which spans 4 days in my case, as I break it in non-working hours) this month.

Also now, manually disabling the scheduled parity check, after enabling you need to set again the parameters, doesn't remember it (this is not a problem of this plugin though, just the stock parity check has this issue). So that simple tick, would be great.

Edited September 28, 2025Sep 28 by NLS

Should we enable `Write corrections to parity disk` in unraid schedule menu for auto fix or better no?

How we find what sectors was errors in case :

Action	Date	Size	Duration	Speed	Status	Errors	Elapsed Time	Increments
Scheduled Non-Correcting Parity-Check	2025-10-02, 03:05:50 (Thursday)	4 TB	16 hr, 5 min, 35 sec	69.1 MB/s	Canceled	58	20 hr, 16 min	2

Edited October 4, 2025Oct 4 by Masterwishx

Two things...
I don't know if it was fixed with the update that came today, but at least for the previous version, parity check tuning stopped following the increments. Right now it is 16:10 local and as you can see below, it should have stopped (for the day) at 12:15, but still goes on. (and yes used to work fine with the exact same settings)

And a cosmetic thing (plus here you can see my actual settings):

Edited November 1, 2025Nov 1 by NLS

On 9/26/2025 at 3:15 AM, BurningSky said:

The error has come back again, from the notifications panel:

Parity_Check_Tuning_1758855103.notify

26 Sept, 08:09
Parity_Check_Tuning_1758855103.notify

This notification is invalid and cannot be displayed! For details, see the logs and the notification file at /tmp/notifications/unread/Parity_Check_Tuning_1758855103.notify

And when I cat that message

~# cat /tmp/notifications/unread/Parity_Check_Tuning_1758855103.notify
timestamp=1758855103
event=Parity Check Tuning
subject=[RAGON] mover running
description=
importance=normal
link=/Settings/Scheduler

Looks like a blank description again so that might have been the cause. My change to the script to replace blank descriptions must have been overwritten

been seeing this for awhile and following this thread hoping for a resolution, any progress? thanks

Same as above - getting the "invalid and cannot be displayed" error still.

I have never been able to reproduce this.

There should be an entry in the syslog at the time the notification occurs giving details about the notification - if I have that information I may be able to track down why it occurs for some people.

I am about to push out a plugin update. Basic functionality has not changed although there are significant changes to the GUI Settings screen to make it more user friendly and to conform to Unraid 7.2 guidelines as well as some bug fixes around edge cases. Be interesting to see if the problem soon still occurs for those who have encountered it.

Just pushed a new release. Does not change basic functionality but has lots of small fixes/changes:

### 2025-12-29

- Changes to comply with security guidelines for plugins

- Updated Unclean shutdown notifcation to separate crashes from array not stopping

- Correct some spelling mistakes in notification messages

- Added some debugging to track reports of history lines going missing.

- Added pause reason to Pause notifications.

- Improved/updated some of the built-in help text.

- Handle built-in parity checks being disabled.

- Fixes for conformance to Unraid 7.2 Responsive GUI requirements

- Hide options in GUI that are not relevant at the moment. E.g.

- if no parity disk installed

- Cumulative mode set at Unraid level

- if appdata backup not installed.

- Options not relevant unless another option set to Yes

- Fix for notifications for mover/backup being displayed when option set to not do so

- Fix for array operations allowed to restart even after a disk change.

If you spot any issues or encounter any problems then please let me know.

thank you for the update!

I am still seeing the same invalid notifications. Hopefully the following is helpful in some manner!

the notifications:

from the log at the same time as the 8:12am notification, none of the others seem to correlate with anything in the log:

Hi @itimpi,

I'm experiencing an error with the resumption of the partity check after an Unraid reboot.

After a reboot, the currently paused check is aborted.

Unraid version is 7.2.3 and the plugin is dated 2025-12-29.

Here's what I found in the system log:

Jan  2 10:13:35 nginx: 2026/01/02 10:13:35 [error] 9468#9468: *385 FastCGI sent in stderr: "Primary script unknown" while reading response header from upstream, client: 192.168.x.x, server: , request: "GET /plugins/parity.check.tuning/parity.check.entries.php HTTP/1.1", upstream: "fastcgi://unix:/var/run/php-fpm.sock:", host: "192.168.x.x", referrer: "http://192.168.x.x/Tools/Parity.check.problems"
Jan  2 10:16:24 ool www[25505]: /usr/local/emhttp/plugins/parity.check.tuning/parity.check.tuning.php 'config'
Jan  2 10:16:30 Parity Check Tuning: Versions: Unraid 7.2.3, Plugin Version: <unbekannt
Jan  2 10:16:30 Parity Check Tuning: Configuration
Jan  2 10:16:30 Check Tuning: Array#012(#012    [parityTuningScheduled] => 1#012    [parityTuningManual] => 1#012    [parityTuningAutomatic] => 1#012    [parityTuningFrequency] => 0#012    [parityTuningResumeCustom] => 5,15,25,35,45,55 * * * *#012    [parityTuningResumeDay] => 0#012    [parityTuningResumeHour] => 0#012    [parityTuningResumeMinute] => 15#012    [parityTuningPauseCustom] => 0,10,20,30,40,50 * * * *#012    [parityTuningPauseDay] => 0#012    [parityTuningPauseHour] => 3#012    [parityTuningPauseMinute] => 30#012    [parityTuningNotify] => 1#012    [parityTuningRecon] => 0#012    [parityTuningClear] => 1#012    [parityTuningRestart] => 1#012    [parityTuningShutdown] => 0#012    [parityTuningMover] => 1#012    [parityTuningBackup] => 0#012    [parityTuningBackground] => 1#012    [parityTuningDocker] => 0#012    [parityTuningContainers] => #012    [parityTuningHeat] => 0#012    [parityTuningHeatHigh] => 3#012    [parityTuningHeatLow] => 8#012    [parityTuningHeatNotify] => 1#012    [parityTuningHeatShutdown] => 0#012    [parityTuningHeatCritical] => 2#012    [parityTuningHeatTooLong] => 30#012    [parityTuningLogging]
Jan  2 10:17:14 ool www[26070]: /usr/local/emhttp/plugins/parity.check.tuning/parity.check.tuning.php 'config'
Jan  2 10:17:27 Parity Check Tuning: Versions: Unraid 7.2.3, Plugin Version: <unbekannt
Jan  2 10:17:27 Parity Check Tuning: Configuration
Jan  2 10:17:27 Parity Check Tuning: Array#012(#012    [parityTuningScheduled] => 1#012    [parityTuningManual] => 1#012    [parityTuningAutomatic] => 1#012    [parityTuningFrequency] => 0#012    [parityTuningResumeCustom] => 5,15,25,35,45,55 * * * *#012    [parityTuningResumeDay] => 0#012    [parityTuningResumeHour] => 0#012    [parityTuningResumeMinute] => 15#012    [parityTuningPauseCustom] => 0,10,20,30,40,50 * * * *#012    [parityTuningPauseDay] => 0#012    [parityTuningPauseHour] => 3#012    [parityTuningPauseMinute] => 30#012    [parityTuningNotify] => 1#012    [parityTuningRecon] => 0#012    [parityTuningClear] => 1#012    [parityTuningRestart] => 1#012    [parityTuningShutdown] => 0#012    [parityTuningMover] => 1#012    [parityTuningBackup] => 0#012    [parityTuningBackground] => 1#012    [parityTuningDocker] => 0#012    [parityTuningContainers] => #012    [parityTuningHeat] => 0#012    [parityTuningHeatHigh] => 3#012    [parityTuningHeatLow] => 8#012    [parityTuningHeatNotify] => 1#012    [parityTuningHeatShutdown] => 0#012    [parityTuningHeatCritical] => 2#012    [parityTuningHeatTooLong] => 30#012    [parityTuningLogging]
Jan  2 10:17:30 Parity Check Tuning: Parity History invoked
Jan  2 10:18:22 Parity Check Tuning: Parity History invoked
Jan  2 10:34:14 Parity Check Tuning: Manual Nicht-korrigierend Paritätsprüfung canceled (0 Fehler)

The configuration itself seems to be fine. Could there be a bug in the plugin?

Edited January 3Jan 3 by Synoxion

5 hours ago, Synoxion said:

The configuration itself seems to be fine. Could there be a bug in the plugin?

There could be, but not clear what it might be. If the plugin cannot restart a check when the restart option is enabled then it is meant to display a notification saying why.

I will see if I can recreate the issue at my end, but if it is possible to enable the Testing mode logging in the plugin settings and recreate the issue then the syslog might give me a clue why this is happening.

EDIT: I have found a reason that a restart can fail and will work on fixing that. I would still be interested in the Testing mode logging to confirm that it is failing in the same way for you although you may prefer to wait to see if the fix I have already found fixes it for you.

The parity check is currently running for quite some time. I'll let it complete fully first. After that, I could manually restart it for a test.

On 9/24/2025 at 5:00 PM, Gico said:

Is there a way to pause a parity check during a power outage rather than having it canceled?

As long as you achieve a clean shutdown then this plugin should allow you to restart from the point previously reached as long as you set that option in the plugin settings.

Having said that I have introduced in the release I made a few days ago a bug that can stop the restart working correctly. I have a fix for this under test and will release it in the next day or so assuming no other issue identified.

Hi itimpi,

I just ran the test mode logging with a manual parity check and a Unraid reboot.

The logs no longer show the error, and based on the logs, it should be working.

But it isn't. The notification about the cancellation was triggered at 08:34:09 and arrived correctly.

Status: Last incomplete check on Sun, Jan 4, 2026, 1:59 AM (Today) Error code: Aborted

Here's the log.
I've only posted the part of the log that I think is what you need. If you need anything else that isn't included, just let me know what you're looking for and I'll find it in the log. I didn't want to post the entire log.

syslog

Jan 4 08:08:01 UNRAID Parity Check Tuning: TESTING:STARTED ----------- STARTED begin ------

Jan 4 08:08:01 UNRAID Parity Check Tuning: TESTING:STARTED waiting 10 seconds to minimnise chance of race conditions

Jan 4 08:08:03 UNRAID reload_services: execute queued job 7

Jan 4 08:08:09 UNRAID rc.docker: Immich_Valkey: started successfully!

Jan 4 08:08:09 UNRAID rc.docker: Immich_Valkey: wait 5 seconds

Jan 4 08:08:11 UNRAID Parity Check Tuning: TESTING:STARTED /boot/config/forcesync marker file present

Jan 4 08:08:11 UNRAID Parity Check Tuning: TESTING:STARTED tidy marker file present

Jan 4 08:08:11 UNRAID Parity Check Tuning: TESTING:STARTED progress marker file present

Jan 4 08:08:11 UNRAID Parity Check Tuning: TESTING:STARTED manual marker file present

Jan 4 08:08:11 UNRAID Parity Check Tuning: TESTING:STARTED increment marker file present

Jan 4 08:08:11 UNRAID Parity Check Tuning: TESTING:STARTED restart marker file present

Jan 4 08:08:11 UNRAID Parity Check Tuning: TESTING:STARTED disks marker file present

Jan 4 08:08:11 UNRAID Parity Check Tuning: DEBUG: Array has just been started

Jan 4 08:08:11 UNRAID Parity Check Tuning: TESTING:STARTED restart information:

Jan 4 08:08:11 UNRAID Parity Check Tuning: TESTING:STARTED mdResync=0

Jan 4 08:08:11 UNRAID Parity Check Tuning: TESTING:STARTED mdResyncPos=67784044

Jan 4 08:08:11 UNRAID Parity Check Tuning: TESTING:STARTED mdResyncSize=15625879500

Jan 4 08:08:11 UNRAID Parity Check Tuning: TESTING:STARTED mdResyncAction=check P

Jan 4 08:08:11 UNRAID Parity Check Tuning: TESTING:STARTED mdResyncCorr=1

Jan 4 08:08:11 UNRAID Parity Check Tuning: TESTING:STARTED startMode=Normal

Jan 4 08:08:11 UNRAID Parity Check Tuning: TESTING:STARTED triggerType=MANUAL

Jan 4 08:08:11 UNRAID Parity Check Tuning: TESTING:STARTED ... appears to be manual parity check

Jan 4 08:08:11 UNRAID Parity Check Tuning: TESTING:STARTED triggerType: MANUAL

Jan 4 08:08:11 UNRAID Parity Check Tuning: TESTING:STARTED actionDescription(check P, 1, Manual, 0) = Manual Korrigiere Paritätsprüfung

Jan 4 08:08:11 UNRAID Parity Check Tuning: TESTING:STARTED restartPos: 135568088, adjustment: 0, paused: 1

Jan 4 08:08:11 UNRAID Parity Check Tuning: TESTING:STARTED Disk configuration appears to be unchanged

Jan 4 08:08:11 UNRAID Parity Check Tuning: restart to be attempted

Jan 4 08:08:11 UNRAID Parity Check Tuning: TESTING:STARTED Last History Line 58: 2026 Jan 4 01:59:05|81438|0|-4|0|check P|15625879500

------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------

Jan 4 08:17:01 UNRAID Parity Check Tuning: TESTING: setting locale from dynamix setting

Jan 4 08:17:01 UNRAID Parity Check Tuning: TESTING: No appdata backupo plugin installed

Jan 4 08:17:01 UNRAID Parity Check Tuning: TESTING:MONITOR ----------- MONITOR begin ------

Jan 4 08:17:01 UNRAID Parity Check Tuning: TESTING:MONITOR waiting 6 seconds to minimnise chance of race conditions

Jan 4 08:17:07 UNRAID Parity Check Tuning: TESTING:MONITOR /boot/config/forcesync marker file present

Jan 4 08:17:07 UNRAID Parity Check Tuning: TESTING:MONITOR tidy marker file present

Jan 4 08:17:07 UNRAID Parity Check Tuning: TESTING:MONITOR progress marker file present

Jan 4 08:17:07 UNRAID Parity Check Tuning: TESTING:MONITOR manual marker file present

Jan 4 08:17:07 UNRAID Parity Check Tuning: TESTING:MONITOR increment marker file present

Jan 4 08:17:07 UNRAID Parity Check Tuning: TESTING:MONITOR restart marker file present

Jan 4 08:17:07 UNRAID Parity Check Tuning: TESTING:MONITOR disks marker file present

Jan 4 08:17:07 UNRAID Parity Check Tuning: TESTING:MONITOR loadVars(30)

Jan 4 08:17:37 UNRAID Parity Check Tuning: TESTING:MONITOR Restart requested - but appears to not be happening

Jan 4 08:17:37 UNRAID Parity Check Tuning: TESTING:MONITOR Deleted restart marker file

Jan 4 08:17:37 UNRAID Parity Check Tuning: TESTING:MONITOR ----------- MONITOR end ------

------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------

Jan 4 08:34:01 UNRAID Parity Check Tuning: TESTING: setting locale from dynamix setting

Jan 4 08:34:01 UNRAID Parity Check Tuning: TESTING: No appdata backupo plugin installed

Jan 4 08:34:01 UNRAID Parity Check Tuning: TESTING:MONITOR ----------- MONITOR begin ------

Jan 4 08:34:01 UNRAID Parity Check Tuning: TESTING:MONITOR waiting 8 seconds to minimnise chance of race conditions

Jan 4 08:34:09 UNRAID Parity Check Tuning: TESTING:MONITOR /boot/config/forcesync marker file present

Jan 4 08:34:09 UNRAID Parity Check Tuning: TESTING:MONITOR tidy marker file present

Jan 4 08:34:09 UNRAID Parity Check Tuning: TESTING:MONITOR progress marker file present

Jan 4 08:34:09 UNRAID Parity Check Tuning: TESTING:MONITOR manual marker file present

Jan 4 08:34:09 UNRAID Parity Check Tuning: TESTING:MONITOR increment marker file present

Jan 4 08:34:09 UNRAID Parity Check Tuning: TESTING:MONITOR disks marker file present

Jan 4 08:34:09 UNRAID Parity Check Tuning: TESTING:MONITOR backGroundTaskHandling: markerName=/boot/config/plugins/parity.check.tuning/parity.check.tuning.mover, configName=parityTuningMover, value=1, isMoverRunning=0, Array: Active=0, Paused=0

Jan 4 08:34:09 UNRAID Parity Check Tuning: TESTING:MONITOR backGroundTaskHandling: return value=0

Jan 4 08:34:09 UNRAID Parity Check Tuning: TESTING:MONITOR backGroundTaskHandling: markerName=/boot/config/plugins/parity.check.tuning/parity.check.tuning.backup, configName=parityTuningBackup, value=0, isBackupRunning=0, Array: Active=0, Paused=0

Jan 4 08:34:09 UNRAID Parity Check Tuning: TESTING:MONITOR backGroundTaskHandling: return value=0

Jan 4 08:34:09 UNRAID Parity Check Tuning: TESTING:MONITOR backGroundTaskRunning: return value=0

Jan 4 08:34:09 UNRAID Parity Check Tuning: TESTING:MONITOR isArrayOperationActive - parityTuningActive:0, parityTuningPos:0

Jan 4 08:34:09 UNRAID Parity Check Tuning: TESTING:MONITOR No action outstanding

Jan 4 08:34:09 UNRAID Parity Check Tuning: TESTING:MONITOR ----------- PROGRESS_ANALYZE begin ------

Jan 4 08:34:09 UNRAID Parity Check Tuning: TESTING:MONITOR Previous array operation finished - analyzing progress information to create history record

Jan 4 08:34:09 UNRAID Parity Check Tuning: TESTING:MONITOR Deleted progress.save marker file

Jan 4 08:34:09 UNRAID Parity Check Tuning: DEBUG: Old progress file available as /boot/config/plugins/parity.check.tuning/parity.check.tuning.progress.save

Jan 4 08:34:09 UNRAID Parity Check Tuning: DEBUG: missing completion line in Progress file - add end TYPE and restart analyze

Jan 4 08:34:09 UNRAID Parity Check Tuning: TESTING:MONITOR COMPLETED record to be written

Jan 4 08:34:09 UNRAID Parity Check Tuning: TESTING:MONITOR written COMPLETED as record 5 to progress.save marker file

Jan 4 08:34:09 UNRAID Parity Check Tuning: TESTING:MONITOR type|date|time|sbSynced|sbSynced2|sbSyncErrs|sbSyncExit|mdState|mdResync|mdResyncPos|mdResyncSize|mdResyncCorr|mdResyncAction|Description

Jan 4 08:34:09 UNRAID Parity Check Tuning: TESTING:MONITOR ignore header record

Jan 4 08:34:09 UNRAID Parity Check Tuning: TESTING:MONITOR MANUAL|2026 Jan 04 02:00:12|1767488412|1767487977|1767488345|0|-4|STARTED|0|67784044|15625879500|1|check P|Manual Korrigiere Paritätsprüfung|

Jan 4 08:34:09 UNRAID Parity Check Tuning: TESTING:MONITOR Size reset from 0 to 15625879500

Jan 4 08:34:09 UNRAID Parity Check Tuning: TESTING:MONITOR correcting set to 1

Jan 4 08:34:09 UNRAID Parity Check Tuning: TESTING:MONITOR PAUSE (MANUAL)|2026 Jan 04 02:00:12|1767488412|1767487977|1767488345|0|-4|STARTED|0|67784044|15625879500|1|check P|Manual Korrigiere Paritätsprüfung|

Jan 4 08:34:09 UNRAID Parity Check Tuning: TESTING:MONITOR changing reachedSector from 0 to 67784044

Jan 4 08:34:09 UNRAID Parity Check Tuning: TESTING:MONITOR increment duration = 368 seconds

Jan 4 08:34:09 UNRAID Parity Check Tuning: TESTING:MONITOR new duration: 368 seconds, elapsed: 368 seconds

Jan 4 08:34:09 UNRAID Parity Check Tuning: TESTING:MONITOR thisStart=1767487977, thisFinish=1767488345, lastFinish=1767488345, thisDuration=368,#012 duration=368, elapsed=368, corrected=0, exitCode=-4

Jan 4 08:34:09 UNRAID Parity Check Tuning: TESTING:MONITOR STOPPING|2026 Jan 04 02:01:29|1767488489|1767487977|1767488345|0|-4|STARTED|0|67784044|15625879500|1|check P|Manual Korrigiere Paritätsprüfung|

Jan 4 08:34:09 UNRAID Parity Check Tuning: TESTING:MONITOR increment duration = 368 seconds

Jan 4 08:34:09 UNRAID Parity Check Tuning: TESTING:MONITOR new duration: 736 seconds, elapsed: 736 seconds

Jan 4 08:34:09 UNRAID Parity Check Tuning: TESTING:MONITOR thisStart=1767487977, thisFinish=1767488345, lastFinish=1767488345, thisDuration=368,#012 duration=736, elapsed=736, corrected=0, exitCode=-4

Jan 4 08:34:09 UNRAID Parity Check Tuning: TESTING:MONITOR PAUSE (RESTART)|2026 Jan 04 02:01:31|1767488491|1767487977|1767488345|0|-4|STARTED|0|67784044|15625879500|1|check P|Manual Korrigiere Paritätsprüfung|

Jan 4 08:34:09 UNRAID Parity Check Tuning: TESTING:MONITOR increment duration = 368 seconds

Jan 4 08:34:09 UNRAID Parity Check Tuning: TESTING:MONITOR new duration: 1104 seconds, elapsed: 1104 seconds

Jan 4 08:34:09 UNRAID Parity Check Tuning: TESTING:MONITOR thisStart=1767487977, thisFinish=1767488345, lastFinish=1767488345, thisDuration=368,#012 duration=1104, elapsed=1104, corrected=0, exitCode=-4

Jan 4 08:34:09 UNRAID Parity Check Tuning: TESTING:MONITOR COMPLETED|2026 Jan 04 08:34:09|1767512049|1767487977|1767488345|0|-4|STARTED|0|0|15625879500|0|check P|No array operation in progress|

Jan 4 08:34:09 UNRAID Parity Check Tuning: TESTING:MONITOR changing reachedSector from 67784044 to 0

Jan 4 08:34:09 UNRAID Parity Check Tuning: TESTING:MONITOR increment duration = 368 seconds

Jan 4 08:34:09 UNRAID Parity Check Tuning: TESTING:MONITOR new duration: 1472 seconds, elapsed: 1472 seconds

Jan 4 08:34:09 UNRAID Parity Check Tuning: TESTING:MONITOR thisStart=1767487977, thisFinish=1767488345, lastFinish=1767488345, thisDuration=368,#012 duration=1472, elapsed=1472, corrected=0, exitCode=-4

Jan 4 08:34:09 UNRAID Parity Check Tuning: TESTING:MONITOR ProgressFile start:2026 Jan 04 01:52:57, finish:2026 Jan 04 01:59:05, canceled, 0.0%Abgeschlossen

Jan 4 08:34:09 UNRAID Parity Check Tuning: TESTING:MONITOR totalSectors: 15625879500, duration: 1472, speed: 10.9 GB/s

Jan 4 08:34:09 UNRAID Parity Check Tuning: TESTING:MONITOR triggerType: MANUAL

Jan 4 08:34:09 UNRAID Parity Check Tuning: TESTING:MONITOR actionDescription(check P, 0, Manual, 1) = Manual Nicht-korrigierend Paritätsprüfung

Jan 4 08:34:09 UNRAID Parity Check Tuning: Manual Nicht-korrigierend Paritätsprüfung canceled (0 Fehler)

Jan 4 08:34:09 UNRAID Parity Check Tuning: Vergangene Zeit 24 Min, 32 Sek, Laufzeit 24 Min, 32 Sek, Inkremente 1, Durchschnittliche Geschwindigkeit 10.9 GB/s

Jan 4 08:34:09 UNRAID Parity Check Tuning: Send notification: Manual Nicht-korrigierend Paritätsprüfung canceled (0 Fehler): Vergangene Zeit 24 Min, 32 Sek, Laufzeit 24 Min, 32 Sek, Inkremente 1, Durchschnittliche Geschwindigkeit 10.9 GB/s (type=alert link=/Settings/Scheduler)

Jan 4 08:34:09 UNRAID Parity Check Tuning: TESTING:MONITOR ... using/usr/local/emhttp/webGui/scripts/notify -e Parity Check Tuning -i alert -l /Settings/Scheduler -s [UNRAID] Manual Nicht-korrigierend Paritätsprüfung canceled (0 Fehler) -d Vergangene Zeit 24 Min, 32 Sek, Laufzeit 24 Min, 32 Sek, Inkremente 1, Durchschnittliche Geschwindigkeit 10.9 GB/s

Jan 4 08:34:09 UNRAID Parity Check Tuning: TESTING:MONITOR looks like line 59 is the one to update, logtime=1767488345 . 2026 Jan 04 01:59:05)

Jan 4 08:34:09 UNRAID Parity Check Tuning: TESTING:MONITOR 2026 Jan 4 01:59:05|81438|0|-4|0|check P|15625879500

Jan 4 08:34:09 UNRAID Parity Check Tuning: TESTING:MONITOR update log entry on line 59

Jan 4 08:34:09 UNRAID Parity Check Tuning: TESTING:MONITOR add size to history record: 15625879500

Jan 4 08:34:09 UNRAID Parity Check Tuning: TESTING:MONITOR add plugin specific fields history record: |1472|1|Manual Nicht-korrigierend Paritätsprüfung

Jan 4 08:34:09 UNRAID Parity Check Tuning: TESTING:MONITOR log record generated from progress: 2026 Jan 4 01:59:05|1472|10.9 GB/s|-4|0|check P|15625879500|1472|1|Manual Nicht-korrigierend Paritätsprüfung

Jan 4 08:34:09 UNRAID Parity Check Tuning: TESTING:MONITOR Creating required cron entries

Jan 4 08:34:09 UNRAID Parity Check Tuning: DEBUG: Created cron entry for scheduled pause (30 3 * * *) and resume (15 0 * * *)

Jan 4 08:34:09 UNRAID Parity Check Tuning: DEBUG: Created cron entry for 17 Minute interval monitoring

Jan 4 08:34:10 UNRAID Parity Check Tuning: DEBUG: Updated cron settings are in /boot/config/plugins/parity.check.tuning/parity.check.tuning.cron

Jan 4 08:34:10 UNRAID Parity Check Tuning: TESTING:MONITOR ----------- PROGRESS_ANALYZE end ------

Jan 4 08:34:10 UNRAID Parity Check Tuning: TESTING:MONITOR no array operation in progress

Jan 4 08:34:10 UNRAID Parity Check Tuning: TESTING:MONITOR No progress file to analyze

Jan 4 08:34:10 UNRAID Parity Check Tuning: TESTING:MONITOR Deleted manual marker file

Jan 4 08:34:10 UNRAID Parity Check Tuning: TESTING:MONITOR Deleted tidy marker file

Jan 4 08:34:10 UNRAID Parity Check Tuning: TESTING:MONITOR Creating required cron entries

Jan 4 08:34:10 UNRAID Parity Check Tuning: DEBUG: Created cron entry for scheduled pause (30 3 * * *) and resume (15 0 * * *)

Jan 4 08:34:10 UNRAID Parity Check Tuning: DEBUG: Created cron entry for 17 Minute interval monitoring

Jan 4 08:34:10 UNRAID Parity Check Tuning: DEBUG: Updated cron settings are in /boot/config/plugins/parity.check.tuning/parity.check.tuning.cron

Jan 4 08:34:10 UNRAID Parity Check Tuning: TESTING:MONITOR ----------- MONITOR end ------

Additionally, the following error was found in the phplog.

phplog

[04-Jan-2026 08:08:11 Europe/Berlin] PHP Fatal error: Uncaught TypeError: copy(): Argument #3 ($context) must be of type resource or null, array given in /usr/local/emhttp/plugins/parity.check.tuning/parity.check.tuning.php:1553

Stack trace:

#0 /usr/local/emhttp/plugins/parity.check.tuning/parity.check.tuning.php(1553): copy('/boot/config/pa...', '/boot/config/pl...', Array)

#1 /usr/local/emhttp/plugins/parity.check.tuning/parity.check.tuning.php(796): removeHistoryCancelEntry()

#2 {main}

thrown in /usr/local/emhttp/plugins/parity.check.tuning/parity.check.tuning.php on line 1553

12 hours ago, Synoxion said:

Here's the log.
I've only posted the part of the log that I think is what you need. If you need anything else that isn't included, just let me know what you're looking for and I'll find it in the log. I didn't want to post the entire log.

The information you posted is enough to show that the restart failed for the same reason I found locally. I am testing the fix and it appears to be working although I want to test a bit more to be sure.

I am also fixing another long-standing bug where allowing mover to pause checks can cause a notification that is not quite right to be generated.

I have a question for anyone using the Restart option in the plugin and what it is desirable to show in the Parity History..

At the moment when you do a restart you end with a "Cancelled" entry in the History generated when the system shutdown/rebooted with a parity operation running and then an entry giving the array operation completion details. I am looking at simply removing this entry and only having the final entry on the operation completing. However I could instead change that entry to indicate that the system was shutdown/rebooted while an array operation was active (and perhaps indicate how far it had reached).

Also what about an entry in the history if a restart fails - is this something that is desirable? If I added it I would also give the reason the restart failed (e.g. unclean shutdown, disk configuration change).

I have pushed a release that I believe fixes all the issues reported against the last release:

### 2026-01-09

- Fix for version not being correctly set up for display on Settings page

- Fix for permissions on the plugin path being changed during install

- Fix for tidying up history file when restart being attempted which could stop restart working.

- Fix for Pause and Resume notifcations not displaying correctly.

- Change: Pause/Resume notifications displayed as warning if errors already found.

Let me know if any issues appear to be still outstanding.

Hi,

Where am I supposed to report the problem that almost none of the translated strings in the lang file paritychecktuning.txt are displayed if the selected display language is not English? Is this a plugin issue or Unraid problem?

Not quite sure what you are saying? I think you are saying you get English even when the language is set to something else, or is the problem something else?

If the problem is you are getting English regardless of the UI language then I am in the process of creating a push request for the English strings so up-to-date translations can be made. It is some time since the English strings have been updated so they are badly out-of-phase with the current plugin release.

I think you are saying you get English even when the language is set to something else...

More or less. Sorry for my complicated wording. As you can see in the screenshot some of the text in English, and some of them were picked up from paritychecktuning.txt - while the language was set to German (also tested with other languages). However, this was the situation even before you issued this new bug-fix release, so I doubt that this is only an 'out-of-phase' problem. Anyway, I've checked your source code on GitHub, and found ca. 6 missing messages in paritychecktuning.txt only. Maybe I missed some more.

11 minutes ago, DelDadam said:

Anyway, I've checked your source code on GitHub, and found ca. 6 missing messages in paritychecktuning.txt only. Maybe I missed some more.

If this is the version from the itimpi/parity.check.tuning project then I would be grateful if you mention them to save me trying to find them. If is the version of the file in the Unraid/langUS project (which is the basis for translations) then I know that one is badly out-of-date.

Hm... Maybe not only the lang file is out-of-phase but my findings of the missing messages? What I've done (~4 days ago):

• looked into the source code on your GitHub project itimpi/parity.check.tuning, and

• compared the strings there against the strings in paritychecktuning.txt from Unraid repo

Then you issued this new release. Maybe it is better if we wait until the Unraid/lang-en_US repo is refreshed with your update, and then I come back to you if I can still find something missing?

And there is another problem too which I don't know whether it has any impact on this here. I've found, I guess, a bug that depending on from where an actual page is opened in Unraid, e.g. from Main tab, or from Settings panel, or from Plugins panel, sometimes those TXT files with the translated messages simply not loaded/used at all. I'm planning to report this problem to Unraid. I just need some time to put the report into some sort of 'digestible' form.

11 hours ago, DelDadam said:

Then you issued this new release. Maybe it is better if we wait until the Unraid/lang-en_US repo is refreshed with your update, and then I come back to you if I can still find something missing?

I have been a bit lazy and not updated the Unraid/lang-en_US repo for some time so waiting makes sense. Over time mismatches will have accumulated. I am currently doing some local testing to try and make sure that all strings used in the current code are correctly reflected in the parity.tuning.txt file in my itimpi/parity.check.tuning repo (just found a few mismatches that will need correcting) before I upload the file to the Unraid/lang-en_US repo.

11 hours ago, DelDadam said:

And there is another problem too which I don't know whether it has any impact on this here. I've found, I guess, a bug that depending on from where an actual page is opened in Unraid, e.g. from Main tab, or from Settings panel, or from Plugins panel, sometimes those TXT files with the translated messages simply not loaded/used at all. I'm planning to report this problem to Unraid. I just need some time to put the report into some sort of 'digestible' form.

That sounds as if it is more likely to be a genuine Unraid bug. I do not see how any plugin authors will have visibility or control over this (although I could be wrong)

Parity.check.tuning.page, lines 498-504 and lines 545-551 containing Sunday, Monday, etc. seem to be not translatable.

On 1/11/2026 at 5:58 PM, DelDadam said:

Parity.check.tuning.page, lines 498-504 and lines 545-551 containing Sunday, Monday, etc. seem to be not translatable.

Good catch - fixing as part of next release (which is about translation support requirements).

I had been running a parity sync for several days. I paused it, stopped the array, and then started it again.

The parity sync restarted from zero — why did that happen?

juno-diagnostics-20260125-1925.zip