Hi 

 

I updated to 7.0.0 and got an error message which stated appdata should be set to cache disk. All my docker containers were not visible. I went into the shares/appdata page but the option to select cache was grayed out.  Thinking there was probably some install error I downgraded back to 6.12.14.

 

It was set to cache in 6.12.14 before I upgraded to 7.0.0 however after downgrading back to 6.12.14 I still get the same error message and the option to select cache is grayed out here too. I cannot figure out any method select the cache disk for appdata.

 

Could someone please look into this and let me know what I am doing wrong. 

 

Screenshots from shares/appdata and Fix common problems is attached. 

 

PS: the first message in Fix Common Problems page is the same as the one I received in 7.0.0, the second message is a new one I received when I downgraded to 6.12.14

 

 

Edited January 13, 20251 yr by frostimunki
info edit

Please post the diagnostics.
 

Hi 

 

Diagnostics zip file attached. 

 

Thanks for taking the time to review the issue. Some other notes

 

When upgrading the system, I stop the array and reboot manually.

 

When the error occurred in 7.0.0 I rebooted the system with the array stopped and then rebooted with the array started. Then power-cycled the system with the array stopped and array started. 

When I downgraded the system to 6.12.14 and faced the same cache disk error, I rebooted and then power-cycled the system with the array stopped and array started both times. 

henereauxbase-diagnostics-20250114-1158.zip

Edited January 14, 20251 yr by frostimunki

With the array stopped, click on the pool and then enable this:

 

Hi 

 

Enabled User Share Assignment

 

I can now choose Cache as the primary and Array as secondary, However the original error "Default docker appdata location is not a cache only share" still appears when I run Fix Common Problems. (see screenshot below)

 

FYI : Yesterday I had installed binhex-Krusader as a test docker install. At that time the appdata directory was created on Disk4/appdata in the array. In that install I had set up some bookmarks which were different from the ones I usually use in Krusader. Once the cache issue was "fixed" per your solution Krusader automatically picked up my regular bookmarks from the cache/appdata. 

 

After applying your solution I also reinstalled the following

- binhex-Krusader

- ich777's SABnzbd, radarr & sonarr

 

All of them worked with their previous configs including bookmarks in Krusader, server passwords in SABnzbd, also the indexers and download clients were picked up from cache/appdata in radarr and sonarr icluding monitored.

 

Since test installs configs are picked up from cache/appdata I assume cache/appdata is able to be read by docker containers. 

 

 

 

 

Please review and see if you can provide further help!

 

 

 

If you look closely at the Suggested Fix section of Fix Common Problems it's telling you that since you have your appdata share set to Cache -> Array and not just have cache as the primary with no secondary, when mover runs applications will have a performance issues. You could ignore it if you don't care about application performance while mover is running, or just set the appdata share to cache as the primary and not have a secondary to remove the error.

Also I think you'd have to manually move the appdata files from the array to the cache drive or you'll get a warning that appdata files exist on the array, or if you're not confident doing it manually you could temporarily set the appdata share to Array -> Cache and run mover, then switch it back to cache only.

@JorgeB

 

Thank you that worked to enable cache for appdata. I have marked it as a solution.

 

@lovaan

 

Thank you for helping me understand the concept of "cache only" for appdata! I followed your instructions and this works. Your instructions combined with the instruction from JorgeB helped solve this issue for me.