im new to unraid after looking for a replacement of my ageing synology

i am running unraid on a Hp DL380e Gen8 the 14 disk variant
dual xeon E5-2450L
192gb ddr3 ecc buff/reg

HP P420 (non i) 2gb cache with new BBU operating in HBA/ IT mode

and the rest of the "default" hardware these units pack 
i have had the server do a full hardware diagnostic check which it passed without errors 

it seems to run somewhat unstable and i keep getting read errors and an increasing CRC error count on all connected disks.
3 disks were new/never used rest was was used prior to installing unraid but all had no errors to start with 
in my search for the problem i have already replaced the storage controller ( P420 in HBA/IT mode) but keep getting the same results, reading many suggestions to replace the sata cables i did the equivalent in the server by replacing the SAS cables with no change in results

before i start looking for a new backplane i installed treunas and WS 2019 just to rule out the os being the issue, with the other operating systems i dont see the CRC value increase or notice read errors 

are there known issues/incompatibility's with running unraid on this kind of hardware and or can it be a setting somewhere in unraid that needs changing?
any help is greatly appreciated 

13 minutes ago, novofine said:

with the other operating systems i dont see the CRC value increase

UDMA CRC errors are recorded in the drive firmware by the drive firmware when the drive receives inconsistent data based on checksum. Unraid itself has nothing to do with that, it just reports those by reading the same SMART report the drive gives to anything that asks for it.

 

Attach diagnostics to your NEXT post in this thread.

Diagnostics included

i know that the behavior i see with the UDMA CRC should or rather cant have nothing to do with Unraid tho this is what i think i am seeing

pegasus-diagnostics-20230113-0031.zip

after not finding any logical explenations for all the issues i decided to do a complete disassembly of the system,clean everything (more or less soaked everything in cleaning alcohol) and rebuild the server again.

 

eversince i had the system running again i had no more errors.