fibreiv

Members
 View Profile  See their activity

  • Posts

    23

  • Joined

  • Last visited

 Content Type 

Posts posted by fibreiv

    [support] Bungy's docker repository

    in Docker Containers

    Posted

    nzbgetvpn is giving the following error: Error response from daemon: driver failed programming external connectivity on endpoint nzbgetvpn (d33975b9767d5da5b947041d7e16a98c6486eaed978724af4f4dd55039d37382): Bind for 0.0.0.0:6789 failed: port is already allocated

     

    I had it all up and running using it fine for over a month and then all the sudden it was downloading and froze so I tried to restart the container and it wouldn't so I finally just ended up restarting the whole server but it would not come up so I removed and readded the container but that's the message I get.

     

    Thanks much!

    Unassigned Devices - Managing Disk Drives and Remote Shares Outside of The Unraid Array

    in Plugin Support

    Posted

    14 minutes ago, dlandon said:

    The problem is that there are two IP addresses assigned to the DROBOSERVER.  UD gets them both from the nmblookup and concatenates them together and a double IP address is created - "192.168.86.5 192.168.50.1".  This won't work when that is ping'd.

     

    Not sure of the answer, but I will probably apply a fix so the first IP address is used and the second one ignored.  This might not work for you.  The solution is for you to reference the DROBOSERVER by IP and not name unless my proposed solution works for you.

    I am pretty sure I tried to access the share via the ip and it didn’t work either but I will confirm. I would think if I used just the ip of the card that connects to my network it would only connect to the droboserver on that ip but I guess I could be wrong on that. Thanks

    Unassigned Devices - Managing Disk Drives and Remote Shares Outside of The Unraid Array

    in Plugin Support

    Posted

    3 minutes ago, dlandon said:

    Give me the result of these commands: 

    
/bin/ping -c 1 -W 1 DROBOSERVER

    and 

    
/usr/bin/nmblookup DROBOSERVER

    and post the results.  Let me know if the commands take a long time to respond.

    root@UnRaid:/usr/local/emhttp/plugins/unassigned.devices/include# /bin/ping -c 1 -W 1 DROBOSERVER
    ping: unknown host DROBOSERVER

     

    root@UnRaid:/usr/local/emhttp/plugins/unassigned.devices/include# /usr/bin/nmblookup DROBOSERVER
    192.168.86.5 DROBOSERVER<00>
    192.168.50.1 DROBOSERVER<00>

     

     

    Well that doesn't seem right.  I know the 192.168.50.1 is the cable between the Drobo and the Network card that is only bound to the VM. the 192.168.86.5 is it's IP on my network, 192.168.86.4 is my UnRaid server.  Hope this helps, thanks!

    Unassigned Devices - Managing Disk Drives and Remote Shares Outside of The Unraid Array

    in Plugin Support

    Posted

    8 hours ago, fibreiv said:

    Hey, sorry for being rude. Just gotten frustrated that I haven't been able to get this working.  I will put together a detailed summary to try and clear up confusion on my issue. I do appropriate the help.

    I have UnRaid 6.6.5 running on a Dell R710 server with 1 network card connected to my network and the other directly connected to a DroboElite for iSCSI. I have a Plex Docker container which needs to talk to the Drobo but since UnRaid doesn't support iSCSI I have a Windows 2016 VM setup in UnRaid as well. It has the following configuration and is working perfectly connecting to the internet, my intranet and to the iSCSI Drobo. Network Bridge 1 goes to my network and that's the card that has the IP is connect to to manage. 2nd Network card is bound to 1 card that is a cable between it and the DroboElite. I have that card passed through to the VM. Using the mount -cif

    image.png.fe36bf7dff6fa1a7024a386a2991f5ad.png  

    image.png.5b2aba71c10d84ac72ea0b554861052a.png

    image.png.e73a94ff335fa84d9c37beee981a66df.png

    image.thumb.png.ce9d09e3561cec1cfe7d9bea1b55b7fe.png

    Unassigned Devices - Managing Disk Drives and Remote Shares Outside of The Unraid Array

    in Plugin Support

    Posted

    2 hours ago, fibreiv said:

    Hey, sorry for being rude. Just gotten frustrated that I haven't been able to get this working.  I will put together a detailed summary to try and clear up confusion on my issue. I do appropriate the help.

    I have UnRaid 6.6.5 running on a Dell R710 server with 1 network card connected to my network and the other directly connected to a DroboElite for iSCSI. I have a Plex Docker container which needs to talk to the Drobo but since UnRaid doesn't support iSCSI I have a Windows 2016 VM setup in UnRaid as well. It has the following configuration and is working perfectly connecting to the internet, my intranet and to the iSCSI Drobo. Network Bridge 1 goes to my network and that's the card that has the IP is connect to to manage. 2nd Network card is bound to 1 card that is a cable between it and the DroboElite. I have that card passed through to the VM. Using the mount -t cifs command I am able to mount the Drobo fine from the terminal so I know all the networking is working and I am also able to add it to the docker container and Plex see the content and it works. It's just the unassigned devices I can't seem to get it mount the share. I use the buttons to populates the server and share and it finds everything ok but it doesn't mount. I have tried both with NFS and SMB shares. NFS it gives me the mount button but doesn't do anything. Log shows this error "nRaid unassigned.devices: Error: Remote SMB/NFS server '192.168.86.5' is offline and share '192.168.86.5://PlexMedia' cannot be mounted." when I try in mount it in the logs. Windows shows the NFS share as 192.168.86.5:/PlexMedia without the second / in it. Not sure if that matters. SMB has the mount button grayed out after adding it. I'm not sure where to go from here with making it work in the webgui. I really didn't want to have to manually do it in the terminal but I can.

    Thanks much!

    image.png.fe36bf7dff6fa1a7024a386a2991f5ad.png  

    image.png.5b2aba71c10d84ac72ea0b554861052a.png

    image.png.e73a94ff335fa84d9c37beee981a66df.png

    image.thumb.png.ce9d09e3561cec1cfe7d9bea1b55b7fe.png

    Unassigned Devices - Managing Disk Drives and Remote Shares Outside of The Unraid Array

    in Plugin Support

    Posted

    1 hour ago, dlandon said:

    You are being rude.  You are throwing a lot at me that has been confusing and now getting an attitude.  I'm sorry if I can't follow everything.  You are one of many people asking for help on UD and other plugins and dockers I support.  I do the best I can.

     

    I can't reproduce your problem and can't see anything in the code that is causing a problem for you.

    Hey, sorry for being rude. Just gotten frustrated that I haven't been able to get this working.  I will put together a detailed summary to try and clear up confusion on my issue. I do appropriate the help.

    Unassigned Devices - Managing Disk Drives and Remote Shares Outside of The Unraid Array

    in Plugin Support

    Posted

    9 minutes ago, dlandon said:

    Your diagnostics showed an attempt to mount the shares on Unraid startup.  There may be an issue with that.  There are times when things aren't ready to mount that early in the boot process.  For example your VM might not be running.  Try mounting the share using the 'Mount' button after the array has started.

    I am not trying to be rude but almost every comment/suggestion I’ve gotten would have been answered if someone review the whole message thread. If you refer to the picture I posted on Wednesday you can see the mount button is grayed out. System is fully booted and I am just trying to mount a share. 

    9 minutes ago, dlandon said:

    Your diagnostics showed an attempt to mount the shares on Unraid startup.  There may be an issue with that.  There are times when things aren't ready to mount that early in the boot process.  For example your VM might not be running.  Try mounting the share using the 'Mount' button after the array has started.

     

    Unassigned Devices - Managing Disk Drives and Remote Shares Outside of The Unraid Array

    in Plugin Support

    Posted

    8 minutes ago, dlandon said:

    UD thinks the server is off-line because it does not respond to a ping from UD.

     

    UD uses this command to ping: 

    
/bin/ping -c 1 -W 1 ip_address

    Try the command and see what the response is from your server.

    Linux 4.18.17-unRAID.
    Last login: Wed Nov 14 13:04:23 -0600 2018 on /dev/pts/0.
    root@UnRaid:~# cd /bin
    root@UnRaid:/bin# ping
    Usage: ping [-aAbBdDfhLnOqrRUvV] [-c count] [-i interval] [-I interface]
                [-m mark] [-M pmtudisc_option] [-l preload] [-p pattern] [-Q tos]
                [-s packetsize] [-S sndbuf] [-t ttl] [-T timestamp_option]
                [-w deadline] [-W timeout] [hop1 ...] destination
    root@UnRaid:/bin# ping -c 1 -W 1 192.168.86.5
    PING 192.168.86.5 (192.168.86.5) 56(84) bytes of data.
    64 bytes from 192.168.86.5: icmp_seq=1 ttl=128 time=0.431 ms

    --- 192.168.86.5 ping statistics ---
    1 packets transmitted, 1 received, 0% packet loss, time 0ms
    rtt min/avg/max/mdev = 0.431/0.431/0.431/0.000 ms
    root@UnRaid:/bin# ^C
    root@UnRaid:/bin#

    Unassigned Devices - Managing Disk Drives and Remote Shares Outside of The Unraid Array

    in Plugin Support

    Posted

    18 hours ago, dlandon said:

    Post your diagnostics.  SMB and NFS share mounting works fine.  There is something unique about your setup that is causing a problem.  I suspect a networking issue.  That's why I suggested a static IP.  You would probably need a static IP address if the VM is a server anyway.

    Here is my diag file.  Also my Windows Server VM has a static IP already. First thing I did when setting it up. ;)

    unraid-diagnostics-20181115-1213.zip

    Unassigned Devices - Managing Disk Drives and Remote Shares Outside of The Unraid Array

    in Plugin Support

    Posted

    17 minutes ago, saarg said:

    My guess is that you have the wrong network for the VM. You have probably chosen virbr0 in the vm template. Change it to br0 and you should be able to reach the VM. 

    With virbr0 you can reach the network on the outside of the vm, but nothing gets in. 

    I have network access with both UnRaid and in the Windows VM just fine. But I did check and it is already set to br0.

     

    image.png.757e4b71a8a73fa62d036906bc1b7a73.png

    Unassigned Devices - Managing Disk Drives and Remote Shares Outside of The Unraid Array

    in Plugin Support

    Posted

    Just now, dlandon said:

    That makes me suspicious about your network and ip addressing.

     

    Why are you setting up a Windows server vm on unraid.  What does that accomplish?

    The Windows VM can bring up the UnRaid webui in it's browser just fine.  I have been able to mount the SMB manually in the Linux console and was able to view all the files but when I tried to add it to Plex it just showed the root folder and everything else was empty.

     

    The goal of having it setup this way is that I have a DroboElite 8 disk unit that only supports iSCSI. From what I have read UnRaid doesn't support iSCSI so in order to get it working without having to have more hardware then is necessary I thought I would just pass the device through a Windows VM since Windows supports it out of the box and then I can share the device out of Windows back to UnRaid using either SMB or NFS since Windows Server 2016 supports both of those and so does UnRaid. If there is a better option to get iSCSI device passed to docker containers that I'm open to other solutions as well but if I'm not way off my rocker this should just work. Windows share to UnRaid's Unassigned Devices plugin.

     

    Thanks Much!

    Unassigned Devices - Managing Disk Drives and Remote Shares Outside of The Unraid Array

    in Plugin Support

    Posted

    1 minute ago, dlandon said:

    Your posts are confusing.  The first one shows referring to the server by ip and it was a Windows server.  Now it’s by name and not a Windows server.

    Sorry for the confusion. The log was when I was trying NFS but SMB wants the name.  Neither work for some odd reason and I have stumped. :(  I'm new to UnRaid and am excited to get my Plex container up and running but have gotten stuck on this issue to pass through my iSCSI DroboElite to UnRaid containers. I have also tried just sharing a folder on the c:\ drive of the Windows Server 2016 to rule out something weird with iSCSI but get the same results. Just a side note, the Windows Server is a VM inside UnRaid. Thanks!

    Unassigned Devices - Managing Disk Drives and Remote Shares Outside of The Unraid Array

    in Plugin Support

    Posted

    I have unRaid 6.6.3 and for the life of me I can't get Unassigned Disks to connect to SMB or NFS. My NFS share shows green bubble but when I click mount it fails. I hit the "Search for Server" button and selected the server and then hit "Load Shares" and selected the share. No Luck. As this share is on a Windows 2016 server I have also tried SMB but when I select server, put in admin creds for server, hit load shares, select share it gives me a gray dot next to smb and the "mount" button is gray and not orange. Any help would be greatly appreciated. Thanks!

      

    Nov 14 11:15:30 UnRaid unassigned.devices: Mount SMB/NFS command: mount -t nfs -o defaults '192.168.86.5://PlexMedia' '/mnt/disks/PlexMedia'
Nov 14 11:15:30 UnRaid unassigned.devices: Mount of '192.168.86.5://PlexMedia' failed. Error message: mount.nfs: mounting 192.168.86.5://PlexMedia failed, reason given by server: No such file or directory 
Nov 14 11:16:15 UnRaid sudo:     root : TTY=pts/1 ; PWD=/mnt/disks ; USER=root ; COMMAND=/usr/bin/chmod +777 PlexMedia/
Nov 14 11:16:20 UnRaid rpcbind[31397]: connect from 127.0.0.1 to getport/addr(status)
Nov 14 11:16:20 UnRaid unassigned.devices: Mount SMB/NFS command: mount -t nfs -o defaults '192.168.86.5://PlexMedia' '/mnt/disks/PlexMedia'
Nov 14 11:16:20 UnRaid unassigned.devices: Mount of '192.168.86.5://PlexMedia' failed. Error message: mount.nfs: mounting 192.168.86.5://PlexMedia failed, reason given by server: No such file or directory