BLKMGK

Appreciate you figuring this out and posting, I just upgraded to 7.2.6 and my driver upgraded too - lots of stuff failed. Downgrading my NVIDIA driver right now! Wondering if the NVIDIA plug-in may have something to do with this as it notes CDI generation in the release notes as fixes and CDI generation appears to be what is screwing my system up :( Perhaps NVIDIA did something cute. The site for the streams changed the path for the script but the hack worked. Hopefully the CDI issues can be sorted out soon although with my older card I'm not sure what advantage newer drivers really have. Back up and running - much thanks!

Ugh, server cannot resolve Github.com - WTH? Pings Google fine, resolves CNN, but is having issues with others. I pull data in containers from many servers too. Something weird with DNS here, I'll investigate this evening - something tells me this isn't an Unraid issue! Hopefully I'll be loading your plugin tonight though P.S. Seems this is JUST my Unraid server too <sigh>

Getting an odd error, is there an issue with the download site? "plugin: installing: tailscale.plg Executing hook script: pre_plugin_checks plugin: downloading: tailscale.plg ... done plugin: downloading: unraid-tailscale-utils-1.12.0-noarch-1.txz ... plugin: unraid-tailscale-utils-1.12.0-noarch-1.txz download failure: Network failure Executing hook script: post_plugin_checks" Server is up and running just fine and accessing the internet too.

Well, no dice. I removed the NIC - no change. I removed the 2 added M.2 drives, no change. I updated the woefully out of date BIOS on the mobo, no change. At that point the only thing in the box was the GPU, my M.2 cache, and the new adapter but at no point were the drives recognized nor was I ever able to see anything from the adapter card that would allow me to configure it in any way. I did see an entry in the unRAID logs that mentioned it else I'd have concluded the card was dead. At some point I'll get this card running in another machine and try out some of the SAS tools. For now, my machine has been down a day and I need it running so I've rerun all of the older cabling and booted on the old PERC and 9203-16i It seems to have come up fine but I need to format the new cache drive to be complete. If anyone can tell me more about this 9305-24i adapter I'm all ears! I won't be racking this for a little while so I can screw with it but once I shove it into the rack I'm not going to be super excited about dragging it out

It's a full-length slot, I tried yanking the NIC out and no change. I'll see about putting it in the slot where the NIC had been and see if that makes a difference, but it will interfere with my USB stick. It does occur to me now that you've mentioned this - I now have a full complement of 3 M.2 drives onboard. I seem to recall that these may also use PCI lanes. I will do some research and see if filling each of those impacts the slots. A distant ringing memory says that's the case but I'll verify it! Putting this card in another machine might also help as if it shows a BIOS there and not in my server it'll be a clue. I'll report back in a bit, thanks for the nudge!

I'm attempting to consolidate two previous SAS controllers to just using this single controller. I've had this on my shelf awhile but had never attempted to install it since it required a complete recable. I believe I have the correct breakout cables sourced and it's wired to a SuperMicro backplane that has individual SATA connections. Upon bootup (Asrock Taichi) I see no BIOS for this adapter during POST and nothing in the UEFI concerning it either. unRAID boots fine except I see NO drives. When I examine my system using one of the unRAID plugins I've installed I see a line that mentions an LSI SAS3224 SAS-3 card so I believe the card is at least seen. My thought at the moment is to install this into a Windows machine I've got and attempt to access it with SAS3Flash for which I believe I've found a current copy w\latest firmware. What I'm unsure of is what configuration may be needed, my understanding is this card is IT Mode out of the box - correct? Should I be seeing any options to access it during POST? Should there be notifications from it during POST? Having NO experience with this particular card I'm not sure what needs to be done - my hope had been it would simply work (lol). My system is down until I can get back to working on it this evening, but I'd appreciate any pointers on basic configuration of it - thanks!

Updated from 6.9.2 all the way to 6.11.4 and appear to be running fine - Ryzen 3700. Large storage system with every disk encrypted, no issues. I halted all VMs and all containers prior to update, made sure no files were open, and it went smoothly. Took the opportunity of downtime to upgrade a disk! Will have to reboot when that rebuild is complete to downgrade an NVIDIA driver that autoupdated. <sigh> Only quirk I've found annoying is my Flash share is no longer visible. I assume this was a security change but I'd like it back and will accept the risks involved. I do seem to need to recreate my SSH key too but no biggie once I get my share back heh. Overall running well (for the last hour anyway) and the upgrade was smooth! Edit: aaaand I got my Flash drive back. On the Main screen just click on the drive and enable the share, easy peasy once I dug a bit in the right place!

I've always wanted an easy way to PXE boot, this sounds promising! Thank you!

I'm hoping Limetech will put the overlay module into their baseline kernel. If they can get to 5.4x we should see X570 chipset support too I believe.

I posted it there as it appeared to be a bug in 6.8, I had missed the change in the release notes and it was pointed out. At that point I had assumed it was the plug-in not having been updated and thus asked here. I will follow this there if you would prefer but I wasn't attempting to seek solution in multiple places at once.

Hopefully this has what you need! I'm currently running a link file in my Go so I'd have to break it to recreate but this isn't a long term fix obv. If you need me to do anything say the word and I'll work it as quick as I can to help out if there's an issue. minion-diagnostics-20191014-0132.zip

Allow me to actually answer the question. Converting from entering a passphrase to a keyfile is something I *just* had to do. The links above will tell you how to setup crypto just fine or even change passwords but you'll have to dig pretty good to find a way to easily go from passphrase to a file so I'll try to save you some trouble. In the end you need to have a file in the root of your ephemeral boot drive named keyfile that contains your passphrase. In my case I did this by creating a file on my USB stick and a line in my GO file to create a link to it as detailed below. Note that this is NOT SECURE if someone snatches your server. For me this is a temporary thing until I can go back to entering it by hand down the road. Others have come up with schemes to transfer the file in question via SFTP from other servers and it's also possible to use binary files like say a picture vs a text file - what I've detailed isn't that but you get the idea.

6.8.0 rc3 may have changed functionality that could be impacting Unassigned Drives. Specifically I have a drive outside of the array I mount using Unassigned Drives that is encrypted that fails to mount either manually or via AutoMount when I upgrade to 6.8.0 rc1. I can SSH into the array and display contents of all drives except the single Unassigned Drive I use for containers and VMs. Here's a link to the post in the prerelease area. Not clear yet where the issue lies but this worked fine in at least two previous releases and it seems behavior changed with the new 6.8 v1 release candidate. Edit: D'oh! There's a statement in the release notes that mentions they no longer save the decryption key to a file and that an API has been provided to allow Unassigned Drives to continue to function. Seems this is intentional, intended, and my use case was anticipated! Pretty please may I volunteer to test should that be needed assuming Unassigned Drives is updated?

Heading over to post a bug, release was a no-go for me. So close and looking forward to the new kernel; and hardware support Edit: Not a bug, a feature! Unassigned Drives needs an update to continue to work with encrypted drives is all. A security update has changed the way you decrypt drives outside the array. Worked around it for now with a link file in my Go but it's not a long-term fix.

Thanks, that's perfect I now have it up and running. Will test out swarm soon! If I can cluster with other machines in my home that will rock.

Attempting to give your kernel a whirl! I attempted to compile my own for testing but ran into issues that I'm still trying to solve where GCC appears broken using your script. However when I use your kernel I get an error about an "incompatible md version". Which version of unRAID was your kernel built for? 6.7 hasn't worked for me and I'd really like to get this working! I now have an AMD processor in my server and swarm would be awesome with a project I'm working. If we can prove this out perhaps we can get Limetech onboard with the proper modules and it could trickle down to the NVIDIA guys Thanks!

Another big thanks! Loaded it up and it's running stable as an unRAID server. I'm still seeing Swarm issues with our project though and at this point I'm starting to suspect something else could be amiss so it would be helpful if someone else could test as well. Same error about a route to host not being found.😣 I have spun up another standard Linux host as a VM and am waiting for my more knowledgeable friend to lend a hand adding it to our swarm and testing in case I screwed something up previously. Docker DNS seems pretty weird so diddling with it is confusing for me trying to troubleshoot it. The suggestion of a single host swarm seems like a good one and maybe we can try that on this test system. Unfortunately I'm about to take a trip away from home for a few weeks. I'll have a laptop and VPN access at least and my partner in crime will be coming along too so hopefully there will be some downtime to better troubleshoot this together. I'll update as I figure things out, I suspect my server will be getting a 12core Ryzen soon so I'd love to be able to utilize it fully BTW it's pretty weird seeing the container appear and disappear as the swarm comes up and down let me tell you! unRAID currently doesn't have an XML file for it so it's being loaded at the CLI. I'll figure out how to more normally load it in the future once the silly thing works. A big THANK YOU to @CHBMB!

So yup, I needed to label the node properly and then it began being available to the swarm, so that was good. However, after some troubleshooting inside the worker container we're still getting errors as it attempts to connect back to it's tasking engine. An error 113 - "no route found to host". Inside the container we can ping by hostname but the IP we get is crazy and seems to change depending upon the instantiation of the container. We are suspecting that Docker's weird DNS mechanisms may be confusing the troubleshooting. In any case we are unable to get a route back to the tasking database so the app fails, the worker cannot get work and never checks in. Not sure what's causing this. I believe tonight I may drop one of the other (not unRAID) nodes and go through the steps of re-adding it to ensure that something hasn't occurred with our container somehow. If it works perfectly with a standard Linux install I'm not sure what the next steps will be. I may try loading up a VM on unRAID, installing Docker, and trying that - this rings incredibly backwards to me however. Will try to troubleshoot this more tonight, it's driving me cxrazy but I've got to get out of the house now lol so just an update

I've got the test system up and running on the custom kernel, it's joined into the swarm (I could to that before tho), but I'm still having some issues that could very easily be my ignorance. A friend of mine who's been working with me on this is going to need to take a look at the error I see. From what I can tell it's a node labeling issue but I had thought I'd built it correctly in the yaml file. Anyway, the kernel appears stable and I'm hopeful that once I figure out my configuration issue (and no doubt learn something) that this will WORK. Fingers crossed and a big THANK YOU to @CHBMB for giving me something to test with! I'm hopeful and truly appreciative of the investigation he did on this as frankly it was beyond me. Stay tuned, as I know more I'll be sure and share it with everyone. If others have need of Swarm and could test their use cases that would be helpful too since I may not be pushing many boundaries here

I appreciate you taking the time to diff these results! I had to run out the door after posting but I'm not surprised there's other differences. The module I highlighted is one of the modules listed as "common", the research I've done seemed to indicate it was a good place to start! I don't blame you for not wanting to tinker with the NVIDIA builds for sure. As it happens I've given a few unRAID systems to friends over the years as gifts, I've reached out to one friend who's not utilizing theirs heavily right now and will be bringing it home to test with using the build you posted earlier My fingers are crossed that I'll find success or at least answers as to what's needed and I can load test with it to see if weirdness occurs. I'm hoping this is enough, I recognize that enabling modules at the kernel level willy nilly isnt a great idea and am hoping that what I need proves benig to what Tom has in place and doesn't harm the KVM support either. I hope to test tonight if someone doesn't beat me to it! I really appreciate the support and responses guys!

Sadly this isn't completely true. Even RipBot allows you to run multiple encoding workers on a single machine. Ffmpeg and x.265 are indeed multithreaded however they don't scale past about 6threads very well. The machine I have with 48threads was one I tested on and it was a failure to say the least. I had a few threads working but quite a few threads sat completely idle. That machine with multiple worker containers pegs all cores and the fans become quite noisy In any case, I currently have three machines in the cluster and would like to add my unRAID machine as a fourth! Edit: Also, Windows is going to be adding Docker support soon and we will make sure our workers can live on those. That would allow me to add at least two more machines including one that's a competitor to my 48thread system 😮

For reference here's what I get when I run the check-config script on a machine that Swarms just fine blkmgk@smaug:~$ ./check-config.sh warning: /proc/config.gz does not exist, searching other paths for kernel config ... info: reading kernel config from /boot/config-4.15.0-50-generic ... Generally Necessary: - cgroup hierarchy: properly mounted [/sys/fs/cgroup] - apparmor: enabled and tools installed - CONFIG_NAMESPACES: enabled - CONFIG_NET_NS: enabled - CONFIG_PID_NS: enabled - CONFIG_IPC_NS: enabled - CONFIG_UTS_NS: enabled - CONFIG_CGROUPS: enabled - CONFIG_CGROUP_CPUACCT: enabled - CONFIG_CGROUP_DEVICE: enabled - CONFIG_CGROUP_FREEZER: enabled - CONFIG_CGROUP_SCHED: enabled - CONFIG_CPUSETS: enabled - CONFIG_MEMCG: enabled - CONFIG_KEYS: enabled - CONFIG_VETH: enabled (as module) - CONFIG_BRIDGE: enabled (as module) - CONFIG_BRIDGE_NETFILTER: enabled (as module) - CONFIG_NF_NAT_IPV4: enabled (as module) - CONFIG_IP_NF_FILTER: enabled (as module) - CONFIG_IP_NF_TARGET_MASQUERADE: enabled (as module) - CONFIG_NETFILTER_XT_MATCH_ADDRTYPE: enabled (as module) - CONFIG_NETFILTER_XT_MATCH_CONNTRACK: enabled (as module) - CONFIG_NETFILTER_XT_MATCH_IPVS: enabled (as module) - CONFIG_IP_NF_NAT: enabled (as module) - CONFIG_NF_NAT: enabled (as module) - CONFIG_NF_NAT_NEEDED: enabled - CONFIG_POSIX_MQUEUE: enabled Optional Features: - CONFIG_USER_NS: enabled - CONFIG_SECCOMP: enabled - CONFIG_CGROUP_PIDS: enabled - CONFIG_MEMCG_SWAP: enabled - CONFIG_MEMCG_SWAP_ENABLED: missing (cgroup swap accounting is currently not enabled, you can enable it by setting boot option "swapaccount=1") - CONFIG_LEGACY_VSYSCALL_EMULATE: enabled - CONFIG_BLK_CGROUP: enabled - CONFIG_BLK_DEV_THROTTLING: enabled - CONFIG_IOSCHED_CFQ: enabled - CONFIG_CFQ_GROUP_IOSCHED: enabled - CONFIG_CGROUP_PERF: enabled - CONFIG_CGROUP_HUGETLB: enabled - CONFIG_NET_CLS_CGROUP: enabled (as module) - CONFIG_CGROUP_NET_PRIO: enabled - CONFIG_CFS_BANDWIDTH: enabled - CONFIG_FAIR_GROUP_SCHED: enabled - CONFIG_RT_GROUP_SCHED: missing - CONFIG_IP_NF_TARGET_REDIRECT: enabled (as module) - CONFIG_IP_VS: enabled (as module) - CONFIG_IP_VS_NFCT: enabled - CONFIG_IP_VS_PROTO_TCP: enabled - CONFIG_IP_VS_PROTO_UDP: enabled - CONFIG_IP_VS_RR: enabled (as module) - CONFIG_EXT4_FS: enabled - CONFIG_EXT4_FS_POSIX_ACL: enabled - CONFIG_EXT4_FS_SECURITY: enabled - Network Drivers: - "overlay": - CONFIG_VXLAN: enabled (as module) Optional (for encrypted networks): - CONFIG_CRYPTO: enabled - CONFIG_CRYPTO_AEAD: enabled - CONFIG_CRYPTO_GCM: enabled - CONFIG_CRYPTO_SEQIV: enabled - CONFIG_CRYPTO_GHASH: enabled - CONFIG_XFRM: enabled - CONFIG_XFRM_USER: enabled (as module) - CONFIG_XFRM_ALGO: enabled (as module) - CONFIG_INET_ESP: enabled (as module) - CONFIG_INET_XFRM_MODE_TRANSPORT: enabled (as module) - "ipvlan": - CONFIG_IPVLAN: enabled (as module) - "macvlan": - CONFIG_MACVLAN: enabled (as module) - CONFIG_DUMMY: enabled (as module) - "ftp,tftp client in container": - CONFIG_NF_NAT_FTP: enabled (as module) - CONFIG_NF_CONNTRACK_FTP: enabled (as module) - CONFIG_NF_NAT_TFTP: enabled (as module) - CONFIG_NF_CONNTRACK_TFTP: enabled (as module) - Storage Drivers: - "aufs": - CONFIG_AUFS_FS: enabled (as module) - "btrfs": - CONFIG_BTRFS_FS: enabled (as module) - CONFIG_BTRFS_FS_POSIX_ACL: enabled - "devicemapper": - CONFIG_BLK_DEV_DM: enabled - CONFIG_DM_THIN_PROVISIONING: enabled (as module) - "overlay": - CONFIG_OVERLAY_FS: enabled (as module) - "zfs": - /dev/zfs: missing - zfs command: missing - zpool command: missing Limits: - /proc/sys/kernel/keys/root_maxkeys: 1000000

Wow, this blew up overnight! As I stated above, I'm no Docker expert but I'm attempting to learn more and I DO have a use case for this. I've been relying on the check-config script and making an educated guess that this "missing" module was what was causing me issues. I understand however that it may not be properly checking our kernels and it's possible there's a different module that's needed for what I'm doing but this seemed a good place to start as it's networking that breaks for my use case. I would agree that having this done in an upstream fashion by @limetech is the way to go. I'm an avid user of the NVIDIA enhanced kernels but the last thing I'd like to see is more work placed upon @CHBMB as he's already got his hands full with crazy support questions and to add to it would be insane! He has the ability to add this but that's asking for too much IMO. I did briefly consider trying to compile and test a custom kernel myself as documentation to do it exists (sans NVIDIA) but I figured I'd ask first as that's a learning curve I'm not yet willing to climb if possible. I'm presently running 6.7.1 RC1 (NVIDIA) but I will attempt to test the v6.7.0RC1 kernel posted above and report back. It may take a day or so as I've got a lengthy list of jobs running right now that I'd like to complete first so anyone else able to help out I'd appreciate it. Either way I need to test to ensure my issue is solved with this addition or figure out what else might be blocking me. I've seen it asked elsewhere what containers would benefit from Swarm. One general thing that might be useful by enabling Swarm is DockerDNS which I don't *think* works right now. DockerDNS as I understand it is an internal Docker DNS system that gets turned on when Swarm is activated and it could prove generally useful as you can reference other containers by name internally. That's not why I want this however so I'll try to explain better what I'm up to in hopes that folks might be a little more eager 😎 ============begin long explanation you can skip=========== Like many I use my unRAID to store video. As such I try to be judicious in how I store it. I can rip a BD and end up with a 30GB file, I can then compress it down with x.265 and store it for a third of that or less while maintaining excellent video quality and not compromising on sound quality. The catch is that this requires some fairly hefty amounts of processing* and time investment. Most of us are familiar with HandBrake, some of us may be also be familiar with RipBot264. RipBot264 allows you to "cluster" Windows computers in order to encode individual videos more quickly. Each computer encodes portions of the video and it's joined back together at the end. RipBot264 is pretty well supported and mostly works well too - I use it on a few Windows machines. However I have a fairly decent amount of Linux hardware in my home and the developer of RipBot is unwilling to support Linux, he advised me to run VMs of Windows instead when I asked, I'm not willing to do so. I sat down and analyzed how the RipBot264 program does it's work, I studied ffmpeg and x.265 functionality, I asked ignorant questions, and I realized that duplicating what he was doing on Linux was completely possible with the exception of AVISynth**. I also realized that it could be done more efficiently without some of the intermediate steps that program takes. I built a proof of concept script, tested it, and it worked WELL! I happen to work with some talented guys and Docker is one of the technologies that we're beginning to use, Swarm is an area of interest too. I managed to interest some of my coworkers (one in particular) in my little project as I'm not a well versed programmer. Working together we've built a system that can cluster encode videos VERY well on a home lab I have setup that includes a 48thread machine***, a 24 thread ESX server, and a small PC tucked in the corner for Kodi use. What I've been unable to join (properly) into this cluster is my 32thread unRAID box 😢 End-state I'd like to end up with a container that can live in the unRAID "app" repo or be easily side-loaded that could allow users to join unRAID servers into a cluster for added compute power with our new toy. I'd tried this by hand from the commandline and was able to load a worker container and join our swarm but unable to get the container to receive any tasking or comms. This is when I began digging into what might be missing from the kernel etc. Thus I've arrived here! So YES, I have some need of unRAID more fully enabling Swarm functionality for our little project. As a side note - yes we intend to release our code to others, ALL of it, and yeah we will need some help in the future. My selfish hope is that when released to others with more skill than we possess features of interest can be built that we're interested in. We still have a few things to add and test before making it public. Yes, there are products that do this commercially - at eye watering prices. As yet I've found no built and supported OpenSource program duplicating this so we've scratched our own itch so to speak as is the OpenSource way! There, sorry for the lengthy dissertation lol *at present time I don't leverage GPU hardware for this but may begin leveraging it in the future, I'd want it just to speedup the math not run through the GPU's onboard encoder as I want as much control over quality as possible. For some reason RipBot refuses to use any of my current desktop GPU hardware - ugh. **see Vapoursynth for a Linux solution that we've yet to touch. AVISynth is pretty powerful though so yes eventually we'll want filtering ability. ***this is all older XEON hardware, when Ryzen 3000 is released I'll be upgrading ALL of it including my unRAID server 😈

The script to check the Docker configuration can be found here-> https://github.com/moby/moby/blob/master/contrib/check-config.sh