trurl

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

Do it again without -n. If it asks for it use -L. Post the results.

If you just move appdata from one pool to the other, it will merge them. If there are duplicates, it will ask if you want to replace. I don't expect duplicates though assuming all your containers only reference /mnt/user/appdata instead of /mnt/cache/appdata, for example.

Unassigned Devices plugin can read NTFS. Dynamix File Manager will let you work with folders and files directly on the server. 

You must have rebooted after disk1 became disabled, so no way to see why that happened.
 
SMART for disk1 looks OK so likely a connection problem. Emulated disk1 is mounted and has plenty of data. Should be OK to rebuild on top after checking connections.
 
https://docs.unraid.net/unraid-os/manual/storage-management/#rebuilding-a-drive-onto-itself

Also, Mover ignores any share where there is no Mover Action specified, which is what you have for all of those.
appdata shareUseCache="only" # Share exists on cache, disk4 domains shareUseCache="only" # Share exists on disk4 isos shareUseCache="only" # Share exists on disk4 P-------e shareUseCache="no" # Share exists on disk3 P---------V shareUseCache="no" # Share exists on disk4 system shareUseCache="only" # Share exists on disk4 They need to be Primary:cache; Secondary:array; Mover Action:array->cache

which is in
 

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

Those small laptop HDDs probably don't perform well. And your parity disk is SMR which might be the reason a pause helps it out.

Basically you just need to move all the data from one of those to other disks in the array, then New Config to get your disks assigned as you want.
 
Unbalanced is probably going to be the simplest way to automate that. You could do it manually with Dynamix File Manager.
 
I haven't used Unbalanced but I think it should work fine. If you are having problems maybe ask on its support thread.
 
You can go directly to the support thread for any of your plugins from its link on the Plugins page of your Unraid webUI.

You can access the current documentation from links at the top and bottom of the forum, or from the "manual" link in lower right corner of your Unraid webUI.

There has been an update to that plugin but I don't know if it is fixed.

Click on the SMART ( 👎 ) warning to acknowledge, and it will warn again if it increases.
 
Parity contains none of your data, so can't corrupt a data disk unless you use it to rebuild one of them.

Delete config/plugins/disklocation.plg file and config/plugins/disklocation folder from your flash drive and reboot.

docker.img is unmountable. Perhaps you filled it up.
 
Recreate
https://docs.unraid.net/unraid-os/manual/docker-management/#re-create-the-docker-image-file
and Reinstall
https://docs.unraid.net/unraid-os/manual/docker-management/#re-installing-docker-applications
 
Then post new diagnostics.

OK. Should be good to New Config and let it rebuild parity.
 

You should never format a disk that contains data you want to keep.
 
Format is a write operation. It writes an empty filesystem to the disk. When you format a disk in the array, Unraid treats this write operation just as it does any other, by updating parity. So, after formatting a disk in the array, the only thing it can rebuild is an empty filesystem.
 
Not enough information at this late date to know exactly what happened.
 
If you had asked for help when you were having problems maybe we could have saved your data.

Try deleting config/domains.cfg from your flash drive.

SSDs in the array cannot be trimmed, and can only be written at speed of parity

Contact support 

https://docs.unraid.net/unraid-os/manual/changing-the-flash-device/#what-to-do-if-you-have-no-backup-and-do-not-know-your-disk-assignments

All of your webUI settings are in the config folder on flash, including the user share settings.
 
But without any data, the shares won't actually exist.
 
You could create an empty top level folder named for the share on an assigned disk. That would be an empty user share and it would have the settings from the corresponding config/shares/*.cfg file.
 
Or you could just create the user shares in the webUI, and copy their settings from your flash backup.

Simple as that, except no need to set slot to no device. Just select the new device in that slot.
 
I prefer to reserve the verb "add" for situations where you are actually adding a disk to a new slot that didn't already have a disk assigned. Parity2, for example, in your case, but could be used when talking about a new data slot. What you are doing with the data disk is "replace".

You only need the config folder from your flash backup. It has all of your configuration (all settings made in the webUI), including your license and your disk assignments.