Scroopy Noopers

I am starting to see constant daemon crashes at this time. As per the screencap below, the daemon crashes and though I can either restart the container or the daemon through the web UI, it crashes again within a few minutes. Has anyone else run into this? As far as I can tell, nothing has changed recently.

Well it's definitely been more than 3 days at this time, but that seems to have fixed my issue. Thanks a bunch.

Ok, I'll give that a shot. I'll report back if it crashes again, or within the next 3 days if it doesn't. Thanks!

I actually had that turned on in the event of another kernel panic. Here it is; you can see the start of the event at line 69923. syslog

Hello everyone, I've been getting kernel panics every few days now for probably the past month and I'm really not sure what could be causing it. I've moved my installation from my R510 to my R620, swapped out thumb drives, and so far it hasn't been resolved. For reference my machine has the following specs: 2 x E5-2650L V2 8 x 8 GB DDR3 ECC Quadro P1000 LSI 9200-8e I've attached my diags if anyone is willing to look through my system here and offer some kind of insight. If there's anything else you need to make diagnosing this issue simpler, please let me know. dellr620-diagnostics-20211118-2221.zip

So, after casually cruising through Radarr and Sonarr, and seeing that, like with my web browser I have no access to deluge, I did what any other good troubleshooter does who has no idea what to do next. I started clicking buttons while saying to myself "Screw it. What's the worst thing that could happen?". Fortunately, that led me to the "Use SSL" switch in Radarr and I clicked it, hit test and waited to see what would happen. It connected! Well, I thought, this must mean that I should be trying to access deluge through my web browser with an https prefix, so I tried it. Lo and behold, it worked! So, all of the prior complaints I put forth was for nought. I just had to do a little thinking with my noggin. Thank you for reading my excessively long TIFU. I hope you got a low chuckle out of it. TL;DR: must have hit the SSL switch in deluge when I wasn't paying attention. Took me two weeks to figure it out and felt supremely dumb when I did.

That's what I'm seeing too. I have no idea where to go from here.

It's set to bridge.

To put a close to this thread, my issue was a dead GPU, not an issue with the software. I would just like to take this opportunity to publicly thank @ich777 for all the time and effort he put into working with me to try and figure out the issue I have been having. @ich777 spent a few days working with me to get to the root of the problem and went over and above what I ever could have expected. Thank you.

It sure is

Hey guys, I'm still not sure what I'm missing. I have no LAN access to the web GUI client, though it seems to me that everything is working correctly.

I'm seeing the following text, though from my understanding of it, it looks like there is an Nvidia related driver installed. root@PowerEdgeR510:~# cd /usr/lib64 && ls -al |grep "nvidia" lrwxrwxrwx 1 root root 23 Nov 15 07:25 libEGL_nvidia.so.0 -> libEGL_nvidia.so.455.38* -rwxr-xr-x 1 root root 1346224 Nov 2 11:27 libEGL_nvidia.so.455.38* lrwxrwxrwx 1 root root 29 Nov 15 07:25 libGLESv1_CM_nvidia.so.1 -> libGLESv1_CM_nvidia.so.455.38* -rwxr-xr-x 1 root root 63784 Nov 2 11:27 libGLESv1_CM_nvidia.so.455.38* lrwxrwxrwx 1 root root 26 Nov 15 07:25 libGLESv2_nvidia.so.2 -> libGLESv2_nvidia.so.455.38* -rwxr-xr-x 1 root root 112344 Nov 2 11:27 libGLESv2_nvidia.so.455.38* lrwxrwxrwx 1 root root 23 Nov 15 07:25 libGLX_indirect.so.0 -> libGLX_nvidia.so.455.38* lrwxrwxrwx 1 root root 23 Nov 15 07:25 libGLX_nvidia.so.0 -> libGLX_nvidia.so.455.38* -rwxr-xr-x 1 root root 1123872 Nov 2 11:27 libGLX_nvidia.so.455.38* lrwxrwxrwx 1 root root 24 Nov 15 07:25 libnvidia-allocator.so -> libnvidia-allocator.so.1* lrwxrwxrwx 1 root root 29 Nov 15 07:25 libnvidia-allocator.so.1 -> libnvidia-allocator.so.455.38* -rwxr-xr-x 1 root root 82280 Nov 2 11:27 libnvidia-allocator.so.455.38* -rwxr-xr-x 1 root root 730176 Nov 2 11:27 libnvidia-cbl.so.455.38* lrwxrwxrwx 1 root root 18 Nov 15 07:25 libnvidia-cfg.so -> libnvidia-cfg.so.1* lrwxrwxrwx 1 root root 23 Nov 15 07:25 libnvidia-cfg.so.1 -> libnvidia-cfg.so.455.38* -rwxr-xr-x 1 root root 206160 Nov 2 11:27 libnvidia-cfg.so.455.38* -rwxr-xr-x 1 root root 50277400 Nov 2 11:27 libnvidia-compiler.so.455.38* lrwxrwxrwx 1 root root 30 Nov 15 07:25 libnvidia-egl-wayland.so.1 -> libnvidia-egl-wayland.so.1.1.5* -rwxr-xr-x 1 root root 37760 Nov 2 11:27 libnvidia-egl-wayland.so.1.1.5* -rwxr-xr-x 1 root root 32335784 Nov 2 11:27 libnvidia-eglcore.so.455.38* lrwxrwxrwx 1 root root 21 Nov 15 07:25 libnvidia-encode.so -> libnvidia-encode.so.1* lrwxrwxrwx 1 root root 26 Nov 15 07:25 libnvidia-encode.so.1 -> libnvidia-encode.so.455.38* -rwxr-xr-x 1 root root 104896 Nov 2 11:27 libnvidia-encode.so.455.38* lrwxrwxrwx 1 root root 18 Nov 15 07:25 libnvidia-fbc.so -> libnvidia-fbc.so.1* lrwxrwxrwx 1 root root 23 Nov 15 07:25 libnvidia-fbc.so.1 -> libnvidia-fbc.so.455.38* -rwxr-xr-x 1 root root 127336 Nov 2 11:27 libnvidia-fbc.so.455.38* -rwxr-xr-x 1 root root 34290928 Nov 2 11:27 libnvidia-glcore.so.455.38* -rwxr-xr-x 1 root root 627144 Nov 2 11:27 libnvidia-glsi.so.455.38* -rwxr-xr-x 1 root root 12211864 Nov 2 11:27 libnvidia-glvkspirv.so.455.38* -rwxr-xr-x 1 root root 1359312 Nov 2 11:28 libnvidia-gtk2.so.455.38* -rwxr-xr-x 1 root root 1368016 Nov 2 11:28 libnvidia-gtk3.so.455.38* lrwxrwxrwx 1 root root 18 Nov 15 07:25 libnvidia-ifr.so -> libnvidia-ifr.so.1* lrwxrwxrwx 1 root root 23 Nov 15 07:25 libnvidia-ifr.so.1 -> libnvidia-ifr.so.455.38* -rwxr-xr-x 1 root root 207064 Nov 2 11:27 libnvidia-ifr.so.455.38* lrwxrwxrwx 1 root root 17 Nov 15 07:25 libnvidia-ml.so -> libnvidia-ml.so.1* lrwxrwxrwx 1 root root 22 Nov 15 07:25 libnvidia-ml.so.1 -> libnvidia-ml.so.455.38* -rwxr-xr-x 1 root root 1922232 Nov 2 11:27 libnvidia-ml.so.455.38* lrwxrwxrwx 1 root root 23 Nov 15 07:25 libnvidia-ngx.so.1 -> libnvidia-ngx.so.455.38* -rwxr-xr-x 1 root root 3046120 Nov 2 11:27 libnvidia-ngx.so.455.38* lrwxrwxrwx 1 root root 26 Nov 15 07:25 libnvidia-opencl.so.1 -> libnvidia-opencl.so.455.38* -rwxr-xr-x 1 root root 38154880 Nov 2 11:27 libnvidia-opencl.so.455.38* lrwxrwxrwx 1 root root 26 Nov 15 07:25 libnvidia-opticalflow.so -> libnvidia-opticalflow.so.1* lrwxrwxrwx 1 root root 31 Nov 15 07:25 libnvidia-opticalflow.so.1 -> libnvidia-opticalflow.so.455.38* -rwxr-xr-x 1 root root 42592 Nov 2 11:27 libnvidia-opticalflow.so.455.38* lrwxrwxrwx 1 root root 29 Nov 15 07:25 libnvidia-ptxjitcompiler.so -> libnvidia-ptxjitcompiler.so.1* lrwxrwxrwx 1 root root 34 Nov 15 07:25 libnvidia-ptxjitcompiler.so.1 -> libnvidia-ptxjitcompiler.so.455.38* -rwxr-xr-x 1 root root 10475688 Nov 2 11:27 libnvidia-ptxjitcompiler.so.455.38* -rwxr-xr-x 1 root root 58569432 Nov 2 11:27 libnvidia-rtcore.so.455.38* -rwxr-xr-x 1 root root 14480 Nov 2 11:27 libnvidia-tls.so.455.38* lrwxrwxrwx 1 root root 31 Nov 15 07:25 libvdpau_nvidia.so -> vdpau/libvdpau_nvidia.so.455.38*

So if the driver number isn't reporting and the device isn't bound to VFIO, does that mean something is up with the kernel, and if so, how do I fix it?

nvidia-smi reports no device found, however here is the screenshot of devices As far as the driver number goes, I'm not sure why it isn't reporting.

Installed Beta 35 > rebooted > installed plugin > rebooted. I'm not seeing my Quadro P400 and it isn't listing my driver version. See below. What am I doing wrong here?

My mistake. Here it is. supervisord.log

Hey guys, I'm seriously loving this software, but after rebooting my machine this morning, I began to have issues. Right now I'm unable to access the web GUI and both Sonarr and Radarr aren't connecting either. Here is a portion of my log: 2020-11-13 15:33:25,644 DEBG 'watchdog-script' stdout output: [info] Deluge process started [info] Waiting for Deluge process to start listening on port 58846... 2020-11-13 15:33:25,986 DEBG 'watchdog-script' stdout output: [info] Deluge process listening on port 58846 2020-11-13 15:33:30,436 DEBG 'watchdog-script' stdout output: Setting "random_port" to: False Configuration value successfully updated. 2020-11-13 15:33:35,235 DEBG 'watchdog-script' stdout output: Setting "listen_ports" to: (32560, 32560) Configuration value successfully updated. 2020-11-13 15:33:40,132 DEBG 'watchdog-script' stdout output: [info] No torrents with state 'Error' found 2020-11-13 15:33:40,133 DEBG 'watchdog-script' stdout output: [info] Starting Deluge Web UI... 2020-11-13 15:33:40,133 DEBG 'watchdog-script' stdout output: [info] Deluge Web UI started 2020-11-13 15:33:40,132 DEBG 'watchdog-script' stdout output: [info] No torrents with state 'Error' found 2020-11-13 15:33:40,133 DEBG 'watchdog-script' stdout output: [info] Starting Deluge Web UI... 2020-11-13 15:33:40,133 DEBG 'watchdog-script' stdout output: [info] Deluge Web UI started I'm hoping someone has encountered this before and I've just simply overlooked something.

I'm seeing the correct output for my P400 but I'm still not able to get unraid nvidia to see my card VGA compatible controller: NVIDIA Corporation GP107GL [Quadro P400] (rev a1) Subsystem: NVIDIA Corporation GP107GL [Quadro P400] Kernel driver in use: nvidia Kernel modules: nvidia_drm, nvidia I'm completely stumped as to why this isn't working for me. I just updated my BIOS to no avail.

My system says legacy. Unfortunately my Dell R510 doesn't seem to play nice with unraid when running in UEFI mode. I do appreciate you thinking of me once you found your solution though. This potential solution confuses me, as unraid still recognizes the GPU under the PCI device list, and is available for passthrough to VMs. So it doesn't seem to me that it would be an issue with the BIOS of my server so much as unraid nvidia itself.

Updates are free after you've initially bought the license.

Given that it is a tainted kernel, I'm thinking that my next step is to replace the unraid nvidia installation of beta 30 with the stock OS and see if the plugin registers the GPU (which I don't expect it to) and then re-install the unraid nvidia kernel and see if that works.

As a follow up to this, I have attempted to downgrade to 6.8.3, but the unraid nvidia is still not seeing the GPU, however it is seeing my cache drive as an unassigned device. When I try to assign it, it comes up as a new drive, so I am going to reinstall (again) beta 30. This being said, I am able to assign the GPU for passthrough to my Win Server VM.

Hey everyone, All of a sudden I'm having issues with unRAID Nvidia not recognizing my GPU. I've got a Quadro P400 running in a Dell R510. I had the whole system running perfectly, and then all of a sudden, my plex installation crashed. After having to hard boot my system and a subsequent failure of plex to start, I narrowed the culprit down to the GPU. I disabled the additional arguments in the docker shell that allowed it to use the GPU for hardware accelerated transcoding and then began my troubleshooting. I moved the GPU into my desktop computer and it seemed to run just fine. I then plugged the GPU into the riser cable I had, and plugged that into my desktop - no go. Assuming I had found the issue, I ordered a new riser cable. It arrived today and so I eagerly shut down the server, plugged the riser cable and GPU in and booted the server. At this time, unRAID Nvidia does not recognize it however when I run the command "lspci | grep -i nvidia" my output is as follows: 03:00.0 VGA compatible controller: NVIDIA Corporation GP107GL [Quadro P400] (rev a1) 03:00.1 Audio device: NVIDIA Corporation GP107GL High Definition Audio Controller (rev a1) In the system log, I see this: Oct 21 18:58:01 PowerEdgeR510 kernel: NVRM: GPU 0000:03:00.0: RmInitAdapter failed! (0x31:0xffff:973) Oct 21 18:58:01 PowerEdgeR510 kernel: NVRM: GPU 0000:03:00.0: rm_init_adapter failed, device minor number 0 Any insight would be fantastic as I'm unsure of what to do next.

I did enter the encryption key, and it was still a no-go. In fact I even attempted to upload the keyfile to the /root/keyfile dir to try and bypass the GUI in case that was the issue. Of note though, I did have to upload the keyfile to that same directory in order to get the system to actually agree to encrypt the drives.

I've tried booting the system in safe mode to go try isolating the plugins in this issue, and even in safe mode the system won't start the array. I also tried uninstalling all my plugins with the exception of CA.