NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
ReadyNas 6.2 (NAS locks up entirely)
EDIT BY MODERATOR: Please see the post at the end of the thread: http://www.readynas.com/forum/viewtopic.php?p=456217#p456217
I guess i am not the only one this is happening to!
everything worked fine for 6.1.9 (except for my root at 99% problem last month)
once I updated, I transferred aprox 2 gigs of information it locks up every time
all apps are working fine.
as a business owner i have come to the conclusion (with the amount of problems i have been having) ReadyNas is not meant for a reliable means of backing up seems majority of the fixes are "back everything up and factory reset!" I think that answer is as good as telling someone with computer problems to hit there computer a few times and see if it works.
now i have gone to support many times yes they are quite helpful but only within 90 days of purchase of the unit! then they insist that i pay for a extension of that support.... i have 3 IBM servers and when there hardware fails (one little problem with a driver one year later) they back up the reseller in making sure my system is back up and running within 48 hours (no they are not leased or have a protection plan)
If it wasent for the guys in the forums i would have beaten the system with a bat (please see Office space the movie)... sorry for the rant just truly frustrated with the system :evil:
I guess i am not the only one this is happening to!
everything worked fine for 6.1.9 (except for my root at 99% problem last month)
once I updated, I transferred aprox 2 gigs of information it locks up every time
all apps are working fine.
as a business owner i have come to the conclusion (with the amount of problems i have been having) ReadyNas is not meant for a reliable means of backing up seems majority of the fixes are "back everything up and factory reset!" I think that answer is as good as telling someone with computer problems to hit there computer a few times and see if it works.
now i have gone to support many times yes they are quite helpful but only within 90 days of purchase of the unit! then they insist that i pay for a extension of that support.... i have 3 IBM servers and when there hardware fails (one little problem with a driver one year later) they back up the reseller in making sure my system is back up and running within 48 hours (no they are not leased or have a protection plan)
If it wasent for the guys in the forums i would have beaten the system with a bat (please see Office space the movie)... sorry for the rant just truly frustrated with the system :evil:
327 Replies
Replies have been turned off for this discussion
- Keep saying that it is a problem of a few users is at least offensive.
I had the same problem since upgrading to 6.2.2 and I wish all those who have the same problem would write an email to put an end to this farce.
I logged in with ssh to see if i can solve the problem and:
1) At one point "ls" seg faulted. Seriously. Never saw a thing like this. Retyped "ls" and worked flawlessly
2) At one point "ps aux" failed. "Signal 11 (SEGV) caught by ps (procps-ng version 3.3.3). ps:display.c:59: please report this bug". Unbelievable.
3) "cat /etc/passwd" and there are some directories that do not exists
4) The kernel is the incredibly old Linux 3.0.101.RN_ARM.3
5) At some point a process named "fvbackup-q" start taking 100% of CPU time. In the time i take to google what that process even "top" failed: "signal 4 (ILL) was caught by top, please report..."
This is not a simple bug, the all packaged system is a mess (wrong compiler version?, wrong c library?)
So please stop writing offensive marketing messages and start working at it seriously.
Fulvio Benini
Italy - Fulvio I can assure you that we are doing all we can to resolve this as soon as possible.
Can you please send in your logs too?
3) which directories don't exist? Home shares for users are created on the first login using SMB (you need to logout and login again before they appear). On systems with e.g. 100s or 1000s of users (e.g. imported from Active Directory) creating home shares automatically without a user even logging in is not practical.
4) This kernel has backported changes from newer kernels. The kernel in 6.2.x is basically the same as what we were using in 6.1.x. From the very first OS6 firmware 6.0.0 through to the latest 6.2.3 beta we have been using 3.0.x kernels. Reports that things were working fine on 6.1.x indicate thus indicate that the kernel is most likely not the problem. Having said that we have a newer longterm kernel 3.12.x in 6.3.x. There is an early access beta of this firmware for users with x86_64 models. We are working on bringing the new kernel to our ARM models such as the 102 and 104.
5) That is used for backup jobs. What backup jobs are you running? What protocol are you using for those? What are the full backup job settings? - From the two systems we were looking at via serial we obtained crash dumps.
We have added a fix to Beta 5: https://www.readynas.com/forum/viewtopic.php?f=154&t=78866
Please let us know if this resolves your problems. - Updated to beta 5, reboot and started a copy over smb to the nas. 30min in it's locked up and frozen...
And again after 15min idle when trying to download the logs from the webui. :( - O.K. Let's see if the systems we are monitoring still lockup and go from there.
- ReadyNAS 6.2.3 beta 5 installed today around 10AM and still no lockups with alot of file transfer done, to and from the RN104.
So far, so good.
**EDIT**
Still no joy. :( 4 lockups after almost 24 hours of testing.
Logs sent. - The 6.2.3 beta still don't work.
However I installed the "stress" program (apt-get install stress) and launched with:
stress --cpu 8 --io 4 --vm 2 --vm-bytes 256MB &
to see if the problem may be caused by some hardware failure.
The answer is no, but the interesting part is that i was finally able to copy all the data with a SMB connection (without the stress running in background the RN102 always freezed).
I don't know if it's because stress prevents some power save mode, or because the network traffic is slower, but I hope it helps to find a solution.
***EDIT***
Just running in background:
stress --cpu 8
is enough to make the system stable. - ReadyNAS 6.2.3 beta 5 installed last night was locked up again this morning so still it's not fixed :(
- As per any company people need to speak with their wallets. I have noticed the 2 main suppliers I use have been offering money off the RN104 for the last 2 months especially. Nearly every 2nd email I get off dabs is flogging off the unit. I tried to leave my review pointing to these forums and for people to have a good read before even thinking about buying the unit. 7 days later my review has not been published and dabs are not replying.
My review is negative due to nearly 2 years of problems that have accumulated in a small black hard drive holder sitting on my desk. Review your system, point to here, explain your views but try to convey them without frustration. - We are continuing to look into why lockups are occurring for a number of users and attempting to reproduce this problem. It is as frustrating for us as it is for you that the issue has not been reproducible. When an issue cannot be reproduced it can add considerable time especially when the cause of the problem is not showing in the logs.
What reviews a reseller chooses to publish is up to them. On the forums we value the openness of users to give their opinions both positive and negative. It's one one of the things I love about community forums.
NETGEAR Academy
Boost your skills with the Netgear Academy - Get trained, certified and stay ahead with the latest Netgear technology!
Join Us!
