After a fresh install, parity-sync started yesterday. It took around 17 hours for it complete. I left it go on overnight. When I came to check today. I had this notification waiting for me saying 'Parity-Sync finished' however, it was colored yellow which is for warnings. On further checking in archived notification is find that the description of said notification is 'Canceled'. I don't understand why it is this way. I never canceled the sync. Additionally, the device status says operation normal under 'Array Devices' section and 'Array is valid' under the 'Array Operations' section.

 

Does the 'canceled' description mean I have sync again? 

 

 

 

Archived Notifications:

Array Devices section:

Array Operations section:

attach diagnostics to your NEXT post in this thread

@trurl Here are the Diagnostics. I started 'Parity-Check' just to be safe and its notification also came as 'warning'. You can see in the screenshot above too. The notification from when 'Parity-Sync' started, its description is also 'Warning'.

Maybe notifications about any action related to parity come up as warnings, what do you think?

astatine-diagnostics-20221225-2252.zip

Edited December 26, 20223 yr by Astatine

On 12/25/2022 at 10:14 PM, trurl said:

attach diagnostics to your NEXT post in this thread

Hey trurl, I attached the diagnostics in my prev. post

I had this happen as well and was confused by it. It was my first parity sync on a new array, FWIW. It appears to be healthy and in-sync, but seeing a warning that says "Canceled" instills a tiny bit out doubt. Attached diagnostics.

plexnas-diagnostics-20230106-0627.zip

Jan  5 09:50:20 PlexNAS kernel: mdcmd (61): nocheck cancel
Jan  5 09:50:20 PlexNAS kernel: md: recovery thread: exit status: -4
Jan  5 09:50:39 PlexNAS kernel: mdcmd (62): check correct
Jan  5 09:50:39 PlexNAS kernel: md: recovery thread: recon P ...
Jan  6 03:40:01 PlexNAS  crond[1122]: exit status 1 from user root /usr/local/sbin/mover &> /dev/null
Jan  6 05:09:29 PlexNAS kernel: md: sync done. time=69530sec
Jan  6 05:09:29 PlexNAS kernel: md: recovery thread: exit status: 0

Looks like it was restarted and completed 

Hello

 

I just had this problem on a new server build after copying data over to new server. I started parity syn late yesterday an it finished per the logs, but the syn was all so canceled. So unraid wants to rerun parity syn. If the fix is just rebooting the server and rerun parity syn, I guess I will try that for tonight, but the question remains why is this happening is this a bug with 6.11.5?

 

2 hours ago, svargas said:

it finished per the logs

Post that log

Here you go... In my archive norification msg Notice [LEGO99] - Parity-Sync finished (0 errors) this morning Thanks for the help

lego99-diagnostics-20230426-1307.zip

Apr 25 19:27:51 LEGO99 kernel: mdcmd (37): check 
Apr 25 19:27:51 LEGO99 kernel: md: recovery thread: recon P ...
...
Apr 25 19:28:15 LEGO99 kernel: mdcmd (38): nocheck pause
Apr 25 19:28:15 LEGO99 kernel: md: recovery thread: exit status: -4
...
Apr 25 19:28:27 LEGO99 kernel: mdcmd (39): check resume
Apr 25 19:28:27 LEGO99 kernel: md: recovery thread: recon P ...
...
Apr 26 07:00:04 LEGO99 kernel: mdcmd (44): nocheck cancel
Apr 26 07:00:04 LEGO99 kernel: md: recovery thread: exit status: -4
...
Apr 26 07:47:41 LEGO99 kernel: mdcmd (52): check 
Apr 26 07:47:41 LEGO99 kernel: md: recovery thread: recon P ...
...
Apr 26 07:48:06 LEGO99 kernel: mdcmd (53): nocheck cancel
Apr 26 07:48:06 LEGO99 kernel: md: recovery thread: exit status: -4

Doesn't look like it has run to completion (exit status: 0)

 

Post a screenshot of Main - Array Operation

The problem is I got notification that it finished and was complete. I did reboot the server per your suggestion yesterday and kick off another parity syn this time it did complete as it should of and my data is protected. If this is some glitch would happens when I run monthly parity syn's will I need to run it twice too. Thanks for taking the time to review my logs....

Similar.

 

06-07-2023 22:17Unraid Parity-CheckNotice [BLACKTOWER] - Parity-Check finished (0 errors)Canceledwarning

 

I didn't cancel it but my server locked (no hardware issues noted yet, but my usb stick was corrupted a couple of weeks ago)

 

Dirty bit set 'some corruption' warnings etc.

 

It appears to me, yet AGAIN that the USB stick is the weak link in Unraid.

 

For God's sake, please add some sort of redundancy at least to this weak link, say, it checks the USB stick against 2 other mirror files of it on the disk as a boot stick check.

 

 

I have similar problem mine get started and canceled 4 times. 

and the parity check history shows only two of them.

 

For 4 days my disk was spinning for 19 hrs,  i didn't canceled. And the logs doesn't tell anything.

 

x99-diagnostics-20230728-2136.zip

 

PS: So today was the same thing happened.. so after more checking i found where the problem was.

 

 

Who in the right mind will use "Every day" literally in the context of other settings and the specific task. Here "Every Day" should mean "Any day" - of the "Last week". And interestingly this is the only options that doesn't have an explanation.

Edited July 29, 20232 yr by ilarion

Been getting the same confusing alerts for my monthly parity check. Server has an uptime of 20 days, parity check finished 1 day ago.

 

 

unraid-diagnostics-20230803-0837.zip

Not directly relevant to your issue, but if you install the Parity Check Tuning plugin then even if you have it set to be disabled it will still mean that you get more detail in the Parity History and the timings there should be accurate as it uses a different mechanism to core Unraid to track what they should be.

mine is doing the same thing. Does the same thing for me, cancelled but I didn't even cancelled it.

prometheus-diagnostics-20240724-1404.zip