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 ...
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
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
NETGEAR Academy
Boost your skills with the Netgear Academy - Get trained, certified and stay ahead with the latest Netgear technology!
Join Us!
