I have my parity check (16tb) segmented so that it takes a few days (from midnight to 5am), it was working fine and was at about 50% complete until I started precleaning two 16tb hard drives.

I thought it was fine to preclear during parity check, since the disks aren't part of the array. I checked the server this morning and saw that it didn't give an update on % complete and says "error code: aborted"

 

On the Parity History it says: 

I'm using the Unassigned Devices Preclear Docker and doing both at once.

 

Is this because i was preclearing drives when parity started at midnight or is something else going on?  Can i continue the parity check or do i need to start it from beginning 

attach diagnostics to your NEXT post in this thread

46 minutes ago, trurl said:

attach diagnostics to your NEXT post in this thread

Here you go.  Thanks for taking a look. 

020923TOWER.zip

 

I didn't notice at first, but i noticed that i got a notification that check finished 

Unraid Parity-Check: 02-04-2023 10:55 PM

Notice [BACKUP] - Parity-Check finished (0 errors)
Duration: 22 hours, 42 minutes, 59 seconds. Average speed: 171.2 MB/s

 

Is this a glitch?

Edited February 9, 20233 yr by danimal86

Anyone know anything about this?

The syslog doesn't have anything about a parity check, maybe the server was rebooted?

9 minutes ago, JorgeB said:

The syslog doesn't have anything about a parity check, maybe the server was rebooted?

 

On 2/9/2023 at 10:14 AM, danimal86 said:

Unraid Parity-Check: 02-04-2023 10:55 PM

This timestamp is before reboot.

2 hours ago, JorgeB said:

The syslog doesn't have anything about a parity check, maybe the server was rebooted?

I did shut the system down to install the new drives, but was up and running well before the segmented parity check would have continued (at midnight for me)

 

1 hour ago, trurl said:

 

This timestamp is before reboot.

My preclear is done.  

On the dashboard under Parity tab it states:

Last check incomplete on Tue 07 Feb 2023 05:00:01 AM PST (three days ago)
 Error code: aborted
 Finding 0 errors

 

I'm running parity checks quarterly, so i'm due.  I'm guessing i should add the precleared drives to the array and run a parity check manually.  

 

Just out of curiousity, i thought it was fine to preclear drives during a parity check.  Is that not the case?  

I've included an updated diagnostic in case anything has changed.  

tower-diagnostics-20230210-0907.zip

Edited February 10, 20233 yr by danimal86

11 minutes ago, danimal86 said:

i thought it was fine to preclear drives during a parity check.

Should be.

 

 

1 minute ago, JorgeB said:

Should be.

 

 

was it the restart or the preclear that aborted the parity?

A restart would always abort the parity check.

18 minutes ago, JorgeB said:

A restart would always abort the parity check.

Even the segmented/scheduled parity check?

Yes, but I believe the parity check plugin can continue after a reboot.