Scroopy Noopers
-
Posts
28 -
Joined
-
Last visited
Content Type
Profiles
Forums
Downloads
Store
Gallery
Bug Reports
Documentation
Landing
Posts posted by Scroopy Noopers
-
-
Well it's definitely been more than 3 days at this time, but that seems to have fixed my issue. Thanks a bunch.
-
1
-
-
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.
-
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.
-
On 11/17/2020 at 7:08 PM, Scroopy Noopers said:
That's what I'm seeing too. I have no idea where to go from here.
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.
-
1 hour ago, strike said:
Then I'm afraid I have no clue, your log seems fine.
That's what I'm seeing too. I have no idea where to go from here.
-
5 minutes ago, strike said:
What do you have as the network type? It should be bridge, br0 or any other custom bridge network won't work.
It's set to bridge.
-
4 hours ago, chesh said:
Is your LAN subnet 192.168.2.0/24?
It sure is
-
On 11/13/2020 at 4:45 PM, Scroopy Noopers said:
My mistake. Here it 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.
-
11 minutes ago, wgstarks said:
That doesn’t show any problem. You should attach the supervisord.log to your next post.
My mistake. Here it is.
-
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 startedI'm hoping someone has encountered this before and I've just simply overlooked something.
-
On 11/7/2020 at 3:37 AM, bytchslappa said:
The drivers in 6.8.3 will work fine with the 1050ti (i use one myself) - the drivers in 6.9.0 beta30 are better for current builds of Plex (if that is the use case)
from terminal run lspci -k this will show the devices found - for example a 1050ti might come up like this in the list:
01:00.0 VGA compatible controller: NVIDIA Corporation GP107 [GeForce GTX 1050 Ti] (rev a1)
Subsystem: Micro-Star International Co., Ltd. [MSI] GP107 [GeForce GTX 1050 Ti]
Kernel driver in use: nvidia
Kernel modules: nvidia_drm, nvidia
If its not showing - either the card itself could be busted - the card might need a monitor or dummy hdmi installed - or the other I have seen that its not actually a 1050ti - but some wish/aliexpress/dodgy ebay special thats not actually a 1050ti
oh and make sure you are not booting into GUI mode either
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, nvidiaI'm completely stumped as to why this isn't working for me. I just updated my BIOS to no avail.
-
8 hours ago, Jarsky said:
I finally figured out my issue.
You might want to check if you're booting UnRAID in UEFI or BIOS...you can check this in UnRAID GUI going to Main > Boot Device (Flash) > scroll down bottom to Server Boot Mode.
If it say's UEFI, try booting to your BIOS and change the Boot Priority to USB: <Device Name> instead of UEFI: <Device Name>
After Reboot, check the Server Boot Mode now says "Legacy".
See if the GPU works now.
Turned out when I updated my server, I set my boot priority to UEFI by mistake.
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.
-
Just now, galego100 said:
But if update to the recent version i have to buy a new unraid licence!!!
Updates are free after you've initially bought the license.
-
19 hours ago, Jarsky said:
I know but just pointing out there may be a larger Linux kernel issue thats affecting Scroopy, given that mine recently stopped working with the same issue.
Mines been working in that setup for a year, and it just stopped working for no reason in the last week...only thing i'd changed up to that point was regular UnRAID and Ubuntu upgrades. The only thing that I can find that appears relevant is entries that say 'tainted kernel'
e.g
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.
-
On 10/21/2020 at 7:06 PM, Scroopy Noopers said:
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 0Any insight would be fantastic as I'm unsure of what to do next.
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 0Any 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.
-
3 minutes ago, trurl said:
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.
-
Hello everyone,
I'm having an issue with starting my array. I recently encrypted 3 of my drives and installed a Quadro P400 card. Now after rebooting, I am unable to start my array. It continues to tell me that it is missing the key. Upon inspection in the log, i see the following line "error: root: /update.php: missing csrf_token".
I have tried booting the machine in safe mode to no avail. As well, following any advice I could find, I restarted my phone and shut down my laptop (the only two other devices to access the server). I would really love some assistance at this point as I have no idea what to do. I've attached the syslog.
oh and make sure you are not booting into GUI mode either
[Support] binhex - DelugeVPN
in Docker Containers
Posted
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.