itimpi

Not if you the ‘md’ device. When you use that it will keep parity in sync. it would have been easier to do it from the GUI then you do not need to worry about getting device names right.

Checked the earlier diagnostics and you are correct. I missed that when I looked at them and it was not that clear in the screenshots. Until parity is rebuilt there will be no protection.

The Use Cache setting determines where NEW files are placed. You should read the help built into the GUI to understand the effect of this setting, and how the settings affect mover behavior. If Unraid was starting from scratch then different words might have been used for the values. However this not the case and originally only the Yes/No options existed. Much later the Prefer and Only options were added and by this time it was too late to change the Yes/No options without confusing existing users.

You could use the Parity Check Tuning plugin instead. That is more flexible and does everything the cumulative check does and much more. It also (although not relevant here) runs on earlier Unraid releases.

The Docker Safe New Permissions option is only available if you have installed the Fix Common Problems plugin. The screenshot you post is for the New Permissions tool that comes as standard with Unraid. Despite the preamble you can run it any time you think you have a permissions issue. Just select what you want it to be applied to and click Start.

There is a lot of out-of-date information in the wiki (although it is largely correct). You should if possible always use the the official online documentation accessible via the ‘Manual’ link at the bottom of the GUI. The relevant part is this

You need to make sure it gets formatted as FAT32. Windows will not do this on drives larger than 32GB so you may need to use a 3rd party tool to achieve this.

The version provided with Unraid will not work with UEFI boot. If you want a version that will download it from memtest86.com

Look like it Not sure how that could happen though ss I did nothing out of the ordinary to make it happen.

Did you click on the link I provided as that should have provided the instructions needed. If you did click on the link then please mention what could be added to make it clearer.

I strongly suspect that is s false value. It is technically not possible for parity to run that fast on HdDs.

It means array operations such as parity check, read check, parity sync, rebuild Just start mover and after a short delay the plugin will detect that mover (assuming you have enabled the option) is running and will pause the array operation and then resume it when mover finishes.

As mentioned elsewhere why not use some of these additional drives in pools rather than the main array?

It is 30 drives in the main array, but you can also have multiple pools of up to 30 drives. I think this makes the max number of drives supported of the order of 1000. There is a roadmap item to add multiple main arrays - no idea on the ETA or the number of such arrays that will be supported when/if this feature arrives.

You should make sure you set a value for the Minimum Free Space for the cache to stop Unraid trying to fill it up (you currently have it set to 0).