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 locking up at random times and preventing users from accessing the share drives. The unit will stay up anywhere from 4 days to 8 days. When it hangs, the only option is to press the power on/off on the unit itself. Luckily the drives have been healthy as the unit boot up and we did not have to rebuild. But I am concern that doing the power on/off so often will result in corrupt data.
When it hangs, I can't access the management webUI either. One time I was able to access but clicking on the Restart option did not do anything. When I finally got to the unit, I saw that the message on the LED says something about "system is restarting..." I had to press the power on/off button in the front to shut it down.
I started a ticket with Egnyte technical support. But they did not find anything unusual with the storage sync app. I also don't believe it's the app because our users can't access the share drives on the RN626X which is on our local network and nothing to do with the app syncing to Egnyte servers.
Please let me know what I can do at this point. This is a mission critical device now that most of our employees are working remotely.
Thank you.
Peter Margolis
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
7 Replies
Replies have been turned off for this discussion
Do you have the option to leave an SSH session open running top to see the status of the processes when the lock-up occurs? There may also be kernal log entries in the log .zip that give some clues.
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
NETGEAR Academy
Boost your skills with the Netgear Academy - Get trained, certified and stay ahead with the latest Netgear technology!
Join Us!
