trurl

Flash drive not working. Try another. 

Aug 27 22:50:10 Tower kernel: critical medium error, dev sda, sector 4489222 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 2 Several of these in syslog. Looks like flash drive should be replaced.

You have to reboot to get Unraid to use it as its boot drive again.
 

Nothing can move or delete open files. You have to disable Docker and VM Manager in Settings to work with these shares.

Unbalanced plugin can move the data. New Config to rearrange your disks 

Does it work if you remove the Mover Tuning plugin?

For appdata, you really want Primary storage to be one of your pools, and Secondary storage as array.
 
Can you select one of your pools as Primary for appdata?
 
Same for your domains and system shares.
 
After you get those shares settings fixed, you will need to disable Docker and VM Manager in Settings so these shares can be moved to your designated pool.

Just in case you have some other idea. FORMAT is definitely NOT what you want to do unless you don't want that data.
 
Filesystem check is what you need to do, and it often won't take a lot of time to complete.
 
So
 
Be sure to do the check using the webUI and not the command line. Easy to get the command wrong.
 
Possibly the filesystem was already unmountable before you did the rebuild and you didn't notice. Rebuilding unmountable will always result in unmountable. We usually recommend filesystem check and repair before rebuild.
 
Also, I never do rebuild or sync in maintenance mode. You should be able to continue to use your server during rebuilds in normal mode, though performance will be impacted so large transfers should be avoided.
 
Sounds like you may still have the original 4TB disk with its contents. You could see if it will mount as an Unassigned Device so that could give another option for recovery.

Your domains and system shares are on the array. You will have to move them to cache yourself (Dynamix File Manager plugin), or set them to Primary:cache; Secondary:array; Mover Action:array->cache to get mover to move them.
 
Nothing can move open files, so you will have to disable Docker and VM Manager in Settings before these can be moved.

You can go directly to the correct support thread for any of your plugins by clicking its Support link on the Plugins page of your Unraid webUI.

In what way did the disk fail? Bad connections are more common than bad disks. Can you get a SMART report from the disk?

USB2 port is more reliable.

Another possibility is to unassign parity until initial load is completed. We often recommend just this. Then parity will rebuild when you reassign it.
 
Do you have another copy of anything important and irreplaceable? Parity is not a substitute for backups.

All of your configuration, any settings you have made in the webUI, is in the config folder on flash.
 
You should always keep a current backup of your flash drive.

You can go directly to the correct support thread for this container by clicking its icon in your Unraid webUI and selecting Support.

Delete or rename config/network.cfg on your flash drive.

Corrupt docker.img
 
https://docs.unraid.net/unraid-os/manual/docker-management/#re-create-the-docker-image-file
 
https://docs.unraid.net/unraid-os/manual/docker-management/#re-installing-docker-applications
 
Also you should fix
Jun 1 10:34:02 Tower root: Fix Common Problems: Warning: Share appdata set to cache-only, but files / folders exist on the array Jun 1 10:34:02 Tower root: Fix Common Problems: Warning: Share tempjunk set to not use the cache, but files / folders exist on the cache drive Jun 1 10:34:03 Tower root: Fix Common Problems: Warning: Plugin unassigned.devices.plg is not up to date  

How do you know you are connected to Unraid with the correct user? 
 
After Windows has established a connection with one user it won't use another even though it might ask you to login again. 
 
Delete the Unraid credentials in Windows Credential Manager and establish the login again. 

6.11.5
 
Disable Docker and VM Manager until you get cache working again. Since there was no filesystem on cache, appdata, domains, system shares have been created on the array.
 
Do you think you might have filled cache? btrfs sometimes seems to have problems if you fill it up. You should set Minimum Free for cache, and for each of your user shares, to larger than the largest file you expect to write to cache or the share.
 
You can try to scrub cache, but I think the usual advice is to reformat.
 
 

Corrupt docker.img. Seems unlikely that you would have filled it though. Have you done memtest? If not, you might do that before anything else just in case. You never want to run any computer unless memory is working perfectly.
 
You will have to delete, recreate, reinstall docker, but we will get to that later.
 
Your appdata and system shares have files on the array.
 
Ideally, appdata, domains, system shares would have all files on cache or other fast pool, with nothing on the array, so Dockers/VMs will perform better, and so array disks can spin down since these files are always open.
 
Nothing can move or delete open files, so you will have to disable Docker and VM Manager in Settings before you can work with these.
 
Then set these shares to Primary:cache; Secondary:array; Mover action:array->cache.
 
Then run Mover, wait for it to finish, and post new diagnostics.