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


Recommended Posts

9 hours ago, Squirreljester said:

 

Network is fine, everything else on the network is working without issue or error.

Friend is able to connect to and play a game on my server hosted on unraid.

People can connect to my Plex hosted on unraid, media streams without issues, and movies with the source files on my Synology play through Plex fine.

 

What you posted was from April third where I rebooted all my network equipment to try and fix this issue.

 

This indicates nothing is set to be shared if in fact you have some UD devices mounted:

Apr 30 06:33:53 Weechflix unassigned.devices: Updating share settings...
Apr 30 06:33:53 Weechflix unassigned.devices: Share settings updated.

In Settings->UD Settings, you'll need to have SMB set to something besides 'Disabled'.  SMB needs to be enabled in Settings->SMB, and the share switch needs to be on for each UD device you want to share.

 

Test the configuration by unmounting a remote share, then mount the share and look at the log to see if UD enabled the SMB share.  If something is not properly set up for sharing, you'll see a log message indicating what is not set.

Link to comment

New release of UD.  Highlights:

  • Added a 'Read Only' switch to remote shares so they can be mounted read only.
  • Fixed special character handling of iso file names that was causing the endless Unraid wave.
  • Some cleanup on remote shares to align text in the table for better readability.
  • Text box for NFS rules so multiple rules can be set for each device.
  • Default force user nobody to 'No' on SMB shares.
  • Some protections to prevent blank serial number or device entries in the config files.
  • Fixed the situation where the same devX name in Historical devices would only show one device.  Two devices with the same default devX name is valid and is changed as necessary when the device is reinstalled or attached.  Unraid fixes the devX designation so each active device has a unique designation.

As stated earlier, if you see the endless Unraid Wave, delete the /flash/config/plugins/unassigned.devices/iso_mount.cfg file, click on the double arrows at the upper right of the UD page, and re-enter your iso shares.

Link to comment

Since that update the device script for my backup drive won't run anymore. 

 

The GUI shows the Mount button so it seems it doesn't automount. Tried toggling automount off and back on and doing a reload of the UD config.

log.txt

Edited by Kilrah
Link to comment

Hello I'm unable to mount my Synology 918+ share via SMB3/2 to my unraid, I've tried mounting it with IP only, local DNS name, changed password to have no special characters, it will still not mount. Any help is appreciated.
*NFS works fine.
*The same share works fine on windows or mac, so UD is the only one that can't mount it.

 

May  1 17:42:24 Loki kernel: CIFS: Attempting to mount \\172.18.108.100\Unraid
May  1 17:42:34 Loki unassigned.devices: Warning: shell_exec(/sbin/mount -t 'cifs' -o rw,noserverino,nounix,iocharset=utf8,file_mode=0777,dir_mode=0777,uid=99,gid=100,credentials='/tmp/unassigned.devices/credentials_Unraid' '//172.18.108.100/Unraid' '/mnt/remotes/172.18.108.100_Unraid' 2>&1) took longer than 10s!
May  1 17:42:34 Loki kernel: CIFS: VFS: \\172.18.108.100 Send error in SessSetup = -512
May  1 17:42:34 Loki kernel: CIFS: VFS: cifs_mount failed w/return code = -512
May  1 17:42:34 Loki unassigned.devices: SMB default protocol mount failed: 'command timed out'.
May  1 17:42:34 Loki unassigned.devices: Mount SMB share '//172.18.108.100/Unraid' using SMB 3.1.1 protocol.
May  1 17:42:34 Loki unassigned.devices: Mount SMB command: /sbin/mount -t cifs -o rw,noserverino,nounix,iocharset=utf8,file_mode=0777,dir_mode=0777,uid=99,gid=100,vers=3.1.1,credentials='/tmp/unassigned.devices/credentials_Unraid' '//172.18.108.100/Unraid' '/mnt/remotes/172.18.108.100_Unraid'
May  1 17:42:34 Loki kernel: CIFS: Attempting to mount \\172.18.108.100\Unraid
May  1 17:42:44 Loki kernel: CIFS: VFS: \\172.18.108.100 Send error in SessSetup = -512
May  1 17:42:44 Loki kernel: CIFS: VFS: cifs_mount failed w/return code = -512
May  1 17:42:44 Loki unassigned.devices: Warning: shell_exec(/sbin/mount -t cifs -o rw,noserverino,nounix,iocharset=utf8,file_mode=0777,dir_mode=0777,uid=99,gid=100,vers=3.1.1,credentials='/tmp/unassigned.devices/credentials_Unraid' '//172.18.108.100/Unraid' '/mnt/remotes/172.18.108.100_Unraid' 2>&1) took longer than 10s!
May  1 17:42:44 Loki unassigned.devices: SMB 3.1.1 mount failed: 'command timed out'.
May  1 17:42:44 Loki unassigned.devices: Mount SMB share '//172.18.108.100/Unraid' using SMB 3.0 protocol.
May  1 17:42:44 Loki unassigned.devices: Mount SMB command: /sbin/mount -t cifs -o rw,noserverino,nounix,iocharset=utf8,file_mode=0777,dir_mode=0777,uid=99,gid=100,vers=3.0,credentials='/tmp/unassigned.devices/credentials_Unraid' '//172.18.108.100/Unraid' '/mnt/remotes/172.18.108.100_Unraid'
May  1 17:42:44 Loki kernel: CIFS: Attempting to mount \\172.18.108.100\Unraid
May  1 17:42:54 Loki kernel: CIFS: VFS: \\172.18.108.100 Send error in SessSetup = -512
May  1 17:42:54 Loki kernel: CIFS: VFS: cifs_mount failed w/return code = -512
May  1 17:42:54 Loki unassigned.devices: Warning: shell_exec(/sbin/mount -t cifs -o rw,noserverino,nounix,iocharset=utf8,file_mode=0777,dir_mode=0777,uid=99,gid=100,vers=3.0,credentials='/tmp/unassigned.devices/credentials_Unraid' '//172.18.108.100/Unraid' '/mnt/remotes/172.18.108.100_Unraid' 2>&1) took longer than 10s!
May  1 17:42:54 Loki unassigned.devices: SMB 3.0 mount failed: 'command timed out'.
May  1 17:42:54 Loki unassigned.devices: Mount SMB share '//172.18.108.100/Unraid' using SMB 2.0 protocol.
May  1 17:42:54 Loki unassigned.devices: Mount SMB command: /sbin/mount -t 'cifs' -o rw,noserverino,nounix,iocharset=utf8,file_mode=0777,dir_mode=0777,uid=99,gid=100,vers=2.0,credentials='/tmp/unassigned.devices/credentials_Unraid' '//172.18.108.100/Unraid' '/mnt/remotes/172.18.108.100_Unraid'
May  1 17:42:54 Loki kernel: CIFS: Attempting to mount \\172.18.108.100\Unraid
May  1 17:43:04 Loki kernel: CIFS: VFS: \\172.18.108.100 Send error in SessSetup = -512
May  1 17:43:04 Loki kernel: CIFS: VFS: cifs_mount failed w/return code = -512
May  1 17:43:04 Loki unassigned.devices: Warning: shell_exec(/sbin/mount -t 'cifs' -o rw,noserverino,nounix,iocharset=utf8,file_mode=0777,dir_mode=0777,uid=99,gid=100,vers=2.0,credentials='/tmp/unassigned.devices/credentials_Unraid' '//172.18.108.100/Unraid' '/mnt/remotes/172.18.108.100_Unraid' 2>&1) took longer than 10s!
May  1 17:43:04 Loki unassigned.devices: SMB 2.0 mount failed: 'command timed out'.
May  1 17:43:04 Loki unassigned.devices: Mount SMB share '//172.18.108.100/Unraid' using SMB 1.0 protocol.
May  1 17:43:04 Loki unassigned.devices: Mount SMB command: /sbin/mount -t 'cifs' -o rw,noserverino,nounix,iocharset=utf8,file_mode=0777,dir_mode=0777,uid=99,gid=100,vers=1.0,credentials='/tmp/unassigned.devices/credentials_Unraid' '//172.18.108.100/Unraid' '/mnt/remotes/172.18.108.100_Unraid'
May  1 17:43:04 Loki kernel: Use of the less secure dialect vers=1.0 is not recommended unless required for access to very old servers
May  1 17:43:04 Loki kernel: 
May  1 17:43:04 Loki kernel: CIFS: VFS: Use of the less secure dialect vers=1.0 is not recommended unless required for access to very old servers
May  1 17:43:04 Loki kernel: CIFS: Attempting to mount \\172.18.108.100\Unraid
May  1 17:43:04 Loki kernel: CIFS: VFS: cifs_mount failed w/return code = -95
May  1 17:43:04 Loki unassigned.devices: SMB 1.0 mount failed: 'mount error(95): Operation not supported Refer to the mount.cifs(8) manual page (e.g. man mount.cifs) and kernel log messages (dmesg) '

 

Link to comment
2 hours ago, ailliano said:
May  1 17:42:44 Loki unassigned.devices: Warning: shell_exec(/sbin/mount -t cifs -o rw,noserverino,nounix,iocharset=utf8,file_mode=0777,dir_mode=0777,uid=99,gid=100,vers=3.1.1,credentials='/tmp/unassigned.devices/credentials_Unraid' '//172.18.108.100/Unraid' '/mnt/remotes/172.18.108.100_Unraid' 2>&1) took longer than 10s!

Your server is not responding to a mount command, or it is taking too long.  Is port 445 open to your remote server?  It looks like you are accessing the remote server through the Internet.  Check with your Internet provider to be sure it's not being blocked.  Hopefully you are using a VPN to connect the two servers.

 

Did you let UD search for the remote shares on that server or set it up manually?  You should set up the remote share using the IP address for the server, then let UD find the available shares.  If you don't get a list of the shares, port 445 is probably not open.

Link to comment
On 4/29/2023 at 9:46 PM, BrazMan said:

Hi @dlandon

 

Thanks again for the support!

 

I turn off the UD debugging.

 

I will share the prints i have in my system.

 

Surprisingly the last time i reboot the system all goes well. I do not if takes some time for unraid "find" the other PC in my network.

 

I will monitor this and keep all logs if happens again, i will post.

 

Thanks!

Braz.  

 

 

 

 

smb settings.png

nfs settings.png

UD2.png

UD1.png

After Reboot automount was unable to mount my share

 

Here the diagnostics. Running unraid 6.11.5.

share.png

u-rjo21-diagnostics-20230501-2132.zip

Link to comment
6 minutes ago, BrazMan said:

After Reboot automount was unable to mount my share

 

It looks like you are using NFSv3 that is not supported on your remote server:

May  1 21:32:22 U-RJO21 unassigned.devices: Mount NFS command: /sbin/mount -t 'nfs' -o rw,noacl 'U-NAS23:/mnt/user/data' '/mnt/remotes/U-NAS23_data'
May  1 21:32:22 U-RJO21 rc.docker: ApacheGuacamole: started succesfully!
May  1 21:32:23 U-RJO21 kernel: br-3a5431a8c481: port 2(vethf665a10) entered blocking state
May  1 21:32:23 U-RJO21 kernel: br-3a5431a8c481: port 2(vethf665a10) entered disabled state
May  1 21:32:23 U-RJO21 kernel: device vethf665a10 entered promiscuous mode
May  1 21:32:23 U-RJO21 kernel: mdcmd (38): nocheck pause
May  1 21:32:23 U-RJO21 kernel: md: recovery thread: exit status: -4
May  1 21:32:25 U-RJO21 unassigned.devices: NFS mount failed: 'mount.nfs: requested NFS version or transport protocol is not supported '.

Go to Settings->Unassigned Devices and set NFSv4 protocol and try to mount it.

Link to comment
38 minutes ago, dlandon said:

 

It looks like you are using NFSv3 that is not supported on your remote server:

May  1 21:32:22 U-RJO21 unassigned.devices: Mount NFS command: /sbin/mount -t 'nfs' -o rw,noacl 'U-NAS23:/mnt/user/data' '/mnt/remotes/U-NAS23_data'
May  1 21:32:22 U-RJO21 rc.docker: ApacheGuacamole: started succesfully!
May  1 21:32:23 U-RJO21 kernel: br-3a5431a8c481: port 2(vethf665a10) entered blocking state
May  1 21:32:23 U-RJO21 kernel: br-3a5431a8c481: port 2(vethf665a10) entered disabled state
May  1 21:32:23 U-RJO21 kernel: device vethf665a10 entered promiscuous mode
May  1 21:32:23 U-RJO21 kernel: mdcmd (38): nocheck pause
May  1 21:32:23 U-RJO21 kernel: md: recovery thread: exit status: -4
May  1 21:32:25 U-RJO21 unassigned.devices: NFS mount failed: 'mount.nfs: requested NFS version or transport protocol is not supported '.

Go to Settings->Unassigned Devices and set NFSv4 protocol and try to mount it.

Hi @dlandon

 

THX again for the support!

 

After reboot it takes about 2 minutes to mount but it worked.

 

I am posting the setup now on both servers.

 

Thank you very much!

 

Take care!

Braz.

 

 

finalsetting.png

Edited by BrazMan
English corrections
Link to comment
10 hours ago, BrazMan said:

After reboot it takes about 2 minutes to mount but it worked.

UD waits for up to two minutes for the network to become available before trying to mount remote shares.  This is to be sure the remote shares can be mounted.

  • Thanks 1
Link to comment
12 hours ago, dlandon said:

Your server is not responding to a mount command, or it is taking too long.  Is port 445 open to your remote server?  It looks like you are accessing the remote server through the Internet.  Check with your Internet provider to be sure it's not being blocked.  Hopefully you are using a VPN to connect the two servers.

 

Did you let UD search for the remote shares on that server or set it up manually?  You should set up the remote share using the IP address for the server, then let UD find the available shares.  If you don't get a list of the shares, port 445 is probably not open.

Server is on same subnet unraid 172.18.108.10 and Synology at 172.18.108.100, I tried with automatic search and IP option, shares load fine with both choices. 

Link to comment
8 minutes ago, ailliano said:

Server is on same subnet unraid 172.18.108.10 and Synology at 172.18.108.100, I tried with automatic search and IP option, shares load fine with both choices. 

Check on the Synology and see if there are settings that controls CIFS mounts.  I assume the Windows and Mac PCs were only browsing the shares and not mounting them with CIFS.

Link to comment
41 minutes ago, dlandon said:

Check on the Synology and see if there are settings that controls CIFS mounts.  I assume the Windows and Mac PCs were only browsing the shares and not mounting them with CIFS.

Anything out of the ordinary ? I never changed anything here and unraid always worked on previous versions.

Screenshot 2023-05-02 at 9.08.53 AM.png

Screenshot 2023-05-02 at 9.09.27 AM.png

Screenshot 2023-05-02 at 9.09.53 AM.png

Link to comment
On 4/30/2023 at 3:19 PM, dlandon said:

 

This indicates nothing is set to be shared if in fact you have some UD devices mounted:

Apr 30 06:33:53 Weechflix unassigned.devices: Updating share settings...
Apr 30 06:33:53 Weechflix unassigned.devices: Share settings updated.

In Settings->UD Settings, you'll need to have SMB set to something besides 'Disabled'.  SMB needs to be enabled in Settings->SMB, and the share switch needs to be on for each UD device you want to share.

 

Test the configuration by unmounting a remote share, then mount the share and look at the log to see if UD enabled the SMB share.  If something is not properly set up for sharing, you'll see a log message indicating what is not set.

 

They are shared because everything is accessible, I just can't see the shares to browse them in Windows explorer like I used to be able to.

 

SMB sharing is set to yes (workgroup) which shouldn't have changed from when it was working, and SMB is set to public in UD. Setting this to public fixed this issue the last time I had it, but it's already set to public.

I've set it to disabled, and then public again in UD, I've unmounted and re-mounted the shares on the main page, even rebooted both the server and the NAS.

 

I even looked on the Synology NAS, saw there was an update for SMB, updated it, and enabled SMB3. Then unmounted and re-mounted the shares in unraid. They still aren't showing up in Windows explorer.

Edited by Squirreljester
Link to comment
11 minutes ago, Squirreljester said:

 

They are shared because everything is accessible, I just can't see the shares to browse them in Windows explorer like I used to be able to.

 

SMB sharing is set to yes (workgroup) which shouldn't have changed from when it was working, and SMB is set to public in UD. Setting this to public fixed this issue the last time I had it, but it's already set to public.

I've set it to disabled, and then public again in UD, I've unmounted and re-mounted the shares on the main page, even rebooted both the server and the NAS.

 

I even looked on the Synology NAS, saw there was an update for SMB, updated it, and enabled SMB3. Then unmounted and re-mounted the shares in unraid. They still aren't showing up in Windows explorer.

Post diagnostics.

Link to comment
May  2 10:47:21 Weechflix unassigned.devices: Successfully mounted '//JESTER/Music' on '/mnt/remotes/JESTER_Music'.
May  2 10:47:21 Weechflix unassigned.devices: Device '//JESTER/Music' is not set to be shared.

 

Set the device share switch:

Screenshot 2023-05-02 175903.png

  • Thanks 1
Link to comment
27 minutes ago, dlandon said:
May  2 10:47:21 Weechflix unassigned.devices: Successfully mounted '//JESTER/Music' on '/mnt/remotes/JESTER_Music'.
May  2 10:47:21 Weechflix unassigned.devices: Device '//JESTER/Music' is not set to be shared.

 

Set the device share switch:

Screenshot 2023-05-02 175903.png

I turned on sharing on all 4 mounts and they are now showing up in my Windows explorer. I've never had to set those before, are these settings being reset when I update the plugin?

Link to comment
4 minutes ago, Squirreljester said:

I turned on sharing on all 4 mounts and they are now showing up in my Windows explorer. I've never had to set those before, are these settings being reset when I update the plugin?

What probably happened was the 'Share' default was changed to not share for security reasons.  If you've never changed the 'Share' switch, it would still be at the default.

Link to comment
1 hour ago, dlandon said:

What probably happened was the 'Share' default was changed to not share for security reasons.  If you've never changed the 'Share' switch, it would still be at the default.

I'll have to keep an eye on those settings after I update.

 

Thanks much for the help, very much appreciated.

Link to comment
2 hours ago, ailliano said:

Anything I can do in the Synology ? @dlandon

 

This is your issue:

May  1 17:42:54 Loki kernel: CIFS: VFS: cifs_mount failed w/return code = -512

 

SMB uses port 445, but CIFS also needs port 139.  Since you have PCs that can connect, I suspect there is an issue with port 139.  Check the firewall on the Synology and verify both ports (445 and 139) are open in the firewall.  If they are, toggle them off and back on again.  Then see if Unraid can connect.  I did a little research and found this was a solution on another server that was not a Synology NAS, but the same principle might apply.

 

What changed you may ask?  Well it seems that Microsoft and samba are in a continuous cat and mouse chase here.  Each update in Windows and samba can bring on new issues as Microsoft and samba up their security.  Any update on a server or client can bring new challenges.

  • Thanks 1
Link to comment
36 minutes ago, dlandon said:

 

This is your issue:

May  1 17:42:54 Loki kernel: CIFS: VFS: cifs_mount failed w/return code = -512

 

SMB uses port 445, but CIFS also needs port 139.  Since you have PCs that can connect, I suspect there is an issue with port 139.  Check the firewall on the Synology and verify both ports (445 and 139) are open in the firewall.  If they are, toggle them off and back on again.  Then see if Unraid can connect.  I did a little research and found this was a solution on another server that was not a Synology NAS, but the same principle might apply.

 

What changed you may ask?  Well it seems that Microsoft and samba are in a continuous cat and mouse chase here.  Each update in Windows and samba can bring on new issues as Microsoft and samba up their security.  Any update on a server or client can bring new challenges.

I did the following upon your suggestion @dlandon
- Rebooted Synology NAS
- Checked ports 119-445 (Open) and Firewall on Synology is OFF
- Rebooted Unraid
- Windows can mount the Synology without issue, as a Drive. not just navigating the share.

The issue is unraid/plug-in  I believe :( 

Link to comment

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.