trurl

No reason to expect xfs_repair to help with windows filesystem. 
 
You can go directly to the correct support thread for Unassigned Devices by clicking its Support link on your Plugins page 

Can't imagine why you think preclear is needed.
 
If you New Config/Trust Parity, you will still need a parity check, so might as well rebuild the disk or rebuild parity. As you say, rebuilding the smaller disk will be faster.

User Scripts plugin

The server requires ethernet

https://docs.unraid.net/unraid-os/manual/vm-support

Maybe not the cause of crash, but you seem to have a problem with the flash drive.
Aug 1 06:57:45 UnRaid kernel: critical medium error, dev sda, sector 15629312 op 0x0:(READ) flags 0x84700 phys_seg 29 prio class 2 Do you have a backup of flash?

Disconnects such as you are experiencing is one of many reasons USB not recommended for array or pools.
 
Also, SSDs in the parity array cannot be trimmed.

If cache drops below Minimum Free, cache:yes (and prefer) shares will overflow to the array, but you have 0 Minimum Free for cache. You must set Minimum Free for cache to larger than the largest file you expect to write to cache.
 
Each user share has a similar setting. If a disk drops below Minimum Free when writing the user share, Unraid will choose another disk. Except... Split Level overrides Minimum Free.

There is no "USB tab" on standard Unraid install.
 
Do you have some plugin for that?

Disable Docker and VM Manager in Settings until you get your cache problems fixed.
 
Your system share should really be set to cache:prefer but we can deal with that later.
 
Do that and let us know

Attach Diagnostics to your NEXT post in this thread instead of linking to external sites. 
 
Did you format the disks after adding them to the array? 

Why 2? Parity is not required. You just need a single data disk in the array to start. And without parity, USB disconnects don't require rebuild since there is no way to do rebuild.
 
Sounds like you want to use the other features of Unraid without its NAS capability. Just assign a single array data disk, can even be a USB flash drive, no need to even use it for anything. That will allow you to start the other services such as Docker.

Looks like multiple drives connection problems. How are your drives connected to power? Any splitters? All on the same power cable?
  
But is that available for the drives? Some PC power supplies expect to give most of the power to GPU with not many disks. What is the exact model of your PSU?

Jun 20 02:08:35 KW-UNRAID move: move_object: /mnt/cache/Veeam/Veeam Backup: Read-only file system Jun 20 02:08:35 KW-UNRAID move: file: //..g/... Jun 20 02:08:35 KW-UNRAID move: create_parent: /mnt/cache/appdata/Plex-Media-Server/Library/Application Support/Plex Media Server/Logs/PMS Plugin Logs error: Read-only file system  
Looks like all your shares are currently cache:yes, perhaps trying to fix the problem of filling cache. Your cache has plenty of capacity. Can you provide more details about how you managed to fill it?
 
Set appdata, domains, system shares cache:only so mover won't try to move them for now. Set Veeam and other shares cache:no so mover won't try to move them for now.
 
You may have to backup files on cache and reformat it.
 
Have you done memtest recently?
 
 

Primary storage: cache
Secondary storage: array
Mover Action: cache --> array

I know you already went past this, but the answer is NO. Some file and folder names have been changed to UPPER CASE for some reason (not sure that matters since flash is FAT anyway) and the first character of some names have been replaced with _
 
But that brings me to this
Copied them from where?
 
As mentioned, parity can't help with this. Parity check only checks parity, it won't do anything to any data disk. Even a correcting parity check only corrects parity, it doesn't do anything to any data disk. Parity itself contains none of your data.
 
Any recovery options probably involve paid software

Use the Unlock 🔒 button on the main bar
 

This is just doing a normal New Config/Parity Rebuild. The only thing that matters is the disk to be removed is not assigned when you rebuild parity.
 
A formatted disk is not a clear disk. A formatted disk contains an empty filesystem. Only a clear disk can be removed without invalidating parity. A clear disk is all zeros so has no effect on the parity results.

Disable Docker and VM Manager in Settings until all your files are back on the server.

Close all browsers, tabs, mobile applications that might be accessing your Unraid webUI. Then open a single new browser tab and see if it shows your array is started.

Have you done memtest?

But definitely not necessary to get swag working on another port. Map those ports in the container to different host ports, port forward in your router to those different host ports.