the share config of system and domains are same to this

Because the appdata share contains files on the cache drive.  (Although generally for performance and hydro savings you would generally want appdata to be confined to the cache drive and then back it up)

 

To fix (if you want it on the array), change the settings to use cache: Yes and then settings - Docker, disable the service.  Main - Array Operations, run mover.  After its done, change the settings back to "No" and then re-enable docker

 

To have the share confined to the cache drive, do the above but set it to use Cache: Yes in the first step and disregard the last step

Those unprotected shares are on your cache which is not part of the parity array and therefore not protected. Mine is the same way, it is normal. If you had a 2nd cache disk this could form a btrfs raid 1 therefore protecting data on the cache. Additionally bare in mind any data written to shares in your array which use the cache disk until the mover moves these files into the array will also be unprotected in the case of hardware failure.

For performance reasons it is recommended to keep said folders on the cache disk.

As @Dissones4U already explained, changing the cache from a single device to a pool with multiple devices, will add protection (green orb)

thanks for your reply

I add a cache disk to fix this