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

Has anyone come across? What is it and why is it happening? How can this affect the transferred files to the remote directory? This only happens when transferring files via RSYNC

 

script example

Spoiler

#!/bin/bash

MOUNTPOINT=/mnt/remotes/unraid_backup
PROG_NAME=DailyBackup_from_WorkServer

logger Started -t$PROG_NAME

/usr/local/sbin/rc.unassigned mount //IP/unraid_backup

sleep 10

if mountpoint -q $MOUNTPOINT; then
  logger Sync Backup Folder -t$PROG_NAME
  rsync -avP /mnt/user/backups/copy_test/ $MOUNTPOINT/ tee $MOUNTPOINT/rsync.log 2>&1

  logger Sync Backup Folder Completed -t$PROG_NAME
  /usr/local/emhttp/webGui/scripts/notify -e "Unraid Server Notice" -s "Server Backup" -d "Daily Sync Backup Folder completed" -i "normal"

  logger Unmounted Remote Share -t$PROG_NAME
  
  sleep 10
  
  /usr/local/sbin/rc.unassigned umount //IP/unraid_backup 2>&1

else
  logger Daily Backup Drive Not Mounted -t$PROG_NAME
fi

 

 

 

And sometimes the distant directory refuses to be unmounted, writes that it is busy with some kind of process. Yes, you can hard-unmounted it with -l, but this is a very bad option. Maybe you can check? That if the directory is not unmounted, then continue to unmount it until it is unmounted

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

Hi.

I ran into this problem. There is a shared resource on Windows Server. I mount remote directory in Unraid via plugin, I specify (IP, USER, PASS, DOMEN) directory is mounted and everything is fine. But... If for some reason connection to remote directory disappears (or to remote server) then directory can't be mounted itself and in log it will be like this

 

Jun  4 04:18:22 kernel: CIFS: VFS: \\IP_ADDRESS Send error in SessSetup = -13
Jun  4 04:18:24 kernel: CIFS: Status code returned 0xc000006d STATUS_LOGON_FAILURE
Jun  4 04:18:24 kernel: CIFS: VFS: \\IP_ADDRESS Send error in SessSetup = -13
Jun  4 04:18:24 kernel: CIFS: Status code returned 0xc000006d STATUS_LOGON_FAILURE
Jun  4 04:18:24 kernel: CIFS: VFS: \\IP_ADDRESS Send error in SessSetup = -13
Jun  4 04:18:25 kernel: CIFS: Status code returned 0xc000006d STATUS_LOGON_FAILURE
Jun  4 04:18:25 kernel: CIFS: VFS: \\IP_ADDRESS Send error in SessSetup = -13
Jun  4 04:18:26 kernel: CIFS: Status code returned 0xc000006d STATUS_LOGON_FAILURE
Jun  4 04:18:26 kernel: CIFS: VFS: \\IP_ADDRESS Send error in SessSetup = -13
Jun  4 04:18:27 kernel: CIFS: Status code returned 0xc000006d STATUS_LOGON_FAILURE
Jun  4 04:18:27 kernel: CIFS: VFS: \\IP_ADDRESS Send error in SessSetup = -13
Jun  4 04:18:27 kernel: CIFS: Status code returned 0xc000006d STATUS_LOGON_FAILURE
Jun  4 04:18:27 kernel: CIFS: VFS: \\IP_ADDRESS Send error in SessSetup = -13
Jun  4 04:18:29 kernel: CIFS: Status code returned 0xc000006d STATUS_LOGON_FAILURE
Jun  4 04:18:29 kernel: CIFS: VFS: \\IP_ADDRESS Send error in SessSetup = -13
Jun  4 04:18:29 kernel: CIFS: Status code returned 0xc000006d STATUS_LOGON_FAILURE
Jun  4 04:18:29 kernel: CIFS: VFS: \\IP_ADDRESS Send error in SessSetup = -13
Jun  4 04:18:31 kernel: CIFS: Status code returned 0xc000006d STATUS_LOGON_FAILURE
Jun  4 04:18:31 kernel: CIFS: VFS: \\IP_ADDRESS Send error in SessSetup = -13
Jun  4 04:18:31 kernel: CIFS: Status code returned 0xc000006d STATUS_LOGON_FAILURE
Jun  4 04:18:31 kernel: CIFS: VFS: \\IP_ADDRESS Send error in SessSetup = -13
Jun  4 04:18:32 kernel: CIFS: Status code returned 0xc000006d STATUS_LOGON_FAILURE
Jun  4 04:18:32 kernel: CIFS: VFS: \\IP_ADDRESS Send error in SessSetup = -13
Jun  4 04:18:32 kernel: CIFS: Status code returned 0xc000006d STATUS_LOGON_FAILURE
Jun  4 04:18:32 kernel: CIFS: VFS: \\IP_ADDRESS Send error in SessSetup = -13

 

The only way to solve this is to manually remount the directory.

 

Also. Maybe there is a ready-made script for user-scripts that automatically mounts the directory, makes a backup via rsync and unmounts the directory?

[Use docker labels for UnRaid-specific information in docker templates to allow for a 1:1 map between UnRaid templates and docker-compose files.]

12 minutes ago, bling said:

just upgraded to 6.10.1.  are the labels working for anyone else?  here's a simple compose file.

 

version: "2.2"
services:
  nginx:
    image: nginx
    labels:
      - net.unraid.docker.icon=https://some.server.com/image.png

 

launched the container, went to the docker tab, but the image doesn't get loaded.

 

Labels

- net.unraid.docker.icon

working only for local path and only .PNG format

 - net.unraid.docker.icon=/mnt/user/appdata/icons/icons.png

 

[Use docker labels for UnRaid-specific information in docker templates to allow for a 1:1 map between UnRaid templates and docker-compose files.]

Quote

It would be great to see this included in the core of unraid since it's such a simple addition. 

 

Edit /usr/local/emhttp/plugins/dynamix.docker.manager/include/DockerClient.php

 

Look for public function getAllInfo($reload=false) { and at the very end of the foreach add:

 

How to fix this bug?

And this changes removed from file DockerClient.php after reboot server

 

[Not Connected to Mothership]

17 hours ago, zspearmint said:

@ScreN is it a duplicate server tile that shouldn't be showing or simply an old license that you're not utilizing?

 

If it's old license that you want to hide please hang tight as we'll have a feature to hide servers Soon™️ (can't provide time frame yet).

 

But if it's a bug please contact support via [email protected] and provide the USB Flash GUID(s) in question, screenshot of your dashboard, and any other details you see as important so we can take a closer look.

This server was running on an old USB flash in a trial period. Then I bought a new USB flash, transferred the backup to it and activated the license for the new USB flash

Do I need to download a registration key? And point to the server? But on the server the license is already activated for the new USB Flash

Spoiler

 

[Not Connected to Mothership]

15 hours ago, zspearmint said:

We've identified a potential cause for the issue and are working on a fix.

Ty

I have the same problem after purchasing the Basic version

And is it possible to somehow remove the old server from the list? Leave only new, with a license?

[[Support] binhex - rTorrentVPN]

What's happening? Deluge and uTorrent work well

I'm behind a NAT provider. Gray IP. So with all rtorrent clients.
VPN is on the router

[[Plugin] rclone]

Not install

Video