Jump to content

theGrok

Members
  • Posts

    101
  • Joined

  • Last visited

Posts posted by theGrok

  1. 41 minutes ago, itimpi said:

    You are being protected against the fact that moving files between a physical device and a User Share in the same command can lead to data loss so this option is not allowed by Dynamix File Manager.  Instead try moving it from the ‘downloads’ User Share to the /Media User Share.    If you must use the physical cache drive as the source then you need to select a physical target drive as well.

     

    Thank you for the info. That is helpful info. I did start my source from the /downloads user share from the shares tab, however despite this I see the source being /mnt/cache_download and not /mnt/user. Does this have to do with the fact that this share is set to a cache pool as the primary storage and NONE as the secondary? It defaults to the physical disk instead of /mnt/user/downloads as the source?

  2. Hi I am trying to move a file from a share called /downloads which is on a cache pool to a share called /Media

     

    If I select the file using the checkbox to the left of it and click the move button at the bottom of the screen , I get this popup, but I dont see see a folder called user to be able to access any user shares or move up in directory structure

    1518735047_ScreenShot2023-08-10at3_08_11PM.thumb.jpg.17e4a10d036b57f03a6e93676ff8622a.jpg

     

     

    If instead I right click the file directly and I choose move instead of using the checkbox , I do get the user folder popping up, however when I click on it does not expand to show me my shares

    1694078659_ScreenShot2023-08-10at3_08_26PM.thumb.jpg.5cbfa35870f26b669ccea6271f2c0b6d.jpg

     

    running unpaid 6.12.3

  3. 18 minutes ago, dlandon said:

     

    Your disk was unmounted by ntfs-3g:

    Apr 13 18:16:16 Medserver unassigned.devices: Adding partition 'sda1'...
    Apr 13 18:16:16 Medserver unassigned.devices: Mounting partition 'sda1' at mountpoint '/mnt/disks/flashbackup'...
    Apr 13 18:16:16 Medserver unassigned.devices: Mount drive command: /sbin/mount -t 'ntfs' -o rw,noatime,nodiratime,nodev,nosuid,nls=utf8,umask=000 '/dev/sda1' '/mnt/disks/flashbackup'
    Apr 13 18:16:17 Medserver ntfs-3g[24979]: Version 2017.3.23 integrated FUSE 27
    Apr 13 18:16:17 Medserver ntfs-3g[24979]: Mounted /dev/sda1 (Read-Write, label "", NTFS 3.1)
    Apr 13 18:16:17 Medserver ntfs-3g[24979]: Cmdline options: rw,noatime,nodiratime,nodev,nosuid,nls=utf8,umask=000
    Apr 13 18:16:17 Medserver ntfs-3g[24979]: Mount options: rw,nodiratime,nodev,nosuid,nls=utf8,allow_other,nonempty,noatime,default_permissions,fsname=/dev/sda1,blkdev,blksize=4096
    Apr 13 18:16:17 Medserver ntfs-3g[24979]: Global ownership and permissions enforced, configuration type 1
    Apr 13 18:16:17 Medserver ntfs-3g[24979]: Unmounting /dev/sda1 ()

     

    Put the disk in a PC and see if there are any issues with the disk.  Do a file system check.  I see nothing in the log that indicates why it unmounted.

     

    You'll need to reboot before you put the disk back in the server.  UD still thinks the disk is mounted.

     

    Hi, So I could not unmount it despite pushing the unmount button. However when I stopped the array it unmounted and I was able to run a file system check and I am happy to report that it looks like it fixed it. What a relief!  Thank you so much for you help!

  4. 4 hours ago, dlandon said:

    Unmount it and click on the blue check mark to run a file system check.  See if that fixes it.

    I am not able to unmount it. When I click the unmount, the button turns grey and I see a spinning wheel and then The unmount button appears again in orange.

     

    Oddly enough  here is the log from the disk nothing new since last night and it seems to say the disk was already mounted and it could not mount it. Is there a way to force unmount and then maybe it will work?

     

    Apr 12 21:52:08 Medserver kernel: sd 8:0:1:0: [sdj] 15628053168 512-byte logical blocks: (8.00 TB/7.28 TiB)
    Apr 12 21:52:08 Medserver kernel: sd 8:0:1:0: [sdj] 4096-byte physical blocks
    Apr 12 21:52:08 Medserver kernel: sd 8:0:1:0: [sdj] Write Protect is off
    Apr 12 21:52:08 Medserver kernel: sd 8:0:1:0: [sdj] Mode Sense: 7f 00 10 08
    Apr 12 21:52:08 Medserver kernel: sd 8:0:1:0: [sdj] Write cache: enabled, read cache: enabled, supports DPO and FUA
    Apr 12 21:52:08 Medserver kernel: sdj: sdj1
    Apr 12 21:52:08 Medserver kernel: sd 8:0:1:0: [sdj] Attached SCSI disk
    Apr 12 21:53:11 Medserver emhttpd: HGST_HDN728080ALE604_R6GSBU2Y (sdj) 512 15628053168
    Apr 12 21:53:11 Medserver emhttpd: read SMART /dev/sdj
    Apr 12 21:53:21 Medserver unassigned.devices: Adding partition 'sdj1'...
    Apr 12 21:53:21 Medserver unassigned.devices: Mounting partition 'sdj1' at mountpoint '/mnt/disks/seed'...
    Apr 12 21:53:21 Medserver unassigned.devices: Partition 'sdj1' is already mounted.
    Apr 12 22:53:19 Medserver emhttpd: spinning down /dev/sdj

     

    A few other things I noticed:

    when I shutdown all services and stopped the array, and all disks unmounted, the folder /mnt/seed still existed and was not removed. I set the "bad" disk to not automount and I erased the /mnt/seed folder and restarted the server. The disk mounted anyways in it's bad state even though the auto mount option was turned off. There was nothing in the system log about attempting to mount the disk either. Also the permissions of the mount were set by root and were different than the other ones set by UA. 

     

     

    Screen Shot 2022-04-13 at 6.24.13 PM.png

  5. Hello,

     

    I rebooted my server yesterday and when the system came back up one of my drives that I auto mount in Unassigned Devices showed up as completely blank with no files and no partition. It also has a red x that says clear next to it and shows as an 8TB disk but has no usable space.

     

    .Did I lose all of my data? Is there a way to repair the file system? Not sure what caused this.

     

    Any help would be appreciated. Thanks.

     

     

    Screen Shot 2022-04-13 at 1.25.36 PM.png

  6. On 7/28/2021 at 11:56 AM, binhex said:

    hmm using the same openvpn file as privoxyvpn which you say works, should get you going, im assuming you havent actually tried restarting privoxyvpn though right?, maybe it will also fail on restart.

     

    in any case, please do this:- https://github.com/binhex/documentation/blob/master/docker/faq/help.md

    Hi. I did a little more digging and you were right. I re-started the other container and had an issue. So I got fresh config files from my VPN provider and all works great now. Thank you for your help and for your awesome containers.

  7. I am currently using 2 binhex VPN containers. This one as well as the privoxy one. I have started getting some ipv6 errors in my logs for the rtorrent container. I don't have ipv6 enabled in unraid and I am not using it anywhere. I am not getting these errors in the privoxy container and I have even tried to using the same .ovpn file for both containers just to see if it was that.  Everything was working fine until yesterday as far as I could tell and I am getting no errors in the privoxy container (no v6 routes are being added in that one). Any idea what this might be? Thank you.

     

    2021-07-28 06:41:31 WARNING: OpenVPN was configured to add an IPv6 route. However, no IPv6 has been configured for tun0, therefore the route installation may fail or may not work as expected.

    2021-07-28 06:41:31 ERROR: Linux IPv6 route can't be added

     

    2021-07-28 06:45:45 sitnl_send: rtnl: generic error (-101): Network is unreachable

     

  8. 7 minutes ago, binhex said:

    i wouldnt of thought so no, can you post a screenshot of your web browsers proxy settings showing the exclusions

     

     

    At first I only had the hosts local IP 192.168.1.12 I added the long number.unraid.net and now it works. I am not sure if this is correct/good practice as I am no expert in any of this. This screenshot is from windows 10

     

    proxy.JPG

  9. 3 hours ago, binhex said:

    This should be able to be resolved by simply adding an exclusion to your you're proxy settings for your browser such that it excludes LAN IP addresses from being routed via the proxy.

    Sent from my CLT-L09 using Tapatalk
     

    Hi @binhex. Thank you That seems to have done the job for everything except the Unraid WebUI. Does that have something to do with the fact that I am using https and it has to go out and validate?

  10. 10 hours ago, DaSlinky said:

    @theGrok Did you get it to work?  I still can't get to my Jackett on :6000.  

    Hi, I don't use jackett but i've added the ADDITIONAL_PORTS variable and I still cannot access my webuis of containers that I route through the VPN if I am using browser that is using the proxy (8118). I can't access anything that has the IP address of the host including the unraid webui. Web browsing works fine. I can access all of the webui from a browser that doesn't use the proxy. I will have to have a fresh look this weekend when I have more time; In clearly doing something wrong

  11. HI.

     

    I have been using this container for while to use a VPN for ZNC and for NZBGET. Both of the containers have the custom network type in the template Custom: container:binhex-privoxyvpn. I have added the ports of NZBGET and ZNC containers to the privoxyvpn one,

     

    I also use the privoxy part of the container and have configured Sonarr and Radarr to use the proxy on port 8118. I also have the proxy configured in windows using port 8118 for web broswing.

     

    Everything has been working great for months. However, I am running into issues now. Not sure if it is due to an update or something on my end.

     

    1) I cannot access the nzbget or the znc webui's at all. This is in a browser going through the proxy or one that does not. ZNC seems to be running fine however as I am able to connect and chat etc.

    2) radarr and sonarr have lost connectivity with nzbget (radarr and sonarr don't have the privoxyvpn network type, only the proxy port configured),

    3) web browsing through the proxy in windows does not work at all.

     

    I am stumped as I have been using this with no problems for months and have not changed anything. Any ideas?

     

    Thank you for the help. Id be happy to attach any logs etc just not sure which ones are needed.

  12. On 8/29/2020 at 7:24 PM, lzrdking71 said:

    @binhex It looks like this is happening again https://github.com/binhex/arch-rtorrentvpn/issues/104

     

    2020-08-29 17:10:49,842 DEBG 'start-script' stdout output:
    [warn] Cannot determine external IP address, performing tests before setting to '127.0.0.1'...
    [info] Show name servers defined for container

     

    IP in the rutorrent settings/bittorent shows 127.0.0.1. I am using Airvpn as my vpn provider and the latest docker container available to unraid.

     

    You helped fix it before, hopefully an easy fix again.

     

    I am having the same exact issue above. I am also using AirVPN as my provider and have the latest available container.

  13. 1 hour ago, binhex said:

    Yes that will do it, obviously you need to configure it with username, password and ovpn etc, you done that?

    Sent from my EML-L29 using Tapatalk
     

    Yes, I put in the user/pass into the template and started the container once. I then copied over my .ovpn config into the openvpn folder. I was then was able to see that the credentials.conf was created. The logs say that privoxy has started. I'll recheck everything. I just wanted to confirm that setting up the host port that way was ok. Thank you.

     

    UPDATE: I tried to use the proxy in a radarr config, and it seems to connect fine. I just can't get it to work in a web browser for some reason.

  14. Hi. Thank you for making this container.

     

    I am already running your ruTorrentVPN container w/ privoxy enabled. I would like to install this one as well in order to have another endpoint available as an option. Since the ruTorrent one is already using 8118 for privoxy, would it be sufficient to change the host port of this container to say 8119 (leaving the container port 8118) in order to get this working? I've tried that, but privoxy does not seem to be working. Thank you.

  15. Well, I figured it out. I took a closer look at the ratio.dat file and it does in fact save my changes. I even restarted the container and it the changes were maintained. I reported that it did not save incorrectly above.

     

    I loaded ruTorrent ui with another browser and lo and behold, the ratio groups were there with my changes. When i went into my original browser (firefox) it did not have the changes. I reloaded the page without cage and it worked. So this appears perhaps to have been a browser cache issue more than anything.

     

    apologies for the confusion.

  16. 6 minutes ago, Spies said:

    Maybe check the contents of that file after you set it in the UI, if it's not updating maybe it's a permission issue, you could try deleting the .dat file and it may create a new one.

    it does not seem to change the files when I make changes to the ui.

  17. On 6/4/2018 at 2:30 PM, Heciruam said:

    Hello,

     

    I have a question regarding the ratio groups.

    Now that I set up sonarr and radarr, I had to set up some ratio rules. And everything works great.

    My problem is that the ratio groups are set to default after the docker gets restarted (within rutorrent). I checked the config file if I can change it there so my ratiogroups survive a restart. 

    What am I doing wrong? Or where can I make my ratio settings permanent?

     

    Thanks in advance.

     

    p.s. thanks binhex for your great dockers

    Did you ever get this solved? I tried to use ratio groups for the first time today and even though I edit the group options, they always seem to go back to default. How can I make these settings permanent? Thank you.

  18. 21 hours ago, lzrdking71 said:

    Is there a possibility that push and clientbuffer modules could be added to the znc docker container? I think these modules would be of great benefit to many. 

     

    This would be great. clientbuffer is a must for those with multiple devices. Push is also very versatile as it works with many notification services. It is a lifesaver for those who are in multiple channels at the same time.

     

     

  19. 17 minutes ago, Frank1940 said:

    Two things:

     

    1---  I believe I saw that you have Fix Common Problems installed.  I would suggest that you turn on the Troubleshooting mode  for that Plugin.  That will write periodic log files to the logs directory/folder on your flash drive.  (I saw nothing in the logs about Call Traces but I suspect that this diagnostics file was from after the reboot of your system.  In which case, it is not of much help here.) 

     

    2---   You could also start up the server in the 'Safe' mode.  That eliminates all plugins, Docker and VM's from the running configuration.  

     

    EDIT:  You could also take a picture ofthe Monitor screen when it happens again.  Be sure that the text is readable as the information is always cryptic, and sharp, unblurry pictures are usually necessary to glean any information from them.  

     

    Thank you for your reply. Indeed these are from after reboot. I thought perhaps old syslogs were saved. I have had more call traces, and I saw out of memory errors as well but have since rebooted. If I get more call traces I will post a new diagnostics. The first time, I did not have access to anything so could not.

×
×
  • Create New...