Hello Unraid Community,

I recently updated my Unraid server from version 6.11 to 6.12, and since then, my SMB share has stopped working. Previously, I was able to mount the share folder on my Windows 11 PC with both Ethernet cards set to the same subnet.

Here are the details of my setup:

Unraid version: 6.12

Previous Unraid version: 6.11

Connection method: Direct Ethernet connection between Windows 11 PC and Unraid server

Network configuration: Both Ethernet cards set to the same subnet

Since the update, I haven't been able to access the SMB share from my Windows 11 PC. I've double-checked the network settings on both machines, and everything seems to be configured correctly.

Has anyone else experienced this issue after updating to 6.12? Are there any additional settings or configurations I need to check or adjust with the new version?

Any help or suggestions would be greatly appreciated. Thank you in advance for your assistance!

1 hour ago, Sleepless In Seattle said:

Has anyone else experienced this issue after updating to 6.12?

Don't remember seeing that before, if you downgrade back to v6.11 does it start working? If yes post diags with both releases.

And be sure that you explain what error messages you are getting on the Windows client.  Screen shots would be nice...

Thanks for the response, here the log files @JorgeB

z420-diagnostics-20240516-1455.zip

Edited May 16, 20242 yr by Sleepless In Seattle
quoting

9 hours ago, Frank1940 said:

And be sure that you explain what error messages you are getting on the Windows client.  Screen shots would be nice...

So it is basically like this when i input \\MyserverIP\sharefolder

44 minutes ago, Sleepless In Seattle said:

So it is basically like this when i input \\MyserverIP\sharefolder

What does it look like if you input     \\MyserverIP        

 

Then try    \\MyServerName   

Edited May 16, 20242 yr by Frank1940

2 hours ago, Frank1940 said:

What does it look like if you input     \\MyserverIP        

 

Then try    \\MyServerName   

Umm it did not work

I just got back to your problem and I looked at your syslog files.  There are 100's of blocks of entries that look like this:

May 16 04:40:03 l kernel: eth0: renamed from vethe91340e
May 16 04:40:03 l kernel: IPv6: ADDRCONF(NETDEV_CHANGE): vethf24ccea: link becomes ready
May 16 04:40:03 l kernel: docker0: port 1(vethf24ccea) entered blocking state
May 16 04:40:03 l kernel: docker0: port 1(vethf24ccea) entered forwarding state
May 16 04:40:27 l kernel: docker0: port 1(vethf24ccea) entered disabled state
May 16 04:40:27 l kernel: vethe91340e: renamed from eth0
May 16 04:40:27 l kernel: docker0: port 1(vethf24ccea) entered disabled state
May 16 04:40:27 l kernel: device vethf24ccea left promiscuous mode
May 16 04:40:27 l kernel: docker0: port 1(vethf24ccea) entered disabled state
May 16 04:40:28 l kernel: docker0: port 1(vethd32f91c) entered blocking state
May 16 04:40:28 l kernel: docker0: port 1(vethd32f91c) entered disabled state
May 16 04:40:28 l kernel: device vethd32f91c entered promiscuous mode
May 16 04:40:28 l kernel: docker0: port 1(vethd32f91c) entered blocking state
May 16 04:40:28 l kernel: docker0: port 1(vethd32f91c) entered forwarding state
May 16 04:40:28 l kernel: docker0: port 1(vethd32f91c) entered disabled state
May 16 04:40:30 l kernel: eth0: renamed from veth39883d6

 

Unfortunately, there have been so many of the entries generated that the beginning of the problem is not in any of the saved log files.   I am not an expert on this type of problem.  (@JorgeB, I believe, has helped out with these problems is the past..  But I believe he is based in Europe so it will be some hours before he is active again.)   But, have a look here at these sections of the Release Notes and see if they might apply in your situation: 

 

       https://docs.unraid.net/unraid-os/release-notes/6.12.0/#call-traces-related-to-macvlan

and

      https://docs.unraid.net/unraid-os/release-notes/6.12.4/#fix-for-macvlan-call-traces

and

     https://docs.unraid.net/unraid-os/release-notes/6.10.0/#docker-custom-networks

You didn't answer my question:

On 5/16/2024 at 9:10 AM, JorgeB said:

if you downgrade back to v6.11 does it start working?

 

As for the current log spam, you likely have a container continuously restarting, you should be able to see which if you look at the containers up-time.