Frank1940

What is your PC running?  (most of the time, this problem is on the PC side of the equation!)
 
I realized that this appears to be a failure to access the Unraid GUI using a Web Browser. 
 
Try using the GUI boot option in the Unraid boot menu.  Then go to the     Settings    >>>  Management Access     There look at the "Use SSL/TLS:" setting and the "Local access URLs:" info.  Turn on the help for both of these.  (Clicking on the 'label' will display the 'Help' for each...)   

Just looked at your smb-extra.conf file....
 
[global] security = USER guest account = nobody public = yes guest ok = yes map to guest = bad user max protocol = SMB2_02  
That last line can give you problems as WIN11 has turned off SMBv1 support.  

Yes!
 
IF you use  Secure, this will be the case.   But read-only allows files to be copied.   And anyone who gains access to your LAN via WiFi also has access.  (I have been told in the past, that hacking into a WiFi network is not that difficult...)
 
If you use Private,  You can set up a special Share Access user for visitors with a password.  You then assign the privileges on each share that you want for your visitors.  (Your choices are 'No access', 'Read-only', or 'read-write'.)   But, again, read-only does allow for copying of files  BUT the big difference is that if you give the Log-in info to a visitor, you probably have more trust in them.  Of course, this means that you have to setup the Share Access user on the server and give out the login and password information to your visitors.   (BTW, you can have several visitors all using the same 'visitor' share-access user account logged on at the same time.  Unraid 'knows' that they are on separate devices and uses that info in processing requests!)
 
IF you want more information about setting up SMB on Windows and Unraid, read the PDF files in the first post of this thread:
 
       https://forums.unraid.net/topic/110580-security-is-not-a-dirty-word-unraid-windows-10-smb-setup/
 
 

Try changing this to this:

 
As pick a value of "Minimum free space:" that is about 25% larger than the biggest file you will ever copy to that share.  (Your current setting of 458GB is probably about 8X larger than it need be.)

That is what the diagnostics are indicating.
 
You mean your original boot drive is still plugged to the first server.  If so, move it over.  Make a backup on your PC as you make the move.  (Doing so will virtually guarantee that you will never need it!)
 
You can actually plug that original boot drive into new server and boot up with it.  That what many of us have done when changing out hardware.  Unraid is very hardware agnostic.  (Until you get to VMs and Dockers that pass a hardware device through to. 
 
JUST remember to never, never agree to a prompt to format a disk until you are sure that you are prepared to lose all the data on that disk.  Intel to AMD conversions can have a vew more issues-- particularly the earlier versions of the Ryzen chip set. 

I would start by attaching a monitor and keyboard to your server.  Restart the server.  (Quick push on power button should result in a clean shutdown.  Long push will force a unclean shutdown...)  During the restart, pick one of the GUI options from Unraid's boot menu. 
 
You should now be able to 'fix' the Docker container.

IF you turn on the help (or click on the 'Split Level', you will get this:

See here:

 
If this doesn't work, you might want to try setting things up so that you are not fighting the security measures that both MS, Linux and Unraid are trying to implement to protect user data.   Read the first post in this thread and the attached PDF:
 
    https://forums.unraid.net/topic/110580-security-is-not-a-dirty-word-unraid-windows-10-smb-setup/
 
Granted that it takes some time to set things up but you will then not be playing wack-a-mole with trying to bypass security enhancements.

Shutdown the server gracefully by pushing the power button for about one second.  Pull the flash drive after shutdown. 
 
Plug it into your PC.  Delete the   /config/network.cfg     file and plug it back into the server and reboot.       
 
You will have to login use the server name as you will have an new IP address assigned by your new modem/router.  You can look at the router GUI interface to find this address. 

I download your Diagnostics.  Are you exporting many of your shares as 'Yes-Hidden'?  (I am not familiar with the code for hidden SMB shares but I don't recognize that code in the diagnostics...)   If you are, un-hide them until you have everything working!   (Linux is case-sensitive and that make a big problem for most windows users!!!)

No.  A UDMA error is  a communication error between the drive and the MB. 
 
The connection is serial data transmission and it has a CRC check code embedded.  The error message indicates that the transmitted CRC code did not match the code calculated by the receiving device.  The data block is then re-transmitted until the codes match.  So there is no hard error that would result in data loss!  
 
Most of the time (when there are hundreds of errors in a very short period of time), replacement of the SATA data cable with checks to make sure that the SATA connectors are fully seated is the standard procedure.   In your case, you can click on that error icon (can't remember if it is right-or-left click) and acknowledge the error.  You will be notified if it happens again.   (I had one disk with 1823  CRC errors on it for over two years and the count never increased after that initial burst.  I did replace it when I needed more storage space a few months ago.)

I suspect the problem is on the server with the Linux permissions to those folders that she is having the problems with.  There are a couple of approaches that you could try.
 
IF you want to  investigate and troubleshoot the problem, use the GUI terminal  (the icon on the right side of the GUI Taskbar).  Type the following command:
ls -alh /mnt/user Look at the listing.  You should see something like this:

 
Column 1 is the permissions d = directory;  r = read; w= write; x = execute;  (a ' -'  in place of the 'd' Indicates a simple file) 
    The  permission letter is means the permission is on.  a   -    means the permission is off.
    The first block of rwx is for the owner, the second group is for group, and the third group is for others.
 
Column 2 is the owner
 
Column 3 the group
 
Column 4 is the name of the resource.  (Partially obscured..)
 
Hit the  <up-arrow> key and the command will reappear.  add a   /   and the name of the share that the problem folder is in and hit <Enter>.
Repeat until you get down to the directory/folder with the issue and look at the permissions.  These are the permissions that we expect to find for directories and files in a Share.

 
(Quick explanation.  When you setup your wife as a Shares Access user, that means that she automatically becomes a member of the group 'users' and she actually gains access to directories and files through the group permissions.) 
 
IF you just want to fix it.  Run the New Permissions tool in the TOOLS  tab.  Run it on the Share with the problem.
 
If this does  not fix it, come back with what you are seeing when you us the   ls     command. 
 
EDIT::    Linux is case-sensitive so you must type all Linux commands, resource names and parameters using the proper case!

Go to the BIOS during startup.  Look to set up the boot order so that the BIOS actually looks for your thumb drive and make it the first device that it tries to boot from.  Sorry but every BIOS is different so I can't give more specified instructions... 

Connect a monitor and keyboard to your server.  Now boot up the server.  At the bottom of the monitor screen just above the login prompt, you will see your IP address.  Write it down. 
 
Now login using root and your Unraid password.
 
Then enter this command:
diagnostics  
Note where the file is saved.   Then push the power button for about one second and the server will power down. 
 
Pull the flash drive and upload the diagnostics file in your next post.
 
Now look at that IP address and compare to the base IP address of your new router-- Not the Internet IP address.  The first three groups of numbers should be identical.  (If they are not that is probably where your problem is.)

Try setting the UMASK to 000 rather than 022
 
EDIT:  And you will probably have to run the    New Permissions    Tools on the share(s) to which this Docker writes. 

Post up screenshots of these two commands run in the GUI Terminal:
ls -al /mnt ls -al /mnt/user  
If you are concerned about privacy, you can crop the directory names off of the second one when you do the screenshot. 
 

These devices can be messy to use depending on how old they are.  If they are old enough that they only support SMBv1, they are basically EOL devices and recent Samba versions often have to be browbeaten to get them to work.  As I recall, if they work now on your current version of Unraid and you do a upgrade to the latest Unraid version, SMBv1 will still be 'active' ('Grandfathered' in) on your Unraid server.  (If you do a new install, SMBv1 will be turned off (if I understand it correctly) and you will have to turn it on.
 
 
With WIN10, it is best to establish a Windows Credential using Credential Manager.  Of course, you will have setup a 'Share Access' user on Unraid.  Doing this generally eliminates problems on both the Unraid side and the Windows client side.   If you should run into a problem, read through the PDF in the first post of this thread:
 
            https://forums.unraid.net/topic/110580-security-is-not-a-dirty-word-unraid-windows-10-smb-setup/
 

I just did this and this was my procedure:
 
1.  Preclear the new 16TB drive.  (I don't want an 'infant mortality' failure in the subsequent operations! But this is optional depending on your tolerance for problems...) Make note of the last four digits of the 16TB drive.  Make note of the serial number of the present 8TB parity drive.
 
2.  If you haven't done a parity check recently, do one now!  (You don't want to be dealing with a undetected disk problem in the following steps...
 
3.  Shut the server down.  Remove the present Parity Drive. Verify serial number on this drive and set aside.  Install new 16TB drive.  (VERIFY that all SATA DATA and Power connectors are firmly seated!!!!)
 
4.  Power up server.  Unraid will detect that the Parity Drive is missing.  Assign the 16TB as Parity.  (Use the dropdown box...) 
 
5.  Start the array and rebuilt parity.
 
6.  Get the last four digits of serial number of the 4TB data drive you want to replace.  Shut the server down again. Pull that drive and verify its serial number.  Install the old Parity drive in its place.   (VERIFY that all SATA DATA and Power connectors are firmly seated!!!!)   Start up server.  Again, it will detect the missing drive.  Assign the old Parity Drive as its replacement. 
 
7. Start the array and rebuild the that disk.
 
All of this will take a few days, so be prepared.   Notice that you will not be losing any data using this procedure and the server will be available throughout the procedure while it is up.  (But using it will impact its performance and extend the time required to complete each step. So a bit of planning may be required to minimize the impact on users.) 
 
It appears that available storage is not currently a problem as you said you have a 4TB drive that is "basically empty".  So you can do steps 6 & 7 at a later date and still have the server running normally until you have a clear window of time to finish the job with minimal disruption.  Remember that you should now be prepared to always buy 16TB drives from this point on.  (Otherwise, you may find yourself removing a perfectly good drive to gain more storage space.  (I know this as I now find myself in this situation...) 
 

On the MAIN tab of the GUI as shown in the following screenshot:

 
You do the timing manually with a stopwatch (or its equivalent).  Great accuracy is not required as the time may vary several seconds from measurement to measurement.  You are after a good approximation of the time required.  Remember if the array can not be stopped within that time setting on the Disk Setting tab, Unraid will force an unclean shutdown!  As I understand it, Unraid will do a clean shutdown as soon as it has detected that the array has been stopped so having a shutdown time that is on the high side has no real penalty if things are working correctly. (The sole exception being if your UPS runs out of battery power as a result of waiting...) 

So you are bypassing the cache entirely for these copies and they are still failing.   I seem to recall that you should make a similar min free space setting on the cache from the  Main   tab.)
 
It might be that there is a  permissions on your Unraid sever.  Let's try this to try to fix them:.
 
1 -- Open up the   Tools    tab. 
 
2--  Find the    New Permissions   tool and open it:
 
3-- Look at the screenshot below.  Select   Shares   from the left dropdown box and the Share with the issue ( Projekte ) from the right dropdown box.  Click  START.

 
It will take some time as it is Bash script and will set the owner/group names and the permissions on each file and directory in the entire share.  
 
 

Is disk6 (serial number     WSD7RWRQ  ) the disk that is missing?    It looks good from the SMART report.  (But it does have some CRC errors but that is not normally a disk problem but a SATA cable or connection problem. So check all SATA cables to be sure they are firmly seated!) 
 
 
Do you have a replacement disk on hand?  If you do, that is what I, personally, would do.   If you don't have a cold spare rebuilt on the current disk.   (That way most of the contents of the disk removed are valid.)   Be sure to double-check that all drive connectors are seated firmly before you power the server back up!   (You have several disks with CRC errors and loose connectors will cause that problem.  (As will 'bad' cables.)
 
No, it will not rebuild by its self!  You have to follow these steps:
 
        https://docs.unraid.net/unraid-os/manual/storage-management/#rebuilding-a-drive-onto-itself
 
If you replace the disk rather than rebuild, I would run a preclear cycle on that removed disk to make sure there is not a problem with it.  If it checks out OK (which I suspect it will), keep as a cold spare.
 

I used rsync and the Unassigned Devices plugin.
 
Basically, you mount the FreeNAS server using the Unassigned Devices plugin.  
 
Then use rysnc from the Command line in the GUI terminal.
 
My rsync command looked like this: 
 
rsync -avhPX /mnt/remotes/192.168.1.245_Media/All\ Movies/ /mnt/user/BackupMedia/All\ Movies/  
Now, before you use rsync, googling it finding lots and lots of pages that will explain how to use it.  There are some gotchas in its use but any good online tutorial will help you avoid them.  The switches that I use (and in the command line above) are not the only ones that you can use and they will do the same job. (Mine is set up so that it gives lots of information as it does its job.  A different combination of switches would run it silently and you will not know what is happening until the command prompt returns after it has finished.  Probably a bad idea as copying 10TB of data will take several days!)   Rsync was written in 1995, in the public domain, and has been ported to virtually every OS in existence.  (As I seem to recall, it does have to be available on both the source and destination devices.  But FreeNAS will either have it installed or it should be available for installation.)
 
One more thing.  Go to    Settings   >>>   Disk Settings  and set the following variable in the Disk Setting section/tab as shown:

The setting will double the write speed to the Unraid array.  (If you have a cache drive for the Unraid, disable it for that share until the initial data from the other server is complete.) 

You should be looking and posting in the support forum thread for Tailscale.   You can find this by going to   PLUGINS    tab, find the plugin in the list and click on the 'Support Thread' link.  If it is a Docker, go to the   DOCKER   tab and left-click on the icon for the Tailscale Docker and select 'Support' from the dropdown list. 

From the manual:
 
     https://docs.unraid.net/unraid-os/manual/storage-management/#parity-swap
 
You can find the manual by clicking on the DOCS Link in header for the Forum or on Manual in the right side of the Taskbar in the GUI. 

The GUI generates network activity updating the GUI screen in your browser on your PC...