-
[Support] ctrlaltd1337's Unraid Templates
Apologies, I wasn't alerted about your comment. I updated your Github issue. Default login is admin:1234.
-
[Support] devzwf - Glance
You should update the "additional info" as well, because it's saying to put the glance.yml file in the app folder, not the app/config folder.
-
ctrlaltd1337 changed their profile photo
-
[Support] ctrlaltd1337's Unraid Templates
I am not the developer of any of the below applications, just the template creator/maintainer. If you run into any issues with a template, please respond in the thread with which template you need help with, or open an issue on my repo: https://github.com/ctrlaltd1337ed/unraid-templates Posteria Posteria is a web-based media poster management system that allows you to organize and store custom posters for your movies, TV shows, seasons, and collections. It provides an elegant interface for uploading, importing, managing, and accessing your media artwork. https://github.com/jeremehancock/Posteria Recommendarr Recommendarr is a web application that generates personalized TV show and movie recommendations based on your Sonarr, Radarr, Plex, and Jellyfin libraries using AI. https://github.com/fingerthief/recommendarr
-
[Plugin] Nvidia-Driver
Thanks! I'll look into this. The PSU is only a year and a half old, but I can do a few tests on it. I can also look into "Resizable Bar Support and Above 4G decoding," but my motherboard is server-grade and over 10 years old, so I doubt there's anything there for me. I've been using this plugin and the LS "variation" before it since release, so it should be fine without. I assume it errored out and Plex was able to continue with CPU transcoding, but after the backup when trying to restart the container, it becomes noticeable because the container errors out when trying to look for that visible device. I'll attempt to re-seat the GPU into the mobo, and re-plug the power. Thanks again.
-
[Plugin] Nvidia-Driver
Hey @ich777, thanks for this plugin - it has worked great for me for some time. I've started to run into some issues lately, and I'm unsure if it is related to your plugin or not. Essentially, after my appdata backup completes on Monday mornings, I get an error that Plex could not start. I've narrowed it down to this plugin not being able to read what GPU is plugged in, and it only happens after appdata backup. When Plex tries to run with the Nvidia Visible Devices variable, it errors out so I need to restart the server to have the GPU be read by your plugin again. I've attached my diagnostics, cheers! ghost-diagnostics-20240916-0814.zip
-
Appdata drive reporting more usage than expected
Yeah, following those steps worked to re-instate my Docker image, and without issue. The size on the disk continues to fluctuate, currently at 209GB. I'll see if the varying in size continues and I'll change my appdata to a proper cache pool and mirror it soon as well. Thanks for talking through this with me, I'll have to see if it happens again!
-
Appdata drive reporting more usage than expected
The first command didn't show any results, and when I restarted my server, the unassigned disk didn't auto-mount. And when I mounted it, my Docker image failed to start again ("Docker Service failed to start." when trying to open Docker tab). 😭 But the used space has gone down to 188GB used out of 250GB again. I'm starting to wonder if it's my SSD, but it didn't throw any errors and the SMART looks to be fine?
-
Appdata drive reporting more usage than expected
Hey, I'm looking to figure out why on the Main tab in Unraid, appdata (unassigned disk) is reporting as 240GB used (1GB more than this morning), when it was about 50GB smaller yesterday. The first thing that comes to mind is that I needed to re-create my docker.img yesterday, but I'm not seeing the old one hiding anywhere. I've attached three images - what Unraid is reporting the drive usage as, and what Krusader and qdirstat are reporting the drive usage as.
-
Docker containers not listing alphabetically
I thought containers used to automatically sort alphabetically? I've noticed the last few months that new containers get put to the top of the list. Any way to change this back?
-
[Plugin] CA Appdata Backup / Restore v2.5
Thanks for the response. I've just changed it to wait a bit longer to kill containers and did a fresh install of your plugin. I'll see how it runs tonight and check the logs of the plugin (forgot those were a thing). Thanks,
-
[Plugin] CA Appdata Backup / Restore v2.5
I'll try to keep this as brief as possible, while also providing enough detail. OS: 6.11.5 Plex Container: linuxserver/plex Involved plugins: CA Backup / Restore Appdata (v2, 2022.12.13) and Appdata Backup/Restore v2.5 (2023.01.28) I have had my appdata backup run on Mondays at 4am for years, even with the recently deprecated plugin. It hadn't been giving me issues until recently and I had read that v2.5 was giving people errors so I stuck with the v2 until last week, but my issue still occurred with v2.5. The issue seems to only be affecting the Plex container, as all other containers backup properly and restart without issue. This obviously makes me think it's an issue with the container, but I've tried to completely re-install it and the same thing keeps happening. The issue is that after the appdata backup, Plex does not restart, and whenever I try to start it I get greeted with "Error: Server Error" with no other information. I cannot start the container, delete the container, I can hardly do anything to it. The one thing I was able to do one time was rename it (I changed it from plex to plex2). I have tried turning the Docker service off and on, but I was unable to unmount my unassigned disk (appdata), so something was stuck. I still could not update, delete, anything. My solve was to set the container to not autostart, restart the server, and then all works as expected when I start it up manually. Where it gets weirder is that while the container is quite obviously not running, htop is still showing Plex Transcoder as working for HOURS, with it still using the CPU. My question is, what can I do to try to pull logs if it happens again this Monday morning, or do you have any thoughts on how to solve this? Let me know if you need any more info or diagnostics, thanks!
-
Plex container doesn't start and has errors after appdata backup
Any thoughts? Should I post to a different sub-forum?
-
Plex container doesn't start and has errors after appdata backup
I'll try to keep this as brief as possible, while also providing enough detail. OS: 6.11.5 Plex Container: linuxserver/plex Involved plugins: CA Backup / Restore Appdata (v2, 2022.12.13) and Appdata Backup/Restore v2.5 (2023.01.28) I have had my appdata backup run on Mondays at 4am for years, even with the recently deprecated plugin. It hadn't been giving me issues until recently and I had read that v2.5 was giving people errors so I stuck with the v2 until last week, but my issue still occurred with v2.5. The issue seems to only be affecting the Plex container, as all other containers backup properly and restart without issue. This obviously makes me think it's an issue with the container, but I've tried to completely re-install it and the same thing keeps happening. The issue is that after the appdata backup, Plex does not restart, and whenever I try to start it I get greeted with "Error: Server Error" with no other information. I cannot start the container, delete the container, I can hardly do anything to it. The one thing I was able to do one time was rename it (I changed it from plex to plex2). I have tried turning the Docker service off and on, but I was unable to unmount my unassigned disk (appdata), so something was stuck. I still could not update, delete, anything. My solve was to set the container to not autostart, restart the server, and then all works as expected when I start it up manually. Where it gets weirder is that while the container is quite obviously not running, htop is still showing Plex Transcoder as working for HOURS, with it still using the CPU. My question is, what can I do to try to pull logs if it happens again this Monday morning, or do you have any thoughts on how to solve this? Let me know if you need any more info or diagnostics, thanks!
-
Docker requests
This worked, cheers! One thing to add is that I needed to log in with [email protected] and MyPassword for the first login regardless of what I had in the container variables.
-
Docker requests
Requesting this too. I see Tandoor Recipes is up, but I would love to try out Mealie as well.