• Posts

  • Joined

  • Last visited

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

glompy's Achievements


Newbie (1/14)



  1. I now get incompatible client, please use 1.17, but I am using the 1.17.1 client. Is there a way to force the server to use 1.17.1 instead of defaulting to the older 1.17.0 version? Restarting the container and it still picks up the old version.
  2. Unfortunately this issue came back randomly several weeks ago. So I tried upgrading to 6.9 did not solve the issue. Looks like something else is loading kernel drivers that is breaking this on some windows machines. Unload modules in Dynamix system settings plugin just "happened" to refresh the kernel and fix it, but as soon as the server restarts it comes back. I'm at a loss.
  3. It lagged, constantly buffered. I even tried to set one of the miner settings with intensity, even setting it to the lowest, it would till use about 75% of my GPU for mining, and that wasn't enough for plex. It would take 2 years (600+days) for my GPU to get enough crypto to even hit the payout threshold of any of the pools, and plex is more important to me. So I just abandoned this idea alltogether. Guess there is a reason why asic's and asic controllers exist
  4. How do you configure it to leave some GPU for Plex to transcode?
  5. I had this issue too!!!!!!!!!!!!!!! Been an issue for months, and even had an issue where one of my windows machines would always crash Explorer.exe whenever navigating to an unraid share (but not the other two windows 10 machines in the house, oddly enough). I was able to solve it by clicking Unload Drivers in the Dynamix system settings plugin. I did not have to uninstall the plugin, just unload the kernel modules. Did not have to reinstall unraid or anything else. Fixed my issue with my windows 10 machine causing explorer to crash with not responding. Also fixed the smbus is busy spamming the syslogs like crazy. THANK YOU FOR THIS POST!
  6. I only have a single parity disk. How does the parity information know that the disks have changed #'s? I figured a full parity rebuild would be required at some point so I wouldn't mind that if required.
  7. When I first started my unRaid system, I just started plugging in drives willy nilly. But now my OCD has kicked in and I would really like to have the disks have some meaning. So Disk1-5 will always be for my personal files share (these disks are PRO level drives, very reliable), and Disk 6-24 will be for Media share (random seagates, etc, expecting failures on any one of these within a year type of thing). When I set these up though, my Pro drive is 3, 6, and 12, 13, 14. I really want these to be Disk 1, 2, 3, 4, 5. When I stopped my array and attempted to change the Disks around inside of unraid, it gave me a warning that the disk didn't match parity, and it would rebuild the disk based on parity! This scared me so I stopped. Do I have to forever live with my disks being labeled as 3,6,12,13,14 in unraid? Also, is there any plugin that lets me "map" my disks, like I have a 24 JBOD server, I would really like to say "Disk 1 = this physical slot on my server on a map". ( found this plugin, looks exactly what I had imagined.
  8. Another interesting note, the MakeMKV instance started by root has a beautiful solid white background, and the one started by nobody has a ugly murky background.
  9. Okay I found out the issue. /home/nobody/ needs to be executed as root. When started as the user nobody, it cannot read the usb devices. I removed and re-added the container, so I knew I was starting out fresh. I would always run my script by going into the uNraid docker tab, and clicking Console for MakeMKV, I never used the terminal built-in. So I just so happened to be running as root. Now that I launched a couple with root, they can read usb, I launched a new one as the nobody user (right click on the background and click Launch MakeMKV on xfce), and that new instance cannot read the usb devices.
  10. I have fiber with google nest router, I've never had an issue with it, but I wouldn't know how to go about testing if google is actively doing something there. That said, I do have VPN connections for work that I leave up all the time and those do not get terminated, so unless they are actively dropping connections to known PIA servers? However I figured they would have done that with the socks5 proxy too. In any case, I signed up for another VPN provider... and it is night and day difference already, port forwarding took a minute to set up, but already getting double the bandwidth though the torrents. Its only been up for 2 hours, but I will be watching it. It will be much nicer to have dedicated ports as well now, so I'm probably just going to stick with it. Still getting the occasional ruTorrent timeout, logs mentioned earlier, on localhost:5000 (netdata reports cpu usage for the container never goes above 4% in the last 24 hours), so I stopped navigating to the built-in ruTorrent and installed a flood-ui container to access rTorrent. ruTorrent still times out and is not usable, but flood continues to work just fine. Not quite sure how to debug that. Edit:: Not a single disconnect in over a day. Looks like I will be dropping PIA like a hot rock and staying with this new vpn provider when it comes to torrents
  11. I switched to switzerland, and the port didn't reset for almost 24 hours, and then it reset 10 times in the last 3 hours. I think I will be looking for a VPN that has static port forwarding, as dealing with PIA and dynamic ports is just too brittle for my taste. Thanks again!
  12. Just to clarify, using the latest docker (from ~19 days ago as the timestamp of this post), I still had to open the docker console and install usbutils with pacman, it didn't seem to "take hold" when installed from the existing script. For now I don't mind, since I have three usb dvd readers, I have to open the console and launch extra instances of makemkv using anytime I restart the container anyways, so I just made this quick script to do it and placed it in the mounted /config directory. #!/bin/sh pacman -S --noconfirm usbutils pkill makemkv /home/nobody/ & /home/nobody/ & /home/nobody/ &
  13. I was also having issues with my usb blu ray reader, using the :latest docker container tag. I can confirm that this fix also works for me, MakeMKV can now see the usb device and read from it.
  14. That was just the first time it happened after restarting the container with debug. Seems to be worse in the evening around 10pm central. It was definitely happening every 10 minutes last night, if it was useful I can wait until tonight and it should do it again at that frequency as this has been an issue for me for over 2 weeks. Instead I will go ahead and switch to another endpoint and monitor for stability. What I take away from your statement is this is a PIA issue and not an issue with the container, and so maybe I should look into another VPN provider if another endpoint proves unstable still? Also I looked up my old settings on my windows box, and I was running it through the PIA socks5 proxy, but NOT the PIA vpn directly, so the socks5 proxy never had port forwarding/closing issues, I was incorrect in saying the vpn didn't randomly close my ports on my windows box, so this is the first time I am actually trying to use the vpn full stream with torrents.