JorgeB

Syslog starts over after every boot, you can enable the syslog server and post that if it happens again.
 
Probably unrelated but I do see some PCIe errors, try this first:
 
https://forums.unraid.net/topic/118286-nvme-drives-throwing-errors-filling-logs-instantly-how-to-resolve/?do=findComment&comment=1165009
 
 

That module is likely not included, suggest making a feature request and mention why you want that included.

All disks dropped offline, most probable reasons would be a power/connection issue or the controller.

That disk doesn't look good, you can run a long SMART test, but it has a lot of reallocated sectors, I would replace it even if it passes the test.

That looks more like a flash drive problem.

Delete/rename /boot/config/network-rules.cfg and reboot

The constant OOM issues are being caused by Jellyfin, check its config or limit it RAM usage.

Disk was still connected to the Marvell controller, those sometimes don't work great, if you have a free port in a different controller try using that one, if not you can also replace cables to rule that out.

Check filesystem on disk10, run it without -n

That looks like a flash drive problem, try replacing it.

Speed can slow down as zfs gets more fragmented, and in my experience those speeds are withing the normal for copies inside the same pool.

Try a manual update:
https://docs.unraid.net/unraid-os/manual/upgrade-instructions/#manual-upgrade-or-downgrade

Sep 4 04:39:30 unRAID kernel: BTRFS error (device sdc1): block=1054228480 write time tree block corruption detected  
Pool went read-only, rebooting should make it read/write again, but note that this error usually means a RAM problem, and running a Ryzen CPU with overclocked RAM like you have is known to cause data corruption, which was also being detected by btrfs, so see here and also recommend running memtest.

That call trace is not complete, but looks like it may be macvlan related, upgrade to latest stable, since macvaln with bridging is no longer an issue there.

Please use the appropriate support thread for that container:
 

Both options will accomplish the same results.

Wipe the device with
blkdiscard -f /dev/nvme0n1 reboot and post the diagnostics if the format still fails

Unraid licenses cannot be transferred, so you'd need to get a new one.

Should be harmless

You can remove it as long as the pool is raid1, in doubt post the diags:
 
https://forums.unraid.net/topic/46802-faq-for-unraid-v6/?do=findComment&comment=480418
 

See if that disk works in another PC, or a different disk with the server.

https://forums.unraid.net/topic/136889-plugin-tailscale/?do=findComment&comment=1459627
 

It uses this:
https://mirrors.edge.kernel.org/pub/linux/kernel/people/hpa/raid6.pdf
 
The latter, IIRC in part because of this from the link above:
 
 

You are using the mover tuning plugin, so you should uninstall it and retry, or if it's not working as expected, ask in the plugin support thread.

These usually mean a bad flash drive:
 
Aug 29 12:59:58 media kernel: SQUASHFS error: xz decompression failed, data probably corrupt Aug 29 12:59:58 media kernel: SQUASHFS error: Failed to read block 0xe4bbdc: -5 Aug 29 12:59:58 media kernel: SQUASHFS error: xz decompression failed, data probably corrupt Aug 29 12:59:58 media kernel: SQUASHFS error: Failed to read block 0xe4bbdc: -5 Aug 29 12:59:58 media kernel: SQUASHFS error: xz decompression failed, data probably corrupt  
Possibly also a corrupt docker image, but you need to fix the flash issue first