cybrnook
Members
-
Joined
Everything posted by cybrnook
-
Yep, just remove your credentials from the opensubtitles portion of the docker template, save and restart.
-
Been scratching my head all afternoon on this one, but I think I finally narrowed it down. What I found is that when you have "Host access to custom networks" enabled in the Docker options, it's fudging the MAC address of the Unraid server as a whole. I found this out because I was attempting to debug the "macvlan" Call Trace issue when we have custom IP's assigned to Docker Containers. To me, having custom IP's (Custom br0) is a requirement so I can implement firewall rules on a per docker container basis. As well, just taking the approach of creating another VLAN on my network is not a suitable workaround because that just adds additional complexity when trying to route to those containers from my primary network. Anyways..... I thought what the hell, let me swap in a different network card to see if it makes a difference (Intel X550 vs X540 vs 82599ES etc..) since the assumption is some people have this issue and others don't, perhaps it's a hardware or driver issue? So, I installed my different network card, and proceeded to do the usual, set static IP in unraid, then in pfsense make sure I tag the proper MAC address (the new one) to make sure I also assign the same static IP. This is where it started getting weird.... The actual MAC of my adapter begins with D0 and ends with 9C: So when I went into pfsense, I was ready to tag D0..9C, but didn't see it. So I checked the ARP table, and low and behold I saw a MAC of 36...52: If I disable "Host access to custom networks", then the real MAC comes back: At least for me, this is an issue as this means that when enabling this option, any static IP assignment I have in my router would be ignored since the MAC is randomized each time with macvlan. As well, I am not sure of the additional macvlan ramifications of this when the MAC for an IP is changing. Perhaps this is working as designed, but I wanted to bring this to light as it may be related to the calltrace for macvlan, and for sure surely breaks my static IP rule that I define in my router. And yes, I know of course that I could set a static IP in unraid (which I do). But I also like to make sure that IP is static in my router as well, as I have had occasions where I needed to nuke the network.cfg file, and still want to come up on the same IP. @limetech I am tagging as "other" for now since I can't make out if this is Urgent, Annoyance, Other or by design.
-
@ich777 thanks for updating the plugin to only display on what is actually installed, much appreciated!
-
Your variable should go in the Extra Parameters section like so:
-
Just noticed a drive in my system that's apparently going into nuclear meltdown. noah-diagnostics-20200717-2159.zip
-
Is there supposed to be a new/different variable other than the regular true/false Beta Build value? Instead of saying "true" should I put "beta25" instead? EDIT, just tested and YES seems instead of putting "true", the value "beta25" also works, so no having to copy, very cool!
-
I world recommend updating the default kernel path from /mnt/cache to /mnt/user, now that we have multiple pools. I run my appdata now on a drive other than cache.
-
Of course, that is expected. What I was thinking to see though, is assuming I left all default values, then only change to Nvidia (BETA now) and latest DVB, then the outcome would be the same (or close). I am sure it's not an issue, as it seems to work fine. I was just pondering why sizing was different if all else was same :-).
-
No worries, just wanted to make sure something wasn't going as expected. 🙂 Compiling now, will report back.
-
Yep, that may very well be it. I will try by modifying the Nvidia driver version to the specific version vs "latest" 🙂
-
@ich777 Is it expected that the sizes of the re-compiled files vary slightly in size? What I mean is I am using this to compile latest 6.9.0 beta 24 for Nvidia and DVB, using the defaults of latest and latest with beta enabled. The compilation seems to go smooth and without issue. But, if I download your pre-compiled beta 24 with nvidia and dvb and look at the file sizes compared to mine, they are slightly different. Does the fact that my architecture is an AMD system make a difference?
-
As suspected 🙂 Only thing that would throw me off a little, I am preloading the modified kernel before I am installing my Hauppauge card as well as my Nvidia GPU, that will come this afternoon. But the wording on the page makes me think that the driver isn't loading properly. I can only assume this message is appearing because I don't yet have the GPU installed. Perhaps it should say something like "Make sure that the latest NVIDIA driver is installed and running and your GPU is properly installed and detected"?
-
Absolutely great Plugin and Docker, truly thank you. Just wanted to report one small, superficial visual anomaly. I run a widescreen, high res monitor and I notice the separation bar on the plugin helper screen breaks in the middle. I use Chromium Edge:
-
@spants just wanted to call out a small typo in the CA Info notice for this template. "make sure that you fixe the unRaid servers dns to point to a real DNS Server." Should probably be something like: "make sure that you have fixed your unRaid servers dns to point to a real DNS Server other than your PiHole."
-
Community Applications Think of it as the app store for unraid. It'll help you install plugins and Dockers with minimal input from your side. It automates the manual parts for you.
-
Love to hear about the new stub system and integrated Nvidia drivers. Made my day hearing that.
-
Super cool, watched the first one and enjoyed it. Still have reconstruct write set in my system 🙂 Will tune in!
-
@wesman it's in the readme in the op: https://github.com/jlesage/docker-makemkv#access-to-optical-drives
-
New Intel vulnerability found dubbed "Cache Out": https://www.pcworld.com/article/3516302/new-cacheout-attack-targets-intel-processors-with-a-fix-arriving-soon.html Intel Processors affected (Intel CPU Skylake/Cascade Lake onward. Broadwell and earlier are seemingly not affected). AMD seemingly not affected: https://software.intel.com/security-software-guidance/insights/processors-affected-l1d-eviction-sampling No mitigation created yet, so time will tell how it's addressed.
-
I don't think filebot works with folders, only files. What you are talking about though programs like sonarr and ranarr do. Assuming these "files" you are pulling are movies and tv shows.
-
@gfjardim thanks a ton for the quick turn around time, and for looking into package handling. I really do like this plugin, and have gotten used to the UD + Preclear integration, don't wanna change... MmmmmmmMmm
-
Well, personally I preclear every drive I add to my unraid server prior to making it a part of my array 🙂 While "most" drives come up uneventful, I did just two weeks ago shuck and add a handful of 8TB's to my backup unraid server and low and behold preclearing saved me ahead of time on a disk that started to mark and reallocate bad sectors. Easier to identify ahead of time, rather than add a disk, put data on the disk, and then in time realize through smart somethings happening. For me, I love the integration of this plugin into UD (UD+), and being able to preclear at the click of a button.
-
When "exit"ing a browser based terminal session, the session closes and then instantly reopens again in the same window. Tested on FireFox and Chrome, same behavior. noah-diagnostics-20200111-1515.zip
-
I think libevent was the only thing, rather than a few things, right? I can confirm that libevent is installed by default, but perhaps the included tmux for example can't find the default? Note sure.. @gfjardim ? root@noah:/usr/lib64# ls -l libevent* lrwxrwxrwx 1 root root 21 Jan 11 03:15 libevent-2.1.so.7 -> libevent-2.1.so.7.0.0* -rwxr-xr-x 1 root root 354048 Aug 2 14:22 libevent-2.1.so.7.0.0* lrwxrwxrwx 1 root root 21 Jan 11 03:15 libevent.so -> libevent-2.1.so.7.0.0* lrwxrwxrwx 1 root root 26 Jan 11 03:15 libevent_core-2.1.so.7 -> libevent_core-2.1.so.7.0.0* -rwxr-xr-x 1 root root 229752 Aug 2 14:22 libevent_core-2.1.so.7.0.0* lrwxrwxrwx 1 root root 26 Jan 11 03:15 libevent_core.so -> libevent_core-2.1.so.7.0.0* lrwxrwxrwx 1 root root 27 Jan 11 03:15 libevent_extra-2.1.so.7 -> libevent_extra-2.1.so.7.0.0* -rwxr-xr-x 1 root root 143264 Aug 2 14:22 libevent_extra-2.1.so.7.0.0* lrwxrwxrwx 1 root root 27 Jan 11 03:15 libevent_extra.so -> libevent_extra-2.1.so.7.0.0* lrwxrwxrwx 1 root root 29 Jan 11 03:15 libevent_openssl-2.1.so.7 -> libevent_openssl-2.1.so.7.0.0* -rwxr-xr-x 1 root root 31336 Aug 2 14:22 libevent_openssl-2.1.so.7.0.0* lrwxrwxrwx 1 root root 29 Jan 11 03:15 libevent_openssl.so -> libevent_openssl-2.1.so.7.0.0* lrwxrwxrwx 1 root root 30 Jan 11 03:15 libevent_pthreads-2.1.so.7 -> libevent_pthreads-2.1.so.7.0.0* -rwxr-xr-x 1 root root 14296 Aug 2 14:22 libevent_pthreads-2.1.so.7.0.0* lrwxrwxrwx 1 root root 30 Jan 11 03:15 libevent_pthreads.so -> libevent_pthreads-2.1.so.7.0.0* -rwxr-xr-x 1 root root 14192 Dec 18 13:34 libevents-samba4.so*
-
I was just looking at the source, and I think it's due to the "less than": elif is_unraid_version '>=' '6.8.0-b1' && is_unraid_version '<' '6.8.1'; then Perhaps there is a dependency on the kernel version in 6.8.1 and what is being brought down for tmux, libevent and utemper. But I think likely the same packages from 6.8.0-b1 would work, will see 🙂
