NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
Solved
Slow SMB access on 314 readynas
after firmware upgrade to 6.5.2 my readynas 314 has become slow to response when browsing its network shares. At times becoming non-accessible. all workstations are windows 10 the nas is on ...
After checking the logs as recommended and finding the above problems, I went on to the domain server and found a MEMORY issues that was slowing the server down under heavy use.
Server fixed and network access to RN back and working.
thanks everyone for the pointers.
Now for the next problem......
yeah, I looked at that but not sure is if i want to commit to that , you cant revert back from it, if i read correct..
what logs should i be looking at for more info..
Which firmware is your RN102 that is working fine on?
You would look at e.g.
- disk health in smart_history.log
- how full the volume is in e.g. volume.log and btrfs.log
- high metadata numbers in btrfs.log relative to data usage
- The number of snapshots on the system (can see in btrfs.log and snapper.log)
If you like you could send your logs in (see the Sending Logs link in my sig) and I could take a look.
Okay thanks everyone, will look at these logs through the week when im back.
Both systems are on the latest firmware.
Hopefully Logs will give me some pointers in the right direction.
Will keep you posted.
Ok so I cleaned up the space hogs on the RNAS box. but nothing improved, but its more manageable now :D
So downloaded the log files and went to the largest log file showing most activity.
I have noticed the massive repetition of the following. at times of slow access..
Oct 07 13:14:56 RNAS winbindd[24930]: tdb_chainlock_with_timeout_internal: alarm (40) timed out for key myserver.domain.local in tdb /var/lock/samba/mutex.tdb
Oct 07 13:14:56 RNAS winbindd[24930]: [2016/10/07 13:14:56.547210, 0] ../source3/winbindd/winbindd_cm.c:1032(cm_prepare_connection)
Oct 07 13:14:56 RNAS winbindd[24930]: cm_prepare_connection: mutex grab failed for myserver.domain.local
Oct 07 13:14:57 RNAS winbindd[24871]: [2016/10/07 13:14:57.881981, 0] ../source3/winbindd/winbindd_dual.c:107(child_write_response)
Oct 07 13:14:57 RNAS winbindd[24871]: Could not write result
Oct 07 13:15:36 RNAS winbindd[24930]: [2016/10/07 13:15:36.551769, 0] ../source3/lib/util_tdb.c:494(tdb_chainlock_with_timeout_internal)Any ideas...
After checking the logs as recommended and finding the above problems, I went on to the domain server and found a MEMORY issues that was slowing the server down under heavy use.
Server fixed and network access to RN back and working.
thanks everyone for the pointers.
Now for the next problem......
NETGEAR Academy
Boost your skills with the Netgear Academy - Get trained, certified and stay ahead with the latest Netgear technology!
Join Us!
