JorgeB

You can try installing v6.11.0-rc4, newer kernel might help, if not not much more you can do other than suppressing the error, unless you are wiling to use a different board (or devices).

Looks like just a controller with two Asmedia 1164 chips, it *should* work fine.

This is SAS2, so having a SAS3 HBA won't change the link speed, it will still help if your board/CPU supports PCIe 3.0, same as a SAS2 HBA with PCIe 3.0 support would, like for example the 9207-8i.

It's a possibility if nothing happens when you push it, easy to test if there's a reset button, just plug that one, or use something to short the pins.

Taking another look at this with more time, I see this on boot: Aug 25 18:48:25 Moulin-Rouge kernel: BTRFS: device fsid 46c809d9-2d8f-48ad-be38-dff41668218c devid 1 transid 2879 /dev/sda1 scanned by udevd (752) ... Aug 25 18:48:25 Moulin-Rouge kernel: BTRFS: device fsid 46c809d9-2d8f-48ad-be38-dff41668218c devid 2 transid 814 /dev/sdc1 scanned by udevd (765) sda was the old cache device, sdc is current parity, note that sdc is device 2 from a pool with sda, trans id differ so it means they were in a pool some time ago, not just before this boot, while it's still a bug looks like the issue happened after a very unusual sequence of events, i.e., parity being in a pool with a former pool device.

RAM in the diags shows as single rank, so 2666MT/s is OK, see that power supply idle control is correctly set.

Set Unraid to use DHCP and see if it gets an IP address from the DHCP server.

Don't think so, those are very common with Unraid, I have some myself. Do you have another board/CPU combo you could test with?

Yes, it's an option in the Unraid boot menu, also are you using another browser other than Firefox?

If you get better speeds with another laptop cannot see how Unraid could be the problem, could be your Wi-Fi router/ap, you can run iperf between various computers to test.

If you haven't yet try with a different browser, and make sure no ad-block are enabled.

Try that device in a different slot, but if it's still not detected it's likely a device problem.

Yep, that looks like just the controller/drives waking up, and normal with the sleep S3 plugin.

For the stability issues see here: https://forums.unraid.net/topic/46802-faq-for-unraid-v6/?do=findComment&comment=819173

Does it happen without running VMs?

Do you see the same issues with the system devices page if you bound the same devices?

I don't use macvlan/ipvlan but from my understanding they work similarity, i.e., you just need to change the custom network type and dockers with a custom IP address should remain working.

Unlikely that it would be incompatible with 3 very different kernels.

Fist you need to fix the Unraid boot problem, photo shows USB disconnects, try a different USB port, ideally USB 2.0, if that doesn't help try a different flash drive.

It won't for this one. Which Intel expander? Also what model disks?

I would expect support as soon as the Linux kernel supports them, last I read some experimental support is expected starting with kernel 6.1.

Try v6.9, but that and the fact that the Unraid driver is crashing with both v6.10 and v6.11 makes me suspect a hardware issue.

It might have been, but it's not now, would not recommended trying to rebuild a disk or fix any filesystem with constant disk errors, there's a chance of making things worse.

Btrfs is already detecting some data corruption, for a new server not a good sign, start by running memtest.

This suggests a plugin problem, remove all plugins and than add one by one.