Jump to content

Johnny4233

Members
  • Posts

    38
  • Joined

  • Last visited

Posts posted by Johnny4233

  1. On 5/15/2023 at 9:55 PM, D4v3 said:

    Hi guys, I am a very new unRaid user and would like to use restic for my backups. Unfortunately, I am not getting anywhere here on my own.

     

    About my setup:

    - Unraid in version 6.11.5
    - Array with 2 HDD in xfs forma
    - Cash with one SSD in brfs
    - Another SSD with unassigned devices in btrfs format on which the repository of restic is.
    - I installed restic 0.15.1 via NerdTools. 

     

    Creating the backups by adding snapshots works as desired, at least manually. Automating the backups is a job for another day.

    What doesn't work is mounting my repository. I use the command: "restic -r /mnt/user/repository mount /mnt/disks/backup/rmount". 

     

    As a result, I get the following error:

    image.png.010d4c637fc253eedd9b49146fba2461.png

     

    Various research in forums, also on the subject of rclone with similar errors on mounting, have brought me to the point that I now suspect that the restic does not get along with the fusermount3 version of unraid. If someone could help me to get restic to mount, I would be very grateful.

     

     

    Getting the same... is there any solution?

  2. Hi,

     

    getting some trouble too.

     

    i was using the docker container for tail scale. was working flawless. since a few days it stops working. I switched to this plugin version. same problem.

     

    i connect 2 unraid server together. then I want to mount a share with unassigned devices. 

     

    Ping Unraid <-Tailscale-> Unraid works good. connection ok.

     

    But unassigned devices say, mount point is offline... 

    in network settings, I set the network extra "tailscale0"...

     

    but there seems a setting I missed? the past 1 year it was working good. 

     

    any idea? 🙂

  3. Hi,

     

    getting some trouble too.

     

    i was using the docker container for tail scale. was working flawless. since a few days it stops working. I switched to this plugin version. same problem.

     

    i connect 2 unraid server together. then I want to mount a share with unassigned devices. 

     

    Ping Unraid <-Tailscale-> Unraid works good. connection ok.

     

    But unassigned devices say, mount point is offline... 

    in network settings, I set the network extra "tailscale1"...

     

    but there seems a setting I missed? the past 1 year it was working good. 

     

    any idea? 🙂

     

    Edit:

    Netbios is off

    tryed the extra smb conf

    NASty-tailscale-diag-20240306-213055.zip

    • Like 1
  4. On 6/22/2023 at 4:52 PM, dlandon said:

    I don't think your remote server is reachable the way you have things setup:

    Jun 22 11:46:33 NASty unassigned.devices: SMB default protocol mount failed: 'mount error(111): could not connect to 100.72.40.79Unable to find suitable address. '.

     

    The 100.72.40.79 address is not reachable.

    Check the 6.12 release notes on setting up networking for tailscale.


    that was it. Thank you. 
     

    a quick question. There was a standard device script in the folder to get notifications when mounting is done or not. I don’t find the .sh script anymore. Was it deleted by accident? Where can I find it? Regards :)

  5. Hi, getting trouble since upgrade to latest unraid with booth unraid servers. 
     

    I want to mount a remote share connected via tailscale. 
     

    connections between servers are active and ping is ok. 
     

    log says: 

     

    Jun 21 14:00:50 NASty kernel: CIFS: VFS: Error connecting to socket. Aborting operation.
    Jun 21 14:00:50 NASty kernel: CIFS: VFS: cifs_mount failed w/return code = -111
    Jun 21 14:00:50 NASty unassigned.devices: SMB 1.0 mount failed: 'mount error(111): could not connect to 100.72.40.79Unable to find suitable address. '.
    Jun 21 14:00:50 NASty unassigned.devices: Share '//100.72.40.79/backup_jan' failed to mount.

     

    I deleted the share and add it again, reinstalled tailscale and rebooted server. No solution for now? :(

  6. hi, thank you for this.

     

    I managed to get this up. Works good for me.

     

    only one thing is left: I can extract the backups to an specific unraid location. but if I try to mount from a repo, the files are accessible in the docker container shell, but I can not see it in unraid file system. 

     

    device dev/fuse in docker template is set, and the folder is mounted to the container.

     

    anything I forgot? :D

     

    regards

    Jan

  7. 5 minutes ago, dlandon said:

    What is the user scrpt that is causing this issue

    No I mean, any userscript did not run in background… in log it shows that it will execute it, but then the error message above appears and the script does not run. It’s a simple mounting script for unassigned devices… look at my other thread here. 

  8. Naja, wann ich das Update für ud preclear gemacht habe weis ich nicht. 
     

    Mir ist das Problem nur heute aufgefallen, da das Script im Hintergrund nicht lief und durch ein wenig googeln und hier stöbern dann rausgefunden hatte, dass das Plugin wohl den Fehler verursacht hat. 
     

    Naja wie gesagt, habe das Plugin erstmal entfernt und neu gestartet. So oft brauch ich preclear nun nicht, das ich drauf verzichten kann erstmal. 
     

    So kommen keine Fehler mehr und die Scripte laufen. 

  9. 5 minutes ago, dlandon said:

    You can install UD Preclear that will update the glibc package

     

    Did that allready.

     

    Removed and installed the plugin again. the message apperas again.

     

    So i think this message is not so terrible? i need to wait for Unraid 6.11-rc1?

  10. Jul 11 15:24:00 NASty atd[18576]: PAM unable to dlopen(/lib64/security/pam_unix.so): /lib64/libc.so.6: version `GLIBC_2.34' not found (required by /lib64/libresolv.so.2)
    Jul 11 15:24:00 NASty atd[18576]: PAM adding faulty module: /lib64/security/pam_unix.so
    Jul 11 15:24:00 NASty atd[18576]: Module is unknown

     

    Ich erhalte im Log sehr oft den oben genannten Eintrag. Was hat das zu bedeuten und wie kann ich das beheben? Reboot hat nicht geholfen.

     

    Gruß

    Jan

  11. Das Script funktioniert nur wenn es NICHT im Hintergrund läuft. Wenn es im Hintergund laufen soll, passiert nichts. 

     

    Im Log steht:

     

    Jul 11 15:44:44 NASty emhttpd: cmd: /usr/local/emhttp/plugins/user.scripts/backgroundScript.sh /tmp/user.scripts/tmpScripts/mountShareLennart/script
    Jul 11 15:44:44 NASty atd[23459]: PAM unable to dlopen(/lib64/security/pam_unix.so): /lib64/libc.so.6: version `GLIBC_2.34' not found (required by /lib64/libresolv.so.2)
    Jul 11 15:44:44 NASty atd[23459]: PAM adding faulty module: /lib64/security/pam_unix.so
    Jul 11 15:44:44 NASty atd[23459]: Module is unknown

     

    #!/bin/bash
    #backgroundOnly=true
    #clearLog=true
    echo "Waiting for 15 seconds befor mounting..."
    sleep 15
    /usr/local/sbin/rc.unassigned mount //100.72.40.79/backup_jan

     

    Auch läuft das Script nicht beim Boot. Ich habe die Option "At Startup of Array" gesetzt. Wie kann ich das ändern? Oder hängt das damit zusammen, das das Script generell nicht im Hintergund zu laufen scheint?

     

     

    image.thumb.png.704540c643436aef9e98afda6ce23ef1.png

     

     

     

     

    Auch erscheint im log vom Script wenn ich es im vordergrund laufen lasse:

     

    Script location: /tmp/user.scripts/tmpScripts/mountShareLennart/script
    Note that closing this window will abort the execution of this script
    Waiting for 15 seconds bevor mounting...
    sh: -c: line 1: syntax error near unexpected token `('
    sh: -c: line 1: `/bin/chmod 0777 escapeshellarg(/mnt/remotes/100.72.40.79_backup_jan) 2>/dev/null'
    sh: -c: line 1: syntax error near unexpected token `('
    sh: -c: line 1: `/bin/chown 99 escapeshellarg(/mnt/remotes/100.72.40.79_backup_jan) 2>/dev/null'
    sh: -c: line 1: syntax error near unexpected token `('
    sh: -c: line 1: `/bin/chgrp 100 escapeshellarg(/mnt/remotes/100.72.40.79_backup_jan) 2>/dev/null'

     

     

     

     

    EDIT 16:57 Uhr: Problem wohl gelöst aktuell. Das Plugin UD PreClear hat den PAM Fehler im Log verursacht. Dadurch wurden die Scripte im Hintergund nicht ausgeführt. Ich habe das UD PreClerar Plugin erstmal entfernt und neu gestartet. 

     

    Danach läuft nun alles wie gewünscht. Es bleiben nur die Fehler im Script log selber. Siehe oben.

     

    Ich hoffe das Unraid 6.11-rc1 das problem mit  Glibc behebt.

     

  12. 5 hours ago, hawihoney said:

     

    Ja. Mounte in einem User Script (Plugin) mit der Einstellung "Bei Start des "Arrays". Dort könntest Du bei Bedarf  eine Pause reinsetzen. Wenn das Device bereits in UD bekannt ist, dann gibt es ab Unraid 6.10 die Möglichkeit das Mounten mit einem UD Tool zu machen. Klick mal in dem UD Bereich auf die Hilfe '?'. Dort ist das akribisch beschrieben.

     


     

    Hi, danke für die Antwort. 
     

    Der Share ist ud bekannt. Ich nutze die aktuellste unraid Version. Wo genau finde ich die Erklärung die du meintest? Habe geschaut aber in den Hilfe Beschreibungen in den Einstellungen  nichts gefunden. 

  13. Hallo,

     

    ich mounte einen externen share per SMB. Dieser Share liegt auf einem externen Unraid Server. Die Verbindung kommt mit VPN zustande. Da ich gern Automount nutzen möchte, ergibt sich ein Problem.

     

    Wenn mein Server startet, wird der Automount bereits schon versucht, bevor die VPN verbindung steht. Heisst, das Mounten funktioniert nicht.

     

    Kann man das Automount verzögern?

  14. Hallo zusammen, 

     

    mich habe per WireGuard eine server zu server Verbindung zu einem anderen unfair host aufgebaut. Per unassigned devices einen share remounted. 
     

    nachts wird dann ein Backup auf den anderen Remote Share gespeichert. 
     

    leider wird die VPN Verbindung geschlossen sobald irgendwann mal die dsl Leitung aufgibt/neu startet oder ähnliches. 
     

    Ich muss dann übers gui den Tunnel abschalten und wieder einschalten. Dann gehts wieder. Keep alive ist Aktiv (20)
     

    Was kann man da machen damit ich da nicht immer manuell eingreifen muss? 
     

    grus

  15. 10 minutes ago, dlandon said:

    Credentials problem:

    Mar 11 21:54:50 NASty kernel: CIFS: Status code returned 0xc000006d STATUS_LOGON_FAILURE
    Mar 11 21:54:50 NASty kernel: CIFS: VFS: \\10.253.1.1 Send error in SessSetup = -13
    Mar 11 21:54:50 NASty kernel: CIFS: VFS: cifs_mount failed w/return code = -13
    Mar 11 21:54:50 NASty unassigned.devices: Running device script: '10.253.1.1_backup_jan.sh' with action 'ERROR_MOUNT'.

     

     

    Hi,

     

    i refreshed the login credentials on the remote unraid server. now it works. Strange 🙂

     

  16. Upgraded to rc3 of 6.10 today. 
     

    i use a server to server connection over WireGuard to mount a share from my friend with unassigned devices. Latest updates… 
     

    so after upgrade I cannot mount the external share. VPN Connection is ok. The share shows me as online but I  Get this error when I try to mount it. The other server is at 6.9.2
     

    kernel: CIFS: VFS: \\10.253.1.1 Send error in SessSetup = -13 Mar 11 14:27:01 NASty kernel: CIFS: VFS: cifs_mount failed w/return code = -13
     

    with rc2 there was no problem. Any suggestions? 

×
×
  • Create New...