3 minutes ago, MrRog said:

ok how do i have to proceed in order to copy the data? from the share to unraid it simply does not go unraid to share

Share both using SMB and do it with a Windows or Mac computer.

i think now it works when i go via disk1 etc and not via the share... very special
thanks in any case for your help

I am experiencing an issue where the Unassigned Devices plugin appears to be preventing a clean array stop (the array stop operation never completes)

I have a VM that exposes an SMB share.  I use UD to mount this share. The share is subsequently used by one of my Docker containers.  When I stop the array, the VMs and Dockers shutdown normally.  The next action seems to be the UD plugin unmounting all mounted disks and shares.  When UD tries to unmount the remote SMB share, it gets an error because the VM exposing the share is already shutdown. I see a timeout error to that effect in the syslog.  The next entry in the syslog appears to be a reconnection attempt to the VM's SMB share.  After that, there are no other entries in the syslog.  

It appears that this SMB error either causes UD to hang waiting on the reconnection attempt or the UD shutdown script somehow does not return the correct response to the Unraid master shutdown script.  Either way, the shutdown process is halted at this point and requires a hard reboot.

Has anyone seen this behaviour? If so, any pointers on how to correct it?

 

Thanks

DM

2 hours ago, DigitalMaestro said:

I am experiencing an issue where the Unassigned Devices plugin appears to be preventing a clean array stop (the array stop operation never completes)

I have a VM that exposes an SMB share.  I use UD to mount this share. The share is subsequently used by one of my Docker containers.  When I stop the array, the VMs and Dockers shutdown normally.  The next action seems to be the UD plugin unmounting all mounted disks and shares.  When UD tries to unmount the remote SMB share, it gets an error because the VM exposing the share is already shutdown. I see a timeout error to that effect in the syslog.  The next entry in the syslog appears to be a reconnection attempt to the VM's SMB share.  After that, there are no other entries in the syslog.  

It appears that this SMB error either causes UD to hang waiting on the reconnection attempt or the UD shutdown script somehow does not return the correct response to the Unraid master shutdown script.  Either way, the shutdown process is halted at this point and requires a hard reboot.

Has anyone seen this behaviour? If so, any pointers on how to correct it?

 

Thanks

DM

Post diagnostics.

56 minutes ago, dlandon said:

Post diagnostics.

Apologies, should have done that. Attached.  Note that the SMB mount is currently not mounted. Let me know if you need the diagnostics with the SMB mounted.

 

Thanks

DMdiagnostics-20250208-2037.zip

15 hours ago, DigitalMaestro said:

Apologies, should have done that. Attached.  Note that the SMB mount is currently not mounted. Let me know if you need the diagnostics with the SMB mounted.

 

Thanks

DMdiagnostics-20250208-2037.zip

The disk you have mounted with UD has a large number of datasets - looks like 33.  That disk would be better off being a Pool disk and not a UD disk.  UD does not handle ZFS disks like Unraid.

1 hour ago, dlandon said:

The disk you have mounted with UD has a large number of datasets - looks like 33.  That disk would be better off being a Pool disk and not a UD disk.  UD does not handle ZFS disks like Unraid.

I actually use that disk to do weekly backups of my ZFS cache drive pool where I host my VMs.  I mount it with UD and use a syncoid script to do the backup.  I then remove it and store it offline (but sometimes it happens to stay mounted for a couple of days until I remember to remove it)

 

So are you indicating that the SMB issue is a red herring and the real issue is UD failing to unmount the drive?  It does unmount when I do it manually.  I swear that I have the same hanging shutdown issue whether the ZFS drive is mounted or not.  However I will run a test where only the SMB is mounted and the ZFS drive is not present and report back.

 

DM

54 minutes ago, DigitalMaestro said:

I actually use that disk to do weekly backups of my ZFS cache drive pool where I host my VMs.  I mount it with UD and use a syncoid script to do the backup.  I then remove it and store it offline (but sometimes it happens to stay mounted for a couple of days until I remember to remove it)

 

So are you indicating that the SMB issue is a red herring and the real issue is UD failing to unmount the drive?  It does unmount when I do it manually.  I swear that I have the same hanging shutdown issue whether the ZFS drive is mounted or not.  However I will run a test where only the SMB is mounted and the ZFS drive is not present and report back.

 

DM

Post diagnostics when you have the issue.  You might have to open a terminal before shutting down so you can gather the diagnostics when it is hanging.

 

UD does an unmount on shutdown to insure that the devices get unmounted.

6 hours ago, dlandon said:

Post diagnostics when you have the issue.  You might have to open a terminal before shutting down so you can gather the diagnostics when it is hanging.

 

UD does an unmount on shutdown to insure that the devices get unmounted.

 

I physically unmounted and removed all UD mounted disks (including the ZFS disk) and mounted the remote SMB that points to the VM.  I then started the shutdown of the array and it never completes.  I have attached the diagnostics I captured while it was stuck (started at 21:37:51 and it is still hung at 21:55:00, diagnostics captured at 21:47).  It does appear that UD is having trouble with the SMB mount from my read of the syslog but I'll defer to your expertise to determine the true root cause.

 

Thanks

DM

diagnostics-20250209-2147.zip

On 10/30/2024 at 10:00 PM, dlandon said:

We have been working on this.  It should be fixed in Unraid 7.0, and we will be releasing an update to 6.12 that should also be fixed.

Hey, i noticed that my CCTV camera kept losing NFS connection (can't use SMB because don't want to use old versions) and i realize it happens everytime i make a change to any share. is this a known issue? disabling NFS exports on the unassigned devices settings and enabling it again fixes it.
 

 

32 minutes ago, Fma965 said:

Hey, i noticed that my CCTV camera kept losing NFS connection (can't use SMB because don't want to use old versions) and i realize it happens everytime i make a change to any share. is this a known issue? disabling NFS exports on the unassigned devices settings and enabling it again fixes it.
 

 

Post your diagnostics.

1 minute ago, dlandon said:

Post your diagnostics.

f9-nas-diagnostics-20250211-1307.zip

5 minutes ago, Fma965 said:

f9-nas-diagnostics-20250211-1307.zip 253.42 kB · 0 downloads

Your log is filled with these entries:
 

Feb 11 04:44:13 F9-NAS sshd-session[2405263]: Starting session: command for root from 192.168.1.2 port 42290 id 0
Feb 11 04:44:13 F9-NAS sshd-session[2405263]: Close session: user root from 192.168.1.2 port 42290 id 0
Feb 11 04:44:13 F9-NAS sshd-session[2405263]: Starting session: command for root from 192.168.1.2 port 42290 id 0
Feb 11 04:44:13 F9-NAS sshd-session[2405263]: Close session: user root from 192.168.1.2 port 42290 id 0
Feb 11 04:44:13 F9-NAS sshd-session[2405263]: Starting session: command for root from 192.168.1.2 port 42290 id 0
Feb 11 04:44:13 F9-NAS sshd-session[2405263]: Close session: user root from 192.168.1.2 port 42290 id 0
Feb 11 04:44:13 F9-NAS sshd-session[2405263]: Starting session: command for root from 192.168.1.2 port 42290 id 0
Feb 11 04:44:13 F9-NAS sshd-session[2405263]: Close session: user root from 192.168.1.2 port 42290 id 0

Making the log impossible to read.  Can you fix that and then provide a new diagnostics after you have the NFS problem?

  

1 hour ago, dlandon said:

Your log is filled with these entries:
 

Feb 11 04:44:13 F9-NAS sshd-session[2405263]: Starting session: command for root from 192.168.1.2 port 42290 id 0
Feb 11 04:44:13 F9-NAS sshd-session[2405263]: Close session: user root from 192.168.1.2 port 42290 id 0
Feb 11 04:44:13 F9-NAS sshd-session[2405263]: Starting session: command for root from 192.168.1.2 port 42290 id 0
Feb 11 04:44:13 F9-NAS sshd-session[2405263]: Close session: user root from 192.168.1.2 port 42290 id 0
Feb 11 04:44:13 F9-NAS sshd-session[2405263]: Starting session: command for root from 192.168.1.2 port 42290 id 0
Feb 11 04:44:13 F9-NAS sshd-session[2405263]: Close session: user root from 192.168.1.2 port 42290 id 0
Feb 11 04:44:13 F9-NAS sshd-session[2405263]: Starting session: command for root from 192.168.1.2 port 42290 id 0
Feb 11 04:44:13 F9-NAS sshd-session[2405263]: Close session: user root from 192.168.1.2 port 42290 id 0

Making the log impossible to read.  Can you fix that and then provide a new diagnostics after you have the NFS problem?

That's from a Home Assistant integration.

 

Snippet of the log, the start is when I made a change to the Media share, NFS then stops working as shown by "refused mount request" then i disable NFS and enable it again in the unassigned devices and it works again.

Feb 11 14:15:42 F9-NAS rpc.mountd[24968]: refused mount request from 10.0.21.1 for /mnt/disks/CCTV_RAW (/): not exported
Feb 11 14:15:43 F9-NAS emhttpd: Starting services...
Feb 11 14:15:43 F9-NAS emhttpd: shcmd (328): /etc/rc.d/rc.samba reload
Feb 11 14:15:43 F9-NAS emhttpd: shcmd (331): exportfs -ra
Feb 11 14:15:44 F9-NAS emhttpd: shcmd (333): /etc/rc.d/rc.avahidaemon reload
Feb 11 14:15:47 F9-NAS emhttpd: Starting services...
Feb 11 14:15:47 F9-NAS emhttpd: shcmd (346): /etc/rc.d/rc.samba reload
Feb 11 14:15:48 F9-NAS emhttpd: shcmd (349): exportfs -ra
Feb 11 14:15:48 F9-NAS emhttpd: shcmd (351): /etc/rc.d/rc.avahidaemon reload
Feb 11 14:15:52 F9-NAS rpc.mountd[24968]: refused mount request from 10.0.21.1 for /mnt/disks/CCTV_RAW (/): not exported
Feb 11 14:16:02 F9-NAS rpc.mountd[24968]: refused mount request from 10.0.21.1 for /mnt/disks/CCTV_RAW (/): not exported
Feb 11 14:16:05 F9-NAS ool www[2946321]: /usr/local/emhttp/plugins/unassigned.devices/scripts/rc.settings 'nfs_settings'
Feb 11 14:16:05 F9-NAS unassigned.devices: Updating share settings...
Feb 11 14:16:05 F9-NAS unassigned.devices: Updating share settings...
Feb 11 14:16:05 F9-NAS unassigned.devices: Removing SMB share 'CCTV_RAW'.
Feb 11 14:16:06 F9-NAS unassigned.devices: Removing NFS share '/mnt/disks/CCTV_RAW'.
Feb 11 14:16:06 F9-NAS unassigned.devices: Removing SMB share 'NC-HomeServer - Media'.
Feb 11 14:16:06 F9-NAS unassigned.devices: Removing NFS share '/mnt/remotes/NC-HomeServer - Media'.
Feb 11 14:16:06 F9-NAS unassigned.devices: Adding SMB share 'CCTV_RAW'.
Feb 11 14:16:06 F9-NAS unassigned.devices: Warning: Unassigned Devices are not set to be shared with NFS.
Feb 11 14:16:06 F9-NAS unassigned.devices: Adding SMB share 'NC-HomeServer - Media'.
Feb 11 14:16:06 F9-NAS unassigned.devices: Warning: Unassigned Devices are not set to be shared with NFS.
Feb 11 14:16:06 F9-NAS unassigned.devices: Share settings updated.
Feb 11 14:16:11 F9-NAS ool www[2946304]: /usr/local/emhttp/plugins/unassigned.devices/scripts/rc.settings 'nfs_settings'
Feb 11 14:16:11 F9-NAS unassigned.devices: Updating share settings...
Feb 11 14:16:11 F9-NAS unassigned.devices: Updating share settings...
Feb 11 14:16:11 F9-NAS unassigned.devices: Removing SMB share 'CCTV_RAW'.
Feb 11 14:16:11 F9-NAS unassigned.devices: Removing SMB share 'NC-HomeServer - Media'.
Feb 11 14:16:11 F9-NAS unassigned.devices: Adding SMB share 'CCTV_RAW'.
Feb 11 14:16:11 F9-NAS unassigned.devices: Adding NFS share '/mnt/disks/CCTV_RAW'.
Feb 11 14:16:11 F9-NAS unassigned.devices: Adding SMB share 'NC-HomeServer - Media'.
Feb 11 14:16:11 F9-NAS unassigned.devices: Adding NFS share '/mnt/remotes/NC-HomeServer - Media'.
Feb 11 14:16:11 F9-NAS unassigned.devices: Share settings updated.
Feb 11 14:16:12 F9-NAS rpc.mountd[24968]: authenticated mount request from 10.0.21.1:781 for /mnt/disks/CCTV_RAW (/mnt/disks/CCTV_RAW)

 

new diagnostic attached,

Feb 11 14:15:34 F9-NAS sshd-session[2955901]: Close session: user root from 192.168.1.2 port 47654 id 0

is the last entry, after that i disabled the HA integration

f9-nas-diagnostics-20250211-1416.zip

f9-nas-diagnostics-20250211-1416.zip

Edited February 11, 20251 yr by Fma965

1 minute ago, Fma965 said:

 

Snippet of the log, the start is when I made a change to the Media share, NFS then stops working as shown by "refused mount request" then i disable NFS and enable it again in the unassigned devices and it works again.

Feb 11 14:15:42 F9-NAS rpc.mountd[24968]: refused mount request from 10.0.21.1 for /mnt/disks/CCTV_RAW (/): not exported
Feb 11 14:15:43 F9-NAS emhttpd: Starting services...
Feb 11 14:15:43 F9-NAS emhttpd: shcmd (328): /etc/rc.d/rc.samba reload
Feb 11 14:15:43 F9-NAS emhttpd: shcmd (331): exportfs -ra
Feb 11 14:15:44 F9-NAS emhttpd: shcmd (333): /etc/rc.d/rc.avahidaemon reload
Feb 11 14:15:47 F9-NAS emhttpd: Starting services...
Feb 11 14:15:47 F9-NAS emhttpd: shcmd (346): /etc/rc.d/rc.samba reload
Feb 11 14:15:48 F9-NAS emhttpd: shcmd (349): exportfs -ra
Feb 11 14:15:48 F9-NAS emhttpd: shcmd (351): /etc/rc.d/rc.avahidaemon reload
Feb 11 14:15:52 F9-NAS rpc.mountd[24968]: refused mount request from 10.0.21.1 for /mnt/disks/CCTV_RAW (/): not exported
Feb 11 14:16:02 F9-NAS rpc.mountd[24968]: refused mount request from 10.0.21.1 for /mnt/disks/CCTV_RAW (/): not exported
Feb 11 14:16:05 F9-NAS ool www[2946321]: /usr/local/emhttp/plugins/unassigned.devices/scripts/rc.settings 'nfs_settings'
Feb 11 14:16:05 F9-NAS unassigned.devices: Updating share settings...
Feb 11 14:16:05 F9-NAS unassigned.devices: Updating share settings...
Feb 11 14:16:05 F9-NAS unassigned.devices: Removing SMB share 'CCTV_RAW'.
Feb 11 14:16:06 F9-NAS unassigned.devices: Removing NFS share '/mnt/disks/CCTV_RAW'.
Feb 11 14:16:06 F9-NAS unassigned.devices: Removing SMB share 'NC-HomeServer - Media'.
Feb 11 14:16:06 F9-NAS unassigned.devices: Removing NFS share '/mnt/remotes/NC-HomeServer - Media'.
Feb 11 14:16:06 F9-NAS unassigned.devices: Adding SMB share 'CCTV_RAW'.
Feb 11 14:16:06 F9-NAS unassigned.devices: Warning: Unassigned Devices are not set to be shared with NFS.
Feb 11 14:16:06 F9-NAS unassigned.devices: Adding SMB share 'NC-HomeServer - Media'.
Feb 11 14:16:06 F9-NAS unassigned.devices: Warning: Unassigned Devices are not set to be shared with NFS.
Feb 11 14:16:06 F9-NAS unassigned.devices: Share settings updated.
Feb 11 14:16:11 F9-NAS ool www[2946304]: /usr/local/emhttp/plugins/unassigned.devices/scripts/rc.settings 'nfs_settings'
Feb 11 14:16:11 F9-NAS unassigned.devices: Updating share settings...
Feb 11 14:16:11 F9-NAS unassigned.devices: Updating share settings...
Feb 11 14:16:11 F9-NAS unassigned.devices: Removing SMB share 'CCTV_RAW'.
Feb 11 14:16:11 F9-NAS unassigned.devices: Removing SMB share 'NC-HomeServer - Media'.
Feb 11 14:16:11 F9-NAS unassigned.devices: Adding SMB share 'CCTV_RAW'.
Feb 11 14:16:11 F9-NAS unassigned.devices: Adding NFS share '/mnt/disks/CCTV_RAW'.
Feb 11 14:16:11 F9-NAS unassigned.devices: Adding SMB share 'NC-HomeServer - Media'.
Feb 11 14:16:11 F9-NAS unassigned.devices: Adding NFS share '/mnt/remotes/NC-HomeServer - Media'.
Feb 11 14:16:11 F9-NAS unassigned.devices: Share settings updated.
Feb 11 14:16:12 F9-NAS rpc.mountd[24968]: authenticated mount request from 10.0.21.1:781 for /mnt/disks/CCTV_RAW (/mnt/disks/CCTV_RAW)

 

f9-nas-diagnostics-20250211-1416.zip 253.9 kB · 0 downloads

I can't reproduce the problem.  There are several choices here:

• Turn off Home Assistant and get me a cleaner log.
• Or better choice, install the "Enhanced Log Viewer" plugin and go to Settings->Enhanced Syslog Settings then click on the "Syslog Filter" tab and filter those log messages.  Use these strings: "Starting session", "Close session".

I'll work on it some more and see if I can get it to fail.  I have a few ideas.

18 minutes ago, dlandon said:

I can't reproduce the problem.  There are several choices here:

• Turn off Home Assistant and get me a cleaner log.
• Or better choice, install the "Enhanced Log Viewer" plugin and go to Settings->Enhanced Syslog Settings then click on the "Syslog Filter" tab and filter those log messages.  Use these strings: "Starting session", "Close session".

I'll work on it some more and see if I can get it to fail.  I have a few ideas.

I already disabled Home Assistant then did the action then shared the diagnostic, anything in the log before Feb 11 14:15:42 F9-NAS was before HA was disabled that is just old entries and not relevant to the issue.

 

The shares that i am modifying also have NFS setup so my guess is they restart NFS but then unassigned devices doesn't handle this configuration and therefore NFS starts up without whatever configuration unassigned devices uses. then when i disable unassigned devices NFS and enable it again the configuration get's reapplied.

 

Thanks for looking in to it :), also why does Unraid forum say i am a moderator lol?

EDIT: maybe it was for something years ago? can't remember tbh 😂

Edited February 11, 20251 yr by Fma965

On 2/9/2025 at 2:58 PM, dlandon said:

Post diagnostics when you have the issue.  You might have to open a terminal before shutting down so you can gather the diagnostics when it is hanging.

 

UD does an unmount on shutdown to insure that the devices get unmounted.

Hi,

Were you able to get any further insight into the issue with Unraid hanging on shutdown from the diagnostics I posted?

Thanks

DM

2 minutes ago, DigitalMaestro said:

Hi,

Were you able to get any further insight into the issue with Unraid hanging on shutdown from the diagnostics I posted?

Thanks

DM

Yes, unmount failed because of mount being busy, but still sorting some other issues I found with shutdown.

2 hours ago, Fma965 said:

The shares that i am modifying also have NFS setup so my guess is they restart NFS but then unassigned devices doesn't handle this configuration and therefore NFS starts up without whatever configuration unassigned devices uses. then when i disable unassigned devices NFS and enable it again the configuration get's reapplied.

There will be a fix for this in the next release of UD.

UD release to address the following:

• NFS export file not updating after a share edit.
• Shutdown hanging when a remote share is offline.

40 minutes ago, dlandon said:

UD release to address the following:

• NFS export file not updating after a share edit.
• Shutdown hanging when a remote share is offline.

Thank you!  Much appreciated.

DM

After updating UD to latest release, my network share configs all broke ( "-- Invalid configuration - remove and re-add --" or something to that effect )

 

Turns out UD no longer likes config entries with a '.' (  ie: '[SERVER.LOCAL:/share_name]' )

 

I was able to solve this issue without removing all of the shares and re-adding ( and specifying all of the credential information again ) :

 1) Open the Terminal on the Unraid server.

 2) Open '/boot/config/unassigned.devices/samba_mount.cfg' in nano ( or your choice of text editors )

 3) Remove '.'s from [ ] entries only.  Mine were '[GUMBY.KNET:/share_name]' which becomes '[GUMBY:/share_name]'

 4) Save file and exit editor.

 5) In the "Main" tab of Unraid, next to Unassigned Devices click the Refresh Disks and Configuration button ( refresh icon next to settings icon ) and click Proceed.

 6) Any containers/VMs that reference these mount points will also need their paths updated to reflect the name change on the remote shares.

 

I have several network shares set up and this saved me having to manually remove and re-add them.  Hope this helps someone.

15 minutes ago, sentient-russ said:

After updating UD to latest release, my network share configs all broke ( "-- Invalid configuration - remove and re-add --" or something to that effect )

 

Turns out UD no longer likes config entries with a '.' (  ie: '[SERVER.LOCAL:/share_name]' )

 

I was able to solve this issue without removing all of the shares and re-adding ( and specifying all of the credential information again ) :

 1) Open the Terminal on the Unraid server.

 2) Open '/boot/config/unassigned.devices/samba_mount.cfg' in nano ( or your choice of text editors )

 3) Remove '.'s from [ ] entries only.  Mine were '[GUMBY.KNET:/share_name]' which becomes '[GUMBY:/share_name]'

 4) Save file and exit editor.

 5) In the "Main" tab of Unraid, next to Unassigned Devices click the Refresh Disks and Configuration button ( refresh icon next to settings icon ) and click Proceed.

 6) Any containers/VMs that reference these mount points will also need their paths updated to reflect the name change on the remote shares.

 

I have several network shares set up and this saved me having to manually remove and re-add them.  Hope this helps someone.

That doesn't make sense since there were no changes in the latest update to cause that to happen, but I'll look into it.

57 minutes ago, sentient-russ said:

After updating UD to latest release, my network share configs all broke ( "-- Invalid configuration - remove and re-add --" or something to that effect )

 

Turns out UD no longer likes config entries with a '.' (  ie: '[SERVER.LOCAL:/share_name]' )

 

I was able to solve this issue without removing all of the shares and re-adding ( and specifying all of the credential information again ) :

 1) Open the Terminal on the Unraid server.

 2) Open '/boot/config/unassigned.devices/samba_mount.cfg' in nano ( or your choice of text editors )

 3) Remove '.'s from [ ] entries only.  Mine were '[GUMBY.KNET:/share_name]' which becomes '[GUMBY:/share_name]'

 4) Save file and exit editor.

 5) In the "Main" tab of Unraid, next to Unassigned Devices click the Refresh Disks and Configuration button ( refresh icon next to settings icon ) and click Proceed.

 6) Any containers/VMs that reference these mount points will also need their paths updated to reflect the name change on the remote shares.

 

I have several network shares set up and this saved me having to manually remove and re-add them.  Hope this helps someone.

The problem you are running into came up a year ago and has been addressed.  The '.LOCAL' being added to the device designation was changed a long time ago.  It is now taken from the 'Local TLD' on the 'Local Management Access' page.  You should update your plugins a bit more often.

2 hours ago, dlandon said:

The problem you are running into came up a year ago and has been addressed.  The '.LOCAL' being added to the device designation was changed a long time ago.  It is now taken from the 'Local TLD' on the 'Local Management Access' page.  You should update your plugins a bit more often.

I have been keeping it up to date regularly.  However I just installed Limetech's 'Unraid Patch' plugin, which installed patches and claimed to have a conflict with some other plugins and asked me to reboot.  The problem came up after the reboot.  I am running Unraid 7.0...

Quote

 

Unraid Patch:

 

1.0.0

Bug Fixes

mover was not moving shares with spaces in the name from array to pool

File Manager: allow access to UD remote shares

Share Listing: tool tip showed '%20' instead of a space

VM Manager: fix issue with blank Discard field on vDisk

Include installed patches in diagnostics

 

 

This could be the catalyst here.

Edited February 13, 20251 yr by sentient-russ