JorgeB

Then it suggests a plugin is the problem, remove them and start installing them one by one to see if you can find the culprit.

Try a different flash drive. 

This happens because old disk1 is confusing the pool, it's this line:
 
Wipe or disconnect that disk and the pool will mount again.

Delete that file, it should not exist.

See if this applies to you, if yes, switching to ipvlan should fix it (Settings -> Docker Settings -> Docker custom network type -> ipvlan (advanced view must be enable, top right)), or see below for more info.:
https://forums.unraid.net/topic/70529-650-call-traces-when-assigning-ip-address-to-docker-containers/
See also here:
https://forums.unraid.net/bug-reports/stable-releases/690691-kernel-panic-due-to-netfilter-nf_nat_setup_info-docker-static-ip-macvlan-r1356/

Check filesystem on disk1.

Try a different browser other than Firefox, if still the same please try rebooting in safe mode, if you get the stale config error post new diags.

"Invalid partition layout" is not a filesystem problem, the disk lost/damaged some part of the MBR, looks like it mostly happens with WD disks, so possibly a firmware problem.
 
To fix you can rebuild the the disk, assuming parity is valid, you just unassign it, start the array, Unraid will recreate the partition correctly and emulated the disk, if all looks good you can then rebuild on top, alternatively you could mount the disk outside the array and copy the data back to it.

Yes.

There's no eth0 on interface rules, delete/rename /config/network-rules.cfg and reboot.

There are some crashes/timeouts related to the NVMe device, please try running without it, keep the syslog server going and post a new one if it crashes again.

Still unpacking going on, suggest you stop all dockers, wat a couple of minutes and see if the utilization goes back to normal, if not post new diags, if yest starting enabling the docker one by one.

Problem with the onboard SATA controller, quite common with some Ryzen servers, reboot and post new diags after array start, if this continues to happen best bet is to get an add-on controller (or use a different board).

Looks like a power/connection problem with the parity disk, check/replace cables and try again, look at the syslog to confirm the ATA errors are gone, or post new diags.

Filesystem is going read-only due to lack of space, but I'm not seeing why it's running out of space at mount time, this usually happens when a balance was started but not signs of "balance resumed" in the log, in any case please try this, with the array stopped type:

 
mkdir /temp mount -o skip_balance /dev/sdf1 /temp btrfs balance cancel /temp umount /temp  
Then start the array and post new diags.

Backup the licensed key, after the backup is done recreate the flash drive with a new install, copy the /config folder from the trial key to the licensed key, restore only the key from the backup.

Try rebooting in normal mode, if you get stale config again uninstall all the plugins then re-install one at a time.

Go to Settings -> Network Settings -> Interface rules and make the Gbit NIC eth0, then reboot, it will have the same settings as the older eth0.
 
eth1 should then use a different subnet for the direct PC connection.

Constant crashing, start by running memtest.

That's usually a flash drive problem, try using a different one to test.

Sdc is part of a different filesystem, should still be able to recover data from the NVMe device using the recovery options here, use the ones that have 'degraded' in the mount options.

Cache replacement is broken in v6.9, I did a bug report some time ago but it's still not fixed.

And the GUI is still inaccessible correct? If yes, I'm not seeing anything obvious, try rebooting in safe mode, disable docker/VM services and start the array to see if there's any difference.

Not possible, but these addresses can change if you change/add/remove any harware, it's done by editing the VM config, in the end, it should be under "other PCI devices", just unselect it with the VM stopped, e.g.:
 

Delete the file manually, on the console type:
rm /mnt/disk4/system/docker/docker.img