JorgeB

There's no driver for that adapter, you can make a feature request.

Forget that for now, the issue is already visible in the after boot log:
 
Nov 24 09:25:26 UnRaid kernel: macvlan_broadcast+0x10a/0x150 [macvlan] Nov 24 09:25:26 UnRaid kernel: ? _raw_spin_unlock+0x14/0x29 Nov 24 09:25:26 UnRaid kernel: macvlan_process_broadcast+0xbc/0x12f [macvlan]  
Macvlan call traces will usually end up crashing the server, switching to ipvlan should fix it (Settings -> Docker Settings -> Docker custom network type -> ipvlan (advanced view must be enabled, top right)), then reboot.

This can help in some cases, on the main GUI page click on the flash drive, scroll down to "Syslinux Configuration", make sure it's set to "menu view" (top right) and add this to your default boot option, after "append initrd=/bzroot"
nvme_core.default_ps_max_latency_us=0 pcie_aspm=off e.g.:
append initrd=/bzroot nvme_core.default_ps_max_latency_us=0 pcie_aspm=off
Reboot and see if it makes a difference.

If you rename EFI- to EFI in the flash drive it can boot either way, the way it boots will depend on the BIOS setting.

Try recreating the flash drive.

Currently the auto key replacement only works if you install the Connect plugin first, alternatively contact support.

Still a network problem, use those DNS servers as DNS1 and DNS2, remove your router as DNS server.

Try with a new flash drive using a stock insatll, no key needed, enable the flash share and see if it can be access, that will show if it's a LAN or server config problem.

Once a disk gets disabled it needs to be rebuilt, if the emulated disk is mounting and contents look correct you can rebuild on top.
 
https://docs.unraid.net/unraid-os/manual/storage-management#rebuilding-a-drive-onto-itself

Because the other device is missing Unraid is not trying to mount the pool degraded (assuming it's raid1), you can do that manually, if successful backup pool contents and re-create the pool after replacing cables on the device that caused issues before.

If the backup is not up to date regarding the assignments suggest you do this instead:
 
https://docs.unraid.net/unraid-os/manual/changing-the-flash-device/#what-to-do-if-you-have-no-backup-and-do-not-know-your-disk-assignments
 
 

Correct, mover won't overwrite a file, delete the older one, docker.img can also be easily recreated if needed.

There are what look like power/connection issues with disk1, but since it's unmountable, first cancel the rebuild, stop array, unassign disk1, check filesystem on the emulated disk, run it without -n, if successful post new diags after array start, with disk1 still unassigned.

That NIC should work fine with Unraid, a quick Google search suggested using pci=realloc=off, see here how to add that option and try it:
 
https://forums.unraid.net/topic/73386-no-hard-drives-9211-it-mode-solved/#comment-674935
 

zfs can be used in the array or pools, but you cannot have a multi device zfs pool in the array, see here for some more info.

Correct, and performance for the downloads should be better, assuming the pool can keep up.

You cannot directly replace a single device pool, if it's empty you can unassign it, start array, stop array, assign new device.

If it's in RAID mode it should be flashed to IT mode.

This is a bug, it happens if that's the only encrypted disk, I believe it's already been fixed for v6.13 but it wasn't easy to backport to 6.12 due to all the changes, see here for a workaround:
 
 

UDMA CRC errors are usually a cable problem, not disk, a single error is nothing to worry about, but if it keeps increasing replace the SATA cable.

Try this first:
https://forums.unraid.net/topic/118286-nvme-drives-throwing-errors-filling-logs-instantly-how-to-resolve/?do=findComment&comment=1165009
 

Not really, but if it was a more serious hardware issue you should see other apps segfaulting.
 
It's a possibility.

I'm seeing the same issue, looks like a plugin problem, I suggest keeping an eye on the support thread thread for an update.

Looks more like a power/connection issue, check/replace cables and try again.

If disk3 was never added to the array you can try this (leave disk3 unassigned), it will only work if parity is still valid:
 
 
-assign the new disk2, replacement disk should be same size or larger than the old one
-IMPORTANT - Check both "parity is already valid" and "maintenance mode" and start the array (note that the GUI will still show that data on parity disk(s) will be overwritten, this is normal as it doesn't account for the checkbox, but it won't be as long as it's checked)
-Stop array
-Unassign disk2
-Start array (in normal mode now), ideally the emulated disk will now mount and contents look correct, if it doesn't post the diags
-If the emulated disk mounts and contents look correct stop the array
-Re-assign disk2 and start array to begin.