NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
Ready NAS 102, slow network speed (and saving data on reset)
RN102 (6.9.3) on Gigabit network using Lan Speed Test I'm getting 80/90 Mbps (not MB/s), similar with a known good cable connected directly. Same speed from different machines. Antivirus not enable...
Sorry, another question.
Q3. What happens if I
remove these drives.
Insert a new one
Factory reset the NAS
Test the network speed
And then reinsert the old drives
Should I be able to access the data ok?
sc101hell wrote:
Q1. Has anyone got any ideas of what could cause this before I factory reset it. To be fair it's been like this for a while and it's only now the annoying speed is an issue.Security software on the PCs, using disk encryption on the NAS, SMB strict sync and transport encryption might have a performance impact.
I suggest looking at the ethernet stats in the log zip file. Perhaps also test with NasTester: http://www.808.dk/?code-csharp-nas-performance
Though I suspect you've tried this already, I'll mention it just in case - try rebooting the NAS.
sc101hell wrote:
Q2. If I do a factory reset on the NAS I will loose all data from the main disks?
But, assuming I disconnect it, the USB disk should be find to keep as is?Yes to both
sc101hell wrote:
Q3. What happens if I
power downremove these drives.
Insert a new one
Factory reset the NAS
Test the network speedpower down
And then reinsert the old drives
Should I be able to access the data ok?Yes if you do the power down steps I added to your sequence.
Thanks for the reply. Much appreciated.
Just to confirm, no disk encryption.
Not sure what strict sync is but will look.
I've got the logs but am not sure where I'm looking for ethernet stats please?
NAS performance tester 1.7 is better.....
Running warmup...
Running a 400MB file write on U: 5 times...
Iteration 1: 32.52 MB/sec
Iteration 2: 30.35 MB/sec
Iteration 3: 28.51 MB/sec
Iteration 4: 31.28 MB/sec
Iteration 5: 30.60 MB/sec
-----------------------------
Average (W): 30.65 MB/sec
-----------------------------
Running a 400MB file read on U: 5 times...
Would still like to see it getting a bit higher ( real copying is about 10Mb) but much more reassuring. I've seen it should be capable of 70-80, 50 would do me.
Having looked a bit further I can see also a ton of errors in journalctl
Oct 15 23:08:35 NETNAS kernel: mvneta d0074000.ethernet eth0: bad rx status 0f830000 (overrun error), size=512
Oct 15 23:08:36 NETNAS kernel: mvneta d0074000.ethernet eth0: bad rx status 0f830000 (overrun error), size=1024
Oct 15 23:08:36 NETNAS kernel: mvneta d0074000.ethernet eth0: bad rx status 0d830000 (overrun error), size=16
Oct 15 23:08:36 NETNAS kernel: mvneta d0074000.ethernet eth0: bad rx status 0f830000 (overrun error), size=1024
Oct 15 23:08:37 NETNAS kernel: mvneta d0074000.ethernet eth0: bad rx status 0f830000 (overrun error), size=896
Oct 15 23:08:37 NETNAS kernel: mvneta d0074000.ethernet eth0: bad rx status 0f830000 (overrun error), size=1024
Oct 15 23:08:37 NETNAS kernel: mvneta d0074000.ethernet eth0: bad rx status 0f830000 (overrun error), size=1024Another post seems to suggest turning on flow control for this, but that it should be a problem - could this be connected? Is that advice accurate?
Also seeing a lot of leafp2p errors but assume that's not connected/ for another dayOct 15 22:49:56 NETNAS leafp2p[2178]: url https://peernetwork.netgear.com:443//peernetwork/services/LeafNetsConfigWebService
Oct 15 22:49:56 NETNAS leafp2p[2178]: SOAP 1.1 fault: SOAP-ENV:Client [no subcode]
Oct 15 22:49:56 NETNAS leafp2p[2178]: "Name or service not known"
Oct 15 22:49:56 NETNAS leafp2p[2178]: Detail: getaddrinfo failed in tcp_connect()
sc101hell wrote:
Another post seems to suggest turning on flow control for this, but that it should be a problem - could this be connected? Is that advice accurate?
The overrun means that the PC is delivering packets faster than NAS can receive them. Those packets need to be sent again, and that will hurt performance. Enabling ethernet flow control on the PC should resolve that.
You'll find the full ethernet stats in network_settings.log "errors", "frame" and "carrier" indicate hardware issues (NIC port or circuitry in one of the devices or a cable issue).
sc101hell wrote:
Also seeing a lot of leafp2p errors but assume that's not connected/ for another dayOct 15 22:49:56 NETNAS leafp2p[2178]: url https://peernetwork.netgear.com:443//peernetwork/services/LeafNetsConfigWebService
Oct 15 22:49:56 NETNAS leafp2p[2178]: SOAP 1.1 fault: SOAP-ENV:Client [no subcode]
Oct 15 22:49:56 NETNAS leafp2p[2178]: "Name or service not known"
Oct 15 22:49:56 NETNAS leafp2p[2178]: Detail: getaddrinfo failed in tcp_connect()These are related to ReadyCloud. Since you are directly connecting the NAS to the PC, cloud services won't work. You should probably disable ReadyCloud during this testing (if only to keep the log clutter down).
But keep in mind resetting the NAS with a different drive is only going to let you test to see if the OS is the issue, and thus a reset with the original drives may help. Once you put the original drives back in without another reset (wiping your data), you'll be running the OS from them again.
NETGEAR Academy
Boost your skills with the Netgear Academy - Get trained, certified and stay ahead with the latest Netgear technology!
Join Us!
