DevanteWeary

Oh sorry to double post but I wanted to say one more thing I noticed after the update: Krusader was showing up in my GPU Statistics widget on my dashboard as one of the apps that was using the GPU. This is even though I don't have /dev/dri assigned to binhex-krusader.

Well I never thought I'd be posting about binhex-krusader but since there was an update (that did who knows what), now I noticed two issues. 1) The icon for Krusader has turned into a bright red Krusader icon. This includes the one on the upper-left of the window and in the task bar at the bottom. 2) In my toolbar, I have a few shortcuts. One is to my torrents folder and I use the round, blue "qb" icon for this. Well with the update, that icon no longer exists. I just went ahead and pulled from binhex/arch-krusader:2.9.0-1-02 for now.

Clicking the icon shows only Start, Logs, and Remove. Name is unclickable. You can tell by the name not being blue (link color).

Hey guys, just a quick one. Anyone know of any way to customize the name and icon of servers installed via Pterodactyl? For example, this is Minecraft: ' Clicking the icon shows only Start, Logs, and Remove. Thank you!

Update Well guys, I don't wanna jinx it but I'm pretty sure I found the issue. You guys ready for this one? tldr; The stats in Prowlarr being called caused the RAM to max out. The culprit: the Prowlarr widget in the Homepage app/container. And only when actually bringing up the Homepage UI. So how did I get to that? Well over the months, I've turned on containers one by one and let it run. All the other times it locked up, I don't remember exactly what was running or what I was doing but I have had a feeling it was either Krusader or Homepage for months. If you see, I mentioned this on Feb. 25. Well a month or so ago I was talking with a friend about Homepage and started it to show my friend and the server locked up. So then I turned everything BUT Homepage on and it was fine. Then I started each app for which there was a Homepage widget until I started Prowlarr and it instantly locked up again. So then I load ONLY Prowlarr and it's fine. I click around and as soon as I click on the stats page, it spikes the RAM and locked up once again. My Prowlarr settings were set to never delete any history and so I had millions of queries from the past couple of years. Once I set it down to like two weeks, it still spikes the RAM if I go to stats but not as much (4GB vs the 20+ GB from before). I removed the Prowlarr widget from Homepage and turned everything else back on and so far it has been fine for a few weeks. One little widget caused me so much pain ha. I'm sure the widget was triggered whatever going to the stats tab in Prowlarr does. I think one thing that was making it harder was all the SIGTERM errors I've been getting. I don't think they're related at all actually. I think they're something else because I'm still getting them and it's still causing my webUI to lock up for a minute or two but the CPU and RAM both are at normal levels when it happens. Grok says it could be my disk IO wait times. I noticed usually when that happens, the busy percentage jumps from under 100% to like over 400%. I'm not sure how to tackle that issue though. I guess I'm just glad I found the original issue! THanks for everyone who tried to help!

I know this is pretty old now but looks like it should still work. However, I can't seem to get it to see my Intel QuickSync. I've tried three repositories, I've tried the /dev/dri thing, the /dev/dri/renderD128 thing, the adding --device=/ev/dri to extra parameters thing, the going into console and using apt install intel-media-va-driver-non-free, and adding UMASK 000 Whatever I do, encoder only shows Software. Am I missing anything? I just wanna use OBS directly on my Unraid server to stream movies on the server itself to Owncast which is also on the server without having to spinup a VM everytime.

So awesome, thank you!!!! I just assumed the file mimicked what was on the settings UI page. Thank you. Have it logging to a file now!

Yeah, at the end of the day, my log will be spammed with the ones from DMV. I wanna know if I can get rid of those. If not, I think I'm gonna disable the plugin unfortunately.

I've been using this plugin for... a long time. I always see these ethernet going up/down messages, but didn't really know what was causing it. Just thought it was normal. Well today I realized it was DVM causing these. Tested by enabling and disabling the plugin. Is there any way to prevent my logs from being spamming with these messages? For example: Apr 29 10:12:21 Devante-NAS kernel: eth0: renamed from veth26d5d6c Apr 29 10:12:21 Devante-NAS kernel: docker0: port 30(veth088fb8b) entered blocking state Apr 29 10:12:21 Devante-NAS kernel: docker0: port 30(veth088fb8b) entered forwarding state Apr 29 10:12:25 Devante-NAS vnstatd[5497]: Interface "veth26d5d6c" disabled. Apr 29 10:12:40 Devante-NAS vnstatd[5497]: Removing interface "veth26d5d6c" from database as it is disabled and has seen no data. Apr 29 10:12:40 Devante-NAS vnstatd[5497]: Interface "veth26d5d6c" no longer in database, stopping monitoring. Apr 29 10:12:40 Devante-NAS vnstatd[5497]: Monitoring (28902): veth088fb8b (10000 Mbit) veth3024cfb (10000 Mbit) veth1dba438 (10000 Mbit) vethcba637f (10000 Mbit) veth67f1a14 (10000 Mbit) veth3b620b6 (10000 Mbit) veth236fb38 (10000 Mbit) veth9273736 (10000 Mbit) veth81945c7 (10000 Mbit) vethe587043 (10000 Mbit) vethc2b008f (10000 Mbit) veth2501945 (10000 Mbit) vethc4056f1 (10000 Mbit) vethc8bd252 (10000 Mbit) vetha7e8b58 (10000 Mbit) vethda641d0 (10000 Mbit) veth4a827f2 (10000 Mbit) veth6a95f8b (10000 Mbit) veth152fa45 (10000 Mbit) vethc2e55a6 (10000 Mbit) vethe3790d6 (1000 Mbit) veth9161d61 (10000 Mbit) vethb6c9c1b (10000 Mbit) veth4ac628c (10000 Mbit) veth2b19c03 (10000 Mbit) vetha4ca8c9 (10000 Mbit) vethfde5e99 (10000 Mbit) veth162ff1f (10000 Mbit) vethf08d493 (10000 Mbit) veth88ecf74 (10000 Mbit) veth06a4c3c (10000 Mbit) vethd7e2b54 (10000 Mbit) veth2056882 (10000 Mbit) vethdc0fc25 (10000 Mbit) vethf49d100 (10000 Mbit) veth07fcfd3 (10000 Mbit) vethe6169b5 (10000 Mbit) veth237fd3d (10000 Mbit) veth7d2b745 (10000 Mbit) ...

Guys can I make a request? I can't quite seem to get it right. I want to remake the theme I was using but I can't get it working, especially the tiles on the main dashboard. Here's a screenshot of my theme before removing Unraid theme manager: and here's the CSS that I messed with trying to get it working: Thank you!!! custom css.txt

OK will do. I actually do have all my containers set not to use 0/1 cores. I remember you mentioning I should increase the file descriptors to 6556848 before so I did that and it's currently set to that. However the max says like... half that ha. So maybe I'll lower it to the max. Also for reference, this issue started when I had my other RAM sticks in: 64GB (which I keep meaning to move back to). Just a note: I'm sort of kind of leaning toward maybe... binhex-Krusader might be the culprit? Because so far it almost seems to last forever until I enable Krusader container. Then it'll lock up within a day or two. Currently in the process of trying to eliminate that as a cause!

OK here's a new lockup. This one is slightly different. It locked up at about 9:45PM. Then after a couple of minutes, it started working again. Then it locked up again at 10:00PM and didn't come back. I had to "Magic SysRq" emergency reboot using my PiKVM. Was hoping having the times and two right next to each other might bring out some new info. Thank you! devante-nas-diagnostics-20260406-2233.zip

I migrated to hotio's qbittorrent vpn and so far the RAM hasn't gone above 3GB. pro-tip: Use Qui's backup/restore function to make migration easy.

I'm in the same boat as you. My binhex-qbittorrentvpn has usually used an abnormal amount of RAM. Kind of hovers around 12GB usage. Always starts small, then grows to that and kind of stays there. Been that way for over a year. Around the same time you started your issue, I also started getting an issue where mine will just never stop growing, then crash my entire Unraid server. Now I limit it to 16GB RAM and it still just keep growing and crashing throughout the day. (the container restarts, not that my server is crashing). I have about 5500 seeds going. Others tell me they have WAAAAAAY more and their RAM usage is around 2GB. At this point, it's restarting every couple of hours and is causing issues with my private trackers, creating ghost torrents and such. I've changed all kinds of settings with forum and AI help. Disabling caching, changing all kinds of numbers, etc. Nothing is working and I have no idea what else to do unfortunately. So, I'm right there in the same boat with you. edit: Welp, today the problem is so bad, qbit won't even load any longer.

Hey just a question. What's a "preview"? I turned it on and don't notice a difference.

Yeah I was just wondering more about the bringing my containers back thing. Won't I have to reinstall all those containers? And really? Well great now you gave me something to be paranoid about! What kind of issues have you seen with the folder method?

Things I wish I knew when starting out. 1) Creating shares at /mnt/user instead of /mnt/user/<base share name> would prevent me from hardlinking a bunch of stuff. 2) Using docker as a folder instead of one big file would prevent issues such as having to keep increasing the docker image size or it getting corrupt. One day I'll tackle number 1, but I'm hoping number 2 is easier to deal with. From my understanding, I literally just stop docker, change it to use a folder instead of docker.img, then turn Docker back on and install everything from Previous Apps. No need to even touch /appdata. This will result is no data loss, no configuration loss, everything running just as it was. Is this correct or do I need to do more? Thank you!!

Wow so fast. It's perfect!! Thank you for implementing it!!!

The icon picker is awesome!!! Great idea and thanks for implementing it!!! Question: Is there a way to disable the stop/started icons next to the container icons? I'm trying to get mine to look like this - icons ONLY: Thank you again!!!

Hey again. It froze again today. Lasted about 9 days. I still had access to the CLI via PiKVM so of course I typed reboot and then immediately remembered you asking this. Doh... Well anyway so it did the exact same thing. Froze at "open pids on /mnt/*" or something, so I pressed the physical power button and it restarted the shutdown process, got stuck there for a while, then kept going until it got stuck on Generating Diagnostics for over an hour. So I forced shut down once again. Well I don't know if it's helpful, but once I got booted it up, I ran your command: Filesystem Size Used Avail Use% Mounted on rootfs 16G 1.1G 15G 7% / The only thing I was actively doing at the time was I went to Sonarr, I went to a show, I clicked on Interactive Search, then it just stayed there doing a little animation for much longer than normal. I just let it sit and eventually I noticed the server locked up again. I do remember one other time a couple of months ago, it locked up when I did a search from Prowlarr. Anyway, just some more info. By the way, all this wouldn't be AS big a deal except I have to force it. Any tips on having it not get stuck on the generating diagnostic part? Thanks!~ devante-nas-diagnostics-20260308-1811.zip

DOh sorry, I had already issued a reboot command before reading that. Now it's just sitting at "rc.local_shutdown: Active pids left on /mnt/*" and probably will be until I can get home to force power it off. I'll remember to run that next time it happens and report back though! edit: Now it's stuck on "Generating diagnostics..." - Sometimes it does actually get past the active pids message but will 100% be stuck at this for until I force power off.

Oh yeah, I ran a memtest for over 24 hours and it showed everything fine. Coincidentally, it JUST froze about 5 minutes ago. CLI is still running, though, albeit extremely slowly. So hopefully I can stop the pre-clear that was running on a new 20TB I just put in yesterday. I thought I had it narrowed down to either Homepage or binhex-Krusader but it just happened as I was loading stats in Prowlarr. So I'm back to having no idea. About ready to give it all up since this thing is probably killing my drives each forced power off.

Thanks but simply doesn't work for me on 7.1.4. The logo still takes me to the Unraid site.

Just a follow up on the situation: it's still happening. I've tried: Different RAM Updating BIOS Updating firmware of HBA LSI card. Disabling VM service. Shutting off every container except Plex Setting max fuse descriptors. Safe mode with nothing running for a day I think, it didn't freeze - also tried safe mode with Plex running but it wouldn't connect externally) Other stuff I'm sure I'm forgetting. Not only does it happen, it started getting worse. Happening like every 30 minutes one day. To add to that, pressing the power button stopped working correctly. Unraid would get stuck "collecting diagnostic data" or whatever indefinitely during shutdown. So I've hard to hard power down. My poor drives. Last try, I ran only Plex for 3 days and it was fine. Then I turned on my streaming and download stack (The *arrs, qbittorrent, etc) and it worked for another three days and just locked up right now. Luckily the power button worked. I still have yet to try: Removing all plugins. (trying to figure out how to do this without losing my plugin settings) Running normally even without Plex for a few days. I'm just really at a lost. I'll try the two above of course. Went from the perfect Unraid system for a couple years to this seemingly over night. And I wouldn't mind so much if not for I'm destroying my hard drives. Anyway, just updating. This diagnostics is from when I happened to be looking and saw my HTOP window go away (which indicates it's crashing) and verified that I couldn't get to the dashboard so pressed the power button. I caught it in time for it to power down properly. Memory usage was hovering around 20GB out of 32GB last I looked (normally I have 64GB but I'm trying different sticks). devante-nas-diagnostics-20260111-1429.zip

Hey, Using Mousehole on Unraid 7.1.4. https://github.com/t-mart/mousehole Whenever I stop (including to restart) the image, I get the following kernal error in Unraid: Dec 25 07:10:06 Devante-NAS kernel: traps: bun[1233822] general protection fault ip:152d4ff0f50f sp:7fff7182edd0 error:0 in libc.so.6[2650f,152d4ff0f000+155000] The numbers in there all change but it's the same message everytime otherwise. I get no error in the actual Mousehole logs. Posting this here because in the hundred~ish containers, this is the first one to cause this error so posting it in both (Mousehole github and here). Below is the Unraid log and the Mousehole log. Unraid (I stopped it twice): Mousehole: Anyone see this kind of error before? Thank you!