trurl

Yes, that is a side effect of deleting docker.img. From command line docker network create proxynet

For more on the general case (or maybe 2 general cases) of writing parity, see here:

1 parity 1 data is a special case

Not enough info in those for me to know. Are you booting from USB2 port?

Yes I have 20G docker.img, only 44% used with 17 dockers running.

Yes, but why did you have 35G allocated to docker.img? Had you had problems filling it? 20G should be more than enough and if it grows then you have application misconfigured. Its contents will be downloaded again when you reinstall dockers. Be sure to use the Previous Apps feature on the Apps page.

A properly prepared flash drive is using FAT32 filesystem which is native to Windows. How did you prepare flash drive originally? Do you mean you can access the webUI on the network but not on the local machine, or is it still not working at all?

Note however that the disabled disk had at least one unsuccessful write that caused it to be disabled, and possibly more emulated writes after that. All those writes would be recovered by rebuilding from parity.

Put the flash drive in your PC. Let it checkdisk, then copy config folder from flash to your PC

Copy config folder from flash. Prepare flash as a new install. Copy config folder to flash. Be sure to boot from USB2 port. If still network issue delete config/network.cfg from flash to use defaults.

no wouldn't hurt

Have you done memtest?

In any case, don't cache initial data load. There is no way to move from cache to array as fast as you can write to cache. Mover is intended for idle time.

Some people wait until after the initial data load before installing parity. Then writes are not slowed down by parity updates, and writing to multiple disks simultaneously as you suggested might perform well without parity.

Just in case anybody goes looking for the diagnostics mentioned, the user has deleted them.

Another note about this. In order to get your templates reused, you must use the Previous Apps feature on the Apps page. If you just try to install a docker without using Previous Apps, you will get a fresh template for that docker.

You can but they will likely perform better if you do them separately since both will require updating parity even if the shares are on different disks.

no But syslog resets on reboot so unless you have older syslogs (Syslog Server?) no way to see what happened before last reboot.

No, just make your appdata source your appdata and only backup appdata that way. There is never any need to backup docker.img since it is only the executable code for the installed dockers and these are easily downloaded again. CA Backup also has a provision for backing up flash and libvirt.img. The usual way is to let mover take care of moving these cache-prefer user shares to cache. That is what cache-prefer means, prefer to keep these on cache. However, mover can't move open files, so you will have to disable Docker and VM Services (Settings - Docker and Settings - VM Manager) before going to Main - Array Operation to Move. You can see which disks each User Share is using by clicking on Compute... for the share. Post diagnostics if you want more detailed advice.

So is (or was) your server on the internet? If so, you have likely already been attacked.

Here is the way Minimum Free works. Unraid has no way to know how large a file will become when it chooses a disk for it. If a disk has more than Minimum remaining, it can be chosen, depending on other things like Allocation Method and Split Level. Note that Minimum Free doesn't mean that it will keep that much free, it just means it won't choose that disk if it has less than Minimum. For example, if Minimum is 50G and a disk has 60G remaining, it can be chosen, even if the file winds up being 40G. Or even if the file winds up being 100G, in which case you get an out-of-space error. The general recommendation is to set Minimum to larger than the largest file your expect to write. I don't know how you chose the Minimum you set but I expect it had nothing to do with the way that setting actually works. Also note that Split Level has precedence over Allocation Method and Minimum Free, so Split Level can make it choose a disk that is completely full. Has it begun to write Movies to disk4 yet? If not then you probably just need to change your Split Level.

According to your diagnostics appdata, domains, system shares are still cache-yes. Did you change them to cache-prefer after taking those diagnostics? Why did you post so many screenshots of your Movies settings? Is there some difference between those that I am supposed to be looking for? I will have more to say about Minimum Free in my next post.

Would everyone please stop. I agree this thread was off to a bad start but if you don't have anything constructive to offer regarding the actual problems please go on to another thread.

Any write operation on any array data disk updates parity. Parity wouldn't be valid otherwise. And anything that is not strictly a read operation is a write operation. For example also updates parity since delete is a write operation.