JonathanM

Can you access the Unraid GUI from another device temporarily and disconnect the network from your main PC?

Something on the network is reading the files on your server. Does the activity stop if you temporarily disconnect your internet service?

According to that screenshot set, you have client(s) accessing the shares and files from across the network.

Stop them and get the open files list.

No.

Your docker containers and VM manager is running.

What shows up on the Tools, Open Files page?

It's a plugin. Click on the checkbox then the remove button on the Dynamix Cache Directories entry on the Installed Plugin page that you posted a screenshot.

Depends on the number of file entries. Remove it and see if the activity stops.

Cache dirs constantly reads drives. If you don't have enough RAM to keep the entries cached, it keeps the drives spun and reading.

I guess the bigger question is, why is yours updating automatically? Unless you do something to change it, updates only happen when you push the update button.

That's only sort of accurate. Each disk in the parity protected array has its own file system, and any given file can only reside on a single disk. However, the user share directory tree will show you a single view that has all the files in identically named folders together, so it looks like just one volume. Because files can't span disks, each individual file can't be larger than the free space on any individual disk.

Unraid unpacks fresh into RAM on every boot, so if you want something custom available, you must recreate it on boot. You can use either user scripts or the go file, depending on the timing you need.

Or, post it here, report it with a comment seeking approval, then immediately hide it. That will get attention but not allow it to be seen by the general public.

1. Yes, the structure is fine. 2. You can't. Krusader is a docker container, which loosely means that it is running its own operating system, not in unraid. It only sees whatever part of unraid you map to it, just like any other container has to have mappings if you want it to interact with the files on unraid. If you look at the container settings for Krusader, you will see that unraid_flashdrive, unraid_shares, and unraid_unassigned_disks are mapped to the appropriate spots on the host (unraid)

https://github.com/linuxserver/docker-plex#application-setup

It's not the memory that's the issue, it's the CPU and motherboard.

Sure, but it will require a custom script or scripts, it's not a built in feature of Unraid. I have no idea of your personal level of expertise, so all I can confidently say is that if you use the virsh and docker commands properly in a script, it's relatively easy.

Not bad, but until you understand why it's showing you that, you will have issues working with it. It's perfectly normal if you are using the Krusader container. There is nothing to be fixed, it's only your understanding that is flawed. Have you watched spaceinvaderone's videos on youtube about unraid?

Be sure you only download movies that are in the public domain, here's one list that should be safe. https://archive.org/details/feature_films If it's available for purchase, it's probably not legal to download through radarr. This is not intended to start a discussion on how people choose to archive their legally aquired blu-ray and dvd disks, I'm simply answering the question asked. Here is an article that briefly discusses the current laws. https://lifehacker.com/is-it-legal-to-rip-a-dvd-that-i-own-5978326

I very seriously doubt that the real path is as shown, because it looks to me like you are viewing the contents of a docker container, likely krusader. What you see there is NOT the actual server paths, only what is mapped in the container configuration. I suspect what you are seeing is perfectly fine, but if you don't get your head around WHY you are seeing it that way, you are going to have a bad time if you try to interact with anything but the unraid_ folders in that view. It likely won't mess up your server, but you will be very confused about what you are seeing. Think of that view as a separate computer, with the unraid flashdrive, shares, and unassigned devices connected to their respective folders. You are not seeing what is actually on the server root, you are seeing the "local computer" that is the docker container. If you want to view and interact with the actual server, you need to use the console, either locally or logging in with ssh or the web gui terminal. Type mc at the prompt for a simple file manager. I'd recommend browsing around but not copying or especially moving files until you get more knowledge of what you are seeing. It's much safer to interact with the shares over the network from your client machines, after all, Unraid is primarily a NAS, Network Attached Storage.

That's neither correct nor incorrect. Just user preference. If you set unraid to "turbo write" it will keep all the drives spun up during writes for extra speed for some configurations. I honestly have not seen any difference in drive longevity between spinning down drives after a reasonable period or keeping them spun up 24/7 as long as you have steady power and keep temperatures consistent. The things that kills drives besides physical trauma seems to be inconsistent temps and power. If you spin down your drives and they cool off to 10C overnight, and spin up every morning in a poorly cooled enclosure that keeps a spun up drive near 40C, you are going to shorten the drive's life significantly vs. leaving them spun up at 40C consistently. If they spin down and drop to 25C and run normally at 30C, then the thermal shock of spinning down and back up isn't significant. The designation of the drive be it NAS, surveillance, desktop, workstation, whatever, doesn't seem to really be a factor in real world longevity.

That's probably not going to be ideal. When you are running VM's, all the virtualized resources need to be managed by the host. By limiting the host so severely, you are doing the equivalent of adding loads of RAM to a slow computer. Make sure the "computer" (VM Host) has enough resources to be fast for each guest.