SUGGESTION: We need a good guid in the FAQ to handle parity issues. Some sort of flow to follow. 

 

First, there were power issues and though I have a UPS, I cannot assure that shutdown wasn't dirty. IIRC, there were some. As of now, UPS load is around 150W with a runtime of 40+ minutes so shutdowns SHOULD be graceful going forward...can't recall what load I had before, been doing some tweaks. (Crypto mining.)

 

No SMART errors, but I'm running extended tests on all my drives. 

 

I'm Dynamix File Integrity is building now. I've been meaning to do that.

 

Sorry, there's no log yet since I've had to shutdown for power issues since the last parity error.

 

Schedule is to run on Sundays. In October, Sunday was 3rd/10/17/24/31. 

 

So, assuming the 16th was a power issue, and maybe I ran the 25th accidentally to correct but that means 7 popped up on the 29th.

 

But none appeared between the 29th and 31st.

 

The 16th must have been for power.

 

My server has ECC so I'm guessing this is not a RAM issue but a dirty shutdown issue.

 

I have two parity disks.

 

When File Integrity is done, I'll run a check and get some logs.

 

 

Log:

 

 

The complete File Integrity hash build should be a good test to see if anything's truly wrong since that'll read every file on the array, correct?

 

Backups to the NAS have seen no big issues, so that's good.

 

 

1 hour ago, RealActorRob said:

Schedule is to run on Sundays.

Seems excessive to me. Most run monthly, some less often than that.

5 hours ago, trurl said:

Seems excessive to me. Most run monthly, some less often than that.

I don't spin down disks, probably would increase wear if I did because I span disks for two storj nodes.

 

If storj takes off, it'd be somewhat harder to increase storage I'd think if I limited it to certain disks.

 

One thing that would make this easier is if unraid had a feature to unspan directories. Would also help to remove a disk without losing parity.