JorgeB

This is a server board, no i5/i7 support, only Xeon, though I think I remember reading someone using them, but it's not guaranteed.

First thing would be to try running the RAM at the max officially support speed, without overclocking.

AFAIK there are no good x4 8port controller options.

Errors are logged as actual disk errors, though this is not 100% reliable, you can run an extended SMART test to confirm.

It's a known issue with Marvell controllers, this works sometimes.

There's always same data loss risk when repairing a filesystem, but usually nothing major with XFS.

I said the board's system event log, usually accessible in the BIOS or over IPMI.

That's a shame, and thanks for the update, also never forget for the future that you should have backups of anything important.

Possibly, a power issue/fluctuation might cause read/write errors.

Run xfs_repair without -n or nothing will be done.

SMART test passed on both disks, so currently they are OK.

Start here: https://forums.unraid.net/topic/46802-faq-for-unraid-v6/?do=findComment&comment=819173

It should.

Those are non ECC

That looks like an ECC RAM corrected error, there might be more information on the board's SEL (system event log)

It's a known issue with the installed firmware: Jun 2 12:13:07 macNAS kernel: mpt2sas_cm0: LSISAS2308: FWVersion(20.00.00.00), ChipRevision(0x05), BiosVersion(07.22.01.00) Update to 20.00.07.00

There are some recovery options here: https://forums.unraid.net/topic/46802-faq-for-unraid-v6/?do=findComment&comment=543490

It's even worse on the last diags, still read errors on disk5 and it ended up dropping offline, and there also read errors on disk2. You have some hardware issue, it might be cables/connection, controller/board, power supply, etc, you need to start swapping some hardware around to find out.

Like usual.

Please post the diagnostics: Tools -> Diagnostics so if nothing less you can see the hardware used.

Do that, and get the diags also, ideally twice, before and after the switch.

Possible but unlikely, at least with most plugins.

Possibly there's some compatibility issue then.

Constant ATA errors: Jun 2 17:30:36 Atlas kernel: ata1.00: status: { DRDY ERR } Jun 2 17:30:36 Atlas kernel: ata1.00: error: { ABRT } Jun 2 17:30:36 Atlas kernel: ata1.00: configured for UDMA/133 Jun 2 17:30:36 Atlas kernel: ata1: EH complete Jun 2 17:30:36 Atlas kernel: ata1.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0 Jun 2 17:30:36 Atlas kernel: ata1.00: irq_stat 0x40000001 Jun 2 17:30:36 Atlas kernel: ata1.00: failed command: READ DMA Jun 2 17:30:36 Atlas kernel: ata1.00: cmd c8/00:08:00:00:00/00:00:00:00:00/e0 tag 22 dma 4096 in Jun 2 17:30:36 Atlas kernel: res 51/04:08:00:00:00/00:00:00:00:00/e0 Emask 0x1 (device error) Jun 2 17:30:36 Atlas kernel: ata1.00: status: { DRDY ERR } Jun 2 17:30:36 Atlas kernel: ata1.00: error: { ABRT } Jun 2 17:30:36 Atlas kernel: ata1.00: configured for UDMA/133 Jun 2 17:30:36 Atlas kernel: ata1: EH complete Jun 2 17:30:36 Atlas kernel: ata1.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0 Jun 2 17:30:36 Atlas kernel: ata1.00: irq_stat 0x40000001 Jun 2 17:30:36 Atlas kernel: ata1.00: failed command: READ DMA Jun 2 17:30:36 Atlas kernel: ata1.00: cmd c8/00:08:00:00:00/00:00:00:00:00/e0 tag 23 dma 4096 in Jun 2 17:30:36 Atlas kernel: res 51/04:08:00:00:00/00:00:00:00:00/e0 Emask 0x1 (device error) Jun 2 17:30:36 Atlas kernel: ata1.00: status: { DRDY ERR } Jun 2 17:30:36 Atlas kernel: ata1.00: error: { ABRT } Jun 2 17:30:36 Atlas kernel: ata1.00: configured for UDMA/133 Try new cables (both power and SATA) and/or a different SATA port, if the same it's likely a disk problem.

You need o check the complete syslog (tools -> syslog) or post it.