Hey guys, a few weeks ago, a refurbished drive I bought in Nov started giving SMART errors so I replaced it and today it finally finished the data rebuild. I am a bit confused though by the notification I got when I logged into the server this morning as it's showing the data rebuild was cancelled at 5:35AM and then a minute later that it completed successfully. Should I be concerned or is this what is supposed to show?

Attach Diagnostics to your NEXT post in this thread.

Note that those two errors are from different parts of the system.  Not sure which one is right, but I suspect the one from the Parity Check Tuning plugin is correct.   Have you had a cancelled one earlier?    The standard Unraid has been known to display the details of the previous one.

If you are on v6 notifications can be wrong, check on the main page, next to the array stop button.

10 hours ago, trurl said:

Attach Diagnostics to your NEXT post in this thread.

Attached. 

ur-server-diagnostics-20250119-2158.zip

10 hours ago, itimpi said:

Note that those two errors are from different parts of the system.  Not sure which one is right, but I suspect the one from the Parity Check Tuning plugin is correct.   Have you had a cancelled one earlier?    The standard Unraid has been known to display the details of the previous one.

 

Yes I did have one prior to this, I was testing to see if the rebuild would pause as stated on this post when I was at about 3%. I figured it was barely starting out so wasn't a huge loss in case it didn't work. For those who come upon this in the future, it will not continue from where you left off, it started me back up at 0% once the system came back online.

2 hours ago, crespoh69 said:

For those who come upon this in the future, it will not continue from where you left off, it started me back up at 0% once the system came back online.

Standard Unraid will always restart array operations from the beginning.

 

Did you have the option set in the Parity Check Tuning to continue array operations on next array start?   If so it will try to restart an active array operation as long as the array shutdown cleanly.

Here are the relevant lines from your syslog

Jan 19 02:18:29 UR-SERVER kernel: md: recovery thread: recon D3 ...
Jan 19 05:34:08 UR-SERVER kernel: md: sync done. time=11739sec
Jan 19 05:34:08 UR-SERVER kernel: md: recovery thread: exit status: 0
Jan 19 05:36:30 UR-SERVER Parity Check Tuning: Parity Sync/Data Rebuild finished (0 errors)
Jan 19 05:36:30 UR-SERVER Parity Check Tuning: Elapsed Time 1 day, 11 hr, 19 min, 46 sec, Runtime 1 day, 11 hr, 1 min, 44 sec, Increments 2, Average Speed 158.6 MB/s
Jan 19 05:36:30 UR-SERVER Parity Check Tuning: Send notification: Parity Sync/Data Rebuild finished (0 errors): Elapsed Time 1 day, 11 hr, 19 min, 46 sec, Runtime 1 day, 11 hr, 1 min, 44 sec, Increments 2, Average Speed 158.6 MB/s (type=normal link=/Settings/Scheduler)

exist status 0 means it was successful.