Quote

Fix: Disk Shares and Exclusive Shares cause issues with a Root Share. A Root Share cannot be added or mounted now if 'Disk Shares' or 'Permit Exclusive Shares' are enabled in Global Share Settings.

What issues was this causing exactly?

It used to just not show the exclusive shares in the shared rootshare which worked fine for me.

 

now it seems i either have to individually share each unraid share or disable exclusive shares.

 

If i have to i would go with option one but for now i reverted to the older version which still works fine.

2 hours ago, fbwr75215 said:

When I try to change the SMB Sharing type from disabled to another value it does not save. I can make the change to the users access type but am not able to change from disabled. Does anyone have an idea of why this would occur. 

It is working for me.  It may be something on your system.  Post diagnostics.

2 hours ago, MammothJerk said:

What issues was this causing exactly?

It used to just not show the exclusive shares in the shared rootshare which worked fine for me.

 

now it seems i either have to individually share each unraid share or disable exclusive shares.

 

If i have to i would go with option one but for now i reverted to the older version which still works fine.

Yes, the exclusive shares will not show in a root share, but with changes in Samba, the recycle bin will not work with exclusive share symlinks in the root share.

2 hours ago, dlandon said:

It is working for me.  It may be something on your system.  Post diagnostics.

Diagnostics is attached. 

 

I also manually edited the unassigned.deices.cfg file to changed the smb_security="private" and I am able to connect to the share. However, the UI still shows as disabled. 

tower-diagnostics-20250224-2026.zip

Edited February 25, 20251 yr by fbwr75215

3 hours ago, dlandon said:

Yes, the exclusive shares will not show in a root share, but with changes in Samba, the recycle bin will not work with exclusive share symlinks in the root share.

So if i get this right:

previously if you accessed the rootshare through SMB and deleted a file that was symlinked to(/from?) an exclusive share, you were unable to send this file to the recycle bin?

 

i never make use of symlinks so this wouldn't affect me, any way to keep the old behaviour other than keeping the downgrade? maybe a warning or such...

16 hours ago, dlandon said:

When looking at the diagnostics, I see the Multichannel feature of SMB is enabled.  That feature requires two NICs and special setup to work properly.  I suggest turning it off and see if it helps.

This is a remnant of what I once tested. By the way, with 2x 1GbE there are no or no relevant advantages with multichannel and 802.3ad LACP.

 

I guess I didn't delete the entry cleanly. Shame. But this is at least a starting point that I can tackle. Thank you for that. I won't be able to test it this week. But I'll probably be able to give feedback at the end of next week.

Edited February 25, 20251 yr by Gorosch

11 hours ago, fbwr75215 said:

I also manually edited the unassigned.deices.cfg file to changed the smb_security="private" and I am able to connect to the share. However, the UI still shows as disabled. 

When you edit the file on the flash device, you need to click the double arrows icon on the UD page since the settings on the flash need to be copied to the /tmp/ file system because UD uses the /tmp/ copy to manage UD.  This is done to save reads on the flash.

14 hours ago, MammothJerk said:

So if i get this right:

previously if you accessed the rootshare through SMB and deleted a file that was symlinked to(/from?) an exclusive share, you were unable to send this file to the recycle bin?

 

i never make use of symlinks so this wouldn't affect me, any way to keep the old behaviour other than keeping the downgrade? maybe a warning or such...

What I found in my testing is that any exclusive share in a rootshare prevents the recycle bin from working on any shares.  There are several choices you have:

• Don't use exclusive shares if you need the recycle bin and a rootshare.
• Don't use the recycle bin if the rootshare and exclusive shares are more important.
• Don't use a root share.

6 hours ago, Gorosch said:

This is a remnant of what I once tested. By the way, with 2x 1GbE there are no or no relevant advantages with multichannel and 802.3ad LACP.

It takes a lot to set it up correctly, and I honestly don't think Multichannel offers any advantage on a home NAS.

2 hours ago, dlandon said:

What I found in my testing is that any exclusive share in a rootshare prevents the recycle bin from working on any shares.  There are several choices you have:

• Don't use exclusive shares if you need the recycle bin and a rootshare.
• Don't use the recycle bin if the roorshare and exclusive shares are more important.
• Don't use a root share.

the 2nd option is preferable for me personally.

19 hours ago, MammothJerk said:

What issues was this causing exactly?

It used to just not show the exclusive shares in the shared rootshare which worked fine for me.

 

now it seems i either have to individually share each unraid share or disable exclusive shares.

 

If i have to i would go with option one but for now i reverted to the older version which still works fine.

 

I'm having 2 issues since the latest update. The same as above, I used to be able to use Root Share with global exclusive shares enabled, but these folders simply wouldnt show up in Root Share, which was fine for my needs as it allowed an easy enable/disable button for SMB access to media.

 

The 2nd issue I'm having is an XFS (non encrypted) HDD that was full of media that was showing up in Unassigned Devices, after server reboot is now showing Format Disk, and unable to mount. I only rebooted server trying to fix the Root Shares glitch before realising it was the update

 

Thank you for any support

yuki-diagnostics-20250225-1631.zip

7 hours ago, MammothJerk said:

the 2nd option is preferable for me personally.

I've been doing some testing and I think it may work with exclusive shares.  I had one situation in my testing where it wouldn't work.  That may be a program issue.  Still testing.

48 minutes ago, FrequencyLost said:

 

I'm having 2 issues since the latest update. The same as above, I used to be able to use Root Share with global exclusive shares enabled, but these folders simply wouldnt show up in Root Share, which was fine for my needs as it allowed an easy enable/disable button for SMB access to media.

 

The 2nd issue I'm having is an XFS (non encrypted) HDD that was full of media that was showing up in Unassigned Devices, after server reboot is now showing Format Disk, and unable to mount. I only rebooted server trying to fix the Root Shares glitch before realising it was the update

 

Thank you for any support

yuki-diagnostics-20250225-1631.zip 173 kB · 0 downloads

If the drive in question is sdc, there is no partition on that disk that I can see.  It looks like the disk may also have some SMART issues.  Someone with more experience with drives may be able to give you some suggestions.

13 hours ago, dlandon said:

When you edit the file on the flash device, you need to click the double arrows icon on the UD page since the settings on the flash need to be copied to the /tmp/ file system because UD uses the /tmp/ copy to manage UD.  This is done to save reads on the flash.

I have done this and it still shows disabled. I have also done a uninstall and reinstall and the issue is still there. I checked the file in the /tmp location and it shows the value of private like the file on the Flash device. 

Edited February 26, 20251 yr by fbwr75215
added the details about /tmp

12 hours ago, fbwr75215 said:

I have done this and it still shows disabled. I have also done a uninstall and reinstall and the issue is still there. I checked the file in the /tmp location and it shows the value of private like the file on the Flash device. 

It sounds like your flash device is having problems.  Shutdown your server and check the flash in a PC.

9 hours ago, dlandon said:

It sounds like your flash device is having problems.  Shutdown your server and check the flash in a PC.

Maybe I was not clear. It still shows disabled in the UI. The files in /tmp and /flash match after I manually edit the file and perform the sync via the UI. The files will be updated for all other settings in the UI except for the SMB Sharing. 

14 minutes ago, fbwr75215 said:

Maybe I was not clear. It still shows disabled in the UI. The files in /tmp and /flash match after I manually edit the file and perform the sync via the UI. The files will be updated for all other settings in the UI except for the SMB Sharing. 

It's possible you found a corner case.  Give me a screen shot of that settings page.

 

Do you have any special characters in the user names?

17 minutes ago, fbwr75215 said:

Maybe I was not clear. It still shows disabled in the UI. The files in /tmp and /flash match after I manually edit the file and perform the sync via the UI. The files will be updated for all other settings in the UI except for the SMB Sharing. 

Go to a command line and do this command 'ud_diagnostics'.  Then post the /flash/logs/ud_diagnostics....zip'

15 minutes ago, dlandon said:

It's possible you found a corner case.  Give me a screen shot of that settings page.

 

Do you have any special characters in the user names?

 

12 minutes ago, dlandon said:

Go to a command line and do this command 'ud_diagnostics'.  Then post the /flash/logs/ud_diagnostics....zip'

File attached. 

ud_diagnostics-20250226-184726.zip

35 minutes ago, fbwr75215 said:

File attached. 

ud_diagnostics-20250226-184726.zip 39.59 kB · 0 downloads

Ok, here is the situation.  There was a decision made long before I took over UD and it was a poor choice.  The SMB Sharing setting (Disabled, Private, Public, etc) setting in the config file is 'smb_security'.  The user names are 'smb_username' in 'Private' mode.  You have a user 'security', so in the config file the 'smb_security' is your user setting and not the 'smb_security' setting which confuses UD.  Until I can come up with a solution to this dilemna, your best bet is to rename the 'security' user and then reconfigure UD SMB settings.

3 minutes ago, dlandon said:

Ok, here is the situation.  There was a decision made long before I took over UD and it was a poor choice.  The SMB Sharing setting (Disabled, Private, Public, etc) setting in the config file is 'smb_security'.  The user names are 'smb_username' in 'Private' mode.  You have a user 'security', so in the config file the 'smb_security' is your user setting and not the 'smb_security' setting which confuses UD.  Until I can come up with a solution to this dilemna, your best bet is to rename the 'security' user and then reconfigure UD SMB settings.

Thank you! I don’t think I even use that user anymore so I’ll review and remove it. 

Hello everyone,

I searched for hours on similar issues but couldn't find anything related to simply let automount the disks.

I can manually mount the ntfs disks, but as soon as I reboot the server the disks do not automount (the automount setting is on at all 5 Disks).

What am I doing wrong or missing?

thank you!

Uche32

 

 

On 1/22/2016 at 2:55 AM, dlandon said:

If any of your UD disks get a gray mount button with the 'not' symbol and the 'Array' text, an array disk probably disconnected and was assigned a new sdX designation by Linux.  You'll need to stop the array and fix this situation.

How? This is driving me nuts. I've installed a new drive, I have this message showing, and I cannot work out a way to fix it. I have no ability to do anything on this drive whether it is plugged in or not plugged in (yes, destructive mode is available). I was able to pre-clear with no issues (but that is literally the only thing I can do with it).

 

Edited to provide a little more context:

• I have a brand new IronWolf drive, sitting an external HDD enclosure
• The slot in the enclosure was previously used for a drive that was in the array (it's not the same physical HDD)
• The new drive can be seen, but I'm seeing the "not" and "array" (first screenshot)
• I want to add the drive to the array. The array has a spare slot available, and all I'm trying to do is to assign this drive to that slot and rebuild the parity.
• I have tried uninstalling and reinstalling all the UD apps. I have tried moving the drive around, shutting down, removing, booting up etc. in many combinations to no avail.

 

The only thing I have not yet tried is simply adding a new config to the array. I've never done that and I'm slightly nervous, but if this is what I need to do then I will.

 

zeus-diagnostics-20250303-0842.zip

Edited March 2, 20251 yr by Cyclical Jester

On 3/1/2025 at 11:51 AM, Uche32 said:

Hello everyone,

I searched for hours on similar issues but couldn't find anything related to simply let automount the disks.

I can manually mount the ntfs disks, but as soon as I reboot the server the disks do not automount (the automount setting is on at all 5 Disks).

What am I doing wrong or missing?

thank you!

Uche32

 

 

Post diangnostics.  Be sure the diagnostics includes where the disks don't auto mount.