I have been trying to do parity sync for a week now and every time I do one I get errors on my drives. When I run my docker containers or run mover. I have changed all my SATA cables to brand-new ones and still errors.

Please post the diagnostics.

Here is my diagnostics.

animeking1987-syslog-20231222-1859.zip

That is not the diagnostics - just the syslog.

 

However it is enough to show that you are getting errors on multiple drives.   Since you say you have checked the cabling (I assume this is the SATA cabling?) are you sure you do not have a power related issue?   Failing that what else is common to multiple drives?

Those are not the diagnostics, just the syslog, based on that looks like a controller issue, full diags may give a better idea.

My apologies, here is my diagnostics. Also @JorgeB I was considering it could be my PS and upgrading it but I did not know if that was the case 

animeking1987-diagnostics-20231222-1327.zip

Why do have so many different sized disks in your cache pool?

 

Is gamingking2 USB?

For the cache pool, I was new and will be rebuilding it to two 4TB SSD's next month and getting rid of all those cache pools. The gamingking is for my gaming VM

USB not recommended for array or pools for many reasons.

All but one of the affected disks are using a controller with a SATA port multiplier, that can be a problem, and it usually is, but one of the disks is using a different controller, so could also be power related.

@JorgeB

I have changed the power supply from 750 to 1000W. Hopefully that fixes the issue. Can i use my docker containers while parity sync is running? Or is it best practice letting it finish first? 

Edited December 23, 20232 yr by animeking1987

8 minutes ago, animeking1987 said:

Can i use my docker containers while parity sync is running? Or is it best practice letting it finish first? 

You can but any access to the main array will have degraded performance.

Ok I will wait then until parity finishes