JorgeB

If you mean docker directory with zfs native, from what I've read that can perform considerably worse, and it will make a mess with the legacy datasets, hence why I still recommend overlay2.

That works, but you just needed to re-import the pool, it's in the release notes.

type zpool detach spinners 3500479797208464185 And then a new zpool status output

Try exporting one share publicly and see if you can access it.

Post the output from: lspci -d 1000: -vv

Is the other PC also using 10GbE?

I forgot to mention this earlier, but since the kernel for beta.3 was downgraded to 6.6, it's no longer a problem using a docker folder with the zfs native driver, since only kernel 6.8+ is affected, this means that if a user wants to keep using a docker directory with the zfs native driver for v7.0, he can, though will likely run into issues again with v7.1 and a newer kernel, so still recommend using overlay2 for any new installs.

Yes, because the kernel was downgraded to 6.6, but there will likely be issues again when the kernel is updated to 6.8+, though that probably will only happen for v7.1. Correct.

Still errors with parity, if the cables were replaced run an extended SMART test.

nvme0 is interfering with the pool, since before it was part of it, you have to wipe it, offline it, or physically disconnect it, to test, you can offline it, since it's the safer/easier option, type echo 1 > /sys/block/nvme0n1/device/delete The restart the array, if the pool still doesn't mount post new diags.

Tools - New config

The r8169 driver is being blacklisted, delete /config/modprobe.d/r8169.conf from the flash drive and reboot.

That could be a disk problem, or bad power, if you are using power splitters for example, but ideally that controller should still be replaced.

That's normal, it starts the other services after stopping docker.

Unraid driver is crashing, that is almost always a hardware problem.