It's working very nicely so far, thank you @Rysz . Great work, really, this fills a very important gap in UnRAID.

This poor machine of mine will be busy generating sets for the next month I imagine.

I was waiting on the nested option. It makes the setup so much easier. A single file in the root of your Movies folder and away it goes.

_par2cron:

glob: "**/*.{mkv,avi,mp4,idx,sub,srt,ass,ssa}"
mode: "nested"

The only thing I haven't tested yet is what it does when it fails during verification. It looks like it repairs and then deletes the corrupt file(s), but there's no kind of notification or persistent log for these encounters is there?

If you're using it on Unraid then you can set up the notifications and cron schedule right in the GUI.
Provided you're using the "par2cron for UNRAID" plugin from "Community Applications" ("Apps" tab).

You can then find the plugin settings at the end of the "Settings" tab ("par2cron") or otherwise via URL:

https://<your Unraid IP>/Settings/dwpar2cron

If verification fails you'd be notified and a repair attempted (depending on your plugin settings).

You can also set it up to just notify you and you can then manually execute the repair, it's all up to you.

Whether it deletes the corrupted file after repair can be configured in the configuration file (by default it does).

"Error Notifications", when enabled, would be what notifies you of a verification failure (due to corruption).

Naturally you will also always see it in the logs section of the GUI for that respective last ran operation.

If you're using it outside of Unraid you'd need to set up your own logs/notifications using your own scripting.

It's been ticking along nicely. Based on the time it's taken and the amount of data it's done so far, this can easily take another 4 to 5 weeks to complete.

But yes, I was thinking, do you have any plans on implementing some cleanup or 'refresh' feature. Something that can check for orphaned or outdated par2 files?

If you were to check and compare the files on the FS with what's in the json. In the event of new files, or where enough of the protected files are missing to invalidate the par2 set, it would recreate it.

If all of the files are missing, the par2 files can simply be deleted.

Just a thought..

On 4/21/2026 at 1:34 AM, Karools said:

It's been ticking along nicely. Based on the time it's taken and the amount of data it's done so far, this can easily take another 4 to 5 weeks to complete.

But yes, I was thinking, do you have any plans on implementing some cleanup or 'refresh' feature. Something that can check for orphaned or outdated par2 files?

If you were to check and compare the files on the FS with what's in the json. In the event of new files, or where enough of the protected files are missing to invalidate the par2 set, it would recreate it.

If all of the files are missing, the par2 files can simply be deleted.

Just a thought..

This is a feature that is definitely planned before the v1.0.0 release.

In fact all the latest updates contain changes paving the way for this very feature.

It's definitely going to be a lot of work, but I want to implement that kind of update command. 😉