I am new to Unraid but successfully built a server and had good success with it up to recently. I have added a number of extra drives to the array and I have done Parity check and sync (took a day). Since I have started to move content onto the server it has crawled to almost a stop when my transfer rates are 5-15Mb/s tops and my cache drive is still trying to move my content (currently been running for 3 days). Any advise on how to figure out what is wrong?

hal-9000-diagnostics-20250316-0954.zip

Edited March 16, 20251 yr by MatrixUK
To attach diagnostics

For the initial data move, it's usually preferable to disable cache for shares, and transfer directly to the array.

 

@JorgeB This was my prefered first way of doing it; however it was quoting me 7 days to transfer 8TB of data and I have a lot more than 8TB to transfer

Mover is intended for idle time.

 

It is impossible to move from fast cache to slow array as fast as you can write to fast cache. So, it fills up.

 

If you have Secondary storage set to Array, and Minimum Free for cache and for the user share configured, when cache fills, it will "overflow" to the array, at which point you are writing to the array anyway. If you don't have Secondary storage and Minimum Free configured, writes will fail when it runs out of space.

 

52 minutes ago, JorgeB said:

For the initial data move, it's usually preferable to disable cache for shares, and transfer directly to the array.

Unraid parity is realtime. Each write to the array also updates parity. Another strategy is to not assign parity until initial load is complete, then build parity after, that way that initial data load will not be impacted by parity updates.

You can also use turbo write, it should improve the array performance considerably, assuming no controller bottlenecks.