I've noticed my docker containers just randomly stop running.. I was just looking to see why a new show hadnt posted an realized several docker containers just disappeared.  Otherwise, my server seems to be running fine. 

 

Thanks for anyone's help.

unraid-diagnostics-20250407-2105.zip

Unlikely to be the cause of your issue, but...

Your appdata, domains, and system shares have files on the array (disk2).

 

Ideally, these shares would have all files on pool and none on the array, so Docker/VM performance isn't impacted by slower array reads and especially writes, and so array disks can spin down since these files are always open.

 

Nothing can move open files, so you have to Disable Docker and VM Manager in Settings before these can be moved.

 

 

Apr  6 21:28:07 unraid root: Fix Common Problems: Error: Invalid folder cache contained within /mnt

This is likely to be the cause of problems, looks like you probably renamed one of your pools, but still have a path specifying /mnt/cache somewhere. Probably a container host volume.

 

Since /mnt/cache isn't mounted storage now, it is a path in RAM, which obviously will not persist after reboot.

Also these

Apr  6 21:28:14 unraid root: Fix Common Problems: Warning: Share domains references non existent pool cache_nvme
Apr  6 21:28:14 unraid root: Fix Common Problems: Warning: Share Downloads references non existent pool cache_nvme

Maybe the reason domains ended up with some files on the array. And the reason Downloads can't "cache" anything and has to put new files directly on the array.

You need to update this plugin

Apr  6 21:28:14 unraid root: Fix Common Problems: Error: Unraid Patch Not Accepted

 

upgradepkg --install-new' returned 127

 

I'm getting this when i try to update that unraid patch plug in. 

3 hours ago, trurl said:

Apr  6 21:28:07 unraid root: Fix Common Problems: Error: Invalid folder cache contained within /mnt

This is likely to be the cause of problems, looks like you probably renamed one of your pools, but still have a path specifying /mnt/cache somewhere. Probably a container host volume.

 

Since /mnt/cache isn't mounted storage now, it is a path in RAM, which obviously will not persist after reboot.

I've removed that folder, and all of the other shares point to non-existant pools. Thank's i'll give it a few days and see if it fix's the docker problems.

Not entirely clear which of my recommendations you followed, or what you did.

 

Post new diagnostics.

13 hours ago, trurl said:

Not entirely clear which of my recommendations you followed, or what you did.

 

Post new diagnostics.

All recommendations followed except updating unraid patch plugin as it keeps giving me error " upgradepkg --install-new' returned 127" 

So far everything seems well. 

unraid-diagnostics-20250408-2051.zip

I'm going to say my server is fixed.. It hasnt had a docker problems since i fixed the aformentioned things.