I have an old server, has been stable, used as a file share and has a Plex docker.

 

Recently (weeks) updated to Unraid 7.01.

 

While on vacation I got warnings of cache disk low on space.  When I got home the plex docker was not running and the cache disk was full.

 

I rebooted just to see if that helped, but it did not.

 

My cache disk is a 256gb ssd, and has been adequate for years with the same docker and utilization.  Plex is setup to record off of antenna, and it did not seem that anyone at home was using plex on a device that would need transcoding.

 

With the cache drive full I assume I’ve lost those files, but how do I recover as gracefully as possible?  I did order a larger cache drive and will set a minimum free space on the new one.  

The config was stable for years, but maybe the 7.01 update changed how things were working.

 

Thanks for any advice!

 

Ross

You are likely to get more informed feedback if you attach your system's diagnostics zip file to your next post in this thread.  
It is always a good idea to do this to allow us to see the current state of your system and so we can see logs.

3 minutes ago, Ross said:

I dragged the zip folder over, but it uploaded as individual files.  Maybe drag was the wrong move.  Using iMac.

 

Ross

We definitely want just the single zip file.  Downloading all the content as individual files is not at all convenient.

Moved to a PC.  So attached is the zip file!

 

Thanks,

 

Ross

wserv-diagnostics-20250423-1452.zip

According to the diagnostics the share anonymised as 

P--------a                        shareUseCache="yes"     # Share exists on cache, disk1, disk2

does not seem to have ‘cache’ set as its primary storage which would explain why files are not being moved.

 

i suggest you go into the settings for that share, check they are correct (and if necessary make a dummy change to get Apply enabled) and then hit Apply to get the .cfg file for that share regenerated.

 

Hopefully that will fix the mover issue, but if not post new diagnostics so we can check the settings now look correct.

That fixed the problem.

 

Thanks!