JorgeB

Switching to ipvlan should fix it (Settings -> Docker Settings -> Docker custom network type -> ipvlan (advanced view must be enabled, top right)).

Copy just the bare minimum, like your key, super.dat and pools folder for the assignments, and the docker user templates, then reconfigure the server or restore a few files at a time to see if you can find the culprit.

Using /dev/sdX won't work, use the GUI, see check filesystem, and run it without -n or nothing will be done.

This is a bytfs issues when using an odd number of devices, all the space will be usable and the free space will get more accurate as the pool is filled up.

Uninstall and re-install the Chinese language pack to updated it to latest.

You're having issues with multiple drives on the onboard SATA controller, likely a connection or power problem.

Try a new flash drive, with a stock Unraid install, no key needed, just to see if you get the same errors.

Cache filesystem is corrupt, suggest to back up and re-format.

Cache filesystem has issues, see here for some recovery options, then re-format the pool.

It's logged as a disk problem and the SMART test failed, so the disk should be replaced.

If I'm understanding correctly it is, it's this:
https://docs.unraid.net/unraid-os/manual/storage-management#rebuilding-a-drive-onto-itself

Shouldn't take long.

Oct 28 19:11:56 Tower kernel: macvlan_broadcast+0x10a/0x150 [macvlan] Oct 28 19:11:56 Tower kernel: ? _raw_spin_unlock+0x14/0x29 Oct 28 19:11:56 Tower 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)).

Oct 30 22:10:14 Tower kernel: REISERFS (device md2p1): Remounting filesystem read-only  
Check filesystem on disk2.

Everything looks normal to me, does it work if you click the link below:
 
http://192.168.68.117

Best bet would be to repost in the existing plugin support thread, I believe the author is no longer supporting it, but maybe other users can help you.

Share floor is set to 780GB, and all your disks are below that, set a new lower floor.

You are running into a bug when using included disks, it doesn't write to all included disks, bug will be fixed for next release, for now you can remove all included disks or use excluded disk instead.

If the log tree is the only problem this may help:
 
btrfs rescue zero-log /dev/nvme0n1p1  
Then restart the array.

Everything looks normal to me so for, but if lines like these keep repeating:
 
ct 28 14:20:14 Unraid kernel: br-cb212d041ce3: port 9(veth2611ba4) entered blocking state Oct 28 14:20:14 Unraid kernel: br-cb212d041ce3: port 9(veth2611ba4) entered forwarding state Oct 28 14:20:16 Unraid rc.docker: nextcloud-aio-fulltextsearch: started succesfully! Oct 28 14:20:17 Unraid kernel: br-cb212d041ce3: port 10(vethb9edd08) entered blocking state Oct 28 14:20:17 Unraid kernel: br-cb212d041ce3: port 10(vethb9edd08) entered disabled state Oct 28 14:20:17 Unraid kernel: device vethb9edd08 entered promiscuous mode Oct 28 14:20:22 Unraid kernel: eth0: renamed from veth0b4df00  
Check your containers, there could be one constantly re-starting, you can find which one based on the uptime.

Yes.
 
Yes.

Try uninstalling the Tailscale plugin.

It is, but affected users need to disabled bridging for eth0, see the release notes, easier change for most users is just switching to ipvlan instead.

There are issues with both cache devices, since they are MX500 see if this helps:
https://forums.unraid.net/topic/134954-warning-crucial-mx500-ssds-world-of-pain-stay-away-from-these/?do=findComment&comment=1255816
 

In this order:
 
 
Keep all assignments in the new config page.
 
 
Before starting you can also move the disks around if you want, so disk6 doesn't stay empty, but it's not required