JorgeB

Yes.

The OS loads to RAM during boot, then runs from there, so no.

Run a parity check and see if it goes to the end without issues.

Sorry, no more ideas then.

Either should be OK, JMB582 is good, don't known those exact models but as long as they are normal quality it's fine, supporting port multipliers is OK, using them is what's not recommended.

There's something writing to the array, it's normal for the rebuild to slow down by a lot during any array access.

Unraid driver is crashing, this sometimes happens with some kernel/hardware combinations, try upgrading to v6.10-rc2

Nothing obvious that I can see, though it's reading from various array devices, is this expected? Does it getter better if you stop whatever is reading them?

Post new diags after booting in safe mode, there was a lot of noise from plugins in the other ones.

If Docker/VM services are using the cache pool disable them, unassign all cache devices, start array to make Unraid "forget" current cache config, stop array, reassign all 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), re-enable Docker/VMs if needed, start array.

Not sure, it's something I've never used, you can ask in the linked thread.

Possibly this: https://forums.unraid.net/bug-reports/prereleases/69x-610x-intel-i915-module-causing-system-hangs-with-no-report-in-syslog-r1674/?do=getNewComment&d=2&id=1674

Is it the same if you boot in safe mode?

If the disk is healthy I would suggest re-creating that filesystem, after backing it up.

Best for this would be a Xeon platform, usually most slots can be bifurcated, and the CPU as more lanes, e.g. on one of my servers I have a Xeon 4114 Silver with 48 lanes, board has 6 CPU slots and all can be bifurcated to x4, I could use 14 NVMe devices with that combo, (2 would go through the PCH).

Not seeing anything out of the ordinary.

According to Intel yes: Up to 1x16+4, 2x8+4 https://ark.intel.com/content/www/us/en/ark/products/134599/intel-core-i912900k-processor-30m-cache-up-to-5-20-ghz.html

Yes, but you should still have console access, using a keyboard and monitor/IPMI or SSH.

Please use the existing plugin support thread:

Log is spammed with USB related issues, reboot and post new diags after array start.

Jan 11 03:38:06 unRaid kernel: macvlan_broadcast+0x10e/0x13c [macvlan] Jan 11 03:38:06 unRaid kernel: macvlan_process_broadcast+0xf8/0x143 [macvlan] Macvlan call traces are usually the result of having dockers with a custom IP address, upgrading to v6.10 and switching to ipvlan might fix it (Settings -> Docker Settings -> Docker custom network type -> ipvlan (advanced view must be enable, top right)), or see below for more info. 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/

Unraid driver crashed, try updating to v6.10-rc2

Jan 10 21:46:44 Tower kernel: BTRFS warning (device sdc1): chunk 69882347520 missing 1 devices, max tolerance is 0 for writable mount Pool can't mount without the missing device since one or more chunks are not redundant, check connections and power the server back up to see if the other device comes back online, if yes post new diags after array start.

Basically the only option you have is to run it again without -n, you should also have backups of anything important, Unraid or any RAID solution is not a backup.

After starting in normal mode get the syslog from the console: cp /var/log/syslog /boot/syslog.txt