Hoopster

See this post for several things that can done to improve unRAID stability with a Ryzen (especially 1st gen.) CPU.

Power outages have been known to occasionally cause corruption on the unRAID USB flash drive.  You can try running checkdisk on the flash drive from a Windows computer.
 
If you have a recent full backup of the flash drive (always recommended), you can reformat the USB flash drive and restore the backup.
 
In a worst-case scenario (physically-damaged USB flash drive), you can restore a backup to a new flash drive and transfer the license/registration to the new flash drive. 
 
If you have no flash drive backup, copy everything you can from the current flash drive (corrupted files will likely not be copied) and restore them to either the same or another flash drive.

I just wanted to confirm that the basic.key file existed on new flash drive.  If not, it was probably trying to use the expired trial key.  You need to register the GUID of the new flash drive.

Make a backup of the unRAID flash drive.  The config folder contains what you need to restore your current settings.  As far as docker containers/plugins you can just restore them from the Apps --> Previous Apps in the GUI after restoring your config folder backup.
 
If you have not already done so, install the CA Backup/Restore Appdata plugin and make a copy of your appdata and store that some place safe.

Version 6.10 allows the docker custom network type to be set to ipvlan instead of macvlan.  This setting was introduced to try to work around the macvlan call trace issue.  For some it has helped.
 

 
Since I implemented a docker VLAN on my router and switch, the problem has disappeared for me.

You might want to start with this post which has some upgrade steps from 6.3.5 to 6.5.x.