JorgeB

Board manual may show that, but not always, worst case do it by trial and error. No, they should be per slot.

Lots of call traces logged, but unclear to me what cause them, was this a one time thing or is the server crashing regularly?

Yes, do a new config (Tools - New config)

Looks like all 3 devices have the same btrfs UUID, that should never happen unless they were used together in the past: Apr 15 14:33:08 Mongo emhttpd: Label: none uuid: d0989cc1-462a-4a25-ac4c-b3fbb1d27a4c Apr 15 14:33:08 Mongo emhttpd: #011Total devices 2 FS bytes used 95.33GiB Apr 15 14:33:08 Mongo emhttpd: #011devid 1 size 931.51GiB used 100.03GiB path /dev/nvme1n1p1 Apr 15 14:33:08 Mongo emhttpd: #011devid 2 size 931.51GiB used 82.03GiB path /dev/sdi1 Apr 15 14:33:08 Mongo emhttpd: #011devid 3 size 931.51GiB used 100.03GiB path /dev/nvme0n1p1 Physically disconnect /dev/sdi and post new output of btrfs fi show

This is the new key for this flash drive or for the old one?

Constant errors with sdr and sdr cache devices, check/replace cables, or try connecting then to a different controller and post new diags.

The former. Yes. Yes, and they are different and not interchangeable. Yes.

parity2 dropped offline, this is usually a power/connection problem, or weak/failing PSU.

Run it again without -n, and if it asks for -L use it.

9267 is a RAID controller, recommend getting a HBA instead, like the 9207, if your current controller is not RAID then it should be plug and play.

Go to Tools - Registration, if it's not yet correct copy the new key manually to the /config folder and then reboot.

Yes, use -L

You can try copying only super.dat and the pools folder from the old flash, that would take care of the assignments, and it should not cause boot issues, but if it does see here: https://docs.unraid.net/unraid-os/manual/changing-the-flash-device/#what-to-do-if-you-have-no-backup-and-do-not-know-your-disk-assignments

You just enable it in the BIOS for the slot you want, I have the similar X11SPL-F and IIRC all CPU PCIe slots support bifurcation. Edit: they are not that similar, different CPU family, check the BIOS for bifurcation support, would still expect it to be supported in that board.

Because it's not logged as a disk problem and SMART for both disks looks fine, also two disks being affected at the same time also points to not a disk problem, so the most logical explanation is a power/connection issue.

Post new diags.

No, it's a 6 port controller natively, but there are models with 8 or 10 ports, those will have a PM.

Please double check, since based on the syslog it does look like there is a port multiplier, for 6 ports you can get an Asmedia 1166 based controller, with just 6 ports, not more.

OK, if there are only four ports it doesn't have a SATA port multiplier, those are a known issue, but please double check, since based on the syslog it does look like there is a port multiplier, if there isn't, it could have some defect, since those Asmedia controllers usually work well with Unraid.

Looks more like a controller issue, does the addon controller have just 4 ports or more?

You can unassign it.

You have two NICs on the same subnet, change the 2nd one to a different one, also remove the gateway from the 2nd NIC, only eth0 should have a gateway configured.

Post the output of btrfs fi show

Constant call traces, start by running memtest, if nothing is found, and because memtest is only definitive if it finds errors, try with just one stick of RAM, if the same try with a different one, that will basically rule out bad RAM, if issues persist, another thing you can try is to boot the server in safe mode with all docker containers/VMs disabled, let it run as a basic NAS for a few days, if it still crashes it's likely a hardware problem, if it doesn't start turning on the other services one by one.There are constant call traces, start by running memtest.

Try checking the filesystem again but without -n