Problem - Readynas pro rndp600e + netgear GS-Serie Switch

From your NetMeter trace, I can see that the red trace is a Read from the Pro and the green/yellow trace is an attempt to Write to the Pro.

What I guess is happening is that the green is the actual Writes, but the red/yellow is control traffic up/down the link as the ends (and the switch in the middle) try to agree on what to do. Then it fails and they start all over again. There's some severe mismatch going on.

The red Read trace is also odd as I would expect that to be much faster. What is the "top plateau" reading ? I see that the end part is also erratic as if the connection agreements have started to break down.

Can you take everything to bits and start by doing a direct connect (no switches) and see what traces you get ?

FYI, I'll see if I can capture some NetMeter traces and post them for comparison - I've never posted pics before so I'll have to learn how.

Here's a set of Netmeter traces :




Uploaded with ImageShack.us


It is a sequence of :

Write to Pro Pioneer
Read from Pro Pioneer
Write to Duo
Read from Duo

The files are 13x 1GB IOMeter files.
Clearly there is a problem reading from the Pro, probably caused by the duff drive. On other occasions I have seen a very smooth trace with 90MBps Write and 80MBps Read.

The forum has cropped the previous trace.
Here are the following :

Pro Write/Read
Duo Write/Read



Uploaded with ImageShack.us



Uploaded with ImageShack.us

Thanks again for these answers and some very nice and regular trace. They all helped me to definitely find out where the problem was coming from.

The graphs were showing problems when data were being read from my computer, or written to the readynas. I took one very high bitrate video (bitrate : 50mb) and had it read on the network by an xtreamer. Result :

Readynas pro --> gs105e --> xtreamer = OK
Computer with win7 --> gs105e --> xtreamer = Choppy
It was in line with what the graphs were suggesting, the Data transmission coming out from the PC was not stable.

Checked with the driver, uninstalled the network card, reinstalled, nothing solved and then, i found this :

Repairing TCP/IP Winsock Catalog Corruption
1/ Click on Start button.
2/ Type Cmd in the Start Search text box.
3/ Press Ctrl-Shift-Enter keyboard shortcut to run Command Prompt as Administrator. Allow elevation request.
4/Type netsh winsock reset in the Command Prompt shell, and then press the Enter key.
5/ Restart the computer.

I tried again netmeter:


The results are not 100% perfect because at the time of the trace, i was transmitting files from a very active hd (OS + P2P) to see what could have been the worst case. And the video file suddenly could be read without any problem.

Thanks again to this forum and its community for this help, it was precious.
One point : Netgear's email support. Sincerely, 3 days after having been proposed to change my switch to a gs105e, i had as an answer : "I disactivate your case, as i think i've given you the solution and/or answered your question".
I don't know if the readynas website include a FAQ on that kind of technical problem, but i wish Netgear could have proposed me this solution. It would have saved them 2 switches that may have been 100% fine.

Glad to see you have found a solution. I would not have thought of that, as I would have assumed that these system catalogues would be reset at reboot.

I've usually found manufacturers' support lines to be useless, but this forum is invaluable - esp if you can get one of the Jedi to be involved.

I found this solution while looking for "windows reset network settings". Often, if some programs corrupt the registry base or whatever vital part of your OS, uninstalling the device won't be enough since some malfunctioning prints will remain.
Right now, i'm not really aware of what the system catalogue and before using this command, i should have made a copy of the preceding catalog and compare where something was faulty

As for Netgear, since i've only used it once, i can't really condamn thei support line but when i see the whole set of questions they asked me to send by email and the poor quality of the answer, i think there's a lot to be improved, and they could provide at least a list of things to do rather than keeping on "change your switch".

Finally, i totally agree with you. This forum is invaluable. The time spent by most of its people to help newcomers is just great and really make you feel more confident in the NAS you bought.

Thanks again victorhortaliveson

Credibility fail.
This morning, once again concerning some regular transfers of files, i met again this loss of the Nas on the network with the copy being canceled. It's killing me.
I'll come back to the step-by-step troubleshooting way of solving things. Crossing my fingers it can solve the problem for more than 2 days.

Oh dear ! Well, back to square 1.

Why not start by checking the drives in the NAS using vendor tools for the drives.
Then see if direct connection gives any problems.

If you do have a bad drive then you should reinstall the NAS firmware using the NAS boot menu option after you have replaced and re-synched the new drive.

Since the NAs was bought this summer and most of its hard disk this autumn, with, for each of them, a check with the seagate tool, i just can't imagine something wrong would happen in the meantime that would have such an effect on the transmission.
Moreover, if there was a hd failure somewhere, all my transmission would be wrong and 5mns ago, i copied 15g of files to the NAS, immediate stop. Transmission canceled. I do it 5mns later, no problem.
I can't see the logic behind this.

I bring back this subject since i found a definitive answer to it.

My problem was that, like plenty of others, when transferring large files to my Readyas Pro, the tranfers started to hang and only occasionnally would it work. Moreover, the drive i mapped to the readynas was always showing a cross over it until i accessed to the readynas by the network.
and last week, i tried an updater software, "Drivereasy", one of those software listing all the driver updates available and doing the job for you. It listed 3 drivers :
- ICH9R/DO/DH SATA 10.5.0.1026
- JMicron JMB36X 1.17.62.0
- Intel(R) 82801 PCI Bridge - 244E

I've updated the 3 of them and can't really see which one was the solution, but since then, NO PROBLEM ANYMORE. As soon as my Windows 7 starts, the drive is correctly mapped and no file transfer problem anymore.

That's all, i wanted to share what has been a real pain for me for months and months and it finally got solved.