So I've been happy running unraid for a fair while now but I haven't run a parity check really since setup. Reading over a few threads here it seems a fair few of you do a monthly check based on a script so I think I'll implement that very shortly. However I do have a few quick questions regarding the best practices for parity checks.

 

I run with Sickbeard, Couchpotato and sabnzbd running from the cache drive (but with the cache drive feature disabled).

 

Is it safe to have there items running (and possibly downloading automatically) while the system is running a parity check?

What happens if data is copied to the shares during a parity check?

 

I can add to the script to unload the 3 applications first, run the parity check and kick the apps back to life but I don't want to unless its a requirement to make sure I don't break anything during the parity checks.

 

Also I'm planning on moving the parity to a 2TB drive very soon (as a starding point to move to 2tb drives in the end) - would it be wise to carry out a parity check before switching out to a new parity drive?

Just keep running as normal. Write to the array as you would normally.

 

This will all be fine whilst the parity check is running, parity will still be updated / calculated for new writes as required. Obviously the more you access the array during the parity check the slower the check will be.