dlandon

Didn't really think it would. Just had to eliminate all possibilities.

Try one last thing, and then I'll go off and do some research if this doesn't work: /etc/rc.d/rc.samba restart

Can't browse to shares, or credential issues still?

Try Private instead of Secure for "Security".

Review your SMB share settings for each share. Alll your shares are set for Public access. Your flash device should not be set to Public. Set it to Private and then set desired user access. Did you intend for all your shares to be Public? If you did, you should set up users in Unraid and the set user access for each share you want them to access. Only set Public access for things that make sense for Public access. I'm wondering if your flash has some issues. I'm seeing some strange entries in your smb-shares.conf.

Show the output of the following command: cat /etc/samba/smb-shares.conf It will show how the shares are set up for user access.

The log shows a lot of master browser elections to Unraid: Sep 24 10:38:40 Tower nmbd[7511]: [2022/09/24 10:38:40.683165, 0] ../../source3/nmbd/nmbd_become_lmb.c:398(become_local_master_stage2) Sep 24 10:38:40 Tower nmbd[7511]: ***** Sep 24 10:38:40 Tower nmbd[7511]: Sep 24 10:38:40 Tower nmbd[7511]: Samba name server TOWER is now a local master browser for workgroup WORKGROUP on subnet 172.17.0.1 Sep 24 10:38:40 Tower nmbd[7511]: Sep 24 10:38:40 Tower nmbd[7511]: ***** Sep 24 10:38:40 Tower nmbd[7511]: [2022/09/24 10:38:40.683231, 0] ../../source3/nmbd/nmbd_become_lmb.c:398(become_local_master_stage2) Sep 24 10:38:40 Tower nmbd[7511]: ***** Sep 24 10:38:40 Tower nmbd[7511]: Sep 24 10:38:40 Tower nmbd[7511]: Samba name server TOWER is now a local master browser for workgroup WORKGROUP on subnet 172.18.0.1 Sep 24 10:38:40 Tower nmbd[7511]: Sep 24 10:38:40 Tower nmbd[7511]: ***** Sep 24 10:43:33 Tower nmbd[7511]: [2022/09/24 10:43:33.862075, 0] ../../source3/nmbd/nmbd_become_lmb.c:398(become_local_master_stage2) Sep 24 10:43:33 Tower nmbd[7511]: ***** Sep 24 10:43:33 Tower nmbd[7511]: Sep 24 10:43:33 Tower nmbd[7511]: Samba name server TOWER is now a local master browser for workgroup WORKGROUP on subnet 192.168.1.50 Sep 24 10:43:33 Tower nmbd[7511]: Sep 24 10:43:33 Tower nmbd[7511]: ***** I think you may have a conflict in the Master Browser election. This might cause SMB server lookup issues. Remove the Master Browser plugin and see if it makes a difference. Edit: Your router may also be trying to be the Master Browser.

Remove NerdPack and reboot.

Post your diagnostics file.

Show a screen shot of the Settings->SMB Settings.

Python 2 is available as a plugin in CA. Search python.

What was upgraded? Works for me. So how about a screen shot. Can't offer any help with your description.

What is the output of the command: ls -la /mnt/disks when your UD disk(s) are mounted?

Ok, it's probably not related to the UD disk itself, but something is triggering udev to re-discover the disks in your server. If that's true, then this might be the explanation. I know you aren't thinking power supply, but take another look. Whatever it is affects all disks.

That UD disk is continually being re-discovered by udev and triggering a udev event. How is it attached to your server? I'd say you have a cable or power supply problem to that disk.

Go to the UD settings and set the "Debug Log Level" to "Udev and Hotplug". Let it run for a few minutes and then post diagnostics so I can see why you are getting those messages. This should not be happening. I think you are getting constant udev events. Be sure to turn off the "Debug Log Level". It can be very chatty.

Yes.

I've got some more information for you. In the change log for 6.11-rc3: "Quit trying to spin down devices which do not support standby mode.". What this means is on 6.11-rc3 and later, Unraid will not spin down disks that don't support standby mode. If you run the array and Unraid spins down the disk, it should not spin back up. If you manually spin down a disk and it doesn't support standby mode, it will probably spin back up. See if this doesn;t explain some of your issues.

Has anyone tried 6.11-rc5? Samba is updated to 4.16.5.

UD also applies these same settings to UD shares based on the Uraid MacOS setting.

Do you have another disk you could try?

That's not an appropriate way to do the MacOS settings. The vfs_ojects can be overwritten by a plugin - the Recycle Bin will eliminate the vfs_objects when it does it's work when you do it this way. Read the first post on how to copy the smb-fruit.conf file to the flash device and how to make changes there that will be applied correctly to the Unraid shares. In the next rc there is a share setting for time machine volume size limit:

If it's already spinning up, then that tells us what we need to know. What disk controller are you using? Post another diagnostics file before you do anything else. To clear a disk, you need to enable "Destructive Mode" in UD settings. You can clear the disk by clicking on the red X next to the disk seral.

You can remove the disk later. The idea is to see if there is a disk and controller combination here that is the problem.

It's documented in one of the first posts.