ReadyNas 6.2 (NAS locks up entirely)

mdgm wrote:
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.

Indeed, my point is to in future look at forums like this for your products. there was 1 review out when I bought my RN104. Sites like dabs will try to put up positive reviews as they want to sell units. Would you imagine people are looking at OS6 and the RN line atm and thinking they will purchase one. But if people review honestly and even update their reviews even the people who don't check forums might be saved making mistakes.

There are resellers which value both positive and negative reviews and publish both for all the products they sell.

With:
cat /sys/devices/system/cpu/cpuidle/current_driver

i have noticed the the system use the "armadaxp_idle" driver for cpuidle (http://www.landley.net/kdocs/ols/2007/ols2007v2-pages-119-126.pdf)

Since the system do not lock when "stress" is running, and since support for the armada 370 is very new (https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/?id=c3c7fe7ce0d8a3ef55ebb88f3b24e074735845dd) and the kernel used is the old 3.0 kernel: there is a way to disable cpuidle at runtime?
Can you provide a beta with a kernel compiled without cpuidle?

Fulvio wrote:
***EDIT*** Just running in background: stress --cpu 8 is enough to make the system stable.

I was curious about this and gave it a try but alas it did not solve my problem. I ended up with a core-dump like one of my recent posts but this time it was stress that died. The strange thing is that pretty much the whole system is broke after that. webui, smbd, you name it. the only thing that still worked after the crash was my current ssh-connection and the top I had running. When I tried to reboot it froze up and needed a power-cycle as usual.

It was a "Internal error: Oops: 17 [#1]" , will post a more complete dump when I reproduce the error.

There is a project regarding adding support for ReadyNAS ARM hardware to the vanilla kernel at natisbad.org

We have been using 3.0.x kernels all the way from 6.0.0 all the way to the latest 6.2.3 beta.

sparhawk765 wrote:
I was curious about this and gave it a try but alas it did not solve my problem.

Which illustrates my point that there might be different issues for different users in this thread.

About to throw this black thing out the Window, can't rely on it at all. Will try 6.2.0 again as it stayed on longer with that firmware before locking up

dickerj wrote:
About to throw this black thing out the Window, can't rely on it at all. Will try 6.2.0 again as it stayed on longer with that firmware before locking up

This ain't a fix and it won't solve the lockup problem, but at least you won't have to pull the power cord from the rn104, every time it lockups:

Access the rn104 through ssh and edit etc/sysctl.conf file. Place the following two lines in the end:

kernel.panic = 1
kernel.panic_on_oops = 1

Save and reboot.

What this will do is to restart the rn104 just before a lockup and since the reboot takes just a few minutes, it's a way to get along until there's a real fix.

yajdam wrote:
kernel.panic = 1 kernel.panic_on_oops = 1 Save and reboot. What this will do is to restart the rn104 just before a lockup and since the reboot takes just a few minutes, it's a way to get along until there's a real fix.

It is worth noting that kernel panics can cause data loss: when saving some changes to a file the kernel can cache the data => the kernel fails before flushing the cache and automatically reboots => the user thinks that everything is ok but in reality lost the changes...

I have been running fine with my readynas for over a year. I updated the firmware to 6.2 and now it locks up regularly. An unacceptable attribute in a piece of hardware that you are entrusting with your backups of your most valuable data. I spoke with custmer service and they informed me that I must pay to have them help repair the damage that the new firmware caused. I was not willing to pay. I paid the local PC supply house to buy a new external HDD. I backed up everything on my ReadyNAS and restored and reformatted the system and then copied my data back on. It is still failing. When will netgear realize that they have released a faulty firmware and it is destroying the credibility of their products. I need to rely on this machine. Should I revert to 6.1.9? Is that even possible? This is a trainwreck. Of course, if you talk to netgear customer service, it is my fault and therefore i must pay them. Should we not install any firmware updates after the support period has ended? Is that the message I am to receive? I am very dissapointed and would like a fix to this flaw immediately. I have already wasted much of my valuable time and money on this mistake made by Netgears software engineers

nomoss269 wrote:

I have been running fine with my readynas for over a year. I updated the firmware to 6.2 and now it locks up regularly. An unacceptable attribute in a piece of hardware that you are entrusting with your backups of your most valuable data. I spoke with custmer service and they informed me that I must pay to have them help repair the damage that the new firmware caused. I was not willing to pay. I paid the local PC supply house to buy a new external HDD. I backed up everything on my ReadyNAS and restored and reformatted the system and then copied my data back on. It is still failing. When will netgear realize that they have released a faulty firmware and it is destroying the credibility of their products. I need to rely on this machine. Should I revert to 6.1.9? Is that even possible? This is a trainwreck. Of course, if you talk to netgear customer service, it is my fault and therefore i must pay them. Should we not install any firmware updates after the support period has ended? Is that the message I am to receive? I am very dissapointed and would like a fix to this flaw immediately. I have already wasted much of my valuable time and money on this mistake made by Netgears software engineers

We have a saying for what we are going through trying to get accountability for this issue and this NAS. It is called pissing against the wind. Your comment will be replied to with some of the follwing copy and paste:

"We were still unable to reproduce the problem"
"This is happening to some users"
"the 90 day support is a norm in the tech industry."

IMO, your lucky to have had 12 months with a working NAS. I am currently 22 months trrying to get this to work as advertised.