I added a new parity drive about a month ago - did all the pre-clear checks etc. 

 

My machine keeps initiating a parity check after a reboot.  I've read somewhere this is because VMs don't shut down properly, so this time I made sure I closed them all before rebooting.  The parity threw up 1525 errors.  I read somewhere that this is normal after a reboot, so I ran it again and this time I got 1524 errors.

 

Should I be worried and replace the parity drive?

highlander-diagnostics-20171118-0008.zip

Edited November 24, 20178 yr by DZMM

Sync errors are normal if there's an unclean shutdown, you need to find out what causing them, diagnostics should be saved to your flash drive when unRAID forces a reboot/shutdown, upload those and maybe the reason will be visible.

Ahh thanks, I thought the errors were only for the first run and I didn't know unRAID saved the diags - here they are.

highlander-diagnostics-20171115-2338.zip

Edited November 18, 20178 yr by DZMM

Can't see what causing the forced shutdowns, there are some USB reset errors and these:

 

Nov 15 23:38:02 Highlander shfs: error: shfs_readdir: No such file or directory (2): fstatat: mongod.lock
Nov 15 23:38:05 Highlander shfs: error: shfs_readdir: No such file or directory (2): fstatat: mongod.lock
Nov 15 23:38:08 Highlander shfs: error: shfs_readdir: No such file or directory (2): fstatat: mongod.lock

 

But never seen them before and don't know what they are about.

thanks.  I've submitted to LT - see if if piques their interest

I've had two runs in a row with no errors, so I'm not worried anymore:

 

Notice [HIGHLANDER] - Parity check finished (0 errors)
Duration: 19 hours, 57 minutes, 14 seconds. Average speed: 111.4