Cache drives (in pools) and boot drives intermittently disappearing then reappearing

[chrisp7]

Hi, something string is happening with my UNRAID server - the pool drives (cache's) and the boot drive keep on disappearing then reappearing in the MAIN UI, on top of that the whle UNRAID homepage randomly times out.

I first discovered the issue when my NVME cache pool (which contains all my downloads) was getting full, but sonarr wasnt able to move the files to the media share as it was also "full" (my UNRAID array has plenty of space however).

I did setup my caches a few months ago and wondering if it is related?

I attached my diagnostics file - its a really odd issue.

dekker-diagnostics-20240719-2018.zip

[JorgeB]

I do see multiple Samba crashes, but no issues with the cache devices, when you say

12 hours ago, chrisp7 said:

keep on disappearing then reappearing in the MAIN UI

do you mean the devices drop or it's just a visual glitch?

[chrisp7]

I am not sure.
My array is saying its full (it isnt), but maybe a drive is?
And with the UNRAID homepage at times timing out, it might mean there is an issue with something related to these drives appearing/disappearing.

[itimpi]

Could you pleas post diagnostics taken with the array started.   It looks like it was not started in the previous  ones posted?

[chrisp7]

Thank you here is is.

I must have done something when changing my cache to be x2 caches. Looking in Krusader I can see my cache folder is "full" while the 2 I created - cache_nvme and cache_ssd have space. I am not sure what "cache" is... 

dekker-diagnostics-20240721-2101.zip

[itimpi]

Since you no longer have a pool called ‘cache’ that is almost certainly a location in RAM the is being used because you have something configured to use /mnt/cache.   It contents will not be persistent.

[chrisp7]

I think it might be "Folder Caching"?

I think that is causing the issues - just a guess?

[chrisp7]

4 minutes ago, itimpi said:

Since you no longer have a pool called ‘cache’ that is almost certainly a location in RAM the is being used because you have something configured to use /mnt/cache.   It contents will not be persistent.

That might explain issues with the system having intermittent issues (full RAM).

should you always have a cache called just cache?

[itimpi]

1 minute ago, chrisp7 said:

should you always have a cache called just cache?

Pools can be named as you like.   It is just traditional for the first pool to default to being named ‘cache’

[chrisp7]

Any idea why this is happening? Or what I can do to stop it?

 

Edited July 21 by chrisp7