ati

Members
  • Posts

    28
  • Joined

  • Last visited

Posts posted by ati

  1. Well I am not sure what I did, but I have 2 versions of the same container. One goes through binhex-delugevpn and the other doesn't. Somehow they got messed up. As soon as I deleted both of those everything was peachy. 

     

    Strange. Probably screwed something up awhile back setting them up and not getting the appdata folders unique. Once it required a rebuild it broke everything as I haven't rebuilt the containers in months.

  2. I use binhex-delugevpn as a proxy container for many services. Today I went to add binhex-lidarr to binhex-delugevpn.

     

    Steps:

     

    1. Downloaded binhex-lidarr and configured the network to none with the extra parameter for the '--net=container:binhex-delugevpn'

    2. Started the binhex-lidarr container

    3. Realized I forgot to add the port mapping in the binhex-delugevpn container and edited it

    4. Added 8686-8686 TCP port mapping to binhex-delugevpn and rebuilt it

    5. This is where everything went sideways. Generally an update to binhex-delugevpn would cause all the containers the routed though it to rebuild. This time they didn't - they all said rebuild ready rebuilding and did nothing. My GUI was freaking out - the auto start icons were flashing and the resource usage counters were flashing and the unRAID refresh logo was popping in and out every 2-3 seconds.

     

    At this point I couldn't select anything on the screen because by the time I could click it would reload/refresh. So I did the following:

    1. From the dashboard screen stopped all the containers - didn't fix anything

    2. Slowly disabled all the auto-starts by timing my clicks

    3. Stopped and restarted the Docker service from settings - no change

    4. No obvious errors/issues in the logs

     

    Even with all my containers stopped the Docker GUI is not working? I deleted the binhex-lidarr container and removed the port mapping from binhex-delugevpn. Still nothing. I have somehow managed to screw everything. What is interesting is if I start the containers from the Dashboard page they work fine, but if I go to the Docker page in the GUI it is unusable. 

  3. I tired searching around, but couldn't find anything that really matched what I was looking for. If this has already been answered, please just point me there. 

     

    I have created a custom docker network for my SWAG container. proxynetwork (172.18.0.0\24)

     

    I have 3 containers in on the proxynetwork:

    1. SWAG

    2. Service 1 

    3. Service 2

     

    Service 1 and service 2 are reversed proxied with SWAG which is mapped to port 1443 on my unRAID server's LAN IP address and port 443 is port forwarded to SWAG via unRAID LAN IP.


    What bothers me is if I SSH into any of the 3 containers on my proxynetwork I can access any other LAN resource. I'd like to firewall off those containers from accessing any LAN resource. Basically make a DMZ of sorts. 

     

    Due to how unRAID NAT's the container network (proxynetwork) to the LAN subnet unRAID sits on (bridge mode), I am unsure I can make firewall rules at my router. Not to mention I'd prefer to lock it down inside unRAID if possible. I am looking in unRAID network settings and see the routing table, but no place to add in firewall rules/IP tables.

     

    My only other thought is to create a DMZ VLAN, make unRAID VLAN aware and then put those containers in that VLAN somehow. I am not exactly sure of the process or if that will even achieve my goal.

     

    Thanks.

  4. One thing to note. In your guide you never said to add the Photonix container to your photonix_net Docker network.

     

    I set a username and password in the Docker settings, but it just stays at loading every time I log in. I've tried restarting the container with no change. It is pointed at a directory with 15 photos for testing, so it shouldn't be taking too long to load them I'd assume. I cannot even log in when I run the container in demo mode.

    • Like 1
  5. I have a 8TB IronWolf from June 2020 in my UnRAID with no issues after the initial pre-clear. Today I took the plunge and upgraded to 6.9 from 6.8 and within a few hours after the update I got a notification from my system that I had a drive in a disabled state. 

     

    I am not very strong in this department, so I am hoping people with more HDD knowledge than me can help shed some light on my SMART results and recommend a course of action. 

     

    The array is currently stopped pending what I learn here. Plus I am not really sure what the warranty process is like with Seagate. How do I prove a drive failure and get a replacement? 

     

    Thank you.

     

     

    Disk error log:

     

    Jun 8 11:14:03 unRAID kernel: sd 5:0:6:0: [sdh] 15628053168 512-byte logical blocks: (8.00 TB/7.28 TiB)
    Jun 8 11:14:03 unRAID kernel: sd 5:0:6:0: [sdh] 4096-byte physical blocks
    Jun 8 11:14:03 unRAID kernel: sd 5:0:6:0: [sdh] Write Protect is off
    Jun 8 11:14:03 unRAID kernel: sd 5:0:6:0: [sdh] Mode Sense: 7f 00 10 08
    Jun 8 11:14:03 unRAID kernel: sd 5:0:6:0: [sdh] Write cache: enabled, read cache: enabled, supports DPO and FUA
    Jun 8 11:14:03 unRAID kernel: sdh: sdh1
    Jun 8 11:14:03 unRAID kernel: sd 5:0:6:0: [sdh] Attached SCSI disk
    Jun 8 11:14:36 unRAID emhttpd: ST8000VN004-2M2101_WKD1WM01 (sdh) 512 15628053168
    Jun 8 11:14:36 unRAID kernel: mdcmd (2): import 1 sdh 64 7814026532 0 ST8000VN004-2M2101_WKD1WM01
    Jun 8 11:14:36 unRAID kernel: md: import disk1: (sdh) ST8000VN004-2M2101_WKD1WM01 size: 7814026532
    Jun 8 11:14:36 unRAID emhttpd: read SMART /dev/sdh
    Jun 8 11:56:57 unRAID emhttpd: spinning down /dev/sdh
    Jun 8 14:16:40 unRAID kernel: sd 5:0:6:0: [sdh] tag#2816 CDB: opcode=0x85 85 06 20 00 00 00 00 00 00 00 00 00 00 40 e5 00
    Jun 8 14:16:43 unRAID kernel: sd 5:0:6:0: [sdh] Synchronizing SCSI cache
    Jun 8 14:16:43 unRAID kernel: sd 5:0:6:0: [sdh] Synchronize Cache(10) failed: Result: hostbyte=0x01 driverbyte=0x00
    Jun 8 14:16:43 unRAID kernel: scsi 5:0:6:0: [sdh] tag#3201 UNKNOWN(0x2003) Result: hostbyte=0x01 driverbyte=0x00 cmd_age=19s
    Jun 8 14:16:43 unRAID kernel: scsi 5:0:6:0: [sdh] tag#3201 CDB: opcode=0x88 88 00 00 00 00 02 49 3c b2 f8 00 00 00 80 00 00
    Jun 8 14:16:43 unRAID kernel: blk_update_request: I/O error, dev sdh, sector 9818649336 op 0x0:(READ) flags 0x0 phys_seg 16 prio class 0
    Jun 8 14:17:07 unRAID emhttpd: read SMART /dev/sdh
    

     

    ST8000VN004-2M2101_WKD1WM01-20210608-1429.txt

  6. 19 hours ago, strike said:

    You didn't mention that in your OP, then you must add that subnet to your LAN_NETWORK as well. The point of the LAN_NETWORK variable is to define your network, and all the subnets you listed are different networks. So if you need access from all of them they need to be listed. There is no magical "catch all type networks" you can add instead, AFAIK anyway. 

    Well I mean that is how subnet masking works. You can summarize (catch all) if you set it up correctly. But whether this docker can support that or not I don't know. 

     

    I changed my LAN_NETWORK to "192.168.10.0/24,192.168.130.0/24" and still no luck.

     

    The reason I didn't mention the other networks is I don't feel that it matters. I need to get one working first. No use troubleshooting 7 things at once. 

     

    I logged into the docker and verified my networks were in the IP tables:

     

    sh-5.1# iptables --list-rules
    -P INPUT DROP
    -P FORWARD DROP
    -P OUTPUT DROP
    -A INPUT -s 172.17.0.0/16 -d 172.17.0.0/16 -j ACCEPT
    -A INPUT -s ***.***.***.***/32 -i eth0 -j ACCEPT
    -A INPUT -s ***.***.***.***/32 -i eth0 -j ACCEPT
    -A INPUT -s ***.***.***.***/32 -i eth0 -j ACCEPT
    -A INPUT -s ***.***.***.***/32 -i eth0 -j ACCEPT
    -A INPUT -i eth0 -p tcp -m tcp --dport 8112 -j ACCEPT
    -A INPUT -i eth0 -p udp -m udp --dport 8112 -j ACCEPT
    -A INPUT -s 192.168.10.0/24 -d 172.17.0.0/16 -i eth0 -p tcp -m tcp --dport 58846 -j ACCEPT
    -A INPUT -s 192.168.130.0/24 -d 172.17.0.0/16 -i eth0 -p tcp -m tcp --dport 58846 -j ACCEPT
    -A INPUT -p icmp -m icmp --icmp-type 0 -j ACCEPT
    -A INPUT -i lo -j ACCEPT
    -A INPUT -i tun0 -j ACCEPT
    -A OUTPUT -s 172.17.0.0/16 -d 172.17.0.0/16 -j ACCEPT
    -A OUTPUT -d ***.***.***.***0/32 -o eth0 -j ACCEPT
    -A OUTPUT -d ***.***.***.***/32 -o eth0 -j ACCEPT
    -A OUTPUT -d ***.***.***.***/32 -o eth0 -j ACCEPT
    -A OUTPUT -d ***.***.***.***/32 -o eth0 -j ACCEPT
    -A OUTPUT -o eth0 -p tcp -m tcp --sport 8112 -j ACCEPT
    -A OUTPUT -o eth0 -p udp -m udp --sport 8112 -j ACCEPT
    -A OUTPUT -s 172.17.0.0/16 -d 192.168.10.0/24 -o eth0 -p tcp -m tcp --sport 58846 -j ACCEPT
    -A OUTPUT -s 172.17.0.0/16 -d 192.168.130.0/24 -o eth0 -p tcp -m tcp --sport 58846 -j ACCEPT
    -A OUTPUT -p icmp -m icmp --icmp-type 8 -j ACCEPT
    -A OUTPUT -o lo -j ACCEPT
    -A OUTPUT -o tun0 -j ACCEPT

     

     

    I am not sure what else to try. This is rather frustrating as I don't have this issue with any other container, so it must be in the IP tables somewhere. I am just not overly familiar with how they're implemented here.

    I am a little lost that port 58846 is specifically called out as allowed from the remote subnets, while 8112 isn't and that is the port the GUI for Deluge runs on. 

     

  7. 2 hours ago, strike said:

     

    This is wrong. You need to set your LAN_NETWORK to 192.168.10.0,192.168.130.0

    You can have multiple subnets defined, just separate them with comma.

    I'll give that a go, though I don't see the difference. I have other devices on other subnets contained within that /16 network that I would like to be able to access the docker as well. 

    What is the difference between 192.168.0.0/16 and 192.168.10.0/24, 192.168.20.0/24, 192.168.30.0/24, 192.168.110.0/24, 192.168.120.0/24, 192.168.130.0/24?

     

    The br0 isn't my goal, it was just for testing to try and gather more data. I need it to run in bridge mode anyway in order to route other dockers through this one.

     

  8. I am running into some trouble with what I believe is the LAN_NETWORK parameter and the IP_TABLES blocking me from accessing the deluge web GUI from a different subnet depending on the docker network configuration. I tired to use the binhex FAQ and some other searches, but I just couldn't find anything that applied to my particular situation.

     

    Here is the setup ONE:

    unRAID is at 192.168.10.40/24

    PC I am attempting to access the binhex-delugevpn web GUI from is at 192.168.130.50/24

    LAN_NETWORK is set to 192.168.0.0/16 to encompass everything

    Docker is configured as a bridge network.

    Here is the docker run command:

    user@localhost:# /usr/local/emhttp/plugins/dynamix.docker.manager/scripts/docker run -d --name='binhex-delugevpn' --net='bridge' --privileged=true -e TZ="America/Chicago" -e HOST_OS="Unraid" -e 'VPN_ENABLED'='yes' -e 'VPN_USER'='user' -e 'VPN_PASS'='pass' -e 'VPN_PROV'='custom' -e 'VPN_CLIENT'='openvpn' -e 'VPN_OPTIONS'='' -e 'STRICT_PORT_FORWARD'='yes' -e 'ENABLE_PRIVOXY'='no' -e 'LAN_NETWORK'='192.168.0.0/16' -e 'NAME_SERVERS'='nameserver' -e 'DELUGE_DAEMON_LOG_LEVEL'='info' -e 'DELUGE_WEB_LOG_LEVEL'='info' -e 'VPN_INPUT_PORTS'='' -e 'VPN_OUTPUT_PORTS'='' -e 'DEBUG'='false' -e 'UMASK'='000' -e 'PUID'='99' -e 'PGID'='100' -p '8112:8112/tcp' -p '58846:58846/tcp' -p '58946:58946/tcp' -p '58946:58946/udp' -p '8118:8118/tcp' -v '/mnt/user/appdata/data':'/data':'rw' -v '/mnt/cache/appdata/binhex-delugevpn':'/config':'rw' --sysctl="net.ipv4.conf.all.src_valid_mark=1" 'binhex/arch-delugevpn'

    When I run this docker, the VPN connects (verified via docker log), but I cannot access it from my PC on a different subnet. However, if I fire up a Firefox docker also in bridge mode, I can access the deluge web GUI. 

     

     

    Here is the setup TWO:

    unRAID is at 192.168.10.40/24

    PC I am attempting to access the binhex-delugevpn web GUI from is at 192.168.130.50/24

    LAN_NETWORK is set to 192.168.10.0/24

    Docker is configured as br0 network with IP of 192.168.10.210/24

    Here is the docker run command:

    user@localhost:# /usr/local/emhttp/plugins/dynamix.docker.manager/scripts/docker run -d --name='binhex-delugevpn' --net='br0' --ip='192.168.10.210' --privileged=true -e TZ="America/Chicago" -e HOST_OS="Unraid" -e 'TCP_PORT_8112'='8112' -e 'TCP_PORT_58846'='58846' -e 'TCP_PORT_58946'='58946' -e 'UDP_PORT_58946'='58946' -e 'TCP_PORT_8118'='8118' -e 'VPN_ENABLED'='yes' -e 'VPN_USER'='user' -e 'VPN_PASS'='pass' -e 'VPN_PROV'='custom' -e 'VPN_CLIENT'='openvpn' -e 'VPN_OPTIONS'='' -e 'STRICT_PORT_FORWARD'='yes' -e 'ENABLE_PRIVOXY'='no' -e 'LAN_NETWORK'='192.168.10.0/24' -e 'NAME_SERVERS'='nameserver' -e 'DELUGE_DAEMON_LOG_LEVEL'='info' -e 'DELUGE_WEB_LOG_LEVEL'='info' -e 'VPN_INPUT_PORTS'='' -e 'VPN_OUTPUT_PORTS'='' -e 'DEBUG'='false' -e 'UMASK'='000' -e 'PUID'='99' -e 'PGID'='100' -v '/mnt/cache/appdata/data':'/data':'rw' -v '/mnt/cache/appdata/binhex-delugevpn/':'/config':'rw' --sysctl="net.ipv4.conf.all.src_valid_mark=1" 'binhex/arch-delugevpn'

    When I run this docker, the VPN connects (verified via docker log) and I can access it from my PC on a different subnet. What is even more confusing for me is if I fire up the same Firefox docker and try and access the deluge web GUI, I cannot even though they are both on the very same layer 2 network. 

     

    The main reason I am trying to get this figured out is I have 2-3 other dockers I'd like to route through this binhex-delugevpn docker to grab the VPN benefits. However, in order for that to work the dockers must be configured in bridge mode. As referenced above, when I am in bridge mode I am unable to access the web GUI of the various services contained within those dockers. 

     

  9. Not quite what I was getting at, but I get it. 

     

    I want to have my unRAID server at 192.168.10.50/24

    I want to have a docker (binhex-delugevpn) at 192.168.10.100/24

    I want to have a docker run through binhex-delugevpn and be accessible at 192.168.10.100 (because the ports are run through binhex-delugevpn). 

     

    They're all on the same network. No layer 3 required, just different IP addresses. I don't want my binhex-delugevpn and my unRAID server at 192.168.10.50/24.

  10. I am slowly trying to learn about routing one docker container through another. 

     

    I've watched SpaceInvaderOne's video which was a great help. I have also read up on the changes to the binhex dockers with regards to passthrough. 

     

    What I am most curious about is networking configurations. I typically prefer to use br0 networks for my dockers to keep different workloads on different addresses. Right or wrong, this is just how I have everything currently set up. What I am learning is that if I want do have one docker route through another docker (binhex-delugevpn in my case) I need to use bridge networking. Is that correct, there is no other way around that? 

     

    I initially setup binhex-delugevpn as a br0 network on my server and I got everything working and running fine. Now that I got into playing with the inter docker routing I tried changing my binhex-delugevpn docker to bridge, and I can no longer access the UI. As soon as I change it back to br0 it's all good again. (probably an unrelated issue)

     

    Is there a way to maintain a br0 docker network and still route traffic through that docker? I believe it comes down to ports. Once you're in br0 mode, my port mapping is ignored unlike when I am in bridge networking. 

     

     

     

     

  11. It shouldn't be a 3 device pool. I set it up with only 2 drives. I replaced one a while back, could that be the 3rd drive? There are no historical drives listed if I stop the array.

    Plus the drive it thinks is missing, it is also reporting as present?

     

    Cache.thumb.jpg.8ed1464dc006d6cd62eb37a1b2446f92.jpg

  12. I believe my 2 drive BTRFS cache pool is falling and is stuck in read-only mode. I cannot get my Docker service to start:

    Sep 30 08:35:59 unRAID root: ERROR: unable to resize '/var/lib/docker': Read-only file system
    Sep 30 08:35:59 unRAID root: Resize '/var/lib/docker' of 'max'
    Sep 30 08:35:59 unRAID emhttpd: shcmd (216): /etc/rc.d/rc.docker start
    Sep 30 08:35:59 unRAID root: starting dockerd ...
    Sep 30 08:36:14 unRAID emhttpd: shcmd (218): umount /var/lib/docker

    I am trying to use the mover to clear out my cache drives so I can replace them, but that will not work either. I figured that would be fine for a read-only file system, but I guess not. Should be moving from cache to disk1.

    Sep 30 08:32:32 unRAID root: mover: started
    Sep 30 08:32:32 unRAID move: move: file /mnt/cache/Movies/MOVIE1.mp4
    Sep 30 08:32:32 unRAID move: move: create_parent: /mnt/cache/Movies/MOVIE1.mp4 error: Read-only file system
    Sep 30 08:32:32 unRAID move: move: create_parent: /mnt/cache/Movies error: Read-only file system
    Sep 30 08:32:32 unRAID move: move: file /mnt/cache/Movies/MOVIE2.mkv
    Sep 30 08:32:32 unRAID move: move: create_parent: /mnt/cache/Movies/MOVIE2.mkv error: Read-only file system
    Sep 30 08:32:32 unRAID move: move: create_parent: /mnt/cache/Movies error: Read-only file system
    Sep 30 08:32:32 unRAID move: move: file /mnt/cache/Movies/MOVIE3.mkv
    Sep 30 08:32:32 unRAID move: move: create_parent: /mnt/cache/Movies/MOVIE3.mkv error: Read-only file system
    Sep 30 08:32:32 unRAID move: move: create_parent: /mnt/cache/Movies error: Read-only file system
    Sep 30 08:32:32 unRAID move: move: file /mnt/cache/Movies/MOVIE4.mkv
    Sep 30 08:32:32 unRAID move: move: create_parent: /mnt/cache/Movies/MOVIE4.mkv error: Read-only file system
    Sep 30 08:32:32 unRAID move: move: create_parent: /mnt/cache/Movies error: Read-only file system
    Sep 30 08:32:32 unRAID move: move: file /mnt/cache/Movies/MOVIE5.mp4
    Sep 30 08:32:32 unRAID move: move: create_parent: /mnt/cache/Movies/MOVIE5.mp4 error: Read-only file system
    Sep 30 08:32:32 unRAID move: move: create_parent: /mnt/cache/Movies error: Read-only file system
    Sep 30 08:32:32 unRAID move: move_object: /mnt/cache/Movies: Read-only file system
    Sep 30 08:32:33 unRAID move: move_object: /mnt/disk1/isos: Read-only file system
    Sep 30 08:32:33 unRAID move: move: file /mnt/disk2/isos/ubuntu-20.04.1-desktop-amd64.iso
    Sep 30 08:32:33 unRAID move: move: create_parent: /mnt/disk2/isos error: Read-only file system
    Sep 30 08:32:33 unRAID move: move_object: /mnt/disk2/isos: Read-only file system

    This issue came about because one of the main drives in my array had some read errors recently. So yesterday I stopped the array, pulled the drive and replaced it. I started the array and allowed it to rebuild. This morning I noticed my Docker service failed to start so I did a little digging. Fix Common Problems called out that my cache drive pool was mounted in read-only mode. I am assuming because of the number of errors? One other strange thing is when I start the array I get a notification that one of the cache pool disks is missing, but it doesn't show as missing after the array starts. 

     

    Tried starting and stopping the array again with no change. I just rebooted the server as well just to see - no change either. 

     

    I'd like to try and move everything off the cache pool into the array so I can replace both cache drives as both have issues. 

     

    Looking for some guidance and I am a unRAID newbie and a little lost with my current situation. 

     

     

    unraid-diagnostics-20200930-0844.zip

  13. 19 hours ago, alturismo said:

    well, i only use automation so ...

     

    but u could try from inside container, just try to move something the way filebot would do, may that brings u closer

     

    open docker shell, cd /storage, check what u see and try to move things there

    Works fine in shell. Issue appears to be with FileBot...

     

    /tmp # cd /storage/temp_files/
    
    /tmp # touch testfile
    
    /tmp # cp testfile /storage/Movies/
    
    /tmp # ls /storage/Movies/ | grep test
    testfile

     

  14. I am running into an issue with permissions and it doesn't seem to pop up in this thread via search. 

     

    I have 3 shares:

    1 - Temporary storage place on my cache drive (/mnt/user/temp_files)

    2 - Movies folder (/mnt/user/Movies)

    3 - TV Shows folder (/mnt/user/TV Shows)

     

    I have my Docker container setup to pass (/mnt/user) to the container as (/storage). When I bring up the WebUI I can configure FileBot to pull my media files from the folder on my Cache drive and tag them, but when I try to copy them to the parity protected share on the array I get an error. I tried using move in FileBot first and it created all the folders, but never moved the content. When I switch to copy I get the following error:

    4.png.d531d50ca87a6fe50b6e50d46f831605.png

     

    I am a little lost as to what to do.

  15. Yeah, the disk has some pending sectors. I can understand it dropped because it's failing - that's fair. 

     

    That doesn't explain why the unRAID webUI still wasn't reading correctly on the dashboard page. Plus, if the drive reconnected, why didn't unRAID recognize that's back and add it back into the cache array? I'm a little lost why there is no notification of a missing disk whatsoever on the main page like there would be for a data drive.

     

    Just seems like I'm missing something more...

  16. I recently setup a new Cache RAID-1 for running a few dockers. Nothing fanny so I used some old mechanical drives. I basically slapped them both into unRAID and assigned them to be cache drives and it did the rest of the work making the RAID-1 array. I then used the unBalance plugin to move the default 4 folders to those drives. 

     

    Overnight one of the cache drives went missing (screenshot 1). 1.png

     

    What is strange is the drive in unRAID on the main page doesn't show the drive as missing (screenshot 2), but it does show up under the Unassigned Devices section. 

    2.png

     

    What is even more strange to me is that when I go to the main unRAID dashboard it doesn't even show the same Unassigned Devices as the main page does (screenshot 3).

    3.png

     

    I am super lost and a little confused. I haven't stopped the array or restarted, but I am sure that'd fix the issue this time around. I am more interested in why it happened and how I can prevent it in the future. What most worries me is the drive doesn't show as missing in the webUI and the main and dashboard pages don't agree on the Unassigned Devices. 

  17. I am moving from FreeNAS to unRAID and in the process I decided to pre-clear my old drives just to ensure their reliability. I had six (6) 4TB WD Red drives in my old RAID-Z2 array on FreeNAS. All the drives were bought together and they have all been in service for approximately 3.5 years. One of them in the last few months has had a few errors causing about 60MB to resilver a few times. I was going to replace that drive when I decided to move to unRAID - so that is a known failure. 

     

    I am just a little taken back that of the remaining 5 drives every single one of them has had 1 or more pending sectors during the pre-clear pre-read. 3 of them (so far) failed instantly on the post-read even after the pending sectors went to zero during the zeroing.

    I am just a little lost and a little bummed that all the drives I was planning on using are seeming to be failing. What confuses me more is why did the pending sector count go to zero without the reallocated sector count increasing? Then after the pre-clear process was finished, the server rebooted (power loss unfortunately) and a SMART test ran on the drives they all show 1 pending sector again.

     

    I ran a short SMART test on a few of the drives. Each one reported back that they had 1 pending sector. One of the drives showed it failed, one showed that it passed. The only data item unRAID highlighted is the pending sector. How can they both have the same issue but one passes and the other doesn't? 

     

    Maybe I just got a bad batch or something, but I never had any indication of an issue with FreeNAS other than the one known issue drive. Just sucks that they are 6 months outside of the warranty.

     

    Is there any more testing or data I should be gathering to prove or disprove that these drives are indeed failing? I am outside of my element here with the SMART data and the unRAID wiki is a little lacking in this area causing my to second guess myself. 

     

     

  18. I have a few questions about how to properly setup the binhex/Plex Docker. I am new to unRAID and even newer to Docker. In the past I have always made my own Ubuntu VM to run Plex in so this is a bit of a learning curve for me. 

     

    As I understand it you're supposed to pass a single directory which houses all your media - something like '/mnt/user/Media'. I however have 3 shares - Movies, TV Shows, and Music. While I could just pass '/mnt/user' that makes me very nervous giving the Docker container access to all my files. That goes against everything I was taught; only give a server/process access to what it needs. Additionally, are the media mounts passed to Docker as read only? 

     

    I guess to sum up my question. I'd really like a way to pass multiple media mounts to the Docker and I'd really prefer to pass them as read only. Plex has no reason to modify my media files, so why give it the option to. 

     

    Hopefully what I am asking is possible.

     

    Anyways the Docker container is awesome, thank you! It's pretty cool to just start a Docker and it just works 100%.