Hello everyone, today updated to ver. 6.12 and suddenly my server lost SMB access in Windows 11, but if i STOP and START the ARRAY on Ver. 6.12, so it works fine, but after server reboot the issue is back again, I have searched everywhere but can't find any solution to this problem, if I go back to ver. 6.11.5, so no problem with SMB, all my Shares are available, attached the diagnostics and much appreciate the help

 

 

tower-diagnostics-20230615-1930.zip

Edited June 16, 20233 yr by serch826

Try rebooting in safe mode, also comment or remove the line you have on SMB extras.

2 hours ago, JorgeB said:

Try rebooting in safe mode, also comment or remove the line you have on SMB extras.

Thanks for your advice, i did that, but still the issue, don't know what to do, attached the new diagnostics, thanks again.

Edit: When in safemode it works after i started the Array so all my shares are OK, before the Array is started works also but ofcourse it show just the Flash drive that isn't in the Array.

When in normal mode it also works after i Stop and Start the Array manually, but after a reboot nothing works again.

tower-diagnostics-20230616-1157.zip

Edited June 16, 20233 yr by serch826

30 minutes ago, serch826 said:

When in normal mode it also works after i Stop and Start the Array manually, but after a reboot nothing works again.

Disable array auto-start, then reboot in normal mode, do you still have assess to flash over SMB?

3 hours ago, JorgeB said:

Disable array auto-start, then reboot in normal mode, do you still have assess to flash over SMB?

But what is the point of canceling array autostart?, yes i've access till flash over SMB

Thanks for your time

 

Edited June 16, 20233 yr by serch826

17 minutes ago, serch826 said:

But what is the point of canceling array autostart?

To confirm if SMB was working before array re-start:

19 hours ago, serch826 said:

but if i STOP and START the ARRAY on Ver. 6.12, so it works fine, but after server reboot the issue is back again

So it's just after first array start that it stops working? That's very strange, do you have any user scripts running at first array start?

3 minutes ago, JorgeB said:

To confirm if SMB was working before array re-start:

So it's just after first array start that it stops working? That's very strange, do you have any user scripts running at first array start?

Hi, okay i understand, no i don't have any script at först array star, with the ver.6.11.5 worked awesome

I have no other ideas other then trying a stock Unraid install and restoring only the bare minimum, like the key, super.dat and pools folder for the assignments, then re-test.

18 minutes ago, JorgeB said:

I have no other ideas other then trying a stock Unraid install and restoring only the bare minimum, like the key, super.dat and pools folder for the assignments, then re-test.

Thanks, i also think to do that, but i will try a little more to see if i get some fix, thanks again

I believe you might have an interface issue.  These are the interfaces in your 'testparm' output:

interfaces = 192.168.50.200 10.253.0.1 127.0.0.1

 

Check that these look right.  The 192.168.50.200 is your server.  The issue might be the application of the interfaces/networking is not taking on first boot.  The are networking changes new to 6.12.

 

When this happens go to a command line and do this command:

/etc/rc.d/rc.samba restart

and see if SMB will work.

9 minutes ago, dlandon said:

The are networking changes new to 6.12.

That's a good point, but in that case why does it work at boot if the array is not started? He can still access the Flash share over SMB, after array start it stops working, then it works again after an array re-start, very weird...

20 minutes ago, JorgeB said:

That's a good point, but in that case why does it work at boot if the array is not started? He can still access the Flash share over SMB, after array start it stops working, then it works again after an array re-start, very weird...

Sequence of events to start services after setting up network?  Samba is restarted on array start and stop.

37 minutes ago, dlandon said:

I believe you might have an interface issue.  These are the interfaces in your 'testparm' output:

interfaces = 192.168.50.200 10.253.0.1 127.0.0.1

 

Check that these look right.  The 192.168.50.200 is your server.  The issue might be the application of the interfaces/networking is not taking on first boot.  The are networking changes new to 6.12.

 

When this happens go to a command line and do this command:

/etc/rc.d/rc.samba restart

and see if SMB will work.

Yes, you're right i'll look at that and will back, thanks a lot

1 hour ago, serch826 said:

Yes, you're right i'll look at that and will back, thanks a lot

If i run the samba restart command it works fine

 

1 hour ago, serch826 said:

interfaces = 192.168.50.200 10.253.0.1 127.0.0.1

The interface:  10.253.0.1 is from Wireguard i think, how to fix that with the interfaces? Thanks again.

Edited June 16, 20233 yr by serch826

That's good information, thanks.  I tried to reproduce your issue and I couldn't.

 

Unraid 6.12 sets up some networking for Samba to be sure it is only listening on the appropriate interfaces - the 'interfaces' command.  I don't know how you have your networking setup, but those 'interfaces' are the IP addresses that Samba is listening on.  What are you doing with the Wireguard interface?  The 127.0.0.1 is the localhost or 'lo'.

 

What I don't understand is why you had to restart Samba to get SMB shares to be visible.

 

I see one thing I'd like you to check.  Take a look at your networking setup and confirm this setting:

 

I'm suspicious because the 'interfaces' in my test system shows:

interfaces = 192.168.1.4/24 127.0.0.1

notice the /24?  You're missing the mask.  This really shouldn't have anything to do with needing to restart Samba, but I'm a little suspicious the 'interfaces' is not getting set properly in a certain case keeping SMB shares from being visible, and a Samba restart fixes it.

3 minutes ago, dlandon said:

That's good information, thanks.  I tried to reproduce your issue and I couldn't.

 

Unraid 6.12 sets up some networking for Samba to be sure it is only listening on the appropriate interfaces - the 'interfaces' command.  I don't know how you have your networking setup, but those 'interfaces' are the IP addresses that Samba is listening on.  What are you doing with the Wireguard interface?  The 127.0.0.1 is the localhost or 'lo'.

 

What I don't understand is why you had to restart Samba to get SMB shares to be visible.

 

I see one thing I'd like you to check.  Take a look at your networking setup and confirm this setting:

 

I'm suspicious because the 'interfaces' in my test system shows:

interfaces = 192.168.1.4/24 127.0.0.1

notice the /24?  You're missing the mask.  This really shouldn't have anything to do with needing to restart Samba, but I'm a little suspicious the 'interfaces' is not getting set properly in a certain case keeping SMB shares from being visible, and a Samba restart fixes it.

Hi and thanks, the Wireguard is my VPN services for accessing the LAN outside the home, i use the a lot, The /24 is automatical configured by Unraid

1 minute ago, serch826 said:

Hi and thanks, the Wireguard is my VPN services for accessing the LAN outside the home, i use the a lot, The /24 is automatical configured by Unraid

So it shows 192.168.50.200/24 in the network setup?

 

Do this command when SMB is working and see if the 'interfaces' command has the /24 added to 192.168.50.200:

testparm -s

it will be near the top.

11 minutes ago, dlandon said:

So it shows 192.168.50.200/24 in the network setup?

 

Do this command when SMB is working and see if the 'interfaces' command has the /24 added to 192.168.50.200:

testparm -s

it will be near the top.

In the setup my interface is 192.168.50.200:24

In testparm -s not there are just those tree interfaces but no /24

It all looks right.  See if you have this setting in Wireguard:

2 minutes ago, dlandon said:

It all looks right.  See if you have this setting in Wireguard:

Yes, same as your

I suspected that.  I'm out of ideas for the moment.

1 minute ago, dlandon said:

I suspected that.  I'm out of ideas for the moment.

No problem, you did your best, thanks for your time, i can stay at the ver. 6.11.5, as then works awesome, thanks again.

14 minutes ago, serch826 said:

No problem, you did your best, thanks for your time, i can stay at the ver. 6.11.5, as then works awesome, thanks again.

Hi, again i managed it to work, but for this i configured Wireguard to not autostart, very stanger, i've to continius to work on this as you said the network has little problem in my settings for ver. 6.12

Yes it works

Edited June 16, 20233 yr by serch826