JorgeB

It's not logged as a disk error and SMART looks OK, check/replace/swap cables to rule that out, and if the emulated disk is still mounting, you can rebuild on top.

Server rebooting on its own is almost always a hardware issue, if it does it mostly under load, first things to check would be PSU and to a lesser extent, the temps.
 
 

Try accessing the pool using a disk share, or enable exclusive shares.

Problems with parity and disk4 at the same time, do they share something, like a power splitter?

Nothing jumps out, is it the same if you try accessing by IP? 192.168.0.125
 
If yes, disable docker service start by editing /config/docker.cfg on the flash drive and changing DOCKER_ENABLED="yes" to "no", then boot in safe mode and retest.

Constant ATA errors with parity2, replace cables and post new diags, also recommend replacing them for the disabled disk, since SMART looks fine.

Try changing to a docker image, docker folder sometimes has weird issues, and create re-install the containers from previous apps
 
https://docs.unraid.net/unraid-os/manual/docker-management/#re-create-the-docker-image-file
Then:
https://docs.unraid.net/unraid-os/manual/docker-management/#re-installing-docker-applications
Also see below if you have any custom docker networks:
https://docs.unraid.net/unraid-os/manual/docker-management/#docker-custom-networks

Are you trimming the vdisks? They can grow a lot if you don't:
 
https://forums.unraid.net/topic/51703-vm-faq/?do=findComment&comment=557606
 

Yes, you should be able to do it.

Jun  5 18:11:23 Tower kernel: macvlan_broadcast+0x10a/0x150 [macvlan] Jun  5 18:11:23 Tower kernel: ? _raw_spin_unlock+0x14/0x29 Jun  5 18:11:23 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)), then reboot.
 
There's also a problem with the pool fileystem:
 
Jun  6 02:01:02 Tower kernel: BTRFS: error (device sdf1: state A) in __btrfs_free_extent:3073: errno=-2 No such entry Jun  6 02:01:02 Tower kernel: BTRFS info (device sdf1: state EA): forced readonly Jun  6 02:01:02 Tower kernel: BTRFS error (device sdf1: state EA): failed to run delayed ref for logical 87782162432 num_bytes 16384 type 176 action 2 ref_mod 1: -2 Jun  6 02:01:02 Tower kernel: BTRFS: error (device sdf1: state EA) in btrfs_run_delayed_refs:2150: errno=-2 No such entry  
Recommend backing up and reformatting that pool, and also recreate the docker image.
 

If the emulated disks are mounting and contents look correct you can do a standard rebuild:
 
https://docs.unraid.net/unraid-os/manual/storage-management#rebuilding-a-drive-onto-itself

Keys are showing as corrupt, that and the corrupt names, suggest re-formatting the flash drive and recreating, if the issue persists use a different one.

You must disable secure boot or UEFI boot won't work, if it's supported, you can still boot legacy, that mode doesn't have secure boot.

Log shows errors with disk1, so possibly some power/connection issue, are you using any power splitters?

Issue appear to be docker related, you can try re-testing with just one container running, or if it's easier, all but one container running, if the same try stopping a different one to see if you find the culprit.

I see that disk1 is a flash drive, I assume there's nothing important there?
 
Regarding the pools, they are being imported in the go file, you must remove all that and reboot, to let Unraid import all the pools.
 
 

That looks normal, considering the SSD model in use, and many small files will always be much slower.
 
 

DHCP server is not assigning an IP, so that's likely the problem
 
Jun 11 16:23:35 [1340]: br0: probing for an IPv4LL address Jun 11 16:23:40 [1340]: br0: using IPv4LL address 169.254.8.32
Assuming it's your router, try rebooting it, also check all contentions from the server to it.

Please use the plugin support thread:
 
 

There's a connected SATA device causing constant errors:
 
Jun 10 14:15:47 Greenplanet kernel: ata8: found unknown device (class 0) Jun 10 14:15:47 Greenplanet kernel: apex 0000:05:00.0: Apex performance not throttled due to temperature Jun 10 14:15:47 Greenplanet kernel: ata8: found unknown device (class 0) Jun 10 14:15:47 Greenplanet kernel: ata8: SATA link down (SStatus 0 SControl 300) Jun 10 14:15:47 Greenplanet kernel: ata8: found unknown device (class 0) ### [PREVIOUS LINE REPEATED 1 TIMES] ### Jun 10 14:15:47 Greenplanet kernel: ata8: SATA link down (SStatus 0 SControl 300) Jun 10 14:15:47 Greenplanet kernel: ata8: illegal qc_active transition (00000000->00000001) Jun 10 14:15:47 Greenplanet kernel: ata8: limiting SATA link speed to 1.5 Gbps Jun 10 14:15:47 Greenplanet kernel: ata8: found unknown device (class 0) Jun 10 14:15:47 Greenplanet kernel: ata8: SATA link down (SStatus 0 SControl 310) Jun 10 14:15:47 Greenplanet kernel: ata8: limiting SATA link speed to 1.5 Gbps Jun 10 14:15:47 Greenplanet kernel: ata8: found unknown device (class 0) Jun 10 14:15:47 Greenplanet kernel: ata8: SATA link down (SStatus 0 SControl 310) Jun 10 14:15:47 Greenplanet kernel: ata8: limiting SATA link speed to 1.5 Gbps Jun 10 14:15:47 Greenplanet kernel: sd 10:0:4:0: device_block, handle(0x000e) Jun 10 14:15:47 Greenplanet kernel: sd 10:0:4:0: [sdf] tag#2151 UNKNOWN(0x2003) Result: hostbyte=0x0e driverbyte=DRIVER_OK cmd_age=17s Jun 10 14:15:47 Greenplanet kernel: sd 10:0:4:0: [sdf] tag#2151 CDB: opcode=0x88 88 00 00 00 00 00 00 00 00 00 00 00 00 08 00 00 Jun 10 14:15:47 Greenplanet kernel: I/O error, dev sdf, sector 0 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 2 Jun 10 14:15:47 Greenplanet kernel: Buffer I/O error on dev sdf, logical block 0, async page read  
Cannot see which device since it's not even being correctly identified, but look in the diags, see what devices are missing from SMART and disconnected them until you find it, then try replacing cables for that device.

Plex media scan segfaulting I believe is normal, at least I'm used to seeing it in various diags, what is not normal are the call traces and not enough memory errors, try limiting the RAM the Plex container can use to see if it helps, if it doesn't, try running the server with Plex disabled for some time to confirm if that is what is causing the problem.

Yes, it won't start if there's a device missing, not sure why it's not the defualt, IMHO it should be.
 
It should still work, possibly it needs to be enabled in the BIOS, power up via IPMI works for sure, you can get a free app like IPMIView
 
 

OK, so if you do that now it will only work at gigabit speeds.

Try recreating the docker image:
 
https://docs.unraid.net/unraid-os/manual/docker-management/#re-create-the-docker-image-file
Also see below if you have any custom docker networks:
https://docs.unraid.net/unraid-os/manual/docker-management/#docker-custom-networks