trurl

There will always be some space used even on a newly formatted disk due to filesystem overhead.

This requires a VPN service outside your network.

I've never seen it ask that. Attach Diagnostics to your NEXT post in this thread.

See if your flash drive has FSCK files at the top level. These will result from running fsck

Are these devices on your LAN? Do they require transcoding?

What exactly do you mean by "same"?

Assuming no RAID controllers involved in old or new system, it should be just that easy.

Did you reinstall all of your containers? It is only using 5.8G. Usage shouldn't grow unless you add containers, and even then shouldn't grow a lot. The usual cause of filling docker.img is an application writing to a path that isn't mapped to host storage. I don't use that. Click its icon and select Support

Delete config/plugins/disklocation.plg file and config/plugins/disklocation folder from your flash drive and reboot.

No way to know since it is unmountable. We can take a look at how much is used after you recreate, but leave it at default 20G for now. Making it larger probably won't keep you from filling it.

docker.img is unmountable. Perhaps you filled it up. Recreate https://docs.unraid.net/unraid-os/manual/docker-management/#re-create-the-docker-image-file and Reinstall https://docs.unraid.net/unraid-os/manual/docker-management/#re-installing-docker-applications Then post new diagnostics.

You should see a SMART ( 👎 ) warning for that disk on the Dashboard page. Setup Notifications to alert you immediately by email or other agent as soon as a problem is detected.

5 Reallocated_Sector_Ct PO--CK 097 097 010 - 9168 Too high for my comfort. Plus Model Family: Seagate BarraCuda 3.5 (SMR) SMR for parity is not ideal. I would replace with CMR drive.

https://docs.unraid.net/unraid-os/manual/storage-management/#rebuilding-a-drive-onto-itself

Attach Diagnostics to your NEXT post in this thread.

Check connections, both ends, SATA and power, including splitters.

Still no SMART report for parity

Do you have a paid license now?

Unrelated to the corruption Your "app" share where you have your docker.img and default appdata location configured, has some files on disk3. Ideally, these would all be on fast pool such as cache, with nothing on the array, so Dockers can perform better, and so array disks can spin down since these files are always open. Instead of reconfiguring things so Mover will move those for you, it's probably simpler to clean this up yourself with Dynamix File Manager plugin. Nothing can move or delete open files so you will have to disable Docker in Settings.

Cache and many other things are discussed on that page of the documentation, but the direct link I gave was not about cache. Please read the exact section I linked.

https://docs.unraid.net/unraid-os/manual/storage-management/#array-write-modes

You can go directly to the correct support thread for this docker by clicking its icon and selecting Support.

These seem to be local IPs. Do you know what computer this is? Mar 14 16:08:45 VicTower login: FAILED LOGIN 1 FROM laptop-7gmqkf7u.lan FOR , Authentication failure

Don't know what else to suggest. Does the monitor have controls you can use to adjust the resolution?