-
Unable to access WebGUI, SSH is slow to respond, diagnostics taking 20+ minutes, containers working fine
Oh. I see. I think that's a syslog file from January. Not sure how I got that there. Should be gone now though, thanks to the heads up!
-
Unable to access WebGUI, SSH is slow to respond, diagnostics taking 20+ minutes, containers working fine
Okie-dokie - I ended up having to "suffocate" the server (holding power button) since powerdown only yielded root: /usr/local/sbin/powerdown has been deprecated and reboot just hung. It does appear to have come up swimmingly, though. Attached is a fresh post-reboot diagnostics zip. Thanks again. merkava-diagnostics-20250429-0912.zip
-
Unable to access WebGUI, SSH is slow to respond, diagnostics taking 20+ minutes, containers working fine
Thanks trurl, here's what I get: Filesystem Size Used Avail Use% Mounted on rootfs 16G 907M 15G 6% / I am sure the array is online in some fashion though as I can play some recorded VHS tapes I have over Jellyfin. Thanks!
-
Unable to access WebGUI, SSH is slow to respond, diagnostics taking 20+ minutes, containers working fine
Attached - thanks! Sorry that took me a bit! p.s. - Interlagos - nice! syslog.txt
-
Unable to access WebGUI, SSH is slow to respond, diagnostics taking 20+ minutes, containers working fine
Hey all, Unraid 6.12.15 ~12 hours ago I was using a Windows client to move some files on a share around. I went up a folder in Explorer and it never loaded. I realized this and attempted to use the Web GUI and found that was locked up, too (nginx 500 Internal Server Error). I attempted to SSH into the system but that was also very slow. The system itself is quiet (not sounding like it's at 100% CPU) so I let it be. This morning I find it in the same state. I can get in via SSH but it takes a few minutes. Once I'm in, some operations (like top, thankfully) is very quick. Others, like "diagnostics", not so quick (20+ minutes & counting). When I had ran top, I did find a "rm" process at 100% CPU (which I imagine to be 100% of one of the 8 cores). I tried to kill it with kill -9 <pid> but it didn't kill. I did access some docker containers and for the most part they're working just fine. Any idea where to go from here? I did try a single tap of the power button, but it's still running. Trying to avoid an unclean shutdown if I can. This is my hardware: https://pcpartpicker.com/user/gkubed/saved/7Hd7vK Please let me know if there's any additional information I can provide! Thanks!
guyon
Members
-
Joined
-
Last visited