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


Recommended Posts

5 hours ago, bluer said:

Yes, I did, but it doesn't seem to make any difference. I even reinstalled Unraid before, and it's the same. So I wonder if I need to config somewhere.

 

I also mounted a NFS foler, they were all mounted to paths like this:

/mnt/disks/192.168.x.x_{directory name}

/mnt/disks/{disk name}

Those are the correct mount points.  So what is the problem you are having?

Link to comment
5 hours ago, dlandon said:

Those are the correct mount points.  So what is the problem you are having?

Sorry for not clarifying the problem. I want to visit the paths from Windows 10, just like the other Unraid shared folder:

\\Tower\{disk name}.

Link to comment
1 hour ago, bluer said:

Sorry for not clarifying the problem. I want to visit the paths from Windows 10, just like the other Unraid shared folder:

\\Tower\{disk name}.

Go to the UD settings and enable SMB security and set the permissions you want for the users.  Turn on the 'Share' switch in UD for the device you want to share.  It might take two or three minutes to show at \\Tower\ because of the SMB refresh time of Unraid.

Link to comment

Hello all!

I have a strange issue I cannot solve by myself, after trying all that came into my mind..

Here is the setup:

Unraid 6.8.3

Unassigned device: latest version as of today (not related to the latest version, as you can see in the last attached picture the issue is also with a file dated January 2020)

The PC can boot Unraid or Windows 10 (latest version, latest patches as of today)

Unraid has a VM, Mac OS Catalina 10.15.4 (updated as of today)

 

I use Unassigned devices to mount a disk (SATA connected) to be usuable inside the virtual machine (smb transfers).

The disk is sde, with the sde1 ntfs partition:

 

CATTURA6.thumb.PNG.b4c6fcf2ece22ab59f151207971ed06f.PNG

 

The issue:

From the virtual machine all is working good: I can transfer files to the disk, from the disk, rename, delete, etc

The problem is when I boot into Windows 10:

1- I cannot copy/cut files transferred with unassigned devices from that harddrive to main C:\ (including via cmd with elevated privileges), by drag and drop, copy/cut menus

2- I cannot copy/cut files transferred with unassigned devices from that harddrive to main C:\ by accessing the external harddrive over network (the drive is shared)

3- I can rename files

4- I can delete files

5- I can zip (archive) files

6- I can open files

 

So it seems I'm not able to "only" copy/cut files.

 

Here is an example:

The problematic HD is a western digital green.

In this example I have a folder D:\HD_DANIELE\LAVORO\CI CF Patente\

Inside this folder there are 2 files: Patente.pdf and CI_CF_Daniel.pdf

 

Patente.pdf can be copied to main C:\, CI_CF_Daniel.pdf not.

When I try to copy CI_CF_Daniel.pdf I get this error:

 

Cattura1.thumb.PNG.a023fbd34719240d441c8cd0e8678f6e.PNG

 

Translated: filename not valid or too long, specify another filename.

 

What I tried:

1- run scandisk (chkdsk /r) to check for damaged sectors: all is ok, smart status is also ok

2- rename into windows 10 the file CI_CF_Daniel.pdf to Patente.pdf: however I can't copy/move

 

It seems a problem of permissions, but as far as I can see CI_CF_Daniel.pdf has proper permissions:

 

Cattura2.PNG.4b79b817d8df5476920740a0fb677ea5.PNG

 

Cattura3.PNG.7cd32810474bdabac54f66f95adb9d03.PNG

 

Cattura4.thumb.PNG.2df4f94336d4da1ae083cbf84a19ede7.PNG

 

Cattura5.png.3ff5ebffb6a633beeaab22f5ce9e4e5d.png

 

I'm really lost now, and I cannot understand what is causing the issue.

Any tip will be much much much appreciated ;)

 

Thanks

Edited by ghost82
Link to comment
20 hours ago, dlandon said:

Go to the UD settings and enable SMB security and set the permissions you want for the users.  Turn on the 'Share' switch in UD for the device you want to share.  It might take two or three minutes to show at \\Tower\ because of the SMB refresh time of Unraid.

I did what you told me, and visit \\Tower use the username "bluer", but I still cannot see those mounted disks. Below are my setting:

 

System Samba setting:

Picpick_0404_000.thumb.jpg.de6a7437d9e8053d957a6c37a96d2296.jpg

 

UD setting:

Picpick_0404_001.thumb.jpg.58fa2592fddfdf4073061a311e10e6ae.jpg

 

UD disks:

Picpick_0404_004.thumb.jpg.5d4ca217c0e61c1a35593486ccda84c6.jpg

 

mounted disks:

Picpick_0404_002.jpg.ed4097558be74ba294d71029cb037ff8.jpg

 

samba share in Windows 10 (log in with username "bluer")

Picpick_0404_003.thumb.jpg.95942c4d265593ca319e0c3bd3c9c12f.jpg

 

Thank you very much.

Link to comment
32 minutes ago, bluer said:

I did what you told me, and visit \\Tower use the username "bluer", but I still cannot see those mounted disks. Below are my setting:

Try to access the share directly to see if it is a SMB share issue or a browsing issue:

 

\\Tower\ShareName

Link to comment
37 minutes ago, dlandon said:

Try to access the share directly to see if it is a SMB share issue or a browsing issue:

 

\\Tower\ShareName

I visit the path \\Tower\ShareName, and a pop-up window prompts for username and passwords.

 

after that it reminds me that Windows cannot visit \\Tower\ShareName.

 

Picpick_0404_001.jpg.deb5e022e99cd6224b2a77b3b9970e06.jpg

 

Picpick_0404_002.jpg.a56b6f7f5145a4ffdbb3c582bd53a15d.jpg

Link to comment
1 hour ago, bluer said:

I visit the path \\Tower\ShareName, and a pop-up window prompts for username and passwords.

 

after that it reminds me that Windows cannot visit \\Tower\ShareName.

It's hard for me to follow when the screens are not in English.  Is the problem from invalid credentials or something else?  Translate the error dialog.

 

You might also try Windows troubleshooting and see if something comes out of that.

 

I suspect a Windows issue.  I don't have any problems with SMB sharing.

Link to comment
Apr  5 06:54:30 MIKESDESKTOP unassigned.devices: Error: shell_exec(/usr/bin/lsof '/mnt/disks/ADATA_120GB' 2>/dev/null | /bin/sort -k8 | /bin/uniq -f7 | /bin/grep -c -e REG) took longer than 5s!
Apr  5 06:54:36 MIKESDESKTOP unassigned.devices: Error: shell_exec(/bin/df '/mnt/disks/192.168.1.98_Music' --output=size,used,avail | /bin/grep -v '1K-blocks' > /tmp/unassigned.devices/df 2>/dev/null) took longer than 2s!
Apr  5 06:54:38 MIKESDESKTOP unassigned.devices: Error: shell_exec(/bin/df '/mnt/disks/192.168.1.98_Video' --output=size,used,avail | /bin/grep -v '1K-blocks' > /tmp/unassigned.devices/df 2>/dev/null) took longer than 2s!
Apr  5 06:54:40 MIKESDESKTOP unassigned.devices: Error: shell_exec(/bin/df '/mnt/disks/192.168.1.98_Downloads' --output=size,used,avail | /bin/grep -v '1K-blocks' > /tmp/unassigned.devices/df 2>/dev/null) took longer than 2s!
Apr  5 06:54:42 MIKESDESKTOP unassigned.devices: Error: shell_exec(/bin/df '/mnt/disks/192.168.1.98_Files' --output=size,used,avail | /bin/grep -v '1K-blocks' > /tmp/unassigned.devices/df 2>/dev/null) took longer than 2s!
Apr  5 07:07:17 MIKESDESKTOP rpcbind[27849]: connect from 127.0.0.1 to getport/addr(status)
Apr  5 07:28:45 MIKESDESKTOP unassigned.devices: Error: shell_exec(/usr/bin/lsof '/mnt/disks/ADATA_120GB' 2>/dev/null | /bin/sort -k8 | /bin/uniq -f7 | /bin/grep -c -e REG) took longer than 5s!
Apr  5 07:28:50 MIKESDESKTOP unassigned.devices: Error: shell_exec(/usr/bin/lsof '/mnt/disks/ADATA_1TB' 2>/dev/null | /bin/sort -k8 | /bin/uniq -f7 | /bin/grep -c -e REG) took longer than 5s!
Apr  5 07:28:52 MIKESDESKTOP unassigned.devices: Error: shell_exec(/bin/df '/mnt/disks/192.168.1.98_Music' --output=size,used,avail | /bin/grep -v '1K-blocks' > /tmp/unassigned.devices/df 2>/dev/null) took longer than 2s!
Apr  5 07:28:54 MIKESDESKTOP unassigned.devices: Error: shell_exec(/bin/df '/mnt/disks/192.168.1.98_Video' --output=size,used,avail | /bin/grep -v '1K-blocks' > /tmp/unassigned.devices/df 2>/dev/null) took longer than 2s!
Apr  5 08:16:53 MIKESDESKTOP unassigned.devices: Error: shell_exec(/usr/bin/lsof '/mnt/disks/ADATA_120GB' 2>/dev/null | /bin/sort -k8 | /bin/uniq -f7 | /bin/grep -c -e REG) took longer than 5s!
Apr  5 08:16:58 MIKESDESKTOP unassigned.devices: Error: sh

Im getting these errors above and I was wondering what could be causing them and id they are serious errors 

 

also added diagnostics just in case

 

 

mikesdesktop-diagnostics-20200405-0817.zip

Link to comment
21 minutes ago, Wavey said:

Apr  5 06:54:30 MIKESDESKTOP unassigned.devices: Error: shell_exec(/usr/bin/lsof '/mnt/disks/ADATA_120GB' 2>/dev/null | /bin/sort -k8 | /bin/uniq -f7 | /bin/grep -c -e REG) took longer than 5s!
Apr  5 06:54:36 MIKESDESKTOP unassigned.devices: Error: shell_exec(/bin/df '/mnt/disks/192.168.1.98_Music' --output=size,used,avail | /bin/grep -v '1K-blocks' > /tmp/unassigned.devices/df 2>/dev/null) took longer than 2s!
Apr  5 06:54:38 MIKESDESKTOP unassigned.devices: Error: shell_exec(/bin/df '/mnt/disks/192.168.1.98_Video' --output=size,used,avail | /bin/grep -v '1K-blocks' > /tmp/unassigned.devices/df 2>/dev/null) took longer than 2s!
Apr  5 06:54:40 MIKESDESKTOP unassigned.devices: Error: shell_exec(/bin/df '/mnt/disks/192.168.1.98_Downloads' --output=size,used,avail | /bin/grep -v '1K-blocks' > /tmp/unassigned.devices/df 2>/dev/null) took longer than 2s!
Apr  5 06:54:42 MIKESDESKTOP unassigned.devices: Error: shell_exec(/bin/df '/mnt/disks/192.168.1.98_Files' --output=size,used,avail | /bin/grep -v '1K-blocks' > /tmp/unassigned.devices/df 2>/dev/null) took longer than 2s!
Apr  5 07:07:17 MIKESDESKTOP rpcbind[27849]: connect from 127.0.0.1 to getport/addr(status)
Apr  5 07:28:45 MIKESDESKTOP unassigned.devices: Error: shell_exec(/usr/bin/lsof '/mnt/disks/ADATA_120GB' 2>/dev/null | /bin/sort -k8 | /bin/uniq -f7 | /bin/grep -c -e REG) took longer than 5s!
Apr  5 07:28:50 MIKESDESKTOP unassigned.devices: Error: shell_exec(/usr/bin/lsof '/mnt/disks/ADATA_1TB' 2>/dev/null | /bin/sort -k8 | /bin/uniq -f7 | /bin/grep -c -e REG) took longer than 5s!
Apr  5 07:28:52 MIKESDESKTOP unassigned.devices: Error: shell_exec(/bin/df '/mnt/disks/192.168.1.98_Music' --output=size,used,avail | /bin/grep -v '1K-blocks' > /tmp/unassigned.devices/df 2>/dev/null) took longer than 2s!
Apr  5 07:28:54 MIKESDESKTOP unassigned.devices: Error: shell_exec(/bin/df '/mnt/disks/192.168.1.98_Video' --output=size,used,avail | /bin/grep -v '1K-blocks' > /tmp/unassigned.devices/df 2>/dev/null) took longer than 2s!
Apr  5 08:16:53 MIKESDESKTOP unassigned.devices: Error: shell_exec(/usr/bin/lsof '/mnt/disks/ADATA_120GB' 2>/dev/null | /bin/sort -k8 | /bin/uniq -f7 | /bin/grep -c -e REG) took longer than 5s!
Apr  5 08:16:58 MIKESDESKTOP unassigned.devices: Error: sh

Im getting these errors above and I was wondering what could be causing them and id they are serious errors 

 

also added diagnostics just in case

 

 

mikesdesktop-diagnostics-20200405-0817.zip 228.81 kB · 0 downloads

You are running out of memory:

Apr  5 03:29:05 MIKESDESKTOP kernel: CPU: 2 PID: 9741 Comm: mono Tainted: P           O      4.19.107-Unraid #1
Apr  5 03:29:05 MIKESDESKTOP kernel: Hardware name: Supermicro PIO-617R-TLN4F+-ST031/X9DRi-LN4+/X9DR3-LN4+, BIOS 3.2 03/04/2015
Apr  5 03:29:05 MIKESDESKTOP kernel: Call Trace:
Apr  5 03:29:05 MIKESDESKTOP kernel: dump_stack+0x67/0x83
Apr  5 03:29:05 MIKESDESKTOP kernel: dump_header+0x66/0x289
Apr  5 03:29:05 MIKESDESKTOP kernel: oom_kill_process+0x9d/0x220
Apr  5 03:29:05 MIKESDESKTOP kernel: out_of_memory+0x3b7/0x3ea
Apr  5 03:29:05 MIKESDESKTOP kernel: mem_cgroup_out_of_memory+0x94/0xc8
Apr  5 03:29:05 MIKESDESKTOP kernel: try_charge+0x52a/0x682
Apr  5 03:29:05 MIKESDESKTOP kernel: ? __alloc_pages_nodemask+0x150/0xae1
Apr  5 03:29:05 MIKESDESKTOP kernel: mem_cgroup_try_charge+0x115/0x158
Apr  5 03:29:05 MIKESDESKTOP kernel: __add_to_page_cache_locked+0x73/0x184
Apr  5 03:29:05 MIKESDESKTOP kernel: add_to_page_cache_lru+0x47/0xd5
Apr  5 03:29:05 MIKESDESKTOP kernel: filemap_fault+0x238/0x47c
Apr  5 03:29:05 MIKESDESKTOP kernel: __do_fault+0x4d/0x88
Apr  5 03:29:05 MIKESDESKTOP kernel: __handle_mm_fault+0xdb5/0x11b7
Apr  5 03:29:05 MIKESDESKTOP kernel: handle_mm_fault+0x189/0x1e3
Apr  5 03:29:05 MIKESDESKTOP kernel: __do_page_fault+0x267/0x3ff
Apr  5 03:29:05 MIKESDESKTOP kernel: ? page_fault+0x8/0x30
Apr  5 03:29:05 MIKESDESKTOP kernel: page_fault+0x1e/0x30
Apr  5 03:29:05 MIKESDESKTOP kernel: RIP: 0033:0x14b61a22efa0
Apr  5 03:29:05 MIKESDESKTOP kernel: Code: Bad RIP value.
Apr  5 03:29:05 MIKESDESKTOP kernel: RSP: 002b:000014b6047eca98 EFLAGS: 00010206
Apr  5 03:29:05 MIKESDESKTOP kernel: RAX: 0000000000000001 RBX: 0000000000000508 RCX: 000000000000185d
Apr  5 03:29:05 MIKESDESKTOP kernel: RDX: 0000000000000002 RSI: 0000000000000000 RDI: 000014b607acde28
Apr  5 03:29:05 MIKESDESKTOP kernel: RBP: 0000000000000000 R08: 0000000000000002 R09: 000014b5f56353b1
Apr  5 03:29:05 MIKESDESKTOP kernel: R10: 000014b6047ecd30 R11: 000000000000001b R12: 00000000000027b3
Apr  5 03:29:05 MIKESDESKTOP kernel: R13: 0000000000000002 R14: 000014b5ec5d49d0 R15: 000014b5f5625af8
Apr  5 03:29:05 MIKESDESKTOP kernel: Task in /docker/a469741e4e9d3605e94e76b94b3d968cfbaafe31bcd4dc0499b6764523f21eab killed as a result of limit of /docker/a469741e4e9d3605e94e76b94b3d968cfbaafe31bcd4dc0499b6764523f21eab
Apr  5 03:29:05 MIKESDESKTOP kernel: memory: usage 1048576kB, limit 1048576kB, failcnt 4331854
Apr  5 03:29:05 MIKESDESKTOP kernel: memory+swap: usage 1048576kB, limit 2097152kB, failcnt 0
Apr  5 03:29:05 MIKESDESKTOP kernel: kmem: usage 28720kB, limit 9007199254740988kB, failcnt 0
Apr  5 03:29:05 MIKESDESKTOP kernel: Memory cgroup stats for /docker/a469741e4e9d3605e94e76b94b3d968cfbaafe31bcd4dc0499b6764523f21eab: cache:9144KB rss:1012216KB rss_huge:2048KB shmem:0KB mapped_file:2640KB dirty:1056KB writeback:1188KB swap:0KB inactive_anon:4KB active_anon:1012424KB inactive_file:4196KB active_file:3104KB unevictable:0KB
Apr  5 03:29:05 MIKESDESKTOP kernel: Tasks state (memory values in pages):
Apr  5 03:29:05 MIKESDESKTOP kernel: [  pid  ]   uid  tgid total_vm      rss pgtables_bytes swapents oom_score_adj name
Apr  5 03:29:05 MIKESDESKTOP kernel: [  16125]     0 16125       51        1    24576        0             0 s6-svscan
Apr  5 03:29:05 MIKESDESKTOP kernel: [  16245]     0 16245       51        1    24576        0             0 s6-supervise
Apr  5 03:29:05 MIKESDESKTOP kernel: [  22539]     0 22539       51        1    24576        0             0 s6-supervise
Apr  5 03:29:05 MIKESDESKTOP kernel: [   8530]    99  8530  4367132   249608  5468160        0             0 mono
Apr  5 03:29:05 MIKESDESKTOP kernel: Memory cgroup out of memory: Kill process 8530 (mono) score 957 or sacrifice child
Apr  5 03:29:05 MIKESDESKTOP kernel: Killed process 8530 (mono) total-vm:17468528kB, anon-rss:998428kB, file-rss:0kB, shmem-rss:4kB

The messages are not a big issue, but running out of memory is a problem.

Link to comment
52 minutes ago, Wavey said:

Ahhhh thanks! Didn’t think I’d run out of 32gb but I’ve been putting some new dockers up so I’ll limit them, thanks. 

The dockers themselves aren't that big an issue, but one that is misconfigured could end up consuming a lot of memory.

  • Like 1
Link to comment

Have created a share in UD, but it does not show across the network (neither on another unRAID machine as a SMB share, nor in Windows).

Have noticed (in Krusader) that when the device is mounted, everything shows fine in the unassigned directory, but /mnt/disks is not populated

(only shows mount point without any directories or contents*)...

When attempting to use the share, no 3rd party software is involved. Setting the eSATA drive to "share" does not show the share across the network.

(not shown in unassigned devices on other machine in "add SMB share" or in Windows Explorer)

(version 2019.12.15)

 

*unassigned directory is a container path, specified to be, "/mnt/disks" that displays the unassigned devices (directly);

whereas viewing "/mnt/disks" via "unRAID" and "drilling down" (vs. unassigned path) DOES NOT SHOW CONTENTS (directories, media, etc.)

Theoretically, not a possibility, but that is what is being displayed as opposed to every other [working] share where the displays match (when mounted).

 

An inspection of the unRAID log shows that "eSATA" (mount point) has SMB share enabled (but is dysfunctional as described)

Diagnostics have been attached.

 

tower-diagnostics-20200407-1631.zip

Edited by CaryV
Link to comment

Resolved the display of "/mnt/disks"; Share still not functional (non-existent across network).

 

Although I had rebooted the system before, this time it was done with "auto-mount" in effect (and of course, "share" is enabled).

(No security is in effect; nor has it been used on SMB shares.)

This corrected the differences in content displayed in Krusader, however, it did not resolve the sharing dysfunction.

 

B.T.W.  Ownership and permissions have been checked and are all normal for the shared device.

 

Link to comment
4 hours ago, CaryV said:

Resolved the display of "/mnt/disks"; Share still not functional (non-existent across network).

 

Although I had rebooted the system before, this time it was done with "auto-mount" in effect (and of course, "share" is enabled).

(No security is in effect; nor has it been used on SMB shares.)

This corrected the differences in content displayed in Krusader, however, it did not resolve the sharing dysfunction.

 

B.T.W.  Ownership and permissions have been checked and are all normal for the shared device.

 

Please update to the latest version of UD.  Then do the following.

 

Your smb-extra.conf file is this:

#unassigned_devices_start
#unassigned_devices_end

include = /etc/samba/unassigned-shares/HEADLESS_media.conf
#vfs_recycle_start
#Recycle bin configuration
[global]
   syslog only = Yes
   log level = 0 vfs:0
#vfs_recycle_end

Please change to this:

#vfs_recycle_start
#Recycle bin configuration
[global]
   syslog only = No
   log level = 0 vfs:0
#vfs_recycle_end
#unassigned_devices_start
#Unassigned devices share includes
   include = /tmp/unassigned.devices/smb-settings.conf
#unassigned_devices_end

 

Link to comment
5 hours ago, dlandon said:

Please update to the latest version of UD.  Then do the following.

 

Your smb-extra.conf file is this:


#unassigned_devices_start
#unassigned_devices_end

include = /etc/samba/unassigned-shares/HEADLESS_media.conf
#vfs_recycle_start
#Recycle bin configuration
[global]
   syslog only = Yes
   log level = 0 vfs:0
#vfs_recycle_end

Please change to this:


#vfs_recycle_start
#Recycle bin configuration
[global]
   syslog only = No
   log level = 0 vfs:0
#vfs_recycle_end
#unassigned_devices_start
#Unassigned devices share includes
   include = /tmp/unassigned.devices/smb-settings.conf
#unassigned_devices_end

 

That worked fine, thanks.

In fact, all of the SMB shares (from other systems) being utilized on the system with the eSATA share that needed rectified

now also appear in Windows - due to all inclusions (in smb-settings.conf) now being referenced.

Is there anything that I need to be aware of as to why the smb-extra.conf file didn't get updated?

 

Link to comment

Good evening, I have the following problem.
I would like to integrate my SMB share coming from my Sysnology NAS into unRaid. I had read that this is possible with this plugin.

Reaching and investing works, but I cannot mount it. So I can't get it into my array.

The user in Synology has full admin rights for the test, but it just doesn't work.

I hope you can help me along with that.

Regards Maggi

Link to comment
14 minutes ago, Maggi0r said:

Oh that was quick. I assume you mean the diagnosis zip file. Sorry I'm still new to unRaid.

Regards Maggi

As another relative newbie (almost a year now) to unRAID, I'm trying to help give back a little to the community. This is my 1st stab at sorting through someone else's syslog diagnostics, so I might be off base but this is what I found:

 

Quote

Apr  8 15:00:44 Tower unassigned.devices: Remote SMB/NFS mount '//192.168.1.13/storj' is not set to auto mount and will not be mounted.
Apr  8 15:00:45 Tower kernel: eth0: renamed from vethe8bc072
Apr  8 15:00:45 Tower kernel: device br0 entered promiscuous mode
Apr  8 15:00:46 Tower rc.docker: iobroker: started succesfully!
Apr  8 15:00:50 Tower kernel: eth0: renamed from veth25f1a18
Apr  8 15:00:51 Tower rc.docker: pihole-template: started succesfully!
Apr  8 15:00:53 Tower kernel: eth0: renamed from vethc171f31
Apr  8 15:00:56 Tower rc.docker: Portainer: started succesfully!
Apr  8 15:01:01 Tower kernel: eth0: renamed from veth92940e8
Apr  8 15:01:03 Tower rc.docker: unifi-controller: started succesfully!
Apr  8 15:04:06 Tower ntpd[1680]: kernel reports TIME_ERROR: 0x41: Clock Unsynchronized
Apr  8 15:10:00 Tower root: Fix Common Problems Version 2020.03.18
Apr  8 15:10:01 Tower root: Fix Common Problems: Warning: disk2 (OCZ-VERTEX3_OCZ-2AX8ITI487T12VZD) is an SSD.
Apr  8 15:27:07 Tower unassigned.devices: Removing configuration '//192.168.1.13/storj'.

 

As it looks like your Synology is at 192.168.1.13/storj, it doesn't appear to show a login attempt as it's not set to auto-mount. Either try a manual mount or set it to automount, then refresh UD and resend the diagnostics so we can see a login attempt.

 

Edited by AgentXXL
spelling
Link to comment
  • trurl pinned this topic

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.

Guest
Reply to this topic...

×   Pasted as rich text.   Restore formatting

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.