NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
Solved
ReadyNAS RN626X 6.10.2 Random hanging
Hello, I have been having problems with the RN626X firmware 6.10.2. We are using it to run Egnyte storage sync app for over 2 years with little issues. For the past month now, the unit has been...
It is a good suggesting to try and monitor the NAS a bit, before the crash happens. It does kinda require that you know when it is about to go down though. Another option could be to fetch top every minute or so and direct that output into a file. That way, you can go back and look at the file post crash. It would also be useful to grab something like dmesg in the process. Along the lines of:
while true; do top -b -n 1 >> /data/share/top.txt; dmesg -T | tail -n50 >> /data/share/dmesg.txt; sleep 60; done
Replace share with an actual share name of yours, where you want these logs stored. Also be aware that if your Putty session dies, then the loop dies too (i.e. logging stops) so it would be advisable to use nohup in front on the command to allow it to run continuously. There are many ways to make such a command into a more elaborate script, etc. It is all a Linux Bash shell so the world is your oyster here. Personally, I would make it into a bash script file and run that as it is more easy to edit and add to, that way.
I can also help take a look a current log-set for you, if you like. Might find something in there. Just download the cluster logs (System > Logs > Download Logs) and download the log zip file. Hereafter, upload that zip to a Google Drive, Dropbox or similar and PM me the link to download them. Don't post them publicly here.
Cheers
Thank you for the suggestion Sandshark. I will leave the top running. Where and how do I look at the log .zip file(s)?
PM
It is a good suggesting to try and monitor the NAS a bit, before the crash happens. It does kinda require that you know when it is about to go down though. Another option could be to fetch top every minute or so and direct that output into a file. That way, you can go back and look at the file post crash. It would also be useful to grab something like dmesg in the process. Along the lines of:
while true; do top -b -n 1 >> /data/share/top.txt; dmesg -T | tail -n50 >> /data/share/dmesg.txt; sleep 60; done
Replace share with an actual share name of yours, where you want these logs stored. Also be aware that if your Putty session dies, then the loop dies too (i.e. logging stops) so it would be advisable to use nohup in front on the command to allow it to run continuously. There are many ways to make such a command into a more elaborate script, etc. It is all a Linux Bash shell so the world is your oyster here. Personally, I would make it into a bash script file and run that as it is more easy to edit and add to, that way.
I can also help take a look a current log-set for you, if you like. Might find something in there. Just download the cluster logs (System > Logs > Download Logs) and download the log zip file. Hereafter, upload that zip to a Google Drive, Dropbox or similar and PM me the link to download them. Don't post them publicly here.
Cheers
Of course, if the entire NAS crashes, then top is also going to stop. But my experience on similar apparent lock-ups is that only readynasd and/or some other critical process(es) have either stopped or are using nearly 100% of CPU time and top is still there giving you a display, so long as you already had it running (since you may be locked out of a new SSH connection). rn_enthusiast 's suggestion would be the next step if the SSH session closes or top also stops without showing a last displayed process list.
Thank you both Sandshark and rn_enthusiast for your suggestions. I will know more in 2 or 3 days if the previous pattern of hanging holds and I will report back.
PM
Hi,
Just thought I would pop back and report what happened. It turns out that the "real time sync" feature of Egnyte's Storage Sync app was the culprit. The constant polling and updating to Egnyte cloud was taxing the CPU. Once I changed the sync schedule to every 5 minutes, everything is back to normal for over a month now. It's possible that our data usage increased recently and that's why the real time sync doesn't work anymore. But for good measure, I also schedule a shutdown of the 626X on a bi-weekly basis. The unit shuts down at 1:00 AM and turns back on at 2:00 AM.
Anyway, thank you both for all your help!
Peter
NETGEAR Academy
Boost your skills with the Netgear Academy - Get trained, certified and stay ahead with the latest Netgear technology!
Join Us!
