SnapRAID AIO Plugin for OMV8

SnapRAID AIO is an OpenMediaVault 8 plugin that wraps the popular snapraid-aio-script around your SnapRAID arrays. It lets you configure, schedule, and monitor one or more arrays independently from the OMV web interface, with support for email, Apprise, and Healthchecks.io notifications, Docker container management, sync/scrub thresholds, and custom hooks.

This plugin requires the openmediavault-snapraid plugin to be installed first. That plugin provides the SnapRAID binary and the array configuration that this plugin reads.

SnapRAID AIO is a full replacement for the built-in diff script included in the openmediavault-snapraid plugin. It covers everything the diff script does (sync, scrub, notifications) and adds significantly more control.

SnapRAID AIO is third-party software. For questions about the underlying
script, see the upstream repository.

• openmediavault-snapraid installed and at least one array configured.
• omv-extras installed (required to install this plugin).
• Email notifications configured under System → Notification if you want email alerts.
• For disk spindown: hd-idle installed manually.
• For Docker management: Docker running on the same host.
• For Apprise notifications: internet access (Apprise is installed automatically via pipx on first run).

1. Navigate to System → Plugins.
2. Search for snapraid-aio.
3. Click Install.

After installation a new entry SnapRAID AIO appears in the Services menu.

The recommended workflow for a new array:

1. In the SnapRAID plugin, create and configure your array (parity, data disks).
2. Run an initial sync from the SnapRAID plugin so the parity is established.
3. Open Services → SnapRAID AIO.
4. Click Create and select your array.
5. Configure notifications, thresholds, and scrub settings.
6. Click Schedule to set up the automated run.

The main view shows a table of all AIO configurations.

Each row has a Tools submenu with the following actions:

The configuration form is divided into several sections.

The top of the form contains a single required field:

• SnapRAID array — select the array this configuration applies to. Each array can have only one AIO configuration. The dropdown is populated from arrays defined in the SnapRAID plugin.

• Enable email notifications — sends a report email after each run using OMV's configured notification address (System → Notification). When enabled, the sender and receiver addresses are shown read-only, pulled directly from the OMV system configuration.

• Enable Healthchecks.io — reports script completion or failure to a Healthchecks.io ping URL. Any warning in the script run counts as a failure.
• Healthchecks UUID — the UUID portion of your ping URL (not the full URL).
• Healthchecks URL — override for self-hosted instances. Must end with a trailing slash. Defaults to https://hc-ping.com/.

Apprise is a unified notification library supporting Telegram, Discord, Slack, Gotify, Ntfy, Pushover, and dozens of other services. It is installed automatically via `pipx` on the first run if enabled.

• Enable Apprise — master toggle for Apprise notifications.
• Apprise URLs — one or more service URLs in Apprise format (e.g. `tgram://token/chatid`). Enter each URL and press Enter to add it as a chip. Multiple services are supported. Service documentation and configuration instructions can be found here.
• Attach report on warnings — attaches the full run report to the notification when a warning is issued. Not all services support attachments.
• Test Apprise button — sends a test notification immediately using the saved URLs. Only available after saving the configuration. It is located at the bottom of the configuration page.

Apprise can also send email directly via SMTP or provider-specific URLs, independently of OMV's built-in notification system.

• Enable Apprise email — toggle for Apprise-based email.
• Apprise Email URL — SMTP or provider URL in Apprise format (e.g. `mailtos://user:pass@smtp.example.com`).
• Attach report on warnings — same as above.
• Test Apprise email button — sends a test email using the configured URL. It is located at the bottom of the configuration page.

Thresholds prevent accidental mass deletions or updates from being synced to parity. The script aborts and issues a warning when a threshold is exceeded, unless the warning count reaches the configured limit.

• Delete threshold — abort sync if more than N files were deleted since the last run. Set to `0` to disable. Default: 500.
• Update threshold — abort sync if more than N files were updated since the last run. Set to `0` to disable. Default: 500.
• Add/Delete ratio threshold — allow sync despite the delete threshold if a sufficient proportion of deletes are accompanied by matching adds (e.g. a large rename operation). Value is a ratio between 0.0 and 1.0. Set to `0` to disable.
• Sync warning threshold — how many times a threshold warning fires before the sync is forced anyway. `0` = always force sync past thresholds. `-1` = never force (always require manual override). Default: -1.

SnapRAID scrub verifies stored parity data against your files to detect silent bit-rot.

• Scrub percentage — percentage of the array to verify per run. Lower values spread verification over many runs. Default: 5%.
• Scrub age (days) — only scrub blocks that have not been verified within the last N days. Default: 10.
• Scrub new blocks after sync — immediately scrub any blocks newly added during this sync run.
• Scrub every N runs — run a scrub only every N script executions (e.g. `7` = weekly if you run daily). `0` = scrub every run.

• Pre-hash data — read data twice before syncing to detect silent read errors before they reach parity. Recommended. Default: enabled.
• Sync zero-sized files — SnapRAID skips empty files by default; enable this to include them.
• Spin down disks when done — spin down drives after the script completes using `hd-idle`. Requires hd-idle to be installed separately.

• Verbose output in notification — include full SnapRAID command output in notification messages. Not recommended for large arrays — produces very large messages.
• Log retention (days) — delete log files older than N days. `0` = keep forever.
• SnapRAID log directory — directory where per-run log files (`SnapRAID-*.txt`) are written. Leave empty to use `/root`. Also used by the Last Log tool action.
• Log SMART data — include SMART drive health data in the run log. Default: enabled.
• Include SMART data in notification — include SMART output in notification messages.
• Log SnapRAID status — run `snapraid status` and include the output in the log.
• Include status in notification — include the status output in notification messages.
• Ignore pattern — space-separated glob patterns to exclude from diff counts only (files matching these patterns are not counted against the delete/update thresholds). This does not affect SnapRAID itself.

When enabled, the script pauses or stops your Docker containers before running SnapRAID operations and restores them afterward, preventing open-file conflicts.

• Manage Docker containers / services — master toggle for Docker management.
• Docker mode — `Pause/unpause` (faster, less disruptive) or `Stop/restart` (full stop, needed for some containers).
• Docker containers — select which containers to manage. The list is populated from currently running containers.
• Service start delay (seconds) — seconds to wait after restarting services before the script continues.

Custom hooks let you run arbitrary shell commands or scripts before and after the SnapRAID operations.

• Enable custom hooks — master toggle.
• Before hook name — display name shown in the log output.
• Before hook command — shell command or script path executed before SnapRAID runs. Runs as root.
• After hook name — display name shown in the log output.
• After hook command — shell command or script path executed after SnapRAID completes. Runs as root.
• Execute after hook before spindown — when disk spindown is enabled, run the after hook before spinning down the disks instead of after.

Each configuration has its own independent schedule. Click the Schedule button on a row to open the schedule form.

The cron job runs as root and calls:

/usr/sbin/snapraid-aio-script.sh --config /etc/snapraid-aio-<uuid>.conf

Each script run produces a dated log file (`SnapRAID-YYYY-MM-DD_HH-MM-SS.txt`) in the configured log directory. These are the files shown by the Last Log tool. A central summary log at `/var/log/snapraid.log` is also maintained and is used to populate the Last Run column in the config list.

The plugin stores two counter files per configuration in `/var/lib/snapraidaio/`:

• `<uuid>.warnCount` — tracks how many consecutive threshold warnings have fired, used against the Sync warning threshold.
• `<uuid>.scrubCount` — tracks run count for the Scrub every N runs feature.

These files are removed when the configuration is deleted.

See the note in the SnapRAID Options section. Disk spindown requires hd-idle to be installed manually before enabling the option.

Use in this guide for more information and how to install it.

• openmediavault-snapraid-aio on GitHub
• snapraid-aio-script on GitHub