I'm trying to increase my knowledge of "where contents end up" on UNRAID.

where the dockers lie, where my shares are, relative to the rest of the filesystem.

Filebrowser, Dynamix File Manager are two discussed although the latter is apparently integrated into the filesystem.

I have tried the integrated filesystem but it seems to direct me to parts of the the filesystem, but I can't see the overall perspective of the filesystem.

Any other ideas ?

I've used Webmin in the past. i don't see it in the community Apps.

i'm also wondering if webmin isn't appropriate as im the only person ever to use it in a title of a forum post.

Edited February 16Feb 16 by digitaldoctor

I am using mc on the command line.

Forinstance,

I wanted to know "where" my .mp3 files are.

First time: nothing (as I had to select the locations I was searching)

then a search of .mp3 found nothing.

then I searched for *.mp3 brought the above.

The terminal is better, and I'll learn terminal over time, but for now I just need to understand the "nix filesystem landscape" in the mean time.

Edited February 16Feb 16 by digitaldoctor

6 minutes ago, googleg said:

I am using mc on the command line.

neat !

i'll probably be able to use that for something.

i foget what dos commander I used before windows

It doesn't have a search function it seems ?

I was also hoping to troubleshoot unraid at times.

I had a slowdown once (rebooted and all was fine) ... where things were still working, but things took about 20-50 times longer. I wanted to see if the CPU was being overused, or whatever else it could be.

Edited February 16Feb 16 by digitaldoctor

Maybe file manager isn't the best word.

Maybe I want a web-based system administration tool for a linux server ?

I suppose I could get the CPU utilization information here but I think I remember it was not loading or I felt it might be accurate.

I probably need terminal commands to help next time.

Terminal command: top (I clicked [ctrl+c] to stop) (google says you should use: q)

shows CPU utilization. That'll be helpful.

Edited February 16Feb 16 by digitaldoctor

Be careful.

Very important! You should never mix disks or pools with user shares when moving or copying files.

Linux doesn't know that user shares are just another view of disks and pools, and will allow you to specify the same folder(s)/file(s) as both source and destination. That will result in it trying to write what it is trying to read. It creates a new file at the destination, then there is nothing but an empty file at the source.

Another possible surprise:

mv will move files, but it will also rename files, and when moving, it will sometimes just "repath" a file. And linux doesn't know about user share settings.

So when you try to move something from one user share to another, it will sometimes "repath" it on the same device, possibly violating settings for the destination user share such as included disks.

The workaround, instead of move, is to copy from source user share to destination user share, then delete from source user share.

43 minutes ago, digitaldoctor said:

The terminal is better, and I'll learn terminal over time, but for now I just need to understand the "nix filesystem landscape" in the mean time.

Here is a terminal sequence that will help you locate files any place on the Linux file system:

The ls command is not really needed, but it shows you where you are in the file system. You can get the 'manual' for all Linux commands by googling linux command_name manual

Linux has all the tools that a good Linux Guru needs to completely diagnose the system. It is a matter of study. (These guys just love writing shell scripts combining simple commands using 'pipes' 'redirection' into tools that can do anything required. When I was working in the old Bell system, I was told that the white pages for all of the Bell Operating Companies were all generated by a Bash Shell script.)

Just to give you some basics– begin here:

The command pwd displays the 'present working directory' which is your user's home directory.

In the first screen shot, the cd / (change directory) changes that starting point to the root directory for the complete files system.

The ls (list) lists the contents of the pwd.

The find -name samba does all of the work. The -name switch tells 'find' to locate every occurrence of 'samba' in the entire file system down the directory for the pwd.

When the cursor returns the job is done. (Be a bit careful as it is possible for you to have thousand of lines of output depending you are looking for!)

PS--- I am not a Linux Guru!!! I know just enough to make me really dangerous...

Edited February 16Feb 16 by Frank1940

this helped me.

If you just want to visualize your file system, this is a good utility:

I guess the "UNRAID folder" is mnt/

Docker takes up the most space and:

it is spanned across all your disk and user shares (all approximately the same size)

mnt/user0/system/docker.img

mnt/user/system/docker.img

mnt/disk1/system/docker.img

and the var/lib/docker/ is impacted by UNRAID as it is the storage for "nix O/S level" DOCKER files (- has 2 main subfolders: overlay2, volumes)

var/lib/docker

Basically I found all the larger files with this terminal command

du -sh * | sort -rh | head -n 10

To find the largest folders in Linux, use

du -sh * | sort -rh | head -n 10

to list the top 10 largest subdirectories in human-readable format, sorted by size. This command is highly effective for identifying directories consuming the most disk space.

Summary of Flags

du: Disk usage command.

-h: Human-readable (e.g., 1K, 234M, 2G).

-s: Summary (only total for each argument).

sort -rh: Reverse, Human-numeric sort.

head: Top part of a file.

-n 10 (Top 10 entries) (use 5 for top 5)

Edited February 16Feb 16 by digitaldoctor

8 hours ago, digitaldoctor said:

I guess the "UNRAID folder" is mnt/

That is where everything is "mounted", the "mounted" storage. "mount" is when the OS loads a filesystem to allow access to the folders and files of the storage.

/mnt/disk1, /mnt/disk2, ... are the array data disks. parity, parity2 are not mounted since they have no filesystem.

/mnt/poolname1, /mnt/poolname2, ... are the pools.

/mnt/user is the user shares, /mnt/user0 is the user shares excluding anything not on the array. The user shares are just another view of the array data disks and pools, the combined top level folders of your assigned storage.

If you create a user share, Unraid creates a top level folder named for the share on array or pools as needed in conformance with settings for that share.

Conversely, if you create a top level folder on array or pools, it is automatically a user share named for the folder. Any user share you have not made settings for has default settings.

/mnt/disks are the mounted Unassigned Devices. /mnt/remotes are the remote storage mounted by Unassigned Devices.

Nothing else should be in /mnt. Any other file or folder you create in /mnt is a mistake, since the OS hasn't "mounted" it, it is not mounted storage. And so it is just another folder or file taking up space inside the OS. The OS is in RAM and if you fill up the OS space in RAM it can become unstable.

9 hours ago, digitaldoctor said:

Docker takes up the most space and:

it is spanned across all your disk and user shares (all approximately the same size)

mnt/user0/system/docker.img

mnt/user/system/docker.img

mnt/disk1/system/docker.img

Those are not approximately the same size, they are just different views of exactly the same files.

If you have things setup correctly, your docker.img should not be on anything except a pool, not on any array disk, so should not appear in /mnt/user0 or /mnt/disk1. Should be on a pool such as /mnt/cache, and so would appear also in /mnt/user but not in /mnt/user0.

Ideally, Docker/VM related shares - appdata, domains, system - should have all files on cache or other pools, with nothing on the array, so Docker/VM will perform better, and so array disks can spin down since these files are always open. Nothing can move or delete open files, so to work with those shares and put them where they should be, you have to disable Docker and VM Manager in Settings.

So, it seems you probably need some work on the configuration of those shares. If you want more specific advice about that...

Attach Diagnostics ZIP to your NEXT post in this thread.

I don't recommend sharing drives on the network, only user shares.

14 hours ago, trurl said:

never mix disks or pools with user shares when moving or copying files.

Built-in File Manager will not let you make this mistake.

14 hours ago, trurl said:

The workaround, instead of move, is to copy from source user share to destination user share, then delete from source user share.

Built-in File Manager also takes care of this.

Command line, Krusader docker, mc, sharing disks on the network along with user shares. All will let you make those mistakes.

8 minutes ago, trurl said:

Built-in File Manager

On 2/16/2026 at 3:02 PM, digitaldoctor said:

It doesn't have a search function it seems ?

Yes, you can perform searches with MC:

Quick search

The Quick search mode allows you to perform fast file search in file panel. Press C-s or Alt-s to start a filename search in the directory listing.

When the search is active, the user input will be added to the search string instead of the command line. If the Show mini-status option is enabled the search string is shown on the mini-status line. When typing, the selection bar will move to the next file starting with the typed letters. The Backspace or DEL keys can be used to correct typing mistakes. If C-s is pressed again, the next match is searched for.

If quick search is started with double pressing of C-s, the previous quick search pattern will be used for current search.

Besides the filename characters, you can also use wildcard characters '*' and '?'.

Edited February 18Feb 18 by googleg

QDirStat is a graphical application to show where your disk space has gone and to help you to clean it up.

The graphical user interface (GUI) of the application can be accessed through a modern web browser, requiring no installation or configuration on the client side, or via any VNC client.

The container is built against Alpine Linux to provide an efficient image in terms of size and resource usage.

For a complete documentation of this container, see https://github.com/jlesage/docker-qdirstat#readme

installed and trying.

Thank you @ConnerVT

This mnt/ is empty.

I don't appear to have access to unraid files via QDirStat

1 hour ago, digitaldoctor said:

This mnt/ is empty.

I don't appear to have access to unraid files via QDirStat

What are your volume mappings for that container?

For me, /mnt on the host is mapped to /storage in the container.