Skip to content
View in the app

A better way to browse. Learn more.

Unraid

A full-screen app on your home screen with push notifications, badges and more.

To install this app on iOS and iPadOS
  1. Tap the Share icon in Safari
  2. Scroll the menu and tap Add to Home Screen.
  3. Tap Add in the top-right corner.
To install this app on Android
  1. Tap the 3-dot menu (⋮) in the top-right corner of the browser.
  2. Tap Add to Home screen or Install app.
  3. Confirm by tapping Install.

Rootfs is getting full (from fix common problems)

Featured Replies

Fix common problems flagged this issue recently. I haven't noticed any issues on my server, everything seems to be running smoothly, but thought I'd see if this is something to be concerned about / what I could do to mitigate it. I don't know enough to know whether this will eventually crash my server, but I suspect it might?

I've attached my server diagnostics to this post, and this is the output when I run df -h:

Filesystem      Size  Used Avail Use% Mounted on
rootfs           16G   16G  162M  99% /
tmpfs           128M  3.2M  125M   3% /run
/dev/sda1        15G  1.7G   13G  12% /boot
overlay          16G   16G  162M  99% /usr
overlay          16G   16G  162M  99% /lib
tmpfs           128M   14M  115M  11% /var/log
devtmpfs        8.0M     0  8.0M   0% /dev
tmpfs            16G     0   16G   0% /dev/shm
efivarfs        192K  144K   44K  77% /sys/firmware/efi/efivars
tmpfs           1.0M     0  1.0M   0% /mnt/disks
tmpfs           1.0M     0  1.0M   0% /mnt/remotes
tmpfs           1.0M     0  1.0M   0% /mnt/addons
tmpfs           1.0M     0  1.0M   0% /mnt/rootshare
/dev/md1p1       19T   16T  2.4T  87% /mnt/disk1
/dev/md2p1       15T   11T  4.6T  69% /mnt/disk2
/dev/md3p1       15T   11T  4.6T  69% /mnt/disk3
/dev/md4p1       19T   11T  7.3T  60% /mnt/disk4
/dev/nvme0n1p1  1.9T   89G  1.8T   5% /mnt/cache
shfs             66T   47T   19T  72% /mnt/user0
shfs             66T   47T   19T  72% /mnt/user
/dev/loop2       50G   30G   20G  60% /var/lib/docker
/dev/loop3      1.0G  6.4M  905M   1% /etc/libvirt
tmpfs           3.2G     0  3.2G   0% /run/user/0

tower-diagnostics-20250907-2313.zip

  • Community Expert

This typically means you have something writing to RAM, most often a container with a bad mapping; check those.

  • Author
21 hours ago, JorgeB said:

This typically means you have something writing to RAM, most often a container with a bad mapping; check those.

Gotcha, I'll take a look at my mappings. I'm not too familiar with how to identify if something is writing to ram though. What kind of patterns or mappings should I be looking for?

  • Community Expert

Anything not writing to a valid /mnt/user/<share name> path will write to RAM, also check for case, if you have a share named Media, mapping to /mnt/user/Media is OK, mapping to /mnt/user/media will go to RAM.

  • Author

Ah man, my server's web gui is now not working (500 Internal Server Error). I can still access the web ui for my docker containers so looks like things are still working, but I need to figure out how to restart the server without the web gui. And I can then look around my docker mappings to see what the root cause is.

  • Author

Was able to physically attach a keyboard to my server and use powerdown and restart. Now running df -h has the rootfs at 6% full, but I know it'll fill back up unless I find out what's causing the issue.

Going through my docker mappings and these are the only ones that aren't a subdirectory of /mnt/user:

  1. Plex has a /dev/dri mapping for the iGPU

  2. Telegraf has a few suspect mappings( host/path -> containter/path ):

    1. /var/run/utmp -> /var/run/utmp

    2. /var/run/docker.sock -> /var/run/docker.sock

    3. / -> /rootfs

    4. /sys -> /rootfs/sys

    5. /etc -> /rootfs/etc

    6. /proc -> /rootfs/proc

    7. /run/udev -> /run/udev

    8. /rootfs/proc set as container variable HOST_PROC

    9. /rootfs/sys set as container variable HOST_SYS

    10. /rootfs/etc set as container variable HOST_ETC

    11. /rootfs set as container variable HOST_MOUNT_PREFIX

  3. UptimeKuma also has the /var/run/docker.sock mapping

  4. code-server has a couple:

    1. /config/workspace set as container variable DEFAULT_WORKSPACE

    2. /mnt/ -> /array

  5. TheLounge has /mnt/cache/appdata/thelounge -> /thelounge

Do any of these look suspect to you?

  • Community Expert
6 hours ago, anubhavrb said:

but I need to figure out how to restart the server without the web gui.

If you have CLI/SSH access, type reboot

  • Author
15 hours ago, JorgeB said:

If you have CLI/SSH access, type reboot

Yep, I was able to get back into my server. I posted my docker mappings above, do any of those look like they may be writing to rootfs instead of to storage?

  • Community Expert

There are multiple mappings to /rootfs

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.

Guest
Reply to this topic...

Account

Navigation

Search

Search

Configure browser push notifications

Chrome (Android)
  1. Tap the lock icon next to the address bar.
  2. Tap Permissions → Notifications.
  3. Adjust your preference.
Chrome (Desktop)
  1. Click the padlock icon in the address bar.
  2. Select Site settings.
  3. Find Notifications and adjust your preference.