JorgeB

Looks more like an SMB issue, try removing/commenting everything you have on SMB extras, reboot and try again.

Constant ATA errors with disk4, replace cables and run a new check, then post new diags.

This, but it's not necessary to be larger, same or larger than existing data disks.

This might have been the issue, something I've never tried, why reboot first?
 
That should do it, you may need to use -f if the new disk is not empty, then reimport the pool, see the end of this FAQ entry for how to.

Reboot.

Unraid does a 
zfs mount -a at array start but it's likely before UD mounts the disks, probably should ask in the UD support thread.

That attribute is not standard with that model, just disable monitoring it.

Found out yesterday that there's a bug if you have more than 6 included disks for a share, remove all and use excluded disks instead, that should work until the bug is fixed.

Oct 2 05:55:45 Ultron kernel: macvlan_broadcast+0x10a/0x150 [macvlan] Oct 2 05:55:45 Ultron kernel: ? _raw_spin_unlock+0x14/0x29 Oct 2 05:55:45 Ultron 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)).
 
If you cannot change the setting and reboot using the GUI now, type reboot in the console, if the server doesn't reboot after 5 minutes you'll need to force it.

Sep 27 02:50:59 Wasp kernel: macvlan_broadcast+0x10a/0x150 [macvlan] Sep 27 02:50:59 Wasp 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)).

That's expected, it will remain disabled until you re-sync it:
https://docs.unraid.net/unraid-os/manual/storage-management#rebuilding-a-drive-onto-itself

I would start by checking/replacing cables, but if you can try a different PSU it might be worth it, and if it happens again save the diags before rebooting.
 
 

Not with read/write/modify write mode, and it's the only one that works when transferring disk to disk.

You cannot for now, possibly for v6.13
 
Cache is another pool, not a share, unless you enable disk shares.
 
It depends if you needed them or not for your use case, for now they can only be added manually, 6.13 will have GUI support.
 
 
 
 

You cannot do that with zfs, need to destroy the pool a create a new one.

Yep, it should be replaced.

Disk is being correctly emulated:
 
Filesystem      Size  Used Avail Use% Mounted on /dev/md3p1      7.3T  4.3T  3.1T  59% /mnt/disk3  
You will see the used/free space on the main GUI page, just need to assign the new disk to rebuild.

Try renaming/deleting /boot/config/network.cfg and rebooting to go back to defaults.

There's a call trace related to the Unraid driver, this usually means a hardware issue, also see this:
 
https://forums.unraid.net/topic/46802-faq-for-unraid-v6/?do=findComment&comment=819173
 

Yep

type in the console:
btrfs rescue zero-log /dev/sdc1 Then restart the array, if the pool mounts run a scrub since there's corruption detected on one of the devices.

It's normal that some things will be corrupted after running some time with bad RAM, docker image can easily be recreated, pools hsould be scrubbed, any corrupt files will be listed in the syslog, and if there are any they should be deleted/restore from a backup

This suggests a plugin problem, remove all plugins, if it works then install one at a time and retest.

I am, see here:
https://forums.unraid.net/topic/46802-faq-for-unraid-v6/?do=findComment&comment=1256329
 

Check filesystem on disk2, run it without -n.