JorgeB

Clear the browser cookies and try again.

Cache2 dropped offline:
 
Sep 14 04:40:02 Tower kernel: sd 2:0:0:0: [sdk] tag#22 UNKNOWN(0x2003) Result: hostbyte=0x04 driverbyte=DRIVER_OK cmd_age=0s Sep 14 04:40:02 Tower kernel: sd 2:0:0:0: [sdk] tag#22 CDB: opcode=0x2a 2a 00 00 00 08 80 00 00 08 00 Sep 14 04:40:02 Tower kernel: blk_update_request: I/O error, dev sdk, sector 2176 op 0x1:(WRITE) flags 0x3800 phys_seg 1 prio class 0 ### [PREVIOUS LINE REPEATED 1 TIMES] ### Sep 14 04:40:02 Tower kernel: BTRFS warning (device sdj1): lost page write due to IO error on /dev/sdk1 (-5)  
Check/replace cables and also see here for better pool monitoring.

Forgot to mention, you must run without -n or nothing will be done.

/mnt/user permissions are wrong, don't ask me why they work with v6.9, but they are still wrong, type
chmod 777 /mnt/user reboot and try again.

Yes.

It's logged as a disk problem but SMART looks mostly OK and the extended test passed, I would keep if for now, but any more errors on the next parity checks would recommend replacing.

Check fans and CPU temp, if the server shuts down vs crashing it's usually a hardware problem and not something easy to diag remotely, one thing you might want to confirm is that no shutdown command is being sent to Unraid, by for example a faulty power button, you can do that by enabling the syslog server and checking it or posting after the next shutdown.
 
P.S. next time please post the diagnostics.zip, not all the files inside it.

2TB 2.5" drives will be SMR, what brand/model? Some SMR models, particularity by Seagate performe decently, SMR drives by Toshiba or WD can have several minutes writing below 5MB/s, even when doing sequential writes.

Sep 19 12:25:53 Tower kernel: BTRFS error (device sdf1): block=2395218591744 write time tree block corruption detected This usually means bad RAM or other kernel memory corruption, Ryzen with overclocked RAM like you have is known to corrupt data, so you should fix that, then run memtest.
 
 
Sep 17 16:59:52 Tower kernel: macvlan_broadcast+0x10e/0x13c [macvlan] Sep 17 16:59:52 Tower kernel: macvlan_process_broadcast+0xf8/0x143 [macvlan] Unrelated, macvlan call traces are usually the result of having dockers with a custom IP address and will end up crashing the server, upgrading to v6.10 and switching to ipvlan should fix it (Settings -> Docker Settings -> Docker custom network type -> ipvlan (advanced view must be enabled, top right)), or see below for more info.

Seems related to the RAID controllers, make sure JBOD mode is enable and the disks are being passed through, Unraid isn't detecting those devices, like if they don't exist.

Disk3 looks OK, 13 mostly OK, run an extended SMART test on 13, both show several UDMA CRC errors so it could have been cable related.

System share has files on disk1, move them to cache, services must be disabled first.

They will be under /mnt/disks/UD_label, e.g. /mnt/disks/TV

Sorry posted the wrong link:
https://forums.unraid.net/bug-reports/stable-releases/6100-vnc-no-longer-connects-r1902/?do=findComment&comment=19127
 

With the array stopped set pool slots to 0, that will delete that pool.

Stop shaking reboot and the shares will come back.

Everything looks fine, hopefully it was a one time thing, if it happens again I suggest going back to last known good release to see if it's driver/kernel related.

https://wiki.unraid.net/Manual/Storage_Management#Rebuilding_a_drive_onto_itself

Formatted with type 2 protection  
You need to remove this from the disks, more info below.
 
https://forums.unraid.net/topic/93432-parity-disk-read-errors/?do=findComment&comment=864078

https://forums.unraid.net/topic/110835-help-with-a-sas-drive/

Sep 13 15:24:39 Proliant-2 kernel: be2net 0000:0d:00.0 eth4: Link is Down Sep 13 15:24:39 Proliant-2 kernel: be2net 0000:0d:00.1 eth5: Link is Up  
Log does show link up on one of the ports, note that you should set it as eth0 (Settings -> Network Settings -> Interface Rules then reboot) if you want to use that NIC as the main one to manage Unraid.

Strange error, please try this:
 
Unassign all cache devices, start array to make Unraid "forget" current cache config, stop array, reassign all cache devices (there can't be an "All existing data on this device will be OVERWRITTEN when array is Started" warning for any cache device), start array, post new diags if it still doesn't mount.
 
 

Still nothing, and the other Intel NIC is now also missing, upgrade to v6.10.3 since there were changes to the NIC rules script and post new diags, might also be a good idea to delete/rename network.cfg to use the default LAN settings.

Sep 9 15:01:30 Tower emhttpd: /mnt/cache ERROR: cannot scan /dev/sdf1: Input/output error This is the problem, sdf is parity and because you have an odd number of btrfs arrays devices makes it look like parity has an invalid btrfs filesystem and causes issues during btrfs device scan, it's a known issue but there's no fix for now, workaround is to use xfs only for the array, use btrfs encrypted, or have an even number of btrfs array devices, this last option usually works but not always.

Check/replace cables on disk7, both power and SATA to see if those ATA errors go away, disk looks OK.

Unassign both pool devices, start array, stop array, reassign both pool devices, start array, that should do it.