JorgeB

For the docker containers you just need to copy the appdata folder, docker image can be recreated and the rest is in the flash drive.

Try a different cable/switch.

@dlandoncan you take a look at the plugin to see if it can cause this?

Did it crash during or right after downloading or when it was seeding for a while?

Run memtest, if no issues are found boot the server in safe mode and run it like that for a couple of days, keep the syslog server enabled.

If it gets stuck in the same place I would start suspecting the RAID controller, in that case try using the onboard SATA or HBA, ideally an LSI, if either is a possibility.

You can try resetting LAN config to defaults and start over, could be related to some old setting.

Yes, just using that setting and keeping c-states enabled works the same, before that setting was available the only solution was to disable c-states globally.

Macvlan causing server crashes is quite common, there's one or more cases every week, most users don't have any issues after switching to ipvlan, but sometimes it doesn't work as before, there have been a couple of other cases reported, but like mentioned can't really say what the problem could be as I don't use custom networks, you can try to simplify your config as much as possible even if it's just for testing to try and find what setting is causing the issues.

Sorry, difficult for me to help with that, I don't use custom networks, you might try to start one container at a time to see if you can find the culprit.

It's not normal for a disk to get disabled without parity, but it's been known to happen sometimes.

Unraid cannot emulate a disk without parity, do a new config (Tools -> New config), keep all assignments and start he array, it should then mount, if it doesn't post new diags.

Yep, looks like the newer firmware was pulled, so keep that one for now.

When it happens to multiple users it suggests a MyServers problem, it should be fixed soon.

The idea for the when it gets implemented in Unraid is not to use just a script, though that would still be better than nothing, but basically monitor the output of "btrfs device stats /mountpoint" (or "zpool status poolname" for zfs) and use the existing GUI errors column for pools, which currently is just for show since it's always 0, to display the sum of all the possible device errors (there are 5 for btrfs and 3 for zfs), and if it's non zero for any pool device generate a system notification, optionally hovering the mouse over the errors would show the type and number of errors like we have now when hovering the mouse over the SMART thumbs down icon in the dash. Additionally you'd also need a button or check mark to reset the errors, it would run "btrfs dev stats -z /mountpoint" or "zpool clear poolname".

It will if you use the physical console, not SSH, you'd need screen or similar. rsync -avX /path/to/source/ /path/to/dest/

I would suggest mounting the Synology share over SMB or NFS with the UD plugin then use rsync.

Intel usually specified the max speed with all sockets populated, so for example CPUs that support DDR4 3200 support it with 4 DIMMs, for Alder Lake with DDR5 this is no longer true: Cannot find this table for Raptor Lake but I would assume there will also be limitations since max speed is now 5600 MT/s with DDR5

That would be great, I think LT is going to implement better pool monitoring in the future, possibly when zfs support is added, but not yet confirmed.

That will work.

The other NIC is being detected and the driver is loaded, it's not detecting a link though, and it's in a bond with eth0, do you intend to use them together?

The write errors suggests one of the cache devices dropped offline before, use the script in the FAQ to monitor the pool for the future, but there are other issues: write time tree block corruption detected This usually indicates a RAM problem or other kernel memory corruption, and you are running the RAM above the officially supported speeds and that is known to corrupt data, see here and adjust accordingly.

Nothing obvious, though the server has not been up for long, was it already showing some issues?

That's the regular syslog, and it starts over after every boot, did you enable the syslog server?

Looks clean so far, try syncing parity again.