Hi,

The last days I moved files from some disks to other disks with UnBlancer to reduce ne number of disks. All went fine and all data I checked where accessible. 

Today I changed my case and psu from one with a backplane to one without. Used the same board rest of hardware.

Before I started the array I created a new config an reorder the drives in the array.

 

After a lot of changes in the last days I decided to make a parity check. Just in case. Now I'm sitting here after about 7 % of check with over 60 mio (yes million) sync errors!

I attached the diagnostics. I cannot see anything in my syslog. But maybe you guys.

 

Hope you could help.

 

Regards.

tower-diagnostics-20220105-1725.zip

4 minutes ago, teqqyde said:

created a new config an reorder the drives in the array

Re-ordering drives invalidates parity2 and changing the number of drives invalidates parity1.   If you clicked the Parity is Valid checkbox to avoid immediately rebuilding parity then the behaviour you are seeing will be expected.

Thanks.

i read that in older threats but with significantly lower numbers. That’s what makes me a bit nervous.

 

Then I let the kind of rebuild run.