Fixes
Parity-check status now reflects reality (#14, thanks @rodaballo)
/api/array/parity/status previously read Unraid's GraphQL array.parityCheckStatus, which doesn't reflect parity checks started outside Connect (via mdcmd, cron, or the webGUI) — so it reported no activity during a running check.
It now reads live md-driver state from mdcmd status (the same source the webGUI uses, consistent with how start/pause/resume/cancel already shell out to mdcmd).
API
Backward compatible — the existing keys keep their names and now carry real data, with new fields added:
| Field | Source |
|---|---|
running |
mdResyncPos>0 ‖ mdResync>0 |
progress |
mdResyncPos / mdResyncSize (0–100) |
speed / speedHuman |
mdResyncDb / mdResyncDt (KiB/s) / MB/s string |
errors |
sbSyncErrs |
paused (new) |
in progress but not advancing |
correcting (new) |
mdResyncCorr |
action (new) |
mdResyncAction (e.g. "check P Q") |
position / size (new) |
KiB done / total |
lastCheck (new) |
start/finish/duration/exit of the previous check |
No changes required for existing API consumers (OpenClaw included).
Full Changelog: v0.1.30...v0.1.31
Contributors
rodaballo