trurl

BIOS sometimes tries to "help" by choosing a boot device when you make any disk changes. Make sure it is still set to boot from the Unraid flash.

On mobile now so haven't looked at diagnostics yet. 
 
Some things to consider. 
 
Nothing can move open files. Mover won't move duplicates. User shares won't show duplicates. 
 
Your screenshots are showing user share contents. You can also display disk contents in a similar manner. 
 
What do you see if you look there on cache? 

Looks like you are installing all packages from devpack and nerdpack. Do you even know what most of that is for? I recommend only installing those things you use regularly.

Do you have a flash backup?

00:11.5 RAID bus controller [0104]: Intel Corporation C620 Series Chipset Family SSATA Controller [RAID mode] [8086:a1d6] (rev 09) 00:17.0 RAID bus controller [0104]: Intel Corporation C620 Series Chipset Family SATA Controller [RAID mode] [8086:a186] (rev 09) 01:00.7 RAID bus controller [0104]: Hewlett-Packard Company Device [103c:193f] (rev 01) b2:00.0 Serial Attached SCSI controller [0107]: Adaptec Smart Storage PQI SAS [9005:028f] (rev 01) DeviceName: Embedded RAID 1 Inconsistent identification of disks is just one of many reasons RAID controllers are NOT recommended with Unraid.

d-------s still has files on cache, maybe they are duplicates or maybe mover just hasn't finished moving them.
 
g---s, m---a have files on cache. Since they are still cache-no mover won't move them.
 
and also so array disks can spin down since these files are always open. appdata can be dealt with after the others are moved.

https://wiki.unraid.net/Manual/Changing_The_Flash_Device

Probably you have corrupted it by filling it. The fact that it is currently using 45G of the 100G allocated is further evidence that you have something wrong with one or more of your docker applications.
 
20G allocated is often more than enough. Maybe a little more depending on how many and which dockers. But not as much as you have.
 
The usual reason for an application to fill docker.img is writing to a path that isn't mapped to host storage.

This file is at /boot/config/network.cfg

Rebuilding from parity will give the same results as the repair. The parity array is emulating the repair you did, and rebuild always results in the same as the emulated disk. (how could it be otherwise?)
 

GUI mode is an Unraid OS mode, but it allows you to work with the webUI on an attached monitor and keyboard.

You might be able to rename the share at the command line.
 
I think I would just create a new user share with an allowed name, and use mc to move the contents of /mnt/user/rootshare to /mnt/user/whatever.

Just to make sure there isn't something else causing sync errors, you should run a correcting check, followed by a non-correcting check, all without rebooting. If there are still sync errors after the non-correcting check then diagnostics would be needed to compare the checks in case you have some other hardware (RAM or something) causing these.

You shouldn't think of cache as temporary storage. Cache is just the default name of a (fast) pool separate from the parity array. More than one pool can be setup, each can have multiple disks, and each can be named as you wish. 
 
Each user share has settings that control how and which pool it uses if any. New files for a share may be written to its pool and moved between pool and array depending on those settings.
 
Files on pool are considered part of the share, so wherever a file already exists is where it will be deleted or modified. 

Do you have backups of anything important and irreplaceable?
 
As you already noted, you can't replace a data disk with a disk larger than any parity disk. With dual parity, you can replace 2 disks at once, but since you already have a disabled disk, only that disabled disk and one other could be replaced at the same time.
 
There is a parity swap procedure that could allow both to be replaced then rebuild the data disk to one of the former parity disks but it is more complicated and it is probably safer to replace one at a time anyway even if everything were good.
 
Replace each parity disk, one at a time, and let parity rebuild.
 
Then replace the disabled disk with one of the former parity disks and let it rebuild.
 
 

All of your configuration is in the config folder of your flash backup. Without that you are starting from scratch. As long as you don't assign a data drive to a parity slot your data should be fine. The screenshot is showing parity disks will be overwritten, not your data. 

username root
password (just hit enter)
 
Only root user has access to the webUI and command line
You should set a good password for root.

Yes 

User Scripts is a plugin. This area of the forum is for request about Unraid core features.
 
You should post to that plugins support thread. You can go directly to the correct support thread for any of your plugins by clicking its Support Thread link on the Plugins page.

I should have looked there first. Another user did the same thing recently.
 

RAID controllers are NOT recommended with Unraid.
 
The usual way to run Windows with Unraid is to create a Windows VM hosted by Unraid. The WIndows VM would need its own graphics card.
 
Documentation linked at bottom of this page. Search for Spaceinvader One on Youtube.

Because 
These are open by Docker and VM Manager, which must be disabled in Settings so the img can be moved 

Put flash in PC and checkdisk. While there make a backup. If checkdisk doesn't fix it, you can get your configuration on a new install by copying the config folder from your flash backup.
 
Often there are USB2 headers on the board.

Each parity drive must be at least as large as the largest data drive. Your parity2 disk is smaller.

explained in the diagnostics link