JorgeB

Docker image is corrupt, delete and re-create: https://docs.unraid.net/unraid-os/manual/docker-management/#re-create-the-docker-image-file Also see below if you have any custom docker networks: https://docs.unraid.net/unraid-os/manual/docker-management/#docker-custom-networks

Enable mover logging, run the mover, look at the syslog. Reboot, if it still gets created it's pretty sure there's a container mapped to that.

Check filesystem on disk1, run it without -n, and if it ask for -L use it.

That looks like a hardware problem, but it can be difficult to troubleshoot remotely, if you have some more spare parts you can try besides the PSU do it.

If it doesn't boot it's a different issue, that line won't affect booting.

Did you run the server with either stick and it still crashed?

Pool is not set as redundant in the cfg, but that can sometimes be incorrect, assuming it is redundant, it should mount if you do this: unassign the pool device start array stop array re-assign the pool device start array If it doesn't mount post new diags.

I would assign both as pools, so that trim is supported, and assign an old flash drive as the required array device.

That would be OK, assuming a single stream iperf test, still, if the Windows explorer transfer graph still looks like the above, it still points to a network problem (or the client PC), when the network is not the issue, you see full speed for the first few seconds of a transfer, while its being cached to RAM, and if it slows after that then it would be the devices not being able to keep up with the required write speed.

Usually a power cycle is required for NVMe devices, not just a restart. Instead of that, which will wipe the other device, I would recommend physically removing the device, in case you still need it.

Please post the diagnostics.

Can still be a disk issue, they can have slower zones.

It doesn't look to me like device problem. it just dropped offline, but you can try to remove it to see if it's better with just the other one.

If you have a key problem you need to contact support, forum can't help with license issues.

The diags posted only have a rebuild, and there weren't any disk errors, but if it's for example RAM problem nothing would be logged anyway.