I get the following warning from Fix Common Problems:

 

**** Share appdata is an implied array-only share, but files / folders exist on the cache ****  **** Share domains is an implied array-only share, but files / folders exist on the cache ****  **** Share isos is an implied array-only share, but files / folders exist on the cache ****  **** Share system is an implied array-only share, but files / folders exist on the cache **** 

 

I have a new install of unRAID 6.2.4 and these shares were created by the installer, not by me.  They all have cache set to "no". What is the easiest / sanest way to fix this?

That's a little odd.  It's worth browsing this post:

 

http://lime-technology.com/forum/index.php?topic=51874.0

 

Specifically this section:

Automatic System Shares

 

When starting the array a share called "system" will be automatically created with the "Prefer" cache mode.  "Prefer" means the share will be created on the cache disk/pool if present, otherwise on the array.  If created on the array, and then later a cache disk/pool becomes available, the "mover" will attempt to move the share to the cache disk/pool.

 

When Docker is started, a subfolder called "docker" will be created in the "system" share where a loopback image file called "docker.img" will be created for the service.  In addition, a share called "appdata" will be automatically created with the "Prefer" cache mode.  The "appdata" share is the default location where per-container "application data" is stored.

 

When Virtual Machine manager is started, a subfolder called "libvirt" will be created in the "system" share where a loopback image file called "libvirt.img" will be created for the service.  In addition, a share called "domains" will be automatically created with the "Prefer" cache mode, and a share called "isos" will be automatically created with "Use cache" mode.  The "domains" share is the default location where virtual machine vdisks are stored, and the "isos" share is the default location where various ISO files are stored for assignment to virtual machines.

 

NOTE:  Existing configured paths for the docker.img and libvirt.img file, as well as for "appdata" and "domains" will not be modified upon upgrade.

So those shares were supposed to be set to "Prefer" by the install process, not "No".  If you change them to "Prefer" the content will be moved from the array back to the cache drive.  That's where you want your appdata, system, and domains files - on the cache drive.  Don't forget to back them up to the array, though.  The Community Applications Plugin can help with Docker backups, if you don't already have another solution.

That seems to have helped.  Thanks.

 

I get the following warning from Fix Common Problems:

 

**** Share appdata is an implied array-only share, but files / folders exist on the cache ****  **** Share domains is an implied array-only share, but files / folders exist on the cache ****  **** Share isos is an implied array-only share, but files / folders exist on the cache ****  **** Share system is an implied array-only share, but files / folders exist on the cache **** 

 

I have a new install of unRAID 6.2.4 and these shares were created by the installer, not by me.  They all have cache set to "no". What is the easiest / sanest way to fix this?

I assume this new install was using disks that already had data on them. In that scenario if you didn't copy the .cfg files from the config/shares folder of the old install, you would probably get default share settings for all top level folders, since top level folders are automatically shares with default settings. And default share settings are cache-no. You might check the settings of all your other shares to make sure they are what you want.