Hello,

first time with UnRaid. OS Version 7.2.3. HW is a Terramaster F2-424 with two 8TB HDD as array (one parity and one as Disk1), an 512Gb SSD configured as cache.

A docker container with UrBackup. I started using UrBackup to backup my laptop, but when the cache (SSD) is full, the mover does not move data to array. Now the Docker container is stopped.

Does anyone have suggestion?

Thank

TheGlider

Attach Diagnostics ZIP to your NEXT post in this thread.

Hello, attached the diagnostic ZIP file. Thanks for the help..

myunraid-diagnostics-20260207-1813.zip

Lots of things not ideal about your configuration. I will go through all of that first then make another post discussing Unraid operation.

USB not recommended for assigned drives for many reasons. And you may be experiencing one or more of those reasons with cache. Plus, nvme in a USB enclosure sort of defeats the purpose of nvme. Those may be OK as a substitute for a removable flash drive, but not for an assigned drive.

I recommend not using ext4 for cache, use one of the filesystems with more history and support with Unraid, btrfs or zfs.

Looks like there may be corruption with your ext4 cache. Since you haven't invoked mover yet don't know if that will be a problem for getting mover to empty cache so you can reformat it. Might make more sense to use that as an Unassigned Device to copy files to the array.

And it looks like cache may have more than one partition, since it is mounting as nvme0n1p2.

Also not getting SMART report for that drive, almost certainly because of USB.

Do you have any way you can reconfigure your hardware so you are not using USB for an assigned drive?

Mover runs on a schedule. Default is once-per-day in the middle of the night. You can manually invoke mover by clicking the MOVE button in Array Operation.

Nothing can move open files. Disable Docker in Settings until you get cache setup again. And make appdata share cache-only before you enable Docker again.

Mover is intended for idle time. It is impossible to move from fast cache to slow array as fast as you can write to cache. And if you try to do both at the same time it is even worse. If you need to write more at one time than cache can hold, don't cache.

For initial data load, you can unassign parity to make array writes faster, then build parity after initial load completes.

21 minutes ago, trurl said:

For initial data load, you can unassign parity to make array writes faster, then build parity after initial load completes.

Since you have single parity, single data drive, it is effectively a mirror simply due to the way the parity calculation works. In this specific case, array writes are not slowed much by having parity.