Squid

It won't show them (never has). What active streams shows is stuff that is being streamed directly to a client (ie: via SMB). So far as media is concerned, this means anything going directly to a Kodi system on your network. Locally opened files (which is what Plex does) do not appear. For that, you want the open files plugin, but it will show everything.

https://forums.unraid.net/topic/57181-docker-faq/page/2/#comment-566087

A new set of diagnostics would tell us why.

I assumed you had it, but you would need to also install Dynamix System Temp and set it up.

You should definitely be using UD to mount an SMB share from the VM to access that drive. Since everything is all stored locally, there's no performance hit.

Try rebooting and start it in safe mode from the boot menu to see if that makes any difference.

Right Also right But, under either of your scenarios, the files that were already on the cache drive are going to be lost. Keep an occasional backup of the appdata for your docker applications (a plugin exists to help with this)

Install NetData from Apps. Open its webUI page and leave it open on the "sensors" section. When the system crashes, you should still be able to view what was happening at the time.

Since it's stuck for some reason, you can't really do anything other than hard reboot. From the terminal, this *might* help powerdown -r (But, it does appear that the drives have all been successfully unmounted so you *should* be good.

Post your diagnostics

If you're seeing an update available when looking at the Dashboard, but not one if you look at the Docker Tab, then that's a bug in unRaid that's fixed on the next release of unRaid.

I had to restart the container a couple of times to get past that. Unfortunately it appears that F@H (on all platforms) has a bug (or their servers are simply overwhelmed) where occasionally it gets into a loop where it doesn't pick up anything at all. Keep restarting the app, or also install BOINC which never seems to suffer the same ill effects

F@H (and probably BOINC now) are prioritizing covid WU's. (With F@H, you select that you're fighting for any disease) But, do to the massive surge in people folding and doing their part, WUs on both platforms for covid aren't always available. BOINC (which has internationally lower adoptance than F@H) seems to never run out of WUs in the interim, whereas F@H seems to be always running short of everything. Net result is that I'm running both as they are complimentary researches and not mutually exclusive.

Completely up to you and your decision wouldn't bother me in the least. But I would suggest that you read the previous post and the linked thread and within it the post from limetech. But, you would not have seen any notification after last wednesday.

Seti@home is closing up shop today permanently

A little birdie has told me I'm going to have a fair amount of free time in the coming weeks to be able to look at some things long standing on my todo list.

Or its a symlink or something within the VM. Not sure how that gets handled over SMB.

Then how do you know that the file(s) are winding up on the unassigned device?

Refuses to load or continually reloads? Common problem across all platforms. Clearing your history fixes it

You *can* however in the plugin's advanced settings set it to not stop the containers

No. You have to do it manually if you want that

Effectively the way that you do that is to set the allocation method for the shares to be "Most Free". There's no real way to do it otherwise, but with "Most Free", the system will wind up balancing itself out with the episode files all stored on different disks. Last access time is disabled by default in unRaid (and many other OS's), as keeping track of that massively slows down file I/O. But, you can look at the Mover Tuning Plugin (in Apps) which will let you selectively move based upon the "age" of the file (creation date) No. The point of the cache drive is to speed up writes, not reads. It was really necessary way back when drive transfer rates on spinners were pathetic compared to now. Nowadays, hard drives can easily keep up with multiple simultaneous reads on the same file (streaming the same file to multiple devices) Many people (including myself) don't even bother with using the cache drive as a "cache drive". Rather they set all the shares to not use it, and relegate the cache drive to being an "application" drive -> data for docker applications, VM's etc

Trouble with that is that to be able to calculate the speed difference, you would have to do the exact same work unit from start to finish twice (which can't happen), and measure the time it takes. Because of their nature, disabling the mitigations will always improve the speed.

Fixed on today's update

unRaid always does a parity check in cases of unclean shutdowns. You don't have to wait though for it to finish. The system is completely usable (but may run slower on disk accesses) during this process. As to why its "blank", that is kinda hard to say. What do you mean exactly by "not showing anything". But for future reference, if this happens again, grab the diagnostics via the terminal by entering in diagnostics and then posting the resulting file stored on the flash drive (logs folder)