NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
MarkJPearce
Jun 16, 2017Aspirant
ReadyNas 104 - Network overrun errors
Hi,
I have a ReadyNAS 104 running at firmware v 6.7.4 and I have recently started noticing the following errors when running journalctl:
Jun 16 13:59:39 GlassNib-NAS kernel: mvneta d0074000.ethernet eth1: bad rx status 0f830000 (overrun error), size=640 Jun 16 14:03:37 GlassNib-NAS kernel: mvneta d0074000.ethernet eth1: bad rx status 0f830000 (overrun error), size=512 Jun 16 14:05:18 GlassNib-NAS clamd[3759]: SelfCheck: Database status OK. Jun 16 14:05:18 GlassNib-NAS clamd[3759]: SelfCheck: Database status OK. Jun 16 14:09:01 GlassNib-NAS CRON[5274]: pam_unix(cron:session): session opened for user root by (uid=0) Jun 16 14:09:01 GlassNib-NAS CRON[5278]: (root) CMD ( [ -x /usr/lib/php5/sessionclean ] && /usr/lib/php5/sessionclean) Jun 16 14:09:05 GlassNib-NAS CRON[5274]: pam_unix(cron:session): session closed for user root Jun 16 14:11:49 GlassNib-NAS kernel: mvneta d0074000.ethernet eth1: bad rx status 0f830000 (overrun error), size=512 Jun 16 14:15:18 GlassNib-NAS clamd[3759]: SelfCheck: Database status OK. Jun 16 14:15:18 GlassNib-NAS clamd[3759]: SelfCheck: Database status OK. Jun 16 14:16:12 GlassNib-NAS kernel: mvneta d0074000.ethernet eth1: bad rx status 0f830000 (overrun error), size=448 Jun 16 14:16:12 GlassNib-NAS kernel: mvneta d0074000.ethernet eth1: bad rx status 0f830000 (overrun error), size=1024 Jun 16 14:16:12 GlassNib-NAS kernel: mvneta d0074000.ethernet eth1: bad rx status 0f830000 (overrun error), size=1152 Jun 16 14:16:14 GlassNib-NAS kernel: mvneta d0074000.ethernet eth1: bad rx status 0f830000 (overrun error), size=512 Jun 16 14:16:16 GlassNib-NAS kernel: mvneta d0074000.ethernet eth1: bad rx status 0f830000 (overrun error), size=1024 Jun 16 14:16:34 GlassNib-NAS kernel: mvneta d0074000.ethernet eth1: bad rx status 0f830000 (overrun error), size=512 Jun 16 14:16:42 GlassNib-NAS kernel: mvneta d0074000.ethernet eth1: bad rx status 0f830000 (overrun error), size=144 Jun 16 14:16:47 GlassNib-NAS kernel: mvneta d0074000.ethernet eth1: bad rx status 0f830000 (overrun error), size=1024 Jun 16 14:16:47 GlassNib-NAS kernel: mvneta d0074000.ethernet eth1: bad rx status 0f830000 (overrun error), size=1024 Jun 16 14:17:01 GlassNib-NAS CRON[5337]: pam_unix(cron:session): session opened for user root by (uid=0) Jun 16 14:17:01 GlassNib-NAS CRON[5341]: (root) CMD ( cd / && run-parts --report /etc/cron.hourly) Jun 16 14:17:02 GlassNib-NAS CRON[5337]: pam_unix(cron:session): session closed for user root Jun 16 14:17:04 GlassNib-NAS kernel: mvneta d0074000.ethernet eth1: bad rx status 0f830000 (overrun error), size=1024 Jun 16 14:17:18 GlassNib-NAS kernel: mvneta d0074000.ethernet eth1: bad rx status 0f830000 (overrun error), size=440 Jun 16 14:17:28 GlassNib-NAS kernel: mvneta d0074000.ethernet eth1: bad rx status 0f830000 (overrun error), size=512 Jun 16 14:17:28 GlassNib-NAS kernel: mvneta d0074000.ethernet eth1: bad rx status 0f830000 (overrun error), size=1024 Jun 16 14:17:28 GlassNib-NAS kernel: mvneta d0074000.ethernet eth1: bad rx status 0f830000 (overrun error), size=1024 Jun 16 14:17:28 GlassNib-NAS kernel: mvneta d0074000.ethernet eth1: bad rx status 0f830000 (overrun error), size=400 Jun 16 14:17:29 GlassNib-NAS kernel: mvneta d0074000.ethernet eth1: bad rx status 0f830000 (overrun error), size=272 Jun 16 14:17:29 GlassNib-NAS kernel: mvneta d0074000.ethernet eth1: bad rx status 0f830000 (overrun error), size=1024 Jun 16 14:17:29 GlassNib-NAS kernel: mvneta d0074000.ethernet eth1: bad rx status 0f830000 (overrun error), size=1408 Jun 16 14:17:29 GlassNib-NAS kernel: mvneta d0074000.ethernet eth1: bad rx status 0f830000 (overrun error), size=1024 Jun 16 14:17:29 GlassNib-NAS kernel: mvneta d0074000.ethernet eth1: bad rx status 0f830000 (overrun error), size=504 Jun 16 14:17:29 GlassNib-NAS kernel: mvneta d0074000.ethernet eth1: bad rx status 0f830000 (overrun error), size=1280 Jun 16 14:17:29 GlassNib-NAS kernel: mvneta d0074000.ethernet eth1: bad rx status 0f830000 (overrun error), size=144 Jun 16 14:17:29 GlassNib-NAS kernel: mvneta d0074000.ethernet eth1: bad rx status 0d830000 (overrun error), size=16 Jun 16 14:17:29 GlassNib-NAS kernel: mvneta d0074000.ethernet eth1: bad rx status 0f830000 (overrun error), size=1024 Jun 16 14:17:29 GlassNib-NAS kernel: mvneta d0074000.ethernet eth1: bad rx status 0f830000 (overrun error), size=1024 Jun 16 14:17:29 GlassNib-NAS kernel: mvneta d0074000.ethernet eth1: bad rx status 0f830000 (overrun error), size=144 Jun 16 14:17:33 GlassNib-NAS kernel: mvneta d0074000.ethernet eth1: bad rx status 0f830000 (overrun error), size=1024 Jun 16 14:17:38 GlassNib-NAS kernel: mvneta d0074000.ethernet eth1: bad rx status 0f830000 (overrun error), size=1024
I have re-installed the OS, due to another issue yesterday which was resolved by the re-install, but I can't seem to get passed this one. I ahve not touched the MTU on the network interfaces, it is set to the standard 1500 on both interfaces.
I am running both Windows and mac computers at home and also have a remote back-up over Rsync coming into this ReadyNAS, but the errors appear during normal operation as well as during the Rsynch backup. I ahve also noticed that my Timemachine backups of my mac keep failing and telling me that they have to start a new backup on a regular basis, not sure if this is connected or not?
Any suggestions would be gratefully received,
Mark
1 Reply
Replies have been turned off for this discussion
- StephenBGuru - Experienced User
Overall, an rx overrun in the NAS means that the NAS itself isn't able to keep up with the data it is receiving.
Try turning on ethernet flow control in your PCs (both tx and rx). If you have managed or smart switches, look for flow control settings in them also.
These shouldn't do damage, as TCP will retransmit.
Related Content
NETGEAR Academy
Boost your skills with the Netgear Academy - Get trained, certified and stay ahead with the latest Netgear technology!
Join Us!