JonesCKevin

This doesn't appear to solve the issue in 6.8.3 Is there any update?

New Update and Probably Final Update: I as many SAS cables to my on board SATA ports which is 6 of my 8 drives. I did this to alleviate the chances of CRC errors during the repair. I did the mentioned above to have disk one start the repair again. Just as an extra measure in case heat is an issue I did place a giant fan on my case which kept all my drives at 26 Degrees Celsius as well. Everything appears to be up and running now.

Small Update: Just an update to the progress so far. I decided to wait on the Firmware update to try and get the drives up and running first. So far this may not be the best method as other drives get 1 error at a random time in the rebuild, which causes those drives to disable. My next step will probably to just change the port the drives are on to SATA instead of the card until it is repaired.

Okay Rog. Ill look into the firmware update then do the mentioned above. Thanks for the assistance, Ill reply back here when I have some results or questions.

I am just curious if it should be mdcmd set invalidslot 2 29 since it's disk 2 that isn't set

Roger that, To confirm before I break something, invalid slot command: mdcmd set invalidslot 2

Hey Guys, Over the weekend, my 10TB Red data drive started getting errors and disabled itself. I did a check on it and it passed, so I set it to no device and re-enabled it to start the rebuild. During the rebuild my 4TB Data drive got a single error and disabled itself. I feel I am in a pickle here. What should I do? I am not overly sure what I am looking at or for in the diag zip. tower-diagnostics-20191223-0828.zip

Thx Guys. I'll do some research on this topic

Possible solution found. Not sure if this is the actual solution though. I was trying to work out the issue after looking at both replies. There are probably other factors involved. What I did was: - Add the Unassigned Device Shares (/mnt/disks/192.168.0.100_PlexMedia) - Remove the Plex server without removing image - Removed my Grafana dockers that I was working on. - Go to Apps - Search for binhex plexpass - This is the one I use - Installed as default ( I did add Host Path 2 as /mnt/user/PlexMedia but I don't think this part is relevant)[This is still set as Read/Write) - Name: Host Path 2 - Container Path: /mnt/disks/192.168.0.100_PlexMedia - Host Path: /mnt/user/PlexMedia - Access Mode: Read/Write - I logged into Plex web gui - Went to my empty Library that was already made - Edit - Add folders - Browse for media folder - Click 192.168.0.100_PlexMedia (which finally showed my subfolders and click the one I needed) - Add - Save Changes - Scan Library files and it started re-adding them in Attached is my Post-Fix Tower Diagnostics Now to find out why Pi-Hole isn't registering my nodes. Update: Still no idea why it wasn't working but I deleted the container without deleting the image. changed appdata to .old and reinstalled from scratch. Changed to a different IP and it worked. tower-diagnostics-20180805-1849.zip

I think I may slightly undereducated on UnAssigned Devices. And I may be lost with Unassigned Devices. Once I create an SMB / NFS or create a new - Access Mode is not an option I have added a picture of one of the transfer rates moving to a different folder. (Everything counts when troubleshooting)

Hey Squid, So I created the /mnt/disks/192.168.0.100_Plexmedia share created with Unassigned devices and added it a Host Path. As well I removed /MNT/USER/PLEXMEDIA as a host path. Results: 192.168.0.100_Plexmedia shows up in the Libray options with no subfolders to choose from Result L2: The share /mnt/User/PlexMedia has been removed from the Library Options - Scan to update makes no changes. (Re-adding the /mnt/user/PlexMedia does the same and shows no subfolders- It use to) Something I did try was to create a new Share and adding some footage to that folder and changing the media destination to that folder. This made all the files disappear with no results showing up in the library. Switching back does not bring them back. It feels like there is something internally wrong. I dont mind spending the hours to almost start from scratch but I did .old the Docker image and create a new set, this did not affect anything and continued to not work. PS. PiHole doesn't seem to work with no changes to the Docker. Does not register clients. It worked before this whole flash drive and Ram change.

Hey MrBilky, From your example, I do not use a Cache drive so that may not affect me?

I did reinstall that docker from scratch and the data is showing up again. However when I try to play or edit something it gives me this error: Please check that the file exists and the necessary drive is mounted. I did try to add Host Path 1 to the share folder but it did not make any changes.

Hey MrBilky, I just tried it and it failed. I did check to see if the appdata folder was there and it does exist. root@localhost:# /usr/local/emhttp/plugins/dynamix.docker.manager/scripts/docker run -d --name='Plex2' --net='host' -e TZ="America/Los_Angeles" -e HOST_OS="unRAID" -e 'TRANS_DIR'='/config/transcode' -e 'UMASK'='000' -e 'PUID'='99' -e 'PGID'='100' -v '/mnt/user':'/media':'rw' -v '/mnt/user/Docker/PlexMediaServer/Library/Application Support/Plex Media Server/Plug-ins/':'\\192.168.0.100\Docker\PlexMediaServer\Library\Application Support\Plex Media Server\Plug-ins\':'rw' -v '/mnt/user/PlexMedia/':'/mnt/user/PlexMedia/':'rw' -v '/mnt/user/appdata/binhex-plexpass':'/config':'rw' 'binhex/arch-plexpass' /usr/bin/docker: Error response from daemon: invalid bind mount spec "/mnt/user/Docker/PlexMediaServer/Library/Application Support/Plex Media Server/Plug-ins/:\\192.168.0.100\Docker\PlexMediaServer\Library\Application Support\Plex Media Server\Plug-ins\:rw": invalid volume specification: '/mnt/user/Docker/PlexMediaServer/Library/Application Support/Plex Media Server/Plug-ins/:\192.168.0.100DockerPlexMediaServerLibraryApplication SupportPlex Media ServerPlug-ins:rw': invalid mount config for type "bind": invalid mount path: '\192.168.0.100DockerPlexMediaServerLibraryApplication SupportPlex Media ServerPlug-ins' mount path must be absolute. See '/usr/bin/docker run --help'. The command failed.

Hey guys, Short point: Plex disappeared off my docker list randomly. When I tried to recover it using a current AppData folder, everything shows but can't connect. Long Point: It started when my computer would shut down all the time. Normally only when I am home. I assumed the dog would touch the machine and shock it to shut down. It turns out there was a bad RAM stick. Once I took the bad ram stick out I got some errors which would not let me boot the machine. After some tricks and such I remade a new flash drive and converted my GUID as well as Copied my config folder. This seemed to work fine on my shares, dockers, and everything really. Currently, most of the dockers appear fine when one and work. They open, show nothing different. However, the plex was fine too. It ran and I watched. Then about 2 days in it drops off the face of the planet. So I add a new container using the AppData folder which seemed to fix it but once I go to play something it would say to make sure the files haven't been renamed or moved. Moving ahead in time, the folders do not show the cached files anymore (I did delete the AppData folder in hopes to start from scratch). So currently I have an empty Plex that won't recognize the shared Videos folders. It just comes up empty when I do a scan. Share name EG: /MNT/USER/PLEXMEDIA /Movies /Tv Shows tower-diagnostics-20180804-0730.zip

Attached Diagnotic tower-diagnostics-20180414-1014.zip

Hey Guys, I am still fairly new. Been playing with the system for about 1.5 Months. At this time I am currently looking for help getting my 1050TI and or 580GTX to work with VM. I think I have everything setup correctly at this point, but when I go to start the VM, it starts up and if I try to use my keyboard or wait long enough it crashes the whole system and I have to hard reset. I am using the BIOS I dumped using Spaceinvader video (How to passthrough an nvidia gpu as primary gpu in unRAID - YouTube) . From here I changed the Graphics ROM BIOS to : /mnt/user/system/asus1050ti.dump which is where I put it. - I am using my monitor and directly plugged into the Graphic card to view the OS. If I use VNC, everything is fine. System Info: M/B: Gigabyte Technology Co., Ltd. - Z97X-Gaming 5 CPU: Intel® Core™ i7-4790 CPU @ 3.60GHz HVM: Enabled IOMMU: Enabled Cache: 256 kB, 1024 kB, 8192 kB Memory: 24 GB (max. installable capacity 32 GB) Array: P-4TB D1-4TB D2-3TB D3-2TB D4-4TB Some SysLogs Apr 13 18:56:10 Tower kernel: BTRFS info (device loop2): disk space caching is enabled Apr 13 18:56:10 Tower kernel: BTRFS info (device loop2): has skinny extents Apr 13 18:56:10 Tower root: Resize '/var/lib/docker' of 'max' Apr 13 18:56:10 Tower kernel: BTRFS info (device loop2): new size for /dev/loop2 is 21474836480 Apr 13 18:56:10 Tower emhttpd: shcmd (99): /etc/rc.d/rc.docker start Apr 13 18:56:10 Tower root: starting dockerd ... Apr 13 18:56:13 Tower kernel: ip_tables: (C) 2000-2006 Netfilter Core Team Apr 13 18:56:13 Tower avahi-daemon[7371]: Joining mDNS multicast group on interface docker0.IPv4 with address 172.17.0.1. Apr 13 18:56:13 Tower avahi-daemon[7371]: New relevant interface docker0.IPv4 for mDNS. Apr 13 18:56:13 Tower avahi-daemon[7371]: Registering new address record for 172.17.0.1 on docker0.IPv4. Apr 13 18:56:13 Tower kernel: IPv6: ADDRCONF(NETDEV_UP): docker0: link is not ready Apr 13 18:56:15 Tower root: error: /plugins/preclear.disk/Preclear.php: wrong csrf_token Apr 13 18:56:16 Tower emhttpd: shcmd (113): /usr/local/sbin/mount_image '/mnt/user/system/libvirt/libvirt.img' /etc/libvirt 1 Apr 13 18:56:16 Tower kernel: BTRFS info (device loop3): disk space caching is enabled Apr 13 18:56:16 Tower kernel: BTRFS info (device loop3): has skinny extents Apr 13 18:56:16 Tower root: Resize '/etc/libvirt' of 'max' Apr 13 18:56:16 Tower kernel: BTRFS info (device loop3): new size for /dev/loop3 is 1073741824 Apr 13 18:56:16 Tower emhttpd: shcmd (115): /etc/rc.d/rc.libvirt start Apr 13 18:56:16 Tower root: Starting virtlockd... Apr 13 18:56:16 Tower root: Starting virtlogd... Apr 13 18:56:16 Tower root: Starting libvirtd... Apr 13 18:56:16 Tower kernel: tun: Universal TUN/TAP device driver, 1.6 Apr 13 18:56:16 Tower kernel: mdcmd (52): check correct Apr 13 18:56:16 Tower kernel: md: recovery thread: check Q ... Apr 13 18:56:16 Tower kernel: md: using 1536k window, over a total of 3907018532 blocks. Apr 13 18:56:16 Tower kernel: ip6_tables: (C) 2000-2006 Netfilter Core Team Apr 13 18:56:16 Tower root: error: /plugins/preclear.disk/Preclear.php: wrong csrf_token Apr 13 18:56:16 Tower kernel: Ebtables v2.0 registered Apr 13 18:56:16 Tower kernel: virbr0: port 1(virbr0-nic) entered blocking state Apr 13 18:56:16 Tower kernel: virbr0: port 1(virbr0-nic) entered disabled state Apr 13 18:56:16 Tower kernel: device virbr0-nic entered promiscuous mode Apr 13 18:56:16 Tower avahi-daemon[7371]: Joining mDNS multicast group on interface virbr0.IPv4 with address 192.168.122.1. Apr 13 18:56:16 Tower avahi-daemon[7371]: New relevant interface virbr0.IPv4 for mDNS. Apr 13 18:56:16 Tower avahi-daemon[7371]: Registering new address record for 192.168.122.1 on virbr0.IPv4. Apr 13 18:56:16 Tower kernel: virbr0: port 1(virbr0-nic) entered blocking state Apr 13 18:56:16 Tower kernel: virbr0: port 1(virbr0-nic) entered listening state Apr 13 18:56:17 Tower dnsmasq[9059]: started, version 2.78 cachesize 150 Apr 13 18:56:17 Tower dnsmasq[9059]: compile time options: IPv6 GNU-getopt no-DBus i18n IDN2 DHCP DHCPv6 no-Lua TFTP no-conntrack ipset auth no-DNSSEC loop-detect inotify Apr 13 18:56:17 Tower dnsmasq-dhcp[9059]: DHCP, IP range 192.168.122.2 -- 192.168.122.254, lease time 1h Apr 13 18:56:17 Tower dnsmasq-dhcp[9059]: DHCP, sockets bound exclusively to interface virbr0 Apr 13 18:56:17 Tower dnsmasq[9059]: reading /etc/resolv.conf Apr 13 18:56:17 Tower dnsmasq[9059]: using nameserver 64.59.184.13#53 Apr 13 18:56:17 Tower dnsmasq[9059]: using nameserver 64.59.190.242#53 Apr 13 18:56:17 Tower dnsmasq[9059]: using nameserver 8.8.8.8#53 Apr 13 18:56:17 Tower dnsmasq[9059]: read /etc/hosts - 2 addresses Apr 13 18:56:17 Tower dnsmasq[9059]: read /var/lib/libvirt/dnsmasq/default.addnhosts - 0 addresses Apr 13 18:56:17 Tower dnsmasq-dhcp[9059]: read /var/lib/libvirt/dnsmasq/default.hostsfile Apr 13 18:56:17 Tower kernel: virbr0: port 1(virbr0-nic) entered disabled state Apr 13 18:56:29 Tower kernel: docker0: port 1(veth7772088) entered blocking state Apr 13 18:56:29 Tower kernel: docker0: port 1(veth7772088) entered disabled state Apr 13 18:56:29 Tower kernel: device veth7772088 entered promiscuous mode Apr 13 18:56:29 Tower kernel: IPv6: ADDRCONF(NETDEV_UP): veth7772088: link is not ready Apr 13 18:56:29 Tower kernel: docker0: port 1(veth7772088) entered blocking state Apr 13 18:56:29 Tower kernel: docker0: port 1(veth7772088) entered forwarding state Apr 13 18:56:29 Tower kernel: docker0: port 1(veth7772088) entered disabled state Apr 13 18:56:32 Tower kernel: docker0: port 2(veth7d3244e) entered blocking state Apr 13 18:56:32 Tower kernel: docker0: port 2(veth7d3244e) entered disabled state Apr 13 18:56:32 Tower kernel: device veth7d3244e entered promiscuous mode Apr 13 18:56:32 Tower kernel: IPv6: ADDRCONF(NETDEV_UP): veth7d3244e: link is not ready Apr 13 18:56:32 Tower kernel: docker0: port 2(veth7d3244e) entered blocking state Apr 13 18:56:32 Tower kernel: docker0: port 2(veth7d3244e) entered forwarding state Apr 13 18:56:32 Tower kernel: docker0: port 2(veth7d3244e) entered disabled state Apr 13 18:56:40 Tower kernel: eth0: renamed from veth294e914 Apr 13 18:56:40 Tower kernel: IPv6: ADDRCONF(NETDEV_CHANGE): veth7772088: link becomes ready Apr 13 18:56:40 Tower kernel: docker0: port 1(veth7772088) entered blocking state Apr 13 18:56:40 Tower kernel: docker0: port 1(veth7772088) entered forwarding state Apr 13 18:56:40 Tower kernel: IPv6: ADDRCONF(NETDEV_CHANGE): docker0: link becomes ready Apr 13 18:56:42 Tower avahi-daemon[7371]: Joining mDNS multicast group on interface docker0.IPv6 with address fe80::42:58ff:fe9d:8470. Apr 13 18:56:42 Tower avahi-daemon[7371]: New relevant interface docker0.IPv6 for mDNS. Apr 13 18:56:42 Tower avahi-daemon[7371]: Registering new address record for fe80::42:58ff:fe9d:8470 on docker0.*. Apr 13 18:56:42 Tower avahi-daemon[7371]: Joining mDNS multicast group on interface veth7772088.IPv6 with address fe80::1404:dff:fef9:534f. Apr 13 18:56:42 Tower avahi-daemon[7371]: New relevant interface veth7772088.IPv6 for mDNS. Apr 13 18:56:42 Tower avahi-daemon[7371]: Registering new address record for fe80::1404:dff:fef9:534f on veth7772088.*. Apr 13 18:56:45 Tower kernel: eth0: renamed from veth1ae39be Apr 13 18:56:45 Tower kernel: IPv6: ADDRCONF(NETDEV_CHANGE): veth7d3244e: link becomes ready Apr 13 18:56:45 Tower kernel: docker0: port 2(veth7d3244e) entered blocking state Apr 13 18:56:45 Tower kernel: docker0: port 2(veth7d3244e) entered forwarding state Apr 13 18:56:45 Tower root: error: /plugins/preclear.disk/Preclear.php: wrong csrf_token Apr 13 18:56:47 Tower avahi-daemon[7371]: Joining mDNS multicast group on interface veth7d3244e.IPv6 with address fe80::5cab:c4ff:feba:206e. Apr 13 18:56:47 Tower avahi-daemon[7371]: New relevant interface veth7d3244e.IPv6 for mDNS. Apr 13 18:56:47 Tower avahi-daemon[7371]: Registering new address record for fe80::5cab:c4ff:feba:206e on veth7d3244e.*. Apr 13 19:11:04 Tower emhttpd: req (2): csrf_token=****************&title=System+Log&cmd=%2FwebGui%2Fscripts%2Ftail_log&arg1=syslog Apr 13 19:11:04 Tower emhttpd: cmd: /usr/local/emhttp/plugins/dynamix/scripts/tail_log syslog