So i have been battling with terrible performance in unraid and after trying for hours i decided to just start with a fresh install.

 

I made a backup of my unraid key and reinstalled unraid to the flash drive so I could start fresh.

I started unraid up but cancelled the parity check to copy backup of my plex appdata back to the cache drive. I dont have critical files. I formatted my two SSD drives as zfs. 2 seperate pools. One for downloads and one for VMs and docker.

I brought up the web terminal and started copying the plex appdata folder to the cache drive. The copying started off quickly copying a few thousand files every 5 seconds or so. Plex is full of small files. Thing is the copying pauses after about 10 seconds completely and I can see high IO wait and CPU usage. Surely copying from HDD to SSD shouldn't be a bottleneck. There is absolutely nothing else installed on this fresh install other than the community applications plugin so that I am ready to install plex after the copy.

 

So I am beginning to think that I have a hardware issue. Does anyone have any suggestions? I will include my diagnostics. Really hope someone can help here. 

 

Thanks for taking the time to read.

tower-diagnostics-20230627-2106.zip

I have my SSDs connected to an LSI hba from 2011. Wonder if that might be the problem. I am going to try and connect all drives to onboard.

Got to 98% of the copy being done and now file transfer has stopped for about 20 minutes. Hmmm. At a loss

Why do you have Docker and VM Manager enabled in Settings if you're not ready to run them yet? Their files have been created on the array since all your shares are set cache:no

I dont remember starting them.

 

Before starting freshI had followed spaceinvaders guide to change my SSD drives to zfs. I changed all shares to move the files from cache to array drive. So maybe because those shares existed when I booted up for the first time docker and VM manager were automatically started? I have disabled them now.

Swapped out my SSD and all is working. Extended tests did not show any issues with that drive. I swapped the sata cable too, so that may have been it.

Did you fix your Docker/VM related shares? appdata, domains, system shares should ideally be all on a fast pool with nothing on the array so Docker/VM performance will not be impacted by slower parity, and so array disks can spin down since these files are always open.