October 27, 2025Oct 27 Hi there,I have two cache drives on my new setup. Despite setting the system share being set to operate off of my cache_system drive, it instead appears to be storing all of the files on my cache_data drive instead. I can't work out why this would be happening and any insights would be great. Diagnostics attachedthemagiceye-diagnostics-20251027-1850.zip Edited October 27, 2025Oct 27 by nametaken_thisonetoo Clarity
October 27, 2025Oct 27 Author 10 hours ago, JorgeB said:Type touch /mnt/user/system/a then post new diagsThanks so much @JorgeB , I've just done that and posted the updated diags. Also, taking a closer look it appears the system folder on my cache_system drive is emptyBut then on the cache_data drive there is also a system folder populated with a single sub-folder called 'docker'. This has lots of folders/files within it and seems to be regularly updated.My Docker settings have the following paths, so I really don't understand how I got myself to this point haha themagiceye-diagnostics-20251028-0704.zip
October 28, 2025Oct 28 Community Expert The new file was created on the correct pool, so the share settings are working. Note that any existing files won't be moved there automatically from the other pool, you would need to move them manually or use the mover.
October 28, 2025Oct 28 Author 1 hour ago, JorgeB said:The new file was created on the correct pool, so the share settings are working. Note that any existing files won't be moved there automatically from the other pool, you would need to move them manually or use the mover.OK will do, thanks @JorgeB. Is it OK to just move them with Krusader as a cut and paste?
October 28, 2025Oct 28 Community Expert Should be, but don't forget to disable Docker and VM services first.
October 28, 2025Oct 28 Community Expert 4 hours ago, nametaken_thisonetoo said:OK will do, thanks @JorgeB. Is it OK to just move them with Krusader as a cut and paste?This wont work, you cannot use Krusader to move docker container files because you will need to stop the entire docker service to move them.Instead you will need to use the built-in file manager by using the buttons at the bottom of the screen when browsing your shares/disks.Alternatively you can use mc from a terminal/console screen/window. Just be aware if you use this you need to leave the window open for it to remain active otherwise closing it will stop the operation. (this only applies to using the console/terminal window from the unraid webgui) shown here -> Edit: Also closing an SSH session will terminate the active mc operation. Edited October 28, 2025Oct 28 by MowMdown
October 28, 2025Oct 28 Community Expert 44 minutes ago, MowMdown said:This wont work, you cannot use Krusader to move docker container files because you will need to stop the entire docker service to move them.Doh! Forgot krusader is a container.
October 28, 2025Oct 28 Author 4 hours ago, JorgeB said:Doh! Forgot krusader is a container.I realised this myself and was wondering how I was going to do it. Didn't know about the buttons at the bottom of the share you mentioned so thanks for the heads up @JorgeB . There are still files being written to the wrong cache disk, so also just wondering if I do this move to the other cache will that mean future writes will be made to the new location?
October 28, 2025Oct 28 Community Expert 2 hours ago, nametaken_thisonetoo said:There are still files being written to the wrong cache disk, so also just wondering if I do this move to the other cache will that mean future writes will be made to the new location?What files are being wrote to the wrong cache pool? You may need to review each one of your docker container templates to make sure all the paths you're using are pointed to the correct locations.For example if you have a direct disk/pool mount it will bypass FUSE and write directly to the location specified.
October 29, 2025Oct 29 Author 5 hours ago, MowMdown said:What files are being wrote to the wrong cache pool? You may need to review each one of your docker container templates to make sure all the paths you're using are pointed to the correct locations.For example if you have a direct disk/pool mount it will bypass FUSE and write directly to the location specified.This is a new install of UnRaid and afaik Unraid automatically creates a system share and in my case put it on a cache drive not planned for this purpose. The files ending up there are system folder and then the docker subfolder with. New writes are happening there all the time despite now setting the system share to my preferred cache drive. Edited October 29, 2025Oct 29 by nametaken_thisonetoo
October 29, 2025Oct 29 Community Expert Anything using /mnt/user should go to the set pool, unless they are using /mnt/cache_data
October 29, 2025Oct 29 Community Expert 19 hours ago, nametaken_thisonetoo said:New writes are happening there all the time despite now setting the system share to my preferred cache drive.If these are existing files, then they are not automatically moved to the location specified. If these are new files then something is configured incorrectly to make this happen.
November 3, 2025Nov 3 Author Just coming back to this after some non-unraid life distractions @JorgeB @itimpi @MowMdown All of my Docker container config pages have a path /mnt/userDocker directory in Docker settings is /mnt/user/system/dockerDefault appdata storage location in Docker settings is /mnt/user/appdataThe System share has a primary storage drive of Cache_system (which is the drive I want system files to be stored), and no secondary storage setThe appdata share also has a primary storage drive of Cache_system and no secondary storage setAll of these setting remain unchanged from my initial config of this new server a few weeks agoThe test file @JorgeB had me create in the terminal has written to the correct Cache_system drive.But somehow despite all of this a "docker" folder in the system share continues to write new files to my other cache drive (Cache_data). See screenshots below sorted by last modifiedIf I move the docker folder from the cache_data drive to cache_system where it should be it appears that future writes will just continue to land on cache_data despite all my correct settings. I'm also concerned that moving this folder might screw with my config, so wanted to check in again before I so anything. Have also attached diagnostics. Any thoughts on what I should do from here?Thanks! themagiceye-diagnostics-20251103-1917.zip
November 3, 2025Nov 3 Community Expert Did you actually move those shares to the new pool? If the appdata and system shares are on the old pool, any changes to those files will keep going to the old pool.
November 3, 2025Nov 3 Community Expert Solution The solution is to move the data over, new files should be wrote to the new storage location. Existing files being modified wont be moved regardless of what storage pool you selected in the share settings.Stop/Disable docker service in the unraid settings. Set cache_data as the secondary storage for your system share and then set the mover action so that the arrow points to cache_system from cache_data so that it looks like cache_data -> cache_system and run mover. Edited November 3, 2025Nov 3 by MowMdown
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.