Constant issues with server after rebuilding two drives

[thejellydude]

Hi all,

 

So a little while ago the CMOS batter on my motherboard died, leading to my SATA controller dying. I believe that this lead to some corruption of my system, but I don't know how to fix it. I'm unable to get the mover to clear my cache, and many of my applications are giving me errors regarding a lack of disk space. Do I need to go scorched earth and redo everything? Some help would be greatly appreciated

nasbox-diagnostics-20240604-1614.zip

[itimpi]

It looks like your ‘appdata’ share is too large to fit onto the cache drive of the size you have, and you also have it set so it cannot move files to the array to free up space on the cache.

 

in addition you gave not set a minimum free space value for the cache which you should have set to avoid that drive getting too full even when the share is set to allow files to be moved to the array.

[thejellydude]

Oh man, I hadn't considered that appdata had ballooned to be the share that was too big. I've adjusted that to move the array and started the mover. I'll figure out how to set a minimum amount of free space for the cache as well. Is there a good app to clean up the appdata folder? I feel like it's become cluttered with old docker images that I'm not using.

[itimpi]

9 hours ago, thejellydude said:

Is there a good app to clean up the appdata folder? I feel like it's become cluttered with old docker images that I'm not using.

The actual docker images are held in the docker.img file (which is located in the 'system' share.  It is not clear from your diagnostics whether that is currently on the array or on the 'cache' pool (which is best for performance reasons).   

 

The 'appdata' share will hold the working set files for docker containers.   If you have followed the normal behaviour of giving each container you install a sub-folder under the appdata share it should be easy enough to use Dynamix File Manager to delete any for containers you no longer run.