Jump to content

6.11.0 upgrade cant open any files via SMB shares

beardymcgee

By beardymcgee
in General Support

Go to solution Solved by beardymcgee,

Recommended Posts

beardymcgee Noob

beardymcgee

Posted
Posted

Hi all,

when i upgrade to 6.11.0, i can browse all my SMB shares, but when i try to open a video file or something it plays for one sec then stops.

 

checking the unraid log on file open there is this error 
Oct  5 17:05:41 yggdrasil  smbd[4171]: [2022/10/05 17:05:41.142515,  0] ../../source3/smbd/smbXsrv_client.c:1116(smbXsrv_client_connection_pass_loop)
Oct  5 17:05:41 yggdrasil  smbd[4171]:   smbXsrv_client_connection_pass_loop: smb2srv_client_connection_passed() failed => NT_STATUS_OBJECT_NAME_NOT_FOUND

 

Samba config files
netbios name = yggdrasil
server string = Media server
hide dot files = no
server multi channel support = yes
multicast dns register = No
disable netbios = yes
server min protocol = SMB2
security = USER
workgroup = ragnarok
map to guest = Bad User
passdb backend = smbpasswd
null passwords = Yes
idmap config * : backend = tdb
idmap config * : range = 3000-7999
map archive = No
map hidden = No
map system = No
map readonly = Yes
create mask = 0777
directory mask = 0777

 

sample smb share config

[Data]
        path = /mnt/user/Data
        comment = 
        browseable = yes
        # Secure
        public = yes
        writeable = no
        write list = admin,media
        case sensitive = auto
        preserve case = yes
        short preserve case = yes

 

 

Reverting back to 6.10.3 resolves the access issues, ive also tried the NTLMv2 reponse only and the NTLM access flag on extra config options on unraid smb settings. also tried the SMB2_02 setting but didnt change anything

 

any idea on what should try next?

 

 

Link to comment
beardymcgee Noob

beardymcgee

Posted
  • Author
Posted
10 hours ago, dlandon said:

Post your diagnostics.

attached both 6.11 and 6.10.03 dianostics

9 hours ago, Frank1940 said:

 

What happens if you try to copy one of these files (that only plays for one second) back to your PC?

 

Same error in logs, and pretty much drops down to 0MB/s then 2 seconds later maxes out at 19MB/s and keep repeating until copied, log is just filled with that "NT_STATUS_OBJECT_NAME_NOT_FOUND" while its copying or it just says unexpected error and stops

yggdrasil-diagnostics-20221006-0915.6.11.0.zip yggdrasil-diagnostics-20221006-0903.6.10.03.zip

Link to comment
dlandon Veteran

dlandon

Posted
Posted

Start by updating your nvidia driver plugin.

 

You have eth1 and eth2 set up with Jumbo frames (MTU = 9000) , while the eth0 and br0 MTUs are set to 1500.  You should set eth1 and eth2 to the default MTU.  Jumbo frames requires every device on the network to be set for Jumbo frames in order to work properly. 

br0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST>  mtu 1500
        inet 192.168.1.200  netmask 255.255.255.0  broadcast 0.0.0.0
        ether 04:d9:f5:21:8e:9a  txqueuelen 1000  (Ethernet)
        RX packets 1607  bytes 563297 (550.0 KiB)
        RX errors 0  dropped 0  overruns 0  frame 0
        TX packets 1444  bytes 1412369 (1.3 MiB)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

docker0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST>  mtu 1500
        inet 172.17.0.1  netmask 255.255.0.0  broadcast 172.17.255.255
        inet6 fe80::42:d0ff:fe84:1c6b  prefixlen 64  scopeid 0x20<link>
        ether 02:42:d0:84:1c:6b  txqueuelen 0  (Ethernet)
        RX packets 312  bytes 63357 (61.8 KiB)
        RX errors 0  dropped 0  overruns 0  frame 0
        TX packets 251  bytes 74263 (72.5 KiB)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

eth0: flags=4419<UP,BROADCAST,RUNNING,PROMISC,MULTICAST>  mtu 1500
        ether 04:d9:f5:21:8e:9a  txqueuelen 1000  (Ethernet)
        RX packets 1649  bytes 591715 (577.8 KiB)
        RX errors 0  dropped 4  overruns 0  frame 0
        TX packets 1853  bytes 1434399 (1.3 MiB)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0
        device memory 0xfc600000-fc61ffff  

eth1: flags=4163<UP,BROADCAST,RUNNING,MULTICAST>  mtu 9000
        inet 10.10.10.200  netmask 255.255.255.0  broadcast 0.0.0.0
        ether 00:25:90:97:0d:f2  txqueuelen 1000  (Ethernet)
        RX packets 1643  bytes 372389 (363.6 KiB)
        RX errors 0  dropped 0  overruns 0  frame 0
        TX packets 12410  bytes 17396792 (16.5 MiB)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

eth2: flags=4163<UP,BROADCAST,RUNNING,MULTICAST>  mtu 9000
        inet 10.10.10.201  netmask 255.255.255.0  broadcast 0.0.0.0
        ether 00:25:90:97:0d:f3  txqueuelen 1000  (Ethernet)
        RX packets 185  bytes 65981 (64.4 KiB)
        RX errors 0  dropped 0  overruns 0  frame 0
        TX packets 82  bytes 24161 (23.5 KiB)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

 

I don't understand your network configuration.  You are not bonding NICs. 

NAME[0]="br0"
BRNAME[0]="br0"
BRSTP[0]="no"
BRFD[0]="0"
BRNICS[0]="eth0"
PROTOCOL[0]="ipv4"
USE_DHCP[0]="no"
IPADDR[0]="192.168.1.200"
NETMASK[0]="255.255.255.0"
GATEWAY[0]="192.168.1.1"
METRIC[0]="1"
DNS_SERVER1="192.168.1.254"
DNS_SERVER2="192.168.1.253"
USE_DHCP6[0]="yes"
DHCP6_KEEPRESOLV="no"
IFNAME[1]="eth1"
PROTOCOL[1]="ipv4"
USE_DHCP[1]="no"
IPADDR[1]="10.10.10.200"
NETMASK[1]="255.255.255.0"
MTU[1]="9000"
IFNAME[2]="eth2"
PROTOCOL[2]="ipv4"
USE_DHCP[2]="no"
IPADDR[2]="10.10.10.201"
NETMASK[2]="255.255.255.0"
MTU[2]="9000"
SYSNICS="3"

 

You need to check your network configuration.  What are you using eth1 and eth2 for?

Link to comment
beardymcgee Noob

beardymcgee

Posted
  • Author
Posted

I have 2 networks eth0 is management subnet and also supplies internet

Eth1 and 2 are on a 10gb fibre non routeable data only subnet. it's 9000 mtu because everything is 9000 mtu on that subnet

And it's not bonded because I use SMB multichannel.

This has worked without issue since I've been using unraid since about when unraid 6 first came out. 

The only time I get the NT_STATUS_OBJECT_NAME_NOT_FOUND error is when I update to 6.11.0 when I revert back issue goes away.

The driver update for NVIDIA was just temp as I was upgrading and downgrading versions for logs

 

Link to comment
beardymcgee Noob

beardymcgee

Posted
  • Author
Posted (edited)
11 hours ago, dlandon said:

Release 6.11.1 will be released shortly.  We've made some changes to SMB that might fix this issue.  Please try that.

nope didnt change anything... cleared the smb config i had in extra, upgraded same error

smbd[7042]: [2022/10/07 19:30:39.379890,  0] ../../source3/smbd/smbXsrv_client.c:1116(smbXsrv_client_connection_pass_loop)
Oct  7 19:30:39 yggdrasil  smbd[7042]:   smbXsrv_client_connection_pass_loop: smb2srv_client_connection_passed() failed => NT_STATUS_OBJECT_NAME_NOT_FOUND
as soon as i revert back no issues

 

also note im using windows 10 and accessing via mapped network drive

 

but even accessing directly has the same issues

Edited by beardymcgee
Link to comment
beardymcgee Noob

beardymcgee

Posted
  • Author
Posted

ok i've figured out what the cause is potentially its SMB multichannel something in 6.11.1/0 has changed and in doing so has broken smb multichannel.

if i disable it in smb settings issue goes away so i am guessing it something to do with how unraid now handles shares available on multiple interfaces in parallel 

Link to comment
dlandon Veteran

dlandon

Posted
Posted
4 minutes ago, beardymcgee said:

ok i've figured out what the cause is potentially its SMB multichannel something in 6.11.1/0 has changed and in doing so has broken smb multichannel.

if i disable it in smb settings issue goes away so i am guessing it something to do with how unraid now handles shares available on multiple interfaces in parallel 

Post a new diagnostics.

Link to comment
dlandon Veteran

dlandon

Posted
Posted
31 minutes ago, beardymcgee said:

ok i've figured out what the cause is potentially its SMB multichannel something in 6.11.1/0 has changed and in doing so has broken smb multichannel.

if i disable it in smb settings issue goes away so i am guessing it something to do with how unraid now handles shares available on multiple interfaces in parallel 

I appreciate the feedback.  I was pretty sure we were looking at a network issue.  I saw you posted a bug report.  We'll be looking into this.

 

I guess the Samba team made some changes that broke Multichannel.  Unfortunately, this is the "whack-a-mole" with Samba - fix one thing and another issue pops up.

Link to comment
  • Solution
beardymcgee Noob

beardymcgee

Posted
  • Author
  • Solution
Posted
2 hours ago, dlandon said:

I appreciate the feedback.  I was pretty sure we were looking at a network issue.  I saw you posted a bug report.  We'll be looking into this.

 

I guess the Samba team made some changes that broke Multichannel.  Unfortunately, this is the "whack-a-mole" with Samba - fix one thing and another issue pops up.

All good, I guess it's kinda still a network issue

 

 

As I've opened this in bug report now I'll mark it resolved and link to bug report

 

https://forums.unraid.net/bug-reports/stable-releases/6111-smb-multichannel-is-broken-r2138/

Link to comment

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.

Guest
Reply to this topic...

×   Pasted as rich text.   Restore formatting

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

×
Go to topic listing
×
×
  • Create New...