NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
Solved
RNDP200U having network issues
hey guys i'm having this issue with our NAS and not sure what's happening. we have a Model: RNDP200U and it loses network connectivity (no pings) upon manual restart it would work again. it'...
luukee wrote:
I coudn't find the OS partitian log, but i found the partition log.
Look at the first device listed in disk_usage.log
Filesystem Size Used Avail Use% Mounted on
/dev/md0 4.0G 1.7G 2.2G 44% /
tmpfs 16K 0 16K 0% /USB
/dev/c/c 14T 8.7T 5.0T 64% /c...
Mine is rather full BTW, normally is is around 20%
luukee wrote:
Settings for eth1:
Speed: 100Mb/sIs this expected? Most people with x86 NAS are using gigabit networks.
If you are connecting to a gigabit switch or router, then you probably have a bad cable. You could shift it to the other ethernet port, and see if that also negotiates the same speed.
I coudn't find the OS partitian log, but i found the partition log.
hmm. looks like there's 2 network ports, i should the other port?
thanks again for your help guys
network settings:
bond0 Link encap:Ethernet HWaddr 00:00:00:00:00:00
UP BROADCAST RUNNING MASTER MULTICAST MTU:1500 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:0 (0.0 b) TX bytes:0 (0.0 b)
eth0 Link encap:Ethernet HWaddr XX:XX:XX:XX:XX
UP BROADCAST MULTICAST MTU:1500 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:0 (0.0 b) TX bytes:0 (0.0 b)
Interrupt:16 Memory:fe9dc000-0
eth1 Link encap:Ethernet HWaddr XX:XX:XX:XX:XX
inet addr:192.168.x.x Bcast:192.168.1.255 Mask:255.255.255.0
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:83950 errors:0 dropped:7 overruns:0 frame:0
TX packets:83980 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:15106850 (14.4 MiB) TX bytes:46824875 (44.6 MiB)
Interrupt:18 Memory:febdc000-0
lo Link encap:Local Loopback
inet addr:127.0.0.1 Mask:255.0.0.0
inet6 addr: ::1/128 Scope:Host
UP LOOPBACK RUNNING MTU:16436 Metric:1
RX packets:33367 errors:0 dropped:0 overruns:0 frame:0
TX packets:33367 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:1905007 (1.8 MiB) TX bytes:1905007 (1.8 MiB)
tunl0 Link encap:IPIP Tunnel HWaddr
NOARP MTU:1480 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:0 (0.0 b) TX bytes:0 (0.0 b)
IPV6_ASSIGN_eth0=OFF
IPV6_ASSIGN_eth1=OFF
JUMBO_FRAMES_eth0=0
JUMBO_FRAMES_eth1=0
SPEED_DUPLEX_eth0=AUTO_NEGOTIATION
SPEED_DUPLEX_eth1=AUTO_NEGOTIATION
Settings for bond0:
Link detected: no
Settings for eth1:
Supported ports: [ TP ]
Supported link modes: 10baseT/Half 10baseT/Full
100baseT/Half 100baseT/Full
1000baseT/Half 1000baseT/Full
Supports auto-negotiation: Yes
Advertised link modes: 10baseT/Half 10baseT/Full
100baseT/Half 100baseT/Full
1000baseT/Half 1000baseT/Full
Advertised auto-negotiation: Yes
Speed: 100Mb/s
Duplex: Full
Port: Twisted Pair
PHYAD: 0
Transceiver: internal
Auto-negotiation: on
Supports Wake-on: g
Wake-on: d
Link detected: yes
Settings for eth0:
Supported ports: [ TP ]
Supported link modes: 10baseT/Half 10baseT/Full
100baseT/Half 100baseT/Full
1000baseT/Half 1000baseT/Full
Supports auto-negotiation: Yes
Advertised link modes: Not reported
Advertised auto-negotiation: No
Speed: Unknown! (65535)
Duplex: Unknown! (255)
Port: Twisted Pair
PHYAD: 0
Transceiver: internal
Auto-negotiation: on
Supports Wake-on: g
Wake-on: d
Link detected: no
bond0:0:
partition log
***** partition output for sda *****
Disk /dev/sda: 3907029168 sectors, 1.8 TiB
Logical sector size: 512 bytes
Disk identifier (GUID): 382CB5B8-A4DA-406C-8966-639849CEAB46
Partition table holds up to 128 entries
First usable sector is 34, last usable sector is 3907029134
Partitions will be aligned on 64-sector boundaries
Total free space is 4092 sectors (2.0 MiB)
Number Start (sector) End (sector) Size Code Name
1 64 8388671 4.0 GiB FD00
2 8388672 9437247 512.0 MiB FD00
3 9437248 3907025072 1.8 TiB FD00
Disk /dev/sda: 243201 cylinders, 255 heads, 63 sectors/track
Units = cylinders of 8257536 bytes, blocks of 1024 bytes, counting from 0
Device Boot Start End #cyls #blocks Id System
/dev/sda1 0+ 242251- 242252- 1953514583+ ee EFI GPT
/dev/sda2 0 - 0 0 0 Empty
/dev/sda3 0 - 0 0 0 Empty
/dev/sda4 0 - 0 0 0 Empty
***** partition output for sdb *****
Disk /dev/sdb: 3907029168 sectors, 1.8 TiB
Logical sector size: 512 bytes
Disk identifier (GUID): 4541E6D7-AA48-4F2D-A43A-D92BC4508639
Partition table holds up to 128 entries
First usable sector is 34, last usable sector is 3907029134
Partitions will be aligned on 64-sector boundaries
Total free space is 4092 sectors (2.0 MiB)
Number Start (sector) End (sector) Size Code Name
1 64 8388671 4.0 GiB FD00
2 8388672 9437247 512.0 MiB FD00
3 9437248 3907025072 1.8 TiB FD00
Disk /dev/sdb: 243201 cylinders, 255 heads, 63 sectors/track
Units = cylinders of 8257536 bytes, blocks of 1024 bytes, counting from 0
Device Boot Start End #cyls #blocks Id System
/dev/sdb1 0+ 242251- 242252- 1953514583+ ee EFI GPT
/dev/sdb2 0 - 0 0 0 Empty
/dev/sdb3 0 - 0 0 0 Empty
/dev/sdb4 0 - 0 0 0 Empty
luukee wrote:
I coudn't find the OS partitian log, but i found the partition log.
Look at the first device listed in disk_usage.log
Filesystem Size Used Avail Use% Mounted on
/dev/md0 4.0G 1.7G 2.2G 44% /
tmpfs 16K 0 16K 0% /USB
/dev/c/c 14T 8.7T 5.0T 64% /c
...
Mine is rather full BTW, normally is is around 20%
luukee wrote:
Settings for eth1:
Speed: 100Mb/s
Is this expected? Most people with x86 NAS are using gigabit networks.
If you are connecting to a gigabit switch or router, then you probably have a bad cable. You could shift it to the other ethernet port, and see if that also negotiates the same speed.
Thanks stephenb, I'll replace the cable first. I'll check if my router is gigabit as well.
If I plug in a second cable to the second nic, would it conflict if I have both connected?
luukee wrote:
If I plug in a second cable to the second nic, would it conflict if I have both connected?
If you don't know what you are doing, yes.
I suggest not connecting both until we sort out your connection issue. You can try moving your cable to the second port.
thanks StephenB, i connected a new cable to the current NIC port, so not sure how stable it'll be but keeping an eye on it.
the port is currently using a static IP, and all my devices are connecting via that IP. So that's why I was wondering about connecting to the second port at the same time if it would conflict. Great tip though, i won't try it. (If i do, i'll change the first port to DHCP first, then set the second to static).
NETGEAR Academy
Boost your skills with the Netgear Academy - Get trained, certified and stay ahead with the latest Netgear technology!
Join Us!
