biiiink

im running xfs_repair right now. i dont quite remember what the error was, but googling it let me to information saying the drive was failing. Replacing the drive wasn't such a big deal as I have a few spares kicking around.

I just built a new Unraid server. Moved all the drives from the old server to the new one. I used the unbalance plugin to move files around so I could convert the file system to XFS. When that was all complete, I had an error on disk 3, so I replaced it and rebuilt it. Now, my Media share shows as empty: However, if I check the individual disks, they all show the data from the Media share: I see an error in the log file: Dec 30 15:05:33 Tower kernel: XFS (md3): metadata I/O error in "xfs_trans_read_buf_map" at daddr 0x156c69f68 len 32 error 117 Dec 30 15:05:33 Tower kernel: XFS (md3): xfs_imap_to_bp: xfs_trans_read_buf() returned error -117. Dec 30 15:05:33 Tower kernel: XFS (md3): Metadata corruption detected at xfs_buf_ioend+0x4c/0x95 [xfs], xfs_inode block 0x156c69f68 xfs_inode_buf_verify Dec 30 15:05:33 Tower kernel: XFS (md3): Unmount and run xfs_repair Dec 30 15:05:33 Tower kernel: XFS (md3): First 128 bytes of corrupted metadata buffer: Dec 30 15:05:33 Tower kernel: 00000000b764e26b: be fa cc 07 c4 c8 71 c1 d6 3e 51 3e a0 cb af dc ......q..>Q>.... Dec 30 15:05:33 Tower kernel: 00000000ee47918b: d1 56 aa 91 0b c1 90 9f 95 2f af 7d 54 ee d1 a9 .V......./.}T... Dec 30 15:05:33 Tower kernel: 000000003f63270c: 1d 5d 78 9e 52 83 f6 b8 30 a5 de 46 6c 4d 1e f3 .]x.R...0..FlM.. Dec 30 15:05:33 Tower kernel: 00000000dcf7f7c5: 2a 1d 6a 11 a3 33 f4 1a 4f cf bd 60 8c 3b 09 e6 *.j..3..O..`.;.. Dec 30 15:05:33 Tower kernel: 000000009db33fd9: d4 38 5a e6 42 bf bf 8b 10 25 73 6a f1 58 5a f5 .8Z.B....%sj.XZ. Dec 30 15:05:33 Tower kernel: 000000002d170146: 93 98 cb 16 97 71 05 c2 a0 08 32 6b 5a 4e ab 26 .....q....2kZN.& Dec 30 15:05:33 Tower kernel: 00000000b756f334: 4e 32 80 f0 e3 72 0a 79 b8 0d 1a 64 68 c6 95 70 N2...r.y...dh..p Dec 30 15:05:33 Tower kernel: 00000000a507f273: 82 bb 13 a9 e6 a8 de 65 f7 b2 8f 14 6e 55 f4 ad .......e....nU.. I have attached my diagnostics files: tower-diagnostics-20181230-1506.zip Any help would be greatly appreciated

Any idea why it would work on my Mac Mini behind my router, but not on Unraid?

So I tried installing PMS of my Mac Mini and it works behind my own router. So now I assume it doesn't have something to do with my router. Maybe something in my unraid setup?

I've looked through all the settings in the router. I dont see anything referring to IP spoofing. I've also already tried turning off the firewall completely and it does not fix the issue

So I am still having this issue. It's been over 2 months now Im pretty sure it is related to my router. I have a router provided by my ISP connected to an ASUS RT-AC86U that I just got today because my old router died on me. I temporarily plugged my Unraid server into the ISP's router, and plex was able to find the media server. But once i put the new router in the network, the problem came back. and the logs in Unraid are identical. I have re-run through this support page again: https://support.plex.tv/articles/204604227-why-can-t-the-plex-app-find-or-connect-to-my-plex-media-server/ The Docker is up to date and running there is no VPN or Proxies running on the router or Unraid I've also tried temporarily disabling the firewall on the new router with no success. So I'm sure it is a setting on the Asus router, but I have no clue what it could be. Any help would be greatly appreciated

UPDATE: My router running DD-WRT died on me this morning. I temporarily plugged everything in to my ISP's router, and checked to see if plex could find the server and it did. I went out and bought an Asus RT-AC86U. Configured it, and its now back to the same issue. The log is identical regardless of the router setup being used Created by... ___. .__ .__ \_ |__ |__| ____ | |__ ____ ___ ___ | __ \| |/ \| | \_/ __ \\ \/ / | \_\ \ | | \ Y \ ___/ > < |___ /__|___| /___| /\___ >__/\_ \ \/ \/ \/ \/ \/ https://hub.docker.com/u/binhex/ 2018-06-28 12:47:16.478725 [info] Host is running unRAID 2018-06-28 12:47:16.515124 [info] System information Linux Titania 4.14.49-unRAID #1 SMP Mon Jun 11 16:21:07 PDT 2018 x86_64 GNU/Linux 2018-06-28 12:47:16.584084 [info] PUID defined as '99' 2018-06-28 12:47:16.631235 [info] PGID defined as '100' 2018-06-28 12:47:16.793320 [info] UMASK defined as '000' 2018-06-28 12:47:16.835369 [info] Permissions already set for volume mappings 2018-06-28 12:47:16.876573 [info] TRANS_DIR defined as '/config/transcode' 2018-06-28 12:47:17.217636 [info] Starting Supervisor... 2018-06-28 12:47:17,588 INFO Included extra file "/etc/supervisor/conf.d/plexmediaserver.conf" during parsing 2018-06-28 12:47:17,588 INFO Set uid to user 0 succeeded 2018-06-28 12:47:17,593 INFO supervisord started with pid 7 2018-06-28 12:47:18,595 INFO spawned: 'plexmediaserver' with pid 47 2018-06-28 12:47:18,595 INFO reaped unknown pid 8 2018-06-28 12:47:19,611 INFO success: plexmediaserver entered RUNNING state, process has stayed up for > than 1 seconds (startsecs) I have re-run through this support page again: https://support.plex.tv/articles/204604227-why-can-t-the-plex-app-find-or-connect-to-my-plex-media-server/ The Docker is up to date and running there is no VPN or Proxies running on the router or Unraid I've also tried temporarily disabling the firewall on the new router with no success. So I'm sure it is a setting on the Asus router, but I have no clue what it could be. Any help would be greatly appreciated

Any idea what might be happening?

I have a router provided from my ISP, in DMZ, and behind it is my own router running DD-WRT. I have had the router running DD-WRT for years, but I have recently changed ISPs. I did also have the previous ISPs router in DMZ mode as well For the record, I did try temporarily turning off the firewall in DD-WRT, but that did not work

I've tried this a bunch of times already and It still wont find the server Just did it again and here is the screenshot Still not finding the server

It's been over a month now, and I have tried everything I can find on the internet with no solution. I would really appreciate some help

Nope. Still the same issue.

I actually do. I just deleted it and re added it. Here is the correct screenshot

I have attached the run command

Yes I have. The server is not listed in the Devices, but the page does not explain how to add a server. I've gone through everything else on that page multiple times and nothing fixes the issue

Is anyone able to help me with this issue at all? its been over a month now and it is getting very frustrating. I've gone as far as completely reinstalling Unraid with no luck. I would really appreciate some support

Any more help with my issue would be greatly appreciated Thanks

I tried your solution, but it did not work for me, and my transcode location is already set to /config/transcode Any more help with my issue would be greatly appreciated

Anyone able to help me with my issue?

I have a Preferences.xml file in /mnt/user/appdata/plex/Library/Application Support/Plex Media Server

Yes. I just did it again. I restarted the Docker, opened the WebUI, logged out, Restarted the docker, opened the WebUI, logged in, restarted the Docker. The message you referred to comes up every time. Although I noticed that the last time I restarted, the log looked different: ------------------------------------- _ () | | ___ _ __ | | / __| | | / \ | | \__ \ | | | () | |_| |___/ |_| \__/ 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 # # plex token found in the preference file # ##################################################### [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[274]: [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 vethdd568c3.IPv6 with address fe80::4c23:22ff:feda:9e2b. New relevant interface vethdd568c3.IPv6 for mDNS. Joining mDNS multicast group on interface vethfe169a7.IPv6 with address fe80::6883:1bff:fe32:bc4b. New relevant interface vethfe169a7.IPv6 for mDNS. Joining mDNS multicast group on interface veth1470a2b.IPv6 with address fe80::90f9:acff:fec8:8263. New relevant interface veth1470a2b.IPv6 for mDNS. Joining mDNS multicast group on interface docker0.IPv6 with address fe80::42:48ff:fe16:8974. 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::ba:e1ff:fe91:340d. New relevant interface br0.IPv6 for mDNS. Joining mDNS multicast group on interface br0.IPv4 with address 13.13.13.2. New relevant interface br0.IPv4 for mDNS. Joining mDNS multicast group on interface bond0.IPv6 with address fe80::92e6:baff:fe2e:d6c9. New relevant interface bond0.IPv6 for mDNS. Network interface enumeration completed. Registering new address record for fe80::4c23:22ff:feda:9e2b on vethdd568c3.*. Registering new address record for fe80::6883:1bff:fe32:bc4b on vethfe169a7.*. Registering new address record for fe80::90f9:acff:fec8:8263 on veth1470a2b.*. Registering new address record for fe80::42:48ff:fe16:8974 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::ba:e1ff:fe91:340d on br0.*. Registering new address record for 13.13.13.2 on br0.IPv4. Registering new address record for fe80::92e6:baff:fe2e:d6c9 on bond0.*. Server startup complete. Host name is Titania.local. Local service cookie is 2159768972. Server startup complete. Host name is Titania.local. Local service cookie is 2159768972.

Yes. I've restarted the Docker multiple times

Any help with my issue would be appreciated

I am also having an issue with Plex finding the Server I was having issues with Plex, and decided to reinstall. I deleted the Plex docker and deleted the plex folder in the appdata folder. Reinstalled the plex docker and that is when the issue started. I've tried the other plex dockers with the same issue. I've also tried deleting and recreating the docker img file, but I still get the same issue. Here is my plex log: Created by... ___. .__ .__ \_ |__ |__| ____ | |__ ____ ___ ___ | __ \| |/ \| | \_/ __ \\ \/ / | \_\ \ | | \ Y \ ___/ > < |___ /__|___| /___| /\___ >__/\_ \ \/ \/ \/ \/ \/ https://hub.docker.com/u/binhex/ 2018-04-20 13:44:07.432159 [info] Host is running unRAID 2018-04-20 13:44:07.466480 [info] System information Linux Titania 4.14.26-unRAID #1 SMP PREEMPT Mon Mar 12 16:21:20 PDT 2018 x86_64 GNU/Linux 2018-04-20 13:44:07.504057 [info] PUID defined as '99' 2018-04-20 13:44:08.145981 [info] PGID defined as '100' 2018-04-20 13:44:08.892164 [info] UMASK defined as '000' 2018-04-20 13:44:08.934091 [info] Setting permissions recursively on volume mappings... 2018-04-20 13:44:08.982979 [info] TRANS_DIR defined as '/config/transcode' 2018-04-20 13:44:09.232266 [info] Starting Supervisor... 2018-04-20 13:44:09,448 INFO Included extra file "/etc/supervisor/conf.d/plexmediaserver.conf" during parsing 2018-04-20 13:44:09,448 INFO Set uid to user 0 succeeded 2018-04-20 13:44:09,451 INFO supervisord started with pid 7 2018-04-20 13:44:10,452 INFO spawned: 'plexmediaserver' with pid 54 2018-04-20 13:44:10,453 INFO reaped unknown pid 8 2018-04-20 13:44:11,454 INFO success: plexmediaserver entered RUNNING state, process has stayed up for > than 1 seconds (startsecs) 2018-04-20 13:44:12,776 DEBG 'plexmediaserver' stderr output: Error in command line:the argument for option '--serverUuid' should follow immediately after the equal sign Crash Uploader options (all are required): --directory arg 2018-04-20 13:44:12,777 DEBG 'plexmediaserver' stderr output: 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 2018-04-22 16:54:35,149 WARN received SIGTERM indicating exit request 2018-04-22 16:54:35,167 DEBG killing plexmediaserver (pid 54) with signal SIGTERM 2018-04-22 16:54:35,168 INFO waiting for plexmediaserver to die 2018-04-22 16:54:36,033 DEBG 'plexmediaserver' stdout output: Critical: libusb_init failed 2018-04-22 16:54:36,436 DEBG fd 8 closed, stopped monitoring <POutputDispatcher at 22959731758000 for <Subprocess at 22959731757784 with name plexmediaserver in state STOPPING> (stdout)> 2018-04-22 16:54:36,437 DEBG fd 10 closed, stopped monitoring <POutputDispatcher at 22959731736016 for <Subprocess at 22959731757784 with name plexmediaserver in state STOPPING> (stderr)> 2018-04-22 16:54:36,437 INFO stopped: plexmediaserver (exit status 0) 2018-04-22 16:54:36,437 DEBG received SIGCLD indicating a child quit Any Help would be greatly appreciated. Thanks

I seem to be having an issue with Plex not finding the server I was having issues with Plex, and decided to reinstall. I deleted the Plex docker and deleted the plex folder in the appdata folder. Reinstalled the plex docker and that is when the issue started. I've tried the other plex dockers with the same issue. I've also tried deleting and recreating the docker img file, but I still get the same issue. Here is my plex log: [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 # # plex token found in the preference file # ##################################################### [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[271]: [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 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::ba:e1ff:fe91:340d. New relevant interface br0.IPv6 for mDNS. Joining mDNS multicast group on interface br0.IPv4 with address 13.13.13.2. New relevant interface br0.IPv4 for mDNS. Joining mDNS multicast group on interface bond0.IPv6 with address fe80::92e6:baff:fe2e:d6c9. New relevant interface bond0.IPv6 for mDNS. Network interface enumeration completed. 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::ba:e1ff:fe91:340d on br0.*. Registering new address record for 13.13.13.2 on br0.IPv4. Registering new address record for fe80::92e6:baff:fe2e:d6c9 on bond0.*. Server startup complete. Host name is Titania.local. Local service cookie is 462890458.