ZenBuddha Posted May 15, 2023 Share Posted May 15, 2023 I tried running the dianostics and other recommendations on here but I'm having trouble understanding what to do with the info. Attaching diagnostics. Thanks in advance tower-diagnostics-20230514-1936.zip Quote Link to comment
JorgeB Posted May 15, 2023 Share Posted May 15, 2023 This means you have something writing to RAM, anything outside /mnt/user and /boot will be going to RAM, check you container mappings. Quote Link to comment
Solution Kilrah Posted May 15, 2023 Solution Share Posted May 15, 2023 You can install the nerd tools plugin, install ncdu there, then run ncdu --exclude /mnt --exclude /var/lib/docker --exclude-kernfs / Should show you what's big in the rootfs. 1 Quote Link to comment
ZenBuddha Posted May 15, 2023 Author Share Posted May 15, 2023 Thank you for that command. So what showed up was 10.6GiB in /tmp and then inside there was /transcode Seems like for some reason Plex left two 5GiB files in there. Restarted Plex and they went away. Thanks again. Quote Link to comment
itimpi Posted May 15, 2023 Share Posted May 15, 2023 13 minutes ago, ZenBuddha said: Thank you for that command. So what showed up was 10.6GiB in /tmp and then inside there was /transcode Seems like for some reason Plex left two 5GiB files in there. Restarted Plex and they went away. Thanks again. You might want to consider mapping /transcode to somewhere on a SSD pool if you want to avoid this issue in the future? Slightly lower performance but safer. Quote Link to comment
Recommended Posts
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.