This topic has been marked solved and closed to new posts due to inactivity. We hope you'll join the conversation by posting to an open topic or starting a new one.
I have a Readynas PRO6 with OS6 (6.10.3) installed.
every once in a while the Readynas loses network connection (Raidar , Putty , windows explorer). Sometimes it happens after 30+ days , sometimes after several hours.
It happens to both network connections (although not always at the same time it seems).
Switching the box off with the front power switch only works at 50% of the times and always takes a long time. Switching off and restarting by keeping the button pressed for 5 seconds always works and restarts the network connection as well.
The diagnostics from Raidar show: (assembled from several files) :
I ran the memory pass 5 times, about an hour . I understood that should be OK.
The strange thing is that the problem seems to change a bit, after the the last OS upgrade for a while it seeme OK. I recently had a run of more than 30days without any problems. The last couple of days has become worse although I did not change anything AFAIK.
After every incident I downloaded the logs but I have no idea where to look or what to look for .
Today I cleaned out the unit of accumulated dust, never hurts .
When you asked about the memory I needed to check and restarted with a DDR2 strip not seated properly which resulted in the unit currently Resynching...
Any ideas what direction to search for an answer ?
I could put the disks in an Ultra6 that I have as a backup unit (same OS) or wouldn't that work ?
I ran the memory pass 5 times, about an hour . I understood that should be OK.
When you asked about the memory I needed to check and restarted with a DDR2 strip not seated properly which resulted in the unit currently Resynching...
5 passes should be enough. I am wondering if you actually were running with 1 GB (given the reseating). But that shouldn't have triggered a resync.
Trouble with the power button and NIC together is usually a sign of a failing power supply. Both of those use the +5VSB (+5 volt standby) power. Since that stay on all the time, even when the NAS is "off" (except via the rear switch or unplugging), so the switch and WoL will work, it's often the first to go.
Don't think the powerbutton is a problem, actually the unit sometime does not shut down by the frontpage command and the WOL is not reliable either (same goes for the restart).
The powerbutton is the last resort to get the unit to do what I want ..
The problem with the memory was because I took them out to check the sizes. I then did not put it in propperly.
When rebooring the unit stopped with "Readynas" showing on the display. I tried to get into the boot menu before finding the memory problem so once everything was in place the unit booted as usual BUT started resynching.
Now at 32% so hopefully it will be finished in the morning (CET !)
actually I also renewed the mainboard battery as this was completely empty. I did not lose any settings by doing this actually. So it seems this doesnt affect things ?
Would there be an advantage in upgrading memory to 4 or 8 GB ?
While the button may not be "a problem", it sounds like a symptom, and my original statement about the possibility of a failing power supply still holds. Your symptoms are quite common of that.
You may see a slight improvement with an upgrade to 4GB RAM. But unless you are doing some major transcoding or other intensive operations, I doubt you will see much additionally going from 4 to 8. Plus, the right kind of 4GB sticks are not cheap. The ones you listed won't work. They are ECC Registered, and I think high density as well (Kingston doesn't list the architecture, but the number of chips per stick makes me think it is). The Pro needs non-ECC, unregistered, low density (2Rx8) memory, and there was little call for that in a 4GB size back when DDR2 memory was commonly used..
The battery only keeps the real-time clock running. Without one, you will usually see the first log entry using a Jan 1 (I forget the year) date, as it's before the NNTP time sync occurs.
I will start looking for a replacement powersupply , as the unit is quite old it wouldn't hurt anyway.
Just to understand a bit better, wouldn't a problem occur more frequently when the Nas is under load ?
Mostly it stops during the night ... Using the two network connections did help sometimes when only one connection went down.
Do you think the file system problems as indicated by Stephen are also created by this ?
A line of thought was a problem with memory, is there another way to see if both strips are recognized ? Could it be that one is placed but not recognized so that the unit is actually running on 1GB iso 2GB ?
A line of thought was a problem with memory, is there another way to see if both strips are recognized ? Could it be that one is placed but not recognized so that the unit is actually running on 1GB iso 2GB ?
You can enable ssh and enter
# cat /proc/meminfo | grep MemTotal
This will be slightly less than the physical memory. I see 3937028 KB when I run this on my RN526x (which has 4 GB of RAM).
Before you invest in a new supply, you can use a standard ATX supply externally. If that fixes the button issue, then you probably don't need to run it till you see the NIC issue. But if you want to, just make sure you seal the gaps in the back where the cable comes through with masking tape or something similar so airflow is as good as it can be. Maybe seal the opening for the power supply fan, to, since it won't be running and air could come in instead of out.
I have seen others post that the Corsair is a good choice. Unlike a lot of others, it has the necessary three Molex connectors. And the modularity makes it easy to eliminate csaables you don't need.
well I didn't recognize the button as the issue actually (I never switched it off), trouble is that the unit becomes unresponsive once in a while and it can't be accessed from the network then. pushing the power switch will always start the shutdown but most of the time it says shutting down and then nothing happens ...
I can then just push the button for 5seconds and it shuts down straight away ! After that I can restart and network connection is active again ...
Shutting down from Raidar mostly gives the same problem.
That is a different kind of button problem that I toght you were talking about, and does sound like more of a software issue than a hardware (including power supply) one, though it doesn't eliminate a hardware issue.
