JorgeB

Looks OK for now.

Find it interesting that the board BIOS checks for that, you should be able to correct that with gdisk, e.g.:

 
gdisk /dev/sdb GPT fdisk (gdisk) version 1.0.5 Caution: invalid main GPT header, but valid backup; regenerating main header from backup! Warning: Invalid CRC on main header data; loaded backup partition table. Warning! One or more CRCs don't match. You should repair the disk! Main header: ERROR Backup header: OK Main partition table: OK Backup partition table: OK Partition table scan: MBR: protective BSD: not present APM: not present GPT: damaged **************************************************************************** Caution: Found protective or hybrid MBR and corrupt GPT. Using GPT, but disk verification and recovery are STRONGLY recommended. **************************************************************************** Command (? for help): w Final checks complete. About to write GPT data. THIS WILL OVERWRITE EXISTING PARTITIONS!! Do you want to proceed? (Y/N): y OK; writing new GUID partition table (GPT) to /dev/sdb. The operation has completed successfully.  

All NICs are being detected, the 10GbE is unable to get an IP address:
 
Oct 2 18:19:29 Tower dhcpcd[1201]: br0: probing for an IPv4LL address Oct 2 18:19:34 Tower dhcpcd[1201]: br0: using IPv4LL address 169.254.173.54  
It it connected to a DHCP server?
 
The gigabit link is reporting link down, if that's the main internet NIC make sure a cable is connected and set it as eth0 (Settings -> Network Settings -> Interface Rules) then reboot (you can access the GUI buy booting into GUI mode).

You cannot check now since there are two invalid disks with single parity, so they cannot both be emulated, if you're not sure it's best to enable only disk4 and see if disk9 can be correctly emulated:
 
-Tools -> New Config -> Retain current configuration: All -> Apply
-Check all disks are assigned, assign any missing disk(s) if needed
-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 disk9
-Start array (in normal mode now), ideally the emulated disk9 will now mount and contents look correct, if it doesn't you should run a filesystem check on the emulated disk
-If the emulated disk mounts and contents look correct stop the array
-Re-assign disk9 to rebuild and start array to begin.
 
 

Those errors come from a 120GB Kingston SSD, it looks to be unassigned, is it being used? If not unplug it, in any case reboot and post new diags after array start.

The problem appear to be the log tree, after it's the backup is complete you can try:
btrfs rescue zero-log /dev/nvme0n1p1 And if that doesn't work format.
 
Btrfs is currently the only option for pools.

Docker image is corrupt, delete and re-create.

Without nothing logged it's difficult to say, maybe it was a one time thing, if it wasn't I would downgrade to v6.10.3 first to see if it's update related, since that's the biggest change.

Try rebooting.

That's normal, you have to format the disk after it's cleared.
 
Disk failing to format is not normal, two of your SATA ports are set to IDE mode, that's a known problem with those AMD chipsets and that disk is using one of them, set them to AHCI/SATA and try again.
 

Go to Settings -> SMB -> SMB Extras and add:
 
log level = 3 logging = syslog Then check the syslog, note that Samba will get very chatty so it can fill it up after a few hours.

diskFsType.1="fuseblk" Not sure what heppend here but this is not a valid filesystem, click on disk1 and change fs to auto, if it's already auto change to a different one, then back to auto and apply.

Easiest way is to mount a Synology SMB share with the UD plugin.

With Linux it's usually under /var/log/syslog, but I've never used Mint, though it should be easy to find with google if it's not that.

Are you using Firefox?

Rebooting should bring the shares back.
 
Unrelated but the external HDD is failing:
197 Current_Pending_Sector -O--CK 200 200 000 - 4  
 

Could be a power/connection problem, but I would suspect more a controller issue, Marvell controllers are not recommend for Unraid, if possible replace it with one of these.

Run a scrub on the pool, check that all errors are corrected, after that delete and re-create the docker image.

So the folders exist but are empty, at least the ones I can see in the screenshot, so you can just delete them.

Disk looks mostly OK, should fine to use, use a different power connect and SATA cable in case that was the problem.

Check that contents look correct, also look for a lost+found folder any lost data there, if all looks good rebuild on top, might be a good idea to replace/swap cables first to rule that out if the same thing happens again.
 
https://wiki.unraid.net/Manual/Storage_Management#Rebuilding_a_drive_onto_itself

Wrong date and time will cause that, make sure NTP service is enabled.

Image file types can grow with time, move everything to the array and check what was using the most space, then copy back with cp --sparse=always.

Sep 3 17:37:21 NASA kernel: macvlan_broadcast+0x116/0x144 [macvlan] Sep 3 17:37:21 NASA kernel: macvlan_process_broadcast+0xc7/0x110 [macvlan]  
Macvlan call traces are usually the result of having dockers with a custom IP address and will 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)).

Try recreating the flash drive, backup current config folder, recreate it manually or using the USB tool, restore the config folder.