Jump to content

HarryRosen

Members
  • Posts

    220
  • Joined

Posts posted by HarryRosen

  1. Need a little help, been running a rclone sync no problem on 6.9.2 but when moving to 6.10 files go to my cache drive and are unable to move because the file permissions are all set to root instead of user/nobody. 

     

    I have my script sync from my google drive to my unraid but will the file permissions messed up and the sync puts everything in cache first. The cache drive just fills up because mover can't move the files with root/root permissions. 

     

    This only happens using 6.10. any thoughts on how to fix this? or if it is possible to just redo the file permissions after the script runs. 

     

    would like to upgrade to the latest version

  2. 51 minutes ago, Stupifier said:

    Your error is because you are using the remote control flag (-rc) in both of your mount commands. If you don't know what that is, just remove it and you will no longer see that error. Research "rclone remote control"....most people don't need it or use it. If you DO in fact need the remote control falgs, then you must assign a unique port to your second mount command. Your second mount command is trying to use the same port as your first mount command (the default port 5572).

    https://rclone.org/rc/

     

    Now, onto your second question. Your mount does NOT need to be in a share in order for it to be seen by Windows Explorer. In your Unraid GUI dashboard, go to Settings ---> SMB Shares. Here is an example of what to put in the Samba Extra Configuration field:

    
    [gdrive]
    path = /mnt/disks/gdrive
    comment =
    browseable = yes
    # Public
    public = yes
    read only=no
    writeable=yes
    writable=yes
    write ok=yes
    guest ok = yes
    vfs objects =

     

    All of that may NOT entirely be necessary, but you get the point.....Also, as it says on that page, obviously your array must be stopped in order to apply these changes. Once you make these changes and applied them, startup your array again. The mount should be available (obviously, be sure to have your rclone mount command active). I typically map them as network drives in Windows.

     

    Fair warning though......rclone mounts ARE NOT good targets to write into frequently. People ALWAYS want to try to write stuff straight into their rclone mounts. It is unreliable at best. You should only expect to READ from an rclone mount.

    Made the changes and all is good, thank you again

  3. 15 hours ago, Stupifier said:


     

     


    Provide both of your rclone mount commands and the reported error message.
    Also, if you are doing rclone mount within a terminal, the mount will exist only as long as the terminal stay active

     

    # Local mountpoint
    mntpoint="/mnt/disks/gdrive"     # It's recommended to mount your remote share in /mnt/disks/subfolder - 
                                    # This is the only way to make it accesible to dockers
    mntpoint2="/mnt/disks/gdrive2"
     
    # Remote share
    remoteshare="gcrypt2:/Plex/"     # If you want to share the root of your remote share you have to 
                                    # define it as "remote:" eg. "acd:" or "gdrive:" 
    remoteshare2="gdrive:/Plex/"

    #---------------------------------------------------------------------------------------------------------------------


    mkdir -p $mntpoint
    mkdir -p $mntpoint2

     

    rclone mount --rc --allow-other --buffer-size 16M --dir-cache-time 2m --drive-chunk-size 64M --fast-list --log-level INFO --vfs-read-chunk-size 64M --vfs-read-chunk-size-limit off --user-agent="backup" $remoteshare $mntpoint &

     

    rclone mount --rc --allow-other --buffer-size 16M --dir-cache-time 2m --drive-chunk-size 64M --fast-list --log-level INFO --vfs-read-chunk-size 64M --vfs-read-chunk-size-limit off --user-agent="backup" $remoteshare2 $mntpoint2 &
     

    I get this error

     

    2019/12/27 09:05:22 Failed to start remote control: start server failed: listen                                      tcp 127.0.0.1:5572: bind: address already in use
     

     

    also is it possible to mount to a share dir instead? like /mnt/user/gdrive ? so i can see it on windows explorer?

  4. Hi another questions

     

    is it possible to have 2 rclone mounts? for example one encrypted and one non encrypted to different folders?

     

    I get an error when i try to mount the second drive

  5. don't know if this is possible, but I am encrypting my google drive now and getting rid of my unencrypted files but I still want to keep a local copy on my unraid which right now, I use rclone sync to download from the unencrypted google drive to my unraid.

     

    my question now is how do I download my encrypted files to unraid but unencrypted as I don't need encryption on my unraid?

  6. I am getting this error on 

     

    Warning: session_write_close(): write failed: No space left on device (28) in /usr/local/emhttp/login.php on line 33

    Warning: session_write_close(): Failed to write session data (files). Please verify that the current setting of session.save_path is correct (/var/lib/php) in /usr/local/emhttp/login.php on line 33

    Warning: Cannot modify header information - headers already sent by (output started at /usr/local/emhttp/login.php:33) in /usr/local/emhttp/login.php on line 35

     

    never mind, just did a reboot and works fine now

  7. anyone can help me with running a unrar script, 

     

    i was running

     

    find /qbit-downloads/ -name '*.rar' -execdir unrar e -o- {}

     

    and it would unrar into the directory properly using a different docker but since I moved to this one it doesn't recognize the -execdir command for find. if anyone can help that would be awesome

  8. Oct 17 16:52:05 HOMESERVER kernel: DMAR: DRHD: handling fault status reg 3
    Oct 17 16:52:05 HOMESERVER kernel: DMAR: [DMA Read] Request device [05:00.0] fault addr f9000000 [fault reason 06] PTE Read access is not set

     

    anyone have an idea how i can fix these errors? or can I ignore them

  9. Hey Guys,

     

    OpenVPN has been running great, however just upgraded to OpenVPN Client Plugin 2016.05.14f (running unRAID 6.1.9) which has killed it.  Receiving the following error when creating the tunnel interface.

     

    Sat May 14 20:05:20 2016 OpenVPN 2.3.11 x86_64-slackware-linux-gnu [sSL (OpenSSL)] [LZO] [EPOLL] [MH] [iPv6] built on May 10 2016

    Sat May 14 20:05:20 2016 library versions: OpenSSL 1.0.1s  1 Mar 2016, LZO 2.03

    Sat May 14 20:05:20 2016 WARNING: file '/boot/config/plugins/openvpnclient/password.txt' is group or others accessible

    openvpn: symbol lookup error: openvpn: undefined symbol: SSL_CTX_get0_certificate

     

    Anyone encountered this? 

     

    BTW, is there an easy way to roll a plugin back to previous release.

     

    Thanks

     

    PJ

     

    can you try this

     

     installpkg /boot/packages/openvpn-2.3.9-x86_64-1.txz

     

    This fixed my issue as well

  10. anyone else getting this

     

    /usr/lib/python2.7/site-packages/pkg_resources/__init__.py:1246: UserWarning: /home/nobody/.python-eggs is writable by group/others and vulnerable to attack when used with get_resource_filename. Consider a more secure location (set with .set_extraction_path or the PYTHON_EGG_CACHE environment variable).

    warnings.warn(msg, UserWarning)

     

    dockers fine but just noticed this now

×
×
  • Create New...