bedpan

Thanks... No way to modify the config file without re-creating? I am sure I can figure out the paths.. I hope... I was not sure which thread to put it in.. The container thread, the getting fancy with Docker thread? Seems like it is not really related to either and more a how to fix stupid mistakes type thing.. Which in the end in my mind just pollutes the main threads with issues most people will not see.. Not arguing.. just explaining...

I clicked the show advanced switch in the Docker tab. I see several unnamed orphan images. I am not missing anything else... Here is the first one: (orphan image) Image ID: 9b60aa70ec67 linuxserver/plex:latest

I have been having some transcoding issue so I have been trying to clean things up a bit so the CPU cores are a little more defined. Anyways I found the Docker Thread Get Fancy with Docker and CPU Pinning.. So I updated my plex container with --cpuset=0,2,4,6 Missed that it should have been --cpuset-cpus I clicked apply. It did its thing and the docker restarted. Then it was gone. It no longer appears in my list of Dockers. Just gone! Its not running and not listed in the Docker list any more. Any thoughts? How do I go about finding the config file? Sorry guys.. I really don't know what I am doing. I pretend well though! I needs my plex!

Might be worth a new post but I am lost.. I updated my plex container with --cpuset=0,2,4,6 Missed that it should have been --cpuset-cpus So I clicked apply. It did its thing and the docker restarted. Then it was gone. It no longer appears in my list of Dockers. Just gone! Any thoughts? How do I go about finding the config file? Sorry guys.. I really don't know what I am doing. I pretend well though! I needs my plex! edit: I clicked advanced view and saw: (orphan image) Image ID: 9b60aa70ec67 linuxserver/plex:latest

Good call.. I have posted that I figured it out but your guess is on the right track.. PFSense was blocking Internet access due to a changed MAC address... I will update the OP so people don't need to waste more time.. Thanks for the reply! It's probably your browser/desktop. I've worked with unRaid while I was taking my LAN apart, as long as the master internal DNS was down, things took forever to access. but once it was up, everything was smooth sailing.

Please mark as resolved..... If in doubt go back to the basics. In my last post I stated that the internet is working. Bad assumption on my part. I did a ping test from UnRaid - no DNS, no traffic outbound through PFSense. I am nota PFSense expert so it took me awhile to find some logging and errors related to UnRaid. Further digging - I had a static IP on UnRaid and a reservation in PFSense. PFsense did not like that an device using the assigned IP address was coming from a unknown MAC on the new Motherboard. I had already blown out the Network config on UnRaid by the time I figured it out. Thanks to all those that took the time to read. This in the end is not an UnRaid issue but network related.. It appears that things are mostly good. Side note. UnRaid does not run well when the internet is not working apparently. Eveything lags and it takes a lot of time to navigate the screens. Cheers, Mike

Well break time for dinner and sports with the kids.. I think I might backtrack a little and attack a more describable problem as I am hopeful it is all related.Well that and I am lost... I cannot update my dockers - they all show as update ready (CP, Dolphin, DuckDNS, Plex, SAB, Sonarr). When I click the update bottom it goes to "Pulling Image" for about 30s or so then shows this: "Pulling image: linuxserver/couchpotato:latest TOTAL DATA PULLED: 0 B Error: Network timed out while trying to connect to https://index.docker.io/v1/repositories/linuxserver/couchpotato/images. You may want to check your internet connection or if you are behind a proxy." This is true of all the dockers with the same message.. The internet is working. I cannot see any filtering or blocking going on. I can access the server from other computers on the LAN. Its like unraid cannot hit the internet for some reason... Thoughts? Mike

Not making any progress. Realized I post just the logs and not the diags so attaching those now. Trying to figure out what the 'Registering new address record for 192.168.122.1 on virbr0.IPv4.' is why its coming up... More reading... Thanks for reading, Mike

THIS IS RESOLVED... I have documented in a later posts but in short PFSense was blocking internet to UnRaid due to the MAC address change. It was messing with me as my VM still had internet access as well as full LAN access.. I missed it. I forgot the basics of trouble shooting.. ________________ Will do my best to describe my issues. I am not entirely sure I understand what is happening right now though so feel free to ask questions. Was running 6.2.3 just upgraded to 6.2.4. I have Dockers and Windows VM. I replaced the Motherboard, CPU and RAM on the weekend. Everything went well and seemed to be working. Today I tried to access my plex docker via the internet and the server is missing. I remoted into VM and attempted to access the server and I could see Plex via local lan, but not via the internet. I have PFSense running and it was my first suspect. Plex is reporting that under network that is is accessible via the internet on the local admin page. Now I screwed up though. At one point it I tried to connect to plex and I selected to delete the server. I clicked ok. Now I cannot see the server at all locally or remotely. I cannot seem to find a way to re-register the server again within Plex. Any guess as to how to do this? The docker is still running just not registered with Plex I believe the overall issues is related to a change in network interfaces. I see in the plex docker log that is registering on some unknown IP's Registering new address record for 192.168.122.1 on virbr0.IPv4. Registering new address record for 172.17.0.1 on docker0.IPv4. Registering new address record for 192.168.1.3 on br0.IPv4. UnRaid is running on 192.168.1.3. The others are not used. I thought I better ask before I monkey with the network settings and wreck any more. A few other things I have noticed: Dockers will not update I am getting a Network timed out while trying to connect error Navigation seems slow moving between tabs in the Unraid manager Many many many thanks in advance for any direction, advice or questions that lead me in the right direction... Below is the PLEX Log and I have also attached the unraid logs. -------------------------------------------- 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 do 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... Atempting to upgrade to: wget: unable to resolve host address 'downloads.plex.tv' ######################################################## # Upgrade attempt failed, this could be because either # # plex update site is down, local network issues, or # # you were trying to get a version that simply doesn't # # exist, check over the VERSION variable thoroughly & # # correct it or try again later. # ######################################################## [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. 6 3000 /config/Library/Application Support d dbus[283]: [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. *** socket() failed: Address family not supported by protocol Failed to create IPv6 socket, proceeding in IPv4 only mode socket() failed: Address family not supported by protocol 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.IPv4 with address 172.17.0.1. New relevant interface docker0.IPv4 for mDNS. Joining mDNS multicast group on interface br0.IPv4 with address 192.168.1.3. New relevant interface br0.IPv4 for mDNS. Network interface enumeration completed. Registering new address record for 192.168.122.1 on virbr0.IPv4. Registering new address record for 172.17.0.1 on docker0.IPv4. Registering new address record for 192.168.1.3 on br0.IPv4. Server startup complete. Host name is tower.local. Local service cookie is 1416527172. tower-syslog-20161115-1352.zip

Thanks folks... It was what I was hoping to hear... I appreciate you taking the time to reply! Onto new issues (Docker issues!) and a new post. Mike

Anyone able to comment on speed/performance of the H310 vs the Intel X79 Sata ports? Thanks!

Hey folks, Wondering if some of you smart peoples can lend me some direction..... I just swapped out the my motherboard/CPU/RAM to a new board - an Asus X79-Deluxe with an i7. Previous board was doing ok but the opportunity was had so I took it. Previous board only had 6 SATA ports so I added in a a Dell Perc H310 reprogrammed etc to get the ports I needed. Now with the new board I has 12 available SATA ports (+2 ESata) Intel® X79 chipset : 2 x SATA 6Gb/s port(s), black 4 x SATA 3Gb/s port(s), black Support Raid 0, 1, 5, 10 Marvell® PCIe 9230 controller : 4 x SATA 6Gb/s port(s), dark brown ASMedia® ASM1061 controller : 2 x SATA 6Gb/s port(s), dark brown 2 x Power eSATA 6Gb/s port(s), green Now the question... I have 8 HD's + 1 SSD connected. Right now the 8 HD's are connected to the H310 and the SSD connected to the X79 port. Performance wise how would the H310 compare to the Onboard sata ports? Am I better use one the other or a mixture of both? Usage wise I am running several dockers, and a windows VM. The array contains 7 HD's, 1 is left out and used as a Data drive for the Windows VM to write out Video surveillance. Any input thought or questions are appreciated! Many thanks! Mike

Getting the same thing.. Joe. L's works fine as suggested. Not all the options your building in though. Any idea? Looks like it running ok in the status on the pluggin, just the popup windows does not display the working stats.

Crashplan works great.. No issues there... What OS are you running on the laptops? If windows the Windows Offline files is probably all you need for syncing. Depends on your goal I guess though.

Thats to bad. I am surprised they would even report it if its of no value. I would have thought it was a virtualized sector ID based on the amalgamation of all the drives. Oh well. Again not the end of the world. I lose a little trust though when we cannot id the cause and effect of this type of issues. Many many thanks all! Mike

Thanks Frank... Based on your write up I have one questionable disk. I will roll the dice for a little bit until I can find some 4TB's on sale. I asked earlier but will throw it out there again. Based on the logs and the sector id? Logs are: May 1 03:30:31 tower kernel: md: correcting parity, sector=1915648 Any way to translate that to a file? Many thanks to all! Mike

Will move on and hope not to many things are messed up :-) Based on the logs and the sector count any way to figure out what files occupy those sectors? unRAID Parity check: 04-05-2016 20:39 Notice [TOWER] - Parity check finished (0 errors) Duration: 13 hours, 7 minutes, 1 second. Average speed: 84.7 MB/s

That might explain it Frank. I did have a improper shutdown at one point during all this. Was trying to take the array offline and it hung. No response anywhere so it was power cycled and parity checked... Time wise it is probably related as well.

To be honest no.. I just setup the alerts a couple days ago as well. I did not notice any errors during the parity check with the new 4TB. Only the new error message with the rebuild. I will wait it out and see how the parity check goes. Again its not the end of the world. I just don't like mysteries ;-) Estimated speed: 105.5 MB/sec Estimated finish: 8 hours, 39 minutes Not to much longer! Again many many thanks for the assistance.

Awesome Johnnie. I appreciate you taking the time breaking this out for me... Gives me some legs to understand what is going on. Any thoughts as to why the email saying I got the errors after the rebuild?

Ok... I newb question... Where are you looking to see the errors? I am reading through the log files and not seeing much that helps me. I am interested in learning to be a little more self sufficient. I have email alerts setup and here is the message I got last night: Event: unRAID Data rebuild: Subject: Notice [TOWER] - Data rebuild: finished (146 errors) Description: Duration: unavailable (no parity-check entries logged) Importance: warning Cheers, Mike

I was hesitant to start a parity check. I was thinking maybe I could revert back to the old disk or something. Oh well.. Parity check started - I am fairly new to Unraid.... thanks! Mike

Hey Folks... I have been doing some work on the server the last few days. I was on the last step until I get some new disks and I had some errors. Wondering if this is life threatening or if I can just ignore it - Ignorance is bliss! Here is what lead me to today.. Array consists of a bunch or 2tb drives. One of the data drives has Relocate sector count of 2. Its been like that for sometime so I was not to worried about it but was gearing towards a replacement. A week or so ago another 2tb data drive failed. I was able to swap in a replacement and rebuilt without a problem. A couple days ago I added a 4TB drive to the array - precleared it then swapped it in as my parity. I left the orginal 2tb parity drive in but unassigned. Yesterday I removed the drive with the relocate errors out of the array and put the old parity drive in its place. During this rebuild is when I got 146 errors. Any thoughts on the matter? Its all just media that can be replaced and backups from desktops that are further backed up to offsite locations. It would suck to loose the media but not the end of the world. Hence my lack of worry. Before I swap any more drives I though I should try and figure this out though.. Attaching logs for reference sake... Many thanks in advance!!!! Mike tower-diagnostics-20160504-0653-anon.zip

Thanks for the replies.. I am out of my league as well.. Part of why I am asking. I was under the impression that the memory like the CPU would pinned to the VM and not available to the Host. I would rather the VM die then UnRaid crash but it seems strange that they would not have other mechanisms in place in unraid to provide for high memory usage. In the ideal world I would just add a pile of memory to the server but I have been having some slot issues that make me nervous to put any money into this board. With the Canadian Dollar as it is, upgrading CPU and/or Board is just not an option I don't think.

You are correct. 12GB total ram - 6GB for VM, 6GB remaining. When I actually witnessed, UnRaid was showing 6.5-7GB usage. What happens in a low memory machine running UnRaid only. For example if I had 4GB ram and was running the dockers mentioned above. Does UnRaid not do any swapping of any sort? Does it just crash if it runs out of memory?