So when I did my parity check this month I had an issue with a drive connection resetting so it took longer than normal.  When i completed the parity check it send a notification (telegram) that said it took "1 day, 9 hr, 4 min, 14 sec".  In reality it took "1 day, 17 hr, 29 min, 10 sec" and I can see that clearly in the history.  Yesterday I went to address the drive that was resetting  connection but since I had a warm spare already in my machine I just used it to rebuild.  The rebuild notification reported "1 day, 17 hr, 29 min, 10 sec" was the completion time.  In reality it took "8 hr, 20 min, 35 sec" as it is clearly listed in the history.  It seems to be sending the previous time.  Is this a known bug?

Edited April 7, 20242 yr by Gragorg

1 hour ago, Gragorg said:

So when I did my parity check this month I had an issue with a drive connection resetting so it took longer than normal.  When i completed the parity check it send a notification (telegram) that said it took "1 day, 9 hr, 4 min, 14 sec".  In reality it took "1 day, 17 hr, 29 min, 10 sec" and I can see that clearly in the history.  Yesterday I went to address the drive that was resetting  connection but since I had a warm spare already in my machine I just used it to rebuild.  The rebuild notification reported "1 day, 17 hr, 29 min, 10 sec" was the completion time.  In reality it took "8 hr, 20 min, 35 sec" as it is clearly listed in the history.  It seems to be sending the previous time.  Is this a known bug?

Yes, and has been present for the several releases now.