So my cache drive filled up overnight. Frustrating, but it happens I guess. I was expecting to need to make free space and be back to business as usual, but no, it's not that simple - far from it in fact.

 

My cache drive was empty, unRAID had decided to move the contents of cache, including the apps directory, on to the array. As a result all of my plugins which stored databases and configuration on /mnt/cache are broken, even after restoring the folders back to cache they've lost data. Starting up the likes of sab and sickbeard I'm greeted with the first start wizard and no data.

 

 

My cache drive was empty, unRAID had decided to move the contents of cache, including the apps directory, on to the array. As a result all of my plugins which stored databases and configuration on /mnt/cache are broken, even after restoring the folders back to cache they've lost data. Starting up the likes of sab and sickbeard I'm greeted with the first start wizard and no data.

Normally this is due to a user configuration error? It sounds as if you did not have the 'apps' share set to be cache-only as doing so should have stopped it being moved to the data disks.  You should check the settings on the share.  If the share IS set to cache-only then you need to look into why the move happened as it should not have done so.

 

Another thing people often do with the cache disk is to forget to set a reasonably large value for the Min Free Space setting.    You want that to avoid errors with running out of space as the cache drive starts to get full.

My cache drive was empty, unRAID had decided to move the contents of cache, including the apps directory, on to the array. As a result all of my plugins which stored databases and configuration on /mnt/cache are broken, even after restoring the folders back to cache they've lost data. Starting up the likes of sab and sickbeard I'm greeted with the first start wizard and no data.

It sounds as if you did not have the 'apps' share set to be cache-only.  Doing so should have stopped it being moved to the data disks.  You should check the settings on the share.  If the share IS set to cache-only then you need to look into why the move happened as it should not have done so.

 

Another thing people often do with the cache disk is to forget to set a reasonably large value for the Min Free Space setting.    You want that to avoid errors with running out of space as the cache drive starts to get full.

Since this is a v5 subforum, I assume you are on v5.

 

In addition to setting the apps share to Use cache: Only you must examine all of your other disks to see if there is a top-level apps folder on them. The way mover works on v5, it will continue to move the apps share if any of it still exists on the array. If you find it on any disk, either move it back or delete it.