trurl

No ethernet connection. Check ports, plugs, cables on server, switch, router.

If you're sure you don't need anything still on the original disk now, you can rebuild the contents of the emulated disk onto that original disk by stopping the array, reassigning the disk to its slot in the array, and starting the array to being rebuild. Note that the contents of that original disk will be completely overwritten by the contents of the emulated disk.
 
Please let us know if you have questions or other problems.

cache:only and cache:no are ignored by mover

Your subject line says NFS but then your text talks about Windows and doesn't mention NFS. Are you sure you don't mean SMB?
 
I think some had permission problems after upgrade perhaps because they were more strictly enforced. You might try Tools - Docker Safe New Perms.
 
 
 
 

all of these shares currently have files on cache and on the array. You also have several cache:no shares with files on cache. Mover ignores cache:no shares.
 
Nothing can move open files. Disable Docker and VM Manager in Settings. Set all these shares to cache:yes, run Mover so it can try to move them to the array. Mover won't replace files so if any are already on the array you will have to decide which to keep. You can use Dynamix File Manager plugin to help with this.
 
After everything is off cache, you can reduce it to the one good disk, might be a good idea to reformat it, then you can set appdata, domains, system shares back to cache:prefer and move them back to cache. Might be best to not cache any other shares until you get things working well and see how much capacity is left for caching.
 
Then you can follow the links I gave above to get dockers recreated.

13+ years!
 
SMART attributes don't look bad, but it looks like it's been a while since it passed an extended SMART test. You could try that if you want but it might be better to just move those shares to the other pool as I suggested until you can replace that disk with SSD.
 
You will have to recreate docker.img
 
 

You will have to check filesystem without -n before it will actually do the repair. And add -L if it asks for it.
 
Filesystem repair very often does not give perfect results. Do you have backups of anything important and irreplaceable?

If there is no data on that particular disk you can just format it in Main-Array Operations 

parity2 not connected. Check connections, SATA and power, both ends, including splitters. Then post new diagnostics

Doesn't look like you have formatted any disks yet so there is no place to put anything.
 
Also, better if you put that SSD assigned as disk2 in a pool (cache). SSDs in the parity array can't be trimmed, and can't be written any faster than parity.

Yes

No point in emptying drives or shrinking the array to replace disks. Just replace and rebuild.
 
If your current parity is as large as the new disks then no problem. If not then you need to replace parity first. Each parity has to be at least as large as the largest single data disk.

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

Filling rootfs will definitely make for an unresponsive server, since the OS has no room to work in if you fill rootfs
/mnt/plex is a path in rootfs. Check your docker host paths.
 
Also, your system share has files on the array

Latching cables can have problems with some WD drives
https://support-en.wd.com/app/answers/detailweb/a_id/15954

https://wiki.unraid.net/Manual/Shares#Default_Shares
 
https://wiki.unraid.net/Manual/Shares#Use_Cache_.28and_Mover_Behavior_with_User_Shares.29

See if you can copy flash drive on windows, config folder is all you need to get going again with your configuration on a new install 

Nov 6 09:52:21 Odin emhttpd: Unraid(tm) System Management Utility version 6.11.2  

The boot disk can't really crash.
 
The Unraid OS runs in RAM. The flash drive just contains the archives of the OS, which are unpacked into RAM at boot, and it runs completely in RAM. Flash drive also saves settings from the webUI so they can be reapplied at boot.
 
When you have problems getting diagnostics what do you get from the command line with this?
df -h  

Assuming your disk assignments are correct

Parity2 depends on the specific slot assignments of each disk. As long as you don't change any slot assignments and just remove the zeroed disk and leave its slot empty then parity2 would be valid. 

RAM buffering
 
Not unusual for writes to parity array
 
https://wiki.unraid.net/Manual/Storage_Management#Performance

Copy key from old flash to new and you can transfer from webUI
 
https://wiki.unraid.net/Manual/Changing_The_Flash_Device

You really mean ethernet is 1Gbps, and 95MBps is reasonable considering the network speed even if the destination drive can handle more.