cammelspit

Every two or three days now after upgrading to 6.6 I get an unrecoverable lockup of my server. My pfSense VM is STILL FUNCTIONING so the machine hasn't locked up entirely when this happens but the unRAID UI is entirely non-responsive, all dockers are unresponsive, no shares of any kind are accessible and I am then forced to locally log into the server and reboot from the command line. My server has been up and going for months under the previous release. I read on Reddit some other people were having lockups that seem to be triggered by NFS shares so I have disabled NFS shares since I don't strictly need them, as a troubleshooting measure but it will be a couple days before I can tell if that really is the problem or not. I don't have access to the GUI when this happens so I can't pull any relevant logs, is there some form of extra logging I can turn on so I can try and get to the bottom of this? Also, what is the easiest way to downgrade back to 6.5.3? Seems 6.6 needs some more time in the oven. Sorry, I'm still learning here and am not super great with Linux so any help in figuring this out would be greatly appreciated. Any diagnostics or whatever I can do?

I too had issues with rclone on the newly updated 6.6. I started a transfer to my google drive and then the 6 cores I have used for unraid itself pinged to max CPU usage and the whole of unraid became unresponsive and was effectively locked. No web GUI, nothing. I ended up having to physically login on the server and restart from the CLI. When I came back and checked plugins page there was a third tab at the top listing plugin errors with rclone. I then uninstalled it entirely, rebooted the server, installed rclone, rebooted one last time and the errors were all gone. I didn't have the mind to take snapshots of it or anything at the time and when the server was locked, I didn't have access to any of the drives or anything. So for the moment, it seems a simple uninstall and reinstall is what it takes to fix rclone on a unRAID6.6 upgrade. though, I haven't started using it yet since then so I will add to this when that happens.

Beautiful, thanks! I just didn't want to set up my spare consumer router and not have my dockers up while it was working. I have a reverse proxy, remote access VM, a lot of things that don't use storage but DO need the array started anyways. This is perfect!

Ok, so I have previously been running two 4TTB drives without a parity. Yeah, I know my data is unsafe. I have that data on an offsite backup and none of it is mission critical anyways. This, however, is changing now that I can afford to toss three 8TB drives in there. So, the plan is to get those drives precleared and add two of them to the array and have one as a parity, finally putting my money where my mouth is and having proper data integrity. Anyways, so I see a lot about rebuilding replacement parity disks and such and it seems to imply that the array is started while building the parity. This is building a new parity and I do need the array to be started and functional while I do the parity build, is this the case? I ask only because I use a pfSense VM and dockers on my server that require the array to be started to function even though all of their data is only on the cache disk, a cheap 120GB SSD I had lying around left over from my main PC after an upgrade. I get the third 8TB drive in this Friday, my brother bought this drive as a donation to my server since he uses my Plex all the time. 😁👍 Pre-clearing is easy as heck while the array is functional since I just have to take the array down for literally 120ish seconds to add the drive to the array once that's done. I just haven't done a parity build before and no one outright states that the array is started and the data is accessible during the build process that I could find. No, I don't care if it's slower than molasses in a snowstorm going uphill as I won't be doing any of my months long file transfers till it's done building the parity so speed is not necessary, only the VMs and Dockers. Thanks in advance for setting my mind at ease.

Holy hell in a handbasket Batman! I now feel rather silly and I think you kindly for pointing out my silly syntax mistake! ?

Hi! I am trying to access my gdrive from this plugin and I am using spaceinvader's video as a rough guide. I am getting issues listing the directories as a test to make sure everything works. rclone lsd google 2018/08/27 12:01:50 ERROR : : error listing: directory not found 2018/08/27 12:01:50 Failed to lsd: directory not found I set the remote to have access to everything during setup, I believe this was option 1 at the point. Is this an issue with the plugin or the version the plugin is using or something with rclone itself. If this isn't the plugins fault, and to this point I am not sure, it would still be nice to get a quick hand figuring out what I am doing wrong. If I explicitly set a directory such as rclone ls google:Client Data Backup It does work and it lists the files as expected but I can't seem to LS or LSD the root. Should I try using the beta plugin instead? I may just be stupid here or I may be wasting your time with problems that I shouldn't be bringing to you but I am super new to Linux in general and this is my first time ever using rclone so I am not sure if the problem is me or not. If it is me then you can please just tell me to take a hike and I will, I promise. ?

I have booted into GUI mode once before for troubleshooting so I know this configuration should be working. I haven't done any upgrades to hardware or unRaid itself since then but now when I tried to boot into the unRaid GUI, all I get is a blank black screen on the server machine itself. Any ideas?

Done, thanks again! ?

Surely, not as much as I do! Thanks again all of you for the assist! EDIT: I actually get a 404 when hitting the donate button.

AAAAHHHH! I FIXED IT!!! WOOO! Alright, sorry, I'm so happy I could literally start running around in circles right now! So, here's what I did. After remembering I use the 'docker network create proxynet' command, I opened the terminal and tried just using 'docker network remove proxynet' but it errored and told me that it had active endpoints. I then recalled I could disable the 'preserver user-defined networks'. I disabled this in the docker settings of unRaid and then after re-enabling the Docker engine, I was finally able to remove this virbr0 entirely. From there, I just opened the Plex WebGUI like always and it instantly showed me the create new server stuff. Hell yes... Honestly, guys, I can not put into words how incredibly frustrating this has been for me over the last two days or so. I have also never gotten as good support before from such a knowledgeable group of people. With the powers of all of you together and a little bouncing of ideas off each other, we have fixed it. Where can I donate to the linuxserver.io? ???

The difference here is this virbr0 I made myself from the command line as part of the tutorial. I should be able to remove this specific network, shouldn't I? It is not part of the docker stuff by default.

I think you are on to something. First off, I originally set up this docker when the server was on the 10.10.10.0/24 subnet, same as my current machine so that's prolly why it worked. And with what @ijuarez and @Hoopster said, it seems that it is binding to some subnet with 192.168. subnet. Ok, so I was following Spaceinvader Ones's tut on nextcloud. In his tutorial, he has you make a new network, low and behold it is set to a 192.168. subnet! So this tells me plex is binding to Vibr0. I have since moved the server back to the 10.10.10.99/24 subnet so that shouldn't be an issue right now. However, in unraid, I can't use the GUI to remove virbr0 route. My issue now is I simply don't know the commands to remove it entirely. I decided after the fact that I didn't want to have any of my docker going through virbr0 since it made them inaccessible locally due to the way my network was set up. I COMPLTELY forgot about this too as I am not using it and sort of haven't thought about it in a bit. I would be willing to put money on this being the problem. Does someone know the commends to remove this virtual network?

Since you mentioned it is trying to use a subnet I simply am not using, is there a way to manually force Plex to use the subnet I am actually using? Would there be any kind of reason why it would be trying to force the wrong subnet in the first place?

I will do it right now and report back! EDIT: After backing up and deleting the docker.img and reinstalling the plex docker, same results. What I don't understand is how this is even possible? When I delete the /appdata/plex folder and have a brand new docker.img it should be as if Plex had never ever been installed in the first place... I simply don't understand how this is possible at all. It should be exactly as if I were starting up for the first time and allow me to setup a new server. ?

Yes, that was the first thing I tried. I have now done it maybe 40 times. That's not a typo, literally at least forty times. I appreciate the sanity check though. ?

I didn't know that using the /mnt/user/ could cause issues. I actually did try using /mnt/cache/ and I got all the same results. that's very interesting because I don't use 192.168.0.0 at all on my network. I actually use three subnets 10.10.10.0/24 which is my personal LAN, 10.10.20.0/24 which is reserved only for the roommates use through an AP, and then I have 10.10.30.0/24 which is a dedicated exclusively to the server itself and nothing else. This way NAT reflection work in pure NAT mode and I have a greater granularity of control where the traffic actually goes. The only time I used 192.168.0.0 was when I first set up my pfSense VM. My modem's access page is 192.168.100.1 and is unconfigurable though. As for the docker template config, I assume you mean what I have in the attached pic? I just don't know much about docker yet, learning every day, so I don't know if this is something specific you are asking for and I'm just too newb to know better. ? @everyone Honestly, I just don't know why using a fresh install of the docker will not allow me to start over. I don't even care about the metadata getting lost, I just want to rebuild it. I did go and test Binhex, LimeTech, and the official docker containers and all of those exhibited the same behavior, even though I have never had them installed before. So there is something that isn't getting wiped clean that is blocking me from starting a new server. Would a rebuild of my docker image be worth trying?

I believe this is what you were looking for? It was already on the cache drive but I moved it to another location anyway and no change. Also, yes, I am connecting directly to it via my local LAN. Plex Media Server.1.log

First, i can't get you the plex logs since there is no server anymore. I tried removing it because it was not showing up. Secondly, Here is the plex docker log. ErrorWarningSystemArrayLogin [s6-init] making user provided files available at /var/run/s6/etc...exited 0. [s6-init] ensuring user provided files have correct perms...exited 0. [fix-attrs.d] applying ownership & permissions fixes... [fix-attrs.d] done. [cont-init.d] executing container initialization scripts... [cont-init.d] 10-adduser: executing... ------------------------------------- _ () | | ___ _ __ | | / __| | | / \ | | \__ \ | | | () | |_| |___/ |_| \__/ Brought to you by linuxserver.io We gratefully accept donations at: https://www.linuxserver.io/donations/ ------------------------------------- GID/UID ------------------------------------- User uid: 99 User gid: 100 ------------------------------------- [cont-init.d] 10-adduser: exited 0. [cont-init.d] 30-dbus: executing... [cont-init.d] 30-dbus: exited 0. [cont-init.d] 40-chown-files: executing... [cont-init.d] 40-chown-files: exited 0. [cont-init.d] 50-plex-update: executing... ##################################################### # Login via the webui at http://<ip>:32400/web # # and restart the docker, because there was no # # preference file found, possibly first startup. # ##################################################### [cont-init.d] 50-plex-update: exited 0. [cont-init.d] done. [services.d] starting services Starting dbus-daemon Starting Plex Media Server. [services.d] done. dbus[270]: [system] org.freedesktop.DBus.Error.AccessDenied: Failed to set fd limit to 65536: Operation not permitted Starting Avahi daemon Found user 'avahi' (UID 106) and group 'avahi' (GID 107). Successfully dropped root privileges. avahi-daemon 0.6.32-rc starting up. No service file found in /etc/avahi/services. *** WARNING: Detected another IPv4 mDNS stack running on this host. This makes mDNS unreliable and is thus not recommended. *** *** WARNING: Detected another IPv6 mDNS stack running on this host. This makes mDNS unreliable and is thus not recommended. *** Joining mDNS multicast group on interface veth8d5e9d8.IPv6 with address fe80::c436:e2ff:fe7b:ba2f. New relevant interface veth8d5e9d8.IPv6 for mDNS. Joining mDNS multicast group on interface veth568ec71.IPv6 with address fe80::6485:42ff:fe8e:3d9c. New relevant interface veth568ec71.IPv6 for mDNS. Joining mDNS multicast group on interface br-0570f03b27d9.IPv6 with address fe80::42:87ff:fe2a:e7c4. New relevant interface br-0570f03b27d9.IPv6 for mDNS. Joining mDNS multicast group on interface br-0570f03b27d9.IPv4 with address 172.18.0.1. New relevant interface br-0570f03b27d9.IPv4 for mDNS. Joining mDNS multicast group on interface docker0.IPv6 with address fe80::42:e0ff:fe88:3e39. New relevant interface docker0.IPv6 for mDNS. Joining mDNS multicast group on interface docker0.IPv4 with address 172.17.0.1. New relevant interface docker0.IPv4 for mDNS. Joining mDNS multicast group on interface virbr0.IPv4 with address 192.168.122.1. New relevant interface virbr0.IPv4 for mDNS. Joining mDNS multicast group on interface br0.IPv6 with address fe80::304a:95ff:fe92:4a54. New relevant interface br0.IPv6 for mDNS. Joining mDNS multicast group on interface br0.IPv4 with address 10.10.30.99. New relevant interface br0.IPv4 for mDNS. Joining mDNS multicast group on interface bond0.IPv6 with address fe80::4216:7eff:fe29:a8e. New relevant interface bond0.IPv6 for mDNS. Network interface enumeration completed. Registering new address record for fe80::c436:e2ff:fe7b:ba2f on veth8d5e9d8.*. Registering new address record for fe80::6485:42ff:fe8e:3d9c on veth568ec71.*. Registering new address record for fe80::42:87ff:fe2a:e7c4 on br-0570f03b27d9.*. Registering new address record for 172.18.0.1 on br-0570f03b27d9.IPv4. Registering new address record for fe80::42:e0ff:fe88:3e39 on docker0.*. Registering new address record for 172.17.0.1 on docker0.IPv4. Registering new address record for 192.168.122.1 on virbr0.IPv4. Registering new address record for fe80::304a:95ff:fe92:4a54 on br0.*. Registering new address record for 10.10.30.99 on br0.IPv4. Registering new address record for fe80::4216:7eff:fe29:a8e on bond0.*. Server startup complete. Host name is ConnollyServer.local. Local service cookie is 1876232988. Error in command line:the argument for option '--serverUuid' should follow immediately after the equal sign Crash Uploader options (all are required): --directory arg Directory to scan for crash reports --serverUuid arg UUID of the server that crashed --userId arg User that owns this product --platform arg Platform string --url arg URL to upload to --help show help message --version arg Version of the product Thirdly, sorry, but I have no idea how to get the docker run command. I'm new to unRaid and Linux in general and have only been using it about a month. I am happy to get it for you if you tell me how. EDIT: Is this what you were looking for? root@localhost:# /usr/local/emhttp/plugins/dynamix.docker.manager/scripts/docker run -d --name='plex' --net='host' -e TZ="America/Phoenix" -e HOST_OS="unRAID" -e 'PUID'='99' -e 'PGID'='100' -e 'VERSION'='latest' -v '/mnt/user/':'/MyMedia':'rw' -v '/mnt/user/appdata/plex':'/config':'rw' 'linuxserver/plex' 292df6f677efbabc050e8bbdc385fb0a70d7f9fd3ff00d571baab54616dc714a

Can someone please help me. My plex disappeared. I know it may seem too little information but I am serious here. My server was unconnectable, I tried to reinstall the docker after I wiped the plex folder from the appdata and I literally can't do anything. I get no server tab. I tried going to the URl that tries to run setup again and I only get it asking for me to download and install one... Except I am already connected to my Plex! This is really Getting me down. I paid for a lifetime Plexpass and now it's gone and I simply can't get it working again! Thanks for any help you can give... Im kinda bummed right now as you can imagine. ?

Just bought 32GB of Hynix ECC for my unRaid server, 8GB just wasn't cutting it for VMs and dockers combined. Problem is, I installed them and in BIOS I see only 16GB and unRaid seems to think I have 32GB installed but only 15.882 GB is allocated. I know this may be a more general hardware issue here but I could really use a hand figuring out why. I tested sticks one at a time and they are being detected as 4GB each when they are 8GB DIMMS. I am using an AMD FX8350 on a Sabertooth V2. Here is the exact model of ram I got and a few pics of how unRaid sees them. it is literally just addressing half of the memory on each stick. I figured you guys here are much smarter than I am so you may have some insight that could help me here. Thanks in advance for any help you can provide.

+1 if for nothing but a much nicer and cleaner integration with password managers. Also, custom images would be an awesome thing.

+1 here too. IS this it though? Has there been no word if this is something LT might be interested in implementing? I have a few AMD and nVidia GPUs and I would love to be able to offload some of the work. My poor little FX8350 struggles on anything over 1080P if it even works at all. I guess the VM passthrough method would work but I only have 8 physical cores and no HT to work with so that's a bit of a stretch.

Hey, could someone help me out here for a minute? I can't seem to access the WebUI and none of my devices can see the server locally anymore. Somehow, Plex.tv/web sees my server but won't play anything. Any help would be appreciated. Below is the LOG. Sorry but I am SUPER noob at this so I don't really know what it is I am looking for. All I did was reboot the server for changing some ISOLCPU values as I am tinkering with optimizing my server recently. Any help is GREATLY appreciated! ErrorWarningSystemArrayLogin [s6-init] making user provided files available at /var/run/s6/etc...exited 0. [s6-init] ensuring user provided files have correct perms...exited 0. [fix-attrs.d] applying ownership & permissions fixes... [fix-attrs.d] done. [cont-init.d] executing container initialization scripts... [cont-init.d] 10-adduser: executing... ------------------------------------- _ () | | ___ _ __ | | / __| | | / \ | | \__ \ | | | () | |_| |___/ |_| \__/ Brought to you by linuxserver.io We gratefully accept donations at: https://www.linuxserver.io/donations/ ------------------------------------- GID/UID ------------------------------------- User uid: 99 User gid: 100 ------------------------------------- [cont-init.d] 10-adduser: exited 0. [cont-init.d] 30-dbus: executing... [cont-init.d] 30-dbus: exited 0. [cont-init.d] 40-chown-files: executing... [cont-init.d] 40-chown-files: exited 0. [cont-init.d] 50-plex-update: executing... No update required [cont-init.d] 50-plex-update: exited 0. [cont-init.d] done. [services.d] starting services Starting dbus-daemon Starting Plex Media Server. [services.d] done. dbus[276]: [system] org.freedesktop.DBus.Error.AccessDenied: Failed to set fd limit to 65536: Operation not permitted Starting Avahi daemon Found user 'avahi' (UID 106) and group 'avahi' (GID 107). Successfully dropped root privileges. avahi-daemon 0.6.32-rc starting up. No service file found in /etc/avahi/services. *** WARNING: Detected another IPv4 mDNS stack running on this host. This makes mDNS unreliable and is thus not recommended. *** *** WARNING: Detected another IPv6 mDNS stack running on this host. This makes mDNS unreliable and is thus not recommended. *** Joining mDNS multicast group on interface veth4fab562.IPv6 with address fe80::60bc:65ff:fea1:e428. New relevant interface veth4fab562.IPv6 for mDNS. Joining mDNS multicast group on interface virbr0.IPv4 with address 192.168.122.1. New relevant interface virbr0.IPv4 for mDNS. Joining mDNS multicast group on interface docker0.IPv6 with address fe80::42:11ff:fecd:bfac. New relevant interface docker0.IPv6 for mDNS. Joining mDNS multicast group on interface docker0.IPv4 with address 172.17.0.1. New relevant interface docker0.IPv4 for mDNS. Joining mDNS multicast group on interface br0.IPv6 with address fe80::3496:c3ff:feeb:c41b. New relevant interface br0.IPv6 for mDNS. Joining mDNS multicast group on interface br0.IPv4 with address 10.10.10.99. New relevant interface br0.IPv4 for mDNS. Joining mDNS multicast group on interface bond0.IPv6 with address fe80::4216:7eff:fe29:a8e. New relevant interface bond0.IPv6 for mDNS. Network interface enumeration completed. Registering new address record for fe80::60bc:65ff:fea1:e428 on veth4fab562.*. Registering new address record for 192.168.122.1 on virbr0.IPv4. Registering new address record for fe80::42:11ff:fecd:bfac on docker0.*. Registering new address record for 172.17.0.1 on docker0.IPv4. Registering new address record for fe80::3496:c3ff:feeb:c41b on br0.*. Registering new address record for 10.10.10.99 on br0.IPv4. Registering new address record for fe80::4216:7eff:fe29:a8e on bond0.*. Server startup complete. Host name is ConnollyServer.local. Local service cookie is 3155243906.

I just tested it and sure enough, it worked fine. No old router, no fiddling, just shut down my VM, shut down my dockers, shut down the array, start the array and everything just powered up fine even considering the pfSense instance was off and there was no internet at that moment. ?

I think I'll just try it and see, then the info on that will be available for everyone. I have to wait for my wife to finish work though, she works from home and overnight. I do want to know the real answer here but I will share that answer once I find out. Thanks for the quick reply though, I appreciate it.