JorgeB

1st LSI should be updated to latest firmware, this one has known issues: Jun 29 10:04:09 Zeus kernel: mpt2sas_cm0: LSISAS2008: FWVersion(20.00.04.00), ChipRevision(0x03), BiosVersion(07.39.02.00) 2nd one is fine: Jun 29 10:04:09 Zeus kernel: mpt2sas_cm1: LSISAS2008: FWVersion(20.00.07.00), ChipRevision(0x03), BiosVersion(07.39.02.00)

Again you can't use more lanes than the available ones, if for example the board shares lanes between an M.2 slot and a PCIe slot you can use one or the other, never both at the same time, it just won't detect the second device/controller.

You can't do this, you can't use more PCIe lanes than there are available.

Yes, it also reads all the disks during a parity check.

There are still errors on disk14, for now only on that one, still no point in continuing with the parity sync.

You appear to be using the same controller, one another identical Marvell based one, which as mentioned are not recommended for Unraid.

Don't see anything logged that would explain the crash reason, could be a hardware issue.

Does it get better if you stop all writing to disk8? Dashboard CPU usage will show i/o load.

Can't think of anything Unraid related that would explain the low read speeds, maybe the disk was doing some housekeeping at the time it was tested with diskspeed.

This, parity check is the same as an extended SMART test, so a good way to see if there are more issues.

Reads look normal, what you're experiencing might just be the normal SMR write penalty.

It's never a good sign, and those disks are SMR so they can always be slower for writes, but several of this model have been known to be extremely slow, even for reads, diskspeed docker might show if that is the case for that one.

If you changed hardware delete/rename /config/vfio-pci.cfg in the flash drive.

That looks like a disk problem.

Jun 26 19:35:05 Server kernel: macvlan_broadcast+0x10e/0x13c [macvlan] It's still related to this: https://forums.unraid.net/topic/70529-650-call-traces-when-assigning-ip-address-to-docker-containers/ See also here: https://forums.unraid.net/bug-reports/stable-releases/690691-kernel-panic-due-to-netfilter-nf_nat_setup_info-docker-static-ip-macvlan-r1356/

Another thing you can try it to boot the server in safe mode with all docker/VMs disable, 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.

The report should mention what and why is failing, if there are no errors it could be temp related.

AFAIK those MegaRAID controllers can't be flashed to IT mode, look for HBAs, like the 9211-8i, 9207-8i, etc, no MegaRAID models, except the 9240-8i, that one can be flashed.

Should work fine, I have the similar X11SSM-F which IMHO is a better option, the M.2 slot on the other one is only x2, you have an extra x4 slot in this one, that can be used with an M.2 adapter at full speed if wanted.

This.

Syslog starts over after every reboot, when there are issues you want to save the diags before rebooting.

Should work, make sure HBA is in IT mode.

This sounds like a hardware issue, nothing being logged at the time points to the same, very difficult top diagnose remotely, basically you need to start swapping hardware, easiest thing to test is using only one DIMM at a time, if that doesn't help and since you already replaced the board PSU next thing would be using a different board.

You can't remove drives from a pool using single profile with the GUI, only manually. You can try this on the removed drive (ckeck that it's still the correct device): btrfs-select-super -s 1 /dev/nvme1n1p1 Then reset the pool config in Unraid: Unassign all cache devices, start array to make Unraid "forget" current cache config, stop array, reassign both cache devices (there can't be an "All existing data on this device will be OVERWRITTEN when array is Started" warning for any cache device), start array and see if it mounts.