Jump to content

binary

Members
  • Posts

    12
  • Joined

  • Last visited

Posts posted by binary

  1. 12 minutes ago, Waseh said:

    Having your plugins update automatically won't do much good if rclone is running when the update is triggered. 

     

    The install didn't succeed. Try rebooting again if you cannot reinstall and/or you don't get any errors when you install 

    Thanks. Uninstalled...rebooted...installed and rebooted again.

    all back to normal thanks

  2. 6 minutes ago, Waseh said:

    Sounds like you didn't have the new version installed. 

    Are you getting any errors when you reinstall?

    thanks for the reply.

    I have my plugins to update automatically

     

    just rebooted server again and plugin isnt there. So iv installed the rclone-beta again but now i get this :

     

    User@Tower:/# rclone config /usr/sbin/rclone: line 21: rcloneorig: command not found

     

     

    ---------------------------------------------

    contents on /usr/sbin/rclone

     

     


    #!/bin/bash
    log=false
    args=()
    for i in "$@" ; do
        if [[ $i = "--log" ]] ; then
            log=true
            continue
        fi
        if [[ $i = "-l" ]] ; then
            log=true
            continue
        fi
            args+=($i)
    done

    config=/boot/config/plugins/rclone-beta/.rclone.conf
    logfile=/boot/config/plugins/rclone-beta/logs/rclone-$(date "+%Y%m%d").log
    if [ "$log" = true ] && [ ${#args[@]} -ge 1 ]; then
            rcloneorig --config $config "${args[@]}" >> $logfile 2>&1
    else
            rcloneorig --config $config "$@";
    fi;

  3. 10 hours ago, dlandon said:

    Those parameters are set according to the type of file system, in this case cifs, and are not really available to modify by the user.  The issue you are running into is the security level that samba uses when mounting a cifs file system.  This has come up before and I do not have a good solution for UD to handle this situation.

     

    The solution that @johnnie.black came up with is the best solution for the moment until I can figure out a better way for UD to handle it.  Limiting the smb protocol on the Freenas is the best answer.

     

    Thanks & Thanks @johnnie.black ! stupid configuration of smb in freenas...from my part. All working now

  4. On 10/15/2017 at 9:32 AM, binary said:

     

    Thanks, It shows the same error i kept getting when i was doing it manually in ssh.

     

    EDIT : Is there a way i can add to the mount parameters? ( eg. vers:3.0, sec=ntlmssp etc )

     

    Mount error (95)

     

    Oct 15 09:30:44 Mount SMB/NFS command: mount -t cifs -o rw,nounix,iocharset=utf8,_netdev,file_mode=0777,dir_mode=0777,username=root,password=******* '//192.168.178.2/TVShows' '/mnt/disks/192.168.178.2_TVShows'
    Oct 15 09:30:44 Mount of '//192.168.178.2/TVShows' failed. Error message: mount error(95): Operation not supported
    Refer to the mount.cifs(8) manual page (e.g. man mount.cifs)

     

    did some more research, apparently its a smb3 thing.

     

    anyone found a solution to add additional parameters to the mount command in UD?

  5. 1 hour ago, dlandon said:

    Try to mount the share with UD and show the UD log where it fails.

     

    Thanks, It shows the same error i kept getting when i was doing it manually in ssh.

     

    EDIT : Is there a way i can add to the mount parameters? ( eg. vers:3.0, sec=ntlmssp etc )

     

    Mount error (95)

     

    Oct 15 09:30:44 Mount SMB/NFS command: mount -t cifs -o rw,nounix,iocharset=utf8,_netdev,file_mode=0777,dir_mode=0777,username=root,password=******* '//192.168.178.2/TVShows' '/mnt/disks/192.168.178.2_TVShows'
    Oct 15 09:30:44 Mount of '//192.168.178.2/TVShows' failed. Error message: mount error(95): Operation not supported
    Refer to the mount.cifs(8) manual page (e.g. man mount.cifs)

     

  6. Dude, Thanks for such a great plugin!

    Recently(2days ago) moved from Freenas to unRaid.

     

    Struggled for 2 days to mount network shares in unRaid with unassigned devices plugin. But then i cracked it using the following :

    mount -t cifs //192.168.178.2/TVShows /mnt/TVShows -o vers=3.0,noperm,sec=ntlmssp,username=myuser,password=mypassword

     

    Apparently freenas wants me to use the following string...is there a way i can add in "vers=.30" into the unassigned devices? If i dont add that i cant connect to freenas shares.

×
×
  • Create New...