NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
SMB not working for some users after upgrade 6.4.0. upgrade
Hi Netgear, I upgraded the firmware of my Readynas 314 to version 6.4.0. Everything worked after the upgrade, except SMB for some of our users (for example Wim) that where in the specified group,...
I'd like to tag onto this thread. It seems that I too have been having SMB issues since at least 10/2/15 (OS 6.2.4). My ReadyNas 312 was upgraded to 6.2.4 on 5/2/15, 6.4.0 on 10/15/15 and 6.4.1 on 12/6/15. I have access to the shares, but it is extremely slow enumerating the directories/thumbnails/file lockouts etc. (see thread https://community.netgear.com/t5/Using-your-ReadyNAS/WIN-10-Slow-Directory-enumeration-SMB/m-p/1020276#M100163).
ReadyNas 312 OS 6.4.1 interacting with a Windows 10 PC.
I examined the smbd.log file and there are errors almost every day involving multiple PIDs. The authentication seems to be working properly. The errors look like this:
===============================================================
[2015/10/21 03:04:48.780437, 0] ../lib/util/fault.c:79(fault_report)
INTERNAL ERROR: Signal 11 in pid 16306 (4.2.4)
Please read the Trouble-Shooting section of the Samba HOWTO
[2015/10/21 03:04:48.780510, 0] ../lib/util/fault.c:81(fault_report)
===============================================================
[2015/10/21 03:04:48.780556, 0] ../source3/lib/util.c:788(smb_panic_s3)
PANIC (pid 16306): internal error
[2015/10/21 03:04:48.902839, 0] ../source3/lib/util.c:899(log_stack_trace)
BACKTRACE: 30 stack frames:
#0 /usr/lib/x86_64-linux-gnu/libsmbconf.so.0(log_stack_trace+0x1a) [0x7f8a81c6841a]
#1 /usr/lib/x86_64-linux-gnu/libsmbconf.so.0(smb_panic_s3+0x1a) [0x7f8a81c684fa]
#2 /usr/lib/x86_64-linux-gnu/libsamba-util.so.0(smb_panic+0x2f) [0x7f8a83a93e5f]
#3 /usr/lib/x86_64-linux-gnu/libsamba-util.so.0(+0x1b081) [0x7f8a83a94081]
#4 /lib/x86_64-linux-gnu/libpthread.so.0(+0xf8d0) [0x7f8a83cbb8d0]
#5 /usr/lib/x86_64-linux-gnu/samba/libsmbd-base-samba4.so(file_close_user+0x9) [0x7f8a83639b19]
#6 /usr/lib/x86_64-linux-gnu/samba/libsmbd-base-samba4.so(smbXsrv_session_logoff+0xdc) [0x7f8a836c4b2c]
#7 /usr/lib/x86_64-linux-gnu/samba/libsmbd-base-samba4.so(+0x13dece) [0x7f8a836c4ece]
#8 /usr/lib/x86_64-linux-gnu/samba/libsmbd-base-samba4.so(+0x13deee) [0x7f8a836c4eee]
#9 /usr/lib/x86_64-linux-gnu/libtalloc.so.2(+0x9368) [0x7f8a808bb368]
#10 /usr/lib/x86_64-linux-gnu/libtalloc.so.2(+0x8f9b) [0x7f8a808baf9b]
#11 /usr/lib/x86_64-linux-gnu/libtalloc.so.2(_talloc_free+0xeb) [0x7f8a808b470b]
#12 /usr/lib/x86_64-linux-gnu/samba/libsmbd-base-samba4.so(+0x1422cd) [0x7f8a836c92cd]
#13 /usr/lib/x86_64-linux-gnu/samba/libsmbd-base-samba4.so(+0x14272e) [0x7f8a836c972e]
#14 /usr/lib/x86_64-linux-gnu/samba/libsmbd-shim-samba4.so(exit_server_cleanly+0x12) [0x7f8a81627d82]
#15 /usr/lib/x86_64-linux-gnu/samba/libsmbd-base-samba4.so(+0x125d5c) [0x7f8a836acd5c]
#16 /usr/lib/x86_64-linux-gnu/samba/libsmbd-base-samba4.so(+0x128a09) [0x7f8a836afa09]
#17 /usr/lib/x86_64-linux-gnu/libsmbconf.so.0(run_events_poll+0x171) [0x7f8a81c7cbe1]
#18 /usr/lib/x86_64-linux-gnu/libsmbconf.so.0(+0x37e57) [0x7f8a81c7ce57]
#19 /usr/lib/x86_64-linux-gnu/libtevent.so.0(_tevent_loop_once+0x8d) [0x7f8a806a843d]
#20 /usr/lib/x86_64-linux-gnu/libtevent.so.0(tevent_common_loop_wait+0x1b) [0x7f8a806a85db]
#21 /usr/lib/x86_64-linux-gnu/samba/libsmbd-base-samba4.so(smbd_process+0x728) [0x7f8a8369fe08]
#22 /usr/sbin/smbd(+0xb550) [0x56025a45a550]
#23 /usr/lib/x86_64-linux-gnu/libsmbconf.so.0(run_events_poll+0x171) [0x7f8a81c7cbe1]
#24 /usr/lib/x86_64-linux-gnu/libsmbconf.so.0(+0x37e57) [0x7f8a81c7ce57]
#25 /usr/lib/x86_64-linux-gnu/libtevent.so.0(_tevent_loop_once+0x8d) [0x7f8a806a843d]
#26 /usr/lib/x86_64-linux-gnu/libtevent.so.0(tevent_common_loop_wait+0x1b) [0x7f8a806a85db]
#27 /usr/sbin/smbd(main+0x185f) [0x56025a456f7f]
#28 /lib/x86_64-linux-gnu/libc.so.6(__libc_start_main+0xf5) [0x7f8a8031cb45]
#29 /usr/sbin/smbd(+0x8085) [0x56025a457085]
[2015/10/21 03:04:48.903452, 0] ../source3/lib/dumpcore.c:318(dump_core)
dumping core in /var/cores
[2015/10/21 06:26:51.027037, 2] ../source3/auth/auth.c:305(auth_check_ntlm_password)
check_ntlm_password: authentication for user [Toby] -> [Toby] -> [Toby] succeeded
[2015/10/21 14:35:08.179233, 2] ../source3/auth/auth.c:305(auth_check_ntlm_password)
check_ntlm_password: authentication for user [Toby] -> [Toby] -> [Toby] succeeded
[2015/10/21 16:10:11.768961, 2] ../source3/auth/auth.c:305(auth_check_ntlm_password)
check_ntlm_password: authentication for user [Toby] -> [Toby] -> [Toby] succeeded
[2015/10/21 16:10:55.608523, 2] ../source3/auth/auth.c:305(auth_check_ntlm_password)
check_ntlm_password: authentication for user [Toby] -> [Toby] -> [Toby] succeeded
[2015/10/21 16:12:21.948669, 2] ../source3/auth/auth.c:305(auth_check_ntlm_password)
check_ntlm_password: authentication for user [Toby] -> [Toby] -> [Toby] succeeded
[2015/10/21 16:22:44.084879, 2] ../source3/auth/auth.c:305(auth_check_ntlm_password)
check_ntlm_password: authentication for user [Toby] -> [Toby] -> [Toby] succeeded
[2015/10/21 16:23:32.149115, 0] ../lib/util/fault.c:78(fault_report)
===============================================================
[2015/10/21 16:23:32.149201, 0] ../lib/util/fault.c:79(fault_report)
INTERNAL ERROR: Signal 11 in pid 30385 (4.2.4)
Please read the Trouble-Shooting section of the Samba HOWTO
[2015/10/21 16:23:32.149252, 0] ../lib/util/fault.c:81(fault_report)
===============================================================
[2015/10/21 16:23:32.149297, 0] ../source3/lib/util.c:788(smb_panic_s3)
PANIC (pid 30385): internal error
[2015/10/21 16:23:32.151019, 0] ../source3/lib/util.c:899(log_stack_trace)
BACKTRACE: 30 stack frames:
===============================================================
This for some reason only seems to effect my Windows 10 machine, and most likely not a Windows 7 laptop. I can't be certain, but this seems to have cropped up since my upgrade to Win10.
This is making me crazy. It can take up to 2 minutes for a directory to display, even from a CMD prompt.
Any help would be appreciated.
Quick Revision,
Seems that I did not explore the issue on my Win 7 laptop closely enough. The issue is also effecting this machine, not just my Win 10 desktop.
Hello TobyE,
Can you try disabling then re-enabling the SMB please?
You might also want to try loading 6.4.2-T59 (Beta 1).
Regards,
JennC
I tried disabling and re-enabling SMB in the settings menu and the browsing results are the same. I downloaded and installed 6.4.2 T59 and rebooted. The server started normally but is still displaying the same symptoms. Examined the smbd.log and the last error thrown by SMB was last night at about 10p as shown below:
[2015/12/30 21:54:12.024665, 0] ../lib/util/fault.c:79(fault_report)
INTERNAL ERROR: Signal 11 in pid 15878 (4.2.4)
Please read the Trouble-Shooting section of the Samba HOWTO
[2015/12/30 21:54:12.024716, 0] ../lib/util/fault.c:81(fault_report)
===============================================================
[2015/12/30 21:54:12.024761, 0] ../source3/lib/util.c:788(smb_panic_s3)
PANIC (pid 15878): internal error
[2015/12/30 21:54:12.026584, 0] ../source3/lib/util.c:899(log_stack_trace)I really don't know what this means, but I tend to think it's not good. Do you have any other suggestions?
Thanks!
Can you send in your logs (see the Sending Logs link in my sig)?
NETGEAR Academy
Boost your skills with the Netgear Academy - Get trained, certified and stay ahead with the latest Netgear technology!
Join Us!
