trurl

That is the best way anyway. Parity swap is really for those situations where you already have a data disk that needs replacement, but you want to buy a disk larger than parity.

Old wiki from old versions.
 
Go to the Documentation link at the bottom of the forum

Check filesystem on disk2.
 
That by itself wouldn't normally cause crash though.
 
Setup syslog server.

Create another pool and put the SSD there 
https://wiki.unraid.net/Manual/Storage_Management#Multiple_Pools

Not just dockers affected
Could not download current plugin versions  

Format the emulated, missing disk to make it an empty filesystem. Make very sure it is the only disk listed for formatting. Then assigning a new disk to that slot will rebuild the newly formatted filesystem onto the new replacement disk.
 
Then restore data from backup.
 

YES
NO
YES
 

Try creating flash drive manually
https://wiki.unraid.net/Articles/Getting_Started#Manual_Install_Method

The initial burst of speed is simply RAM buffering. After that, write speed will be slower than single drive speed due to parity updates. Turbo would often be faster than 30 though. One thing you could do is remove parity until initial data load is done, then build parity after.
 
Attach diagnostics to your NEXT post in this thread and we can check your hardware and configuration.

Your krusader appdata mapping goes to /mnt/cache, but you have no pool named 'cache'. Probably you renamed your pool without fixing that mapping.

Each user share has settings to control whether and how it uses cache. If you are copying to a user share and don't want it cached set it cache:no.
 

You can see how much of each disk is used by each user share by clicking Compute... for the share on the User Shares page. Ultimately you want all of appdata, domains, system shares on cache, and all of other shares on the array. Then you can cache that m---a share if you want, but it must be set cache:yes or it will not get moved to the array.

First high-water on 14 is at 7. Since 7 is still larger than other disks it continues to next high-water at 3.5 before deciding whether to switch. 

In the Unraid webUI of your server, there is a Dashboard page that displays your dockers, and there is also a Docker page that displays your dockers.
 
If you click on the icon for the specific docker you want support for, on either of those pages, and click Support, it should take you to the support thread already created for that specific docker.
 
I don't have that docker installed, but another way to get to the support thread for a specific docker is to choose the docker from the Apps page and click the Support link displayed with its description.
 
Here is the Support thread for that docker which I got from the Apps page as I just described.
 
 

Do you have a current backup of the config folder from your flash drive? The config folder is all you need to get going again with your configuration on a new install.
 
Prepare a new install of whatever version on a good flash drive and see if that will boot.

Simply changing that setting just controls what it will do with new files, and mover ignores cache:only
 
You have to set it cache:prefer to get mover to move it to cache.
 
And nothing can move open files, so you have to disable Docker and VM Manager in Settings so it can be moved.
 
Also, mover won't replace files, so if anything is already on cache you will have to decide whether to keep those or the system files on disk1.
 
Install Dynamix File Manager plugin it will let you work with files directly on the server.
 
What do you get from command line with this?
ls -lah /mnt/cache/system and this?
ls -lah /mnt/disk1/system  

Recreate flash drive as a new install of whatever version. Copy config folder from your backup.
 
Not clear the guacd segfaults are related.
 
Have you done memtest lately?

This means the server is not getting DHCP from the router. Check network connections
Also, link to diagnostics instructions

setup syslog server
 
also
 

Jan 5 09:50:20 PlexNAS kernel: mdcmd (61): nocheck cancel Jan 5 09:50:20 PlexNAS kernel: md: recovery thread: exit status: -4 Jan 5 09:50:39 PlexNAS kernel: mdcmd (62): check correct Jan 5 09:50:39 PlexNAS kernel: md: recovery thread: recon P ... Jan 6 03:40:01 PlexNAS crond[1122]: exit status 1 from user root /usr/local/sbin/mover &> /dev/null Jan 6 05:09:29 PlexNAS kernel: md: sync done. time=69530sec Jan 6 05:09:29 PlexNAS kernel: md: recovery thread: exit status: 0 Looks like it was restarted and completed 

I would say you can just move the disks over, but things get more complicated if there are RAID controllers involved on either server. One of many reasons RAID controllers are not recommended. And it might also be more complicated if you have USB drives, as it sounds like you do. One of many reasons USB connections are not recommended.

How will you access the 8TB if the array is stopped?
 
With the array started, you can mount the old 4TB disk as an Unassigned Device and copy files to it.
 
Then you can New Config with the 4TB in place of the 8TB and rebuild parity.

Tools - New Permissions on only that share.