- Minor
Unraid 6.12.13 (see note at bottom)
I just removed a slower hard drive from my array (without replacing it) and had to rebuild parity. The parity SYNC notifications included the duration and speed statistics from the previous parity CHECK, not the parity SYNC that just completed.
The attached screenshots are probably clearer, but I'll describe here in case of attachment issues:
- Parity sync completed 2024-12-11. I received notifications via email and Pushover, that said the sync finished with 0 errors, taking 1 day 4 hr 9 min 13 sec, at 157.9 MB/s.
- I checked Parity Operation History in Unraid and I see that the Parity Sync operation that finished on 2024-12-11 took 21 hr 59 min 17 sec at 202.1 MB/s. This does not match the notification.
- My previous Parity Check operation finished on 2024-12-09 and took 1 day 4 hr 9 min 13 sec at 157.9 MB/s. These stats match perfectly with the latest notifications received.
I checked my last few parity check notifications, and they appear to be correct, referencing the duration and speed from the current operation rather than the previous operation. I suspect the bug only affects parity sync notifications and not all parity-related notifications.
I recognize that I'm reporting from v6.12.13 while v6.12.14 is available, but I don't see this issue mentioned in the .14 release notes as a bug fix, and I'm not going to do an unnecessary parity sync on my array to confirm a relatively minor bug. Perhaps someone who has recently done a parity sync (and has notifications enabled) on the latest version can confirm. Thanks for understanding!