dlandon

I think your smb-extra.conf file is corrupted. Tyoe this command: echo "" > /boot/config/smb-extra.conf at a command prompt. then restart samba: /etc/rc.d/rc.samba restart and see if testparm gives errors.

While I look at the diags, type 'testparm' at a command prompt and post warnings/errors.

Post diagnostics with UD installed.

Post the output of this command: cat /etc/samba/smb.conf with UD installed.

These are correct. Any settings you put in smb-extra.conf will overwrite those because smb-extra.conf is included after those settings. The problem with the ones you removed is that they were after the smb-extra.conf include and were overwriting your settings. You hadn't rebooted in a while and the legacy settings were building up. Normally this doesn't cause any problems, but you are changing those settings in smb-extra.conf. This is the reason for my latest changes. You can check your settings with 'testparm' to be sure they are set the way you want.

Remove these.

Reboot. Some changes were made and the legacy settings are still in the smb.conf.

Try the update. I think it was some manipulation of the smb.conf file I was doing that caused the problem.

I have an idea. I'll have a new release for you to try.

Post the contents of your smb-extra.conf file.

How long did it take to fail? You got 8% of the file and then it failed. What version of Unraid are you using?

Just worked for me. Try again.

Why would you want to unmount and remount a partition? There hasn’t been any request for this. Leave it mounted.

Define the shares as Unraid shares cache only, set "Enhanced macOS interoperability" to "Yes" and set up the smb-fruit.conf for the fruit customizations. The recycle bin would be applied automatically. You are doing too much customization for my comfort.

That's by design.

This isn't the place to define a share. As it is now, the "include = /etc/samba/smb-shares.conf" is being added to the [system] share because it is right after the smb-extra.conf include in smb.conf and the scope is still [system] when it returns to smb.conf and not [global]. The smb-extra.conf settings are global. I don't know your disk and shares configuration, but set up a [system] share on your cache disk? Hopefully your cache is not on the array. There is no need to add it manually. The include is in smb.conf. Again, don't depend on testparm to show the includes properly.

What's gloing on here is a change I made to UD to put the share includes in the smb.conf file instead of the smb-extra.conf. The idea was to get the settings out of the smb-extra.conf because of users making all kinds of changes now in the smb-extra.conf and the UD settings would be confusing. When I added the include in the smb.conf file, it was added after the shares include entry. Previously it was before the shares include because it was in smb-extra.conf. This is what caused the "include =" statements to show in the shares with testparm. It looks like testparm is actually including the [global] file includes in the share inappropriately. If no errors or warnings are appearing in testparm regarding the include statements, it appears that it's just a display aberation in testparm. That being said, I'm going to put the include for UD in the smb.conf before shares include and not after. This will prevent the includes from showing in the shares in testparm. Look for a UD update soon.

Does the testparm -v show any errors?

Working on a fix.

A fix will be in a future release so you don’t have to add this to the smb-extra.conf.

All sounds good.

Disk caching and disk spinup can cause momentary pauses.

Just as the error says. You need to be sure each mount pont is unique. You have duplicates. Click on the blue mount point, and change the name to be unique. Then you can mount disks.

Looks like that will do it.

Try putting this in the smb-extra.conf file: max open files = 40960 and restart samba: /etc/rc.d/rc.samba restart