Hi.

 

I recently swapped my laptop mSATA, so I took the old one, put it into a SATA adapter and added is as a cache drive. In the same operation, I moved the Docker file to the cache, and have the working directory ".appdata" there as well.

 

Now I have hust realised, that the cache drive is displaying as "Unmountable" in the UI. Looking in the logs, it says "shfs/user: cache disk full".

 

I don't know if the two are related, but I suspect they are.

 

If I look at the Docker, it still works. If I browse from Windows to \\tower\cache I can see approx. 40GB data (of the 80), but it reports 80GB occupied - can't see the rest of the data.

 

I don't understand that it reports unmountable, but can still be browsed to.

I also don't understand how the docker can continue working if the cache is unmountable

 

I'm probably missing the plot and how the cache is working, so my question is:

 

• How did this happen?
  
• What do I do now?
  
• How do I prevent it from happening again?
  

Logs and selected screendumps attached (had to separate syslog1 out due to size constraints).

tower-diagnostics-20160411-1801-after-stop-start.zip

syslog1.txt

syslog.1.zip

Web-UI reporting unmountable.

Probably already contains a filesystem unRAID recognizes but doesn't support for cache. May also have multiple partitions. Try preclearing it then adding it again and unRAID should format it.

Hi trurl.

 

Thanks for responding.

 

It has already been formatted by unRAID from the start, and was working fine - this is a condition that has happened approx. one month after it got mounted to start with.

Hi.

 

In the posts here, it appears as if there is an issue with native mSATA. Could it be related (even though my mSATA is 'behind' a SATA adapter), or is my problem a more simple issue?

 

Any thoughts, anyone?

 

/NiA