Hello-- I was recently having issues with my motherboard's onboard sata controllers. (some data drives were showing link degradation and dropping link speed. My system was also experiencing hard reboots with increasing frequency which may have been memory related (I was pushing my onboard memory controller with 3x64gb DDR5 ECC UDIMMs, when I had it powered down I eased it back to 2x64. part of the issue was every time it would hard reboot it would come back up and start a new parity check which stressed the already struggling SATA controller situation so I couldn't complete a parity check before another hard reboot.

both of my parity drives were on the one of the motherboards onboard sata controllers (there is a ASM1064 and a PCH controller) they were on the ASM1064 and the drives with issues were on the PCH. I decided to move both of the drives having issues and the two parity drives to connect via my HBA instead. I powered down, moved the drives, and when I powered up it the two data drives I'd moved to the HBA connected ports came up fine, and the two parity drives came up as disabled due to errors. I have attached the diagnostics and have not done anything else to this point. I'm about to go to bed and my plan is to stop docker and VMs to minimize any writes/reads to the unprotected array and check back here for further guidance, which is much appreciateed!

mother-diagnostics-20260615-0059.zip

Not logged as a disk problem, do those disks share anything like a power splitter?

2 hours ago, JorgeB said:

Not logged as a disk problem, do those disks share anything like a power splitter?

They share a 4 drive backplane cage which is powered by 2 molex (off of a splitter) the entire backplane cage and splitter and power//data cables were recently replaced to rule out similar issues I had a few months ago with drives in these slots. I ended up leaving them empty at the time but perhaps falsely assumed they had been resolved.

I can move the parity drives back to their previous positions on the onboard controller or put two drives from then 24 bay disk shelf on the onboard controller and put the parity drives in the disk shelf, but I want to be very careful about order of operations to avoid any data loss or loss of parity if possible. I do believe all the drives are healthy and the issue is related to signal integrity, but I can't say for certain that multiple hard resets during parity checks with docker running did not create issues with the parity.

Appreciate your help!

I would change one or both to use different ports or cables, then do a new config and check "parity is already valid", then run a correcting parity check.

28 minutes ago, JorgeB said:

I would change one or both to use different ports or cables, then do a new config and check "parity is already valid", then run a correcting parity check.

Ok thank you. I will try this