clowncracker

It ended up being a power problem, I replaced the sata power cables and the problem is now resolved.

There has been no unclean shutdown since the last check. Both of those drives are on power splitters though, not sure if that makes a huge difference. https://www.amazon.com/gp/product/B012BPLW08/ref=ppx_yo_dt_b_asin_title_o01_s00?ie=UTF8&psc=1 Attached are my PSU specs. Just for my own knowledge, how did you identify the issues were disk9 and parity?

Any way to check which device it is referring to? That can be any drive or any cable, it's near impossible to troubleshoot.

Parity check started last night and I'm already at 873 errors. Parity check completed last month with no errors, so I was hoping someone could look at the diagnostics and troubleshoot the issue.

So I should leave that blank if I only want to keep 4 backups?

I want to only keep 4 backups, but the older versions are not getting deleted (5 copies are here). I want to make sure I have my settings set up correctly: Delete backups if older than x days:28 Keep at least this many backups: 4

That ended up being the issue, parity check and mover were running at the same time.

I think I found the issue, it looks like mover started running during the parity check. I thought that couldn't normally happen, but that explains the writes to drive 3 and the parity drives. I noticed the amount of free storage on my cache was increasing, so I paused the parity check and sure enough mover was running. Once mover is done I'll resume the parity check and see if that solves the problem.

I'd like to note that writes to parity and disk 3 are continually increasing every second:

I've started running my monthly non-correcting parity check and it was going smoothly until about an hour ago. Now the estimated finish is in ~30 days. It looks like a lot of writing is happening to disk 3, but I don't know what is happening:

@itimpi I opted to go for the correcting parity check since it was functionally the same. Did a second parity check afterwards and there were 0 issues. @trurl thank you for your help with the original issue, I wish I could give you both the solution.

So I shouldn't be deselecting any drives then? What is the functional difference between doing a sync by creating a new config and and just doing a correcting parity check?

Then won't @JorgeB's solution lead to permanent data loss? Aren't I just better off just doing a correcting parity check?

Just wanted to follow up.

Based on my comments what do you think about checking the parity drives? Do you think it's worth the risk, especially since they are essentially brand new? Something else I'm curious about. If I start the array with a new config and a disk missing, won't I just lose the data currently on the disk? Since it isn't on the array and it won't be emulated since the disk doesn't exist in the new array.