March 26, 20251 yr Seems like the only way to find out what's going on is to post on the forums based on the help article here tower-diagnostics-20250326-0901.zip
March 26, 20251 yr Community Expert Solution rootfs is the RAM reserved for the OS files. Filling that can cause lots of problems since the OS has no space left to work in. Also, since it is in RAM, whatever you put there will be gone when you reboot. If a container or something else is writing to a path that isn't actual mounted storage, that path is in rootfs. Most likely you have some container host volume wrong. Mounted storage paths are: the user shares (/mnt/user/sharename) the array data disks (/mnt/disk#/sharename) the pools (/mnt/poolname/sharename) mounted unassigned devices (/mnt/disks/mountname) mounted remote shares (/mnt/remotes/mountname). Or the boot flash drive (/boot). (It is not recommended to write to the boot flash drive.)
March 26, 20251 yr Community Expert Probably you renamed a pool without fixing the name in one or more of your containers. /dev/sdk1 954G 54G 900G 6% /mnt/cache_pool /dev/nvme0n1p1 932G 100G 830G 11% /mnt/nvme_cache
March 26, 20251 yr Community Expert Unrelated, your appdata share has files on the array. It is configured to be moved to nvme_cache, but nothing can move open files. Go to Settings - Docker and disable the docker service, then run mover.
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.