NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
villa1
Dec 18, 2014Tutor
READYNAS Ultra 2 looses network connectivity
Hi,
Im having an issue with the network connection of my ReadyNas DUO Ultra 2.
When I start copying files into the NAS device, it looses network connectivity and it disappear from network. Neither RAIDar 4.3.8 cannot find it nor cannot ping it or connect through the browser. Also the second network interface doesnt work plugin a network cable.
Ive downloaded the logs and here are the errors showed for the second interface (date is wrong)
Feb 9 02:57:47 DATAReady kernel: eth1: -- ERROR --
Feb 9 02:57:47 DATAReady kernel: Class: Hardware failure
Feb 9 02:57:47 DATAReady kernel: Nr: 0x272
Feb 9 02:57:47 DATAReady kernel: Msg: Uncorrectable PCI Express error
DATAReady:/etc# Feb 9 02:57:52 DATAReady kernel: eth1: -- ERROR --
Feb 9 02:57:52 DATAReady kernel: Class: Hardware failure
Feb 9 02:57:52 DATAReady kernel: Nr: 0x272
Feb 9 02:57:52 DATAReady kernel: Msg: Uncorrectable PCI Express error
Feb 9 02:58:14 DATAReady kernel: eth1: Port A failed.
For the first interface, I cannot find any error but it just stop working. Looks like the device continues up (I can see the leds blinking, but it is unaccessible).
Boot messages:
RAIDIator version: 4.2.26:
Linux version 2.6.37.6.RNx86_64.2.4 (jmaggard@calzone) (gcc version 4.1.2 20061115 (prerelease) (Debian 4.1.1-21)) #1 SMP Tue Nov 12 18:53:39 PST 2013
e1000e: Intel(R) PRO/1000 Network Driver - 1.2.7-k2
e1000e: Copyright (c) 1999 - 2010 Intel Corporation.
Intel(R) Gigabit Ethernet Network Driver - version 2.1.0-k2
Copyright (c) 2007-2009 Intel Corporation.
ixgbe: Intel(R) 10 Gigabit PCI Express Network Driver - version 2.0.84-k2
ixgbe: Copyright (c) 1999-2010 Intel Corporation.
bonding: Ethernet Channel Bonding Driver: v3.7.0 (June 2, 2010)
bonding: Warning: either miimon or arp_interval and arp_ip_target module parameters must be specified, otherwise bonding will not detect link failures! see bonding.txt for details.
sky2: driver version 1.28
sky2 0000:01:00.0: Fall back to sk98lin instead.
sky2: probe of 0000:01:00.0 failed with error -1
sky2 0000:03:00.0: Fall back to sk98lin instead.
sky2: probe of 0000:03:00.0 failed with error -1
sk98lin 0000:01:00.0: PCI INT A -> GSI 16 (level, low) -> IRQ 16
sk98lin: Network Device Driver v10.70.1.3
(C)Copyright 1999-2008 Marvell(R).
sk98lin 0000:01:00.0: setting latency timer to 64
eth0: Marvell Yukon 88E8057 Gigabit Ethernet Controller
PrefPort:A RlmtMode:Check Link State
sk98lin 0000:03:00.0: PCI INT A -> GSI 18 (level, low) -> IRQ 18
sk98lin 0000:03:00.0: setting latency timer to 64
eth1: Marvell Yukon 88E8057 Gigabit Ethernet Controller
PrefPort:A RlmtMode:Check Link State
tun: Universal TUN/TAP device driver, 1.6
tun: (C) 1999-2004 Max Krasnyansky <maxk@qualcomm.com>
Fusion MPT base driver 3.04.17
Copyright (c) 1999-2008 LSI Corporation
Fusion MPT SAS Host driver 3.04.17
Fusion MPT misc device (ioctl) driver 3.04.17
mptctl: Registered with Fusion MPT base driver
mptctl: /dev/mptctl @ (major,minor=10,220)
eth0: network connection down
eth0: network connection up using port A
speed: 1000
autonegotiation: yes
duplex mode: full
flowctrl: symmetric
role: slave
irq moderation: disabled
tcp offload: enabled
scatter-gather: enabled
tx-checksum: enabled
rx-checksum: enabled
rx-polling: enabled
sk98lin 0000:01:00.0: PME# enabled
sk98lin 0000:03:00.0: PME# enabled
device eth0 entered promiscuous mode
tun0: Disabled Privacy Extensions
LeafNets: no IPv6 routers present
eth1: Port A failed.
ADDRCONF(NETDEV_UP): eth1: link is not ready
eth0: network connection down
eth0: network connection up using port A
speed: 1000
autonegotiation: yes
duplex mode: full
flowctrl: symmetric
role: slave
irq moderation: disabled
tcp offload: enabled
scatter-gather: enabled
tx-checksum: enabled
rx-checksum: enabled
rx-polling: enabled
I've tested OS6 in the READYNAS device to see whether that version solves the network issue, but also happens same issue, primary interface loose connectivity after some network activity, and second network interface doesn't detect cable connected.
eth0: Marvell Yukon 88E8057 Gigabit Ethernet Controller
PrefPort:A RlmtMode:Check Link State
sk98lin 0000:03:00.0: PCI INT A -> GSI 18 (level, low) -> IRQ 18
sk98lin 0000:03:00.0: setting latency timer to 64
eth1: Generic Marvell Yukon chipset Ethernet device
PrefPort:A RlmtMode:Check Link State
Data can be deleted in the READYnas device, as I have external backups done.
I'm using MacBook pro for connectivity. ISP provider (Telecable in Spain) through Cable.
Im having an issue with the network connection of my ReadyNas DUO Ultra 2.
When I start copying files into the NAS device, it looses network connectivity and it disappear from network. Neither RAIDar 4.3.8 cannot find it nor cannot ping it or connect through the browser. Also the second network interface doesnt work plugin a network cable.
Ive downloaded the logs and here are the errors showed for the second interface (date is wrong)
Feb 9 02:57:47 DATAReady kernel: eth1: -- ERROR --
Feb 9 02:57:47 DATAReady kernel: Class: Hardware failure
Feb 9 02:57:47 DATAReady kernel: Nr: 0x272
Feb 9 02:57:47 DATAReady kernel: Msg: Uncorrectable PCI Express error
DATAReady:/etc# Feb 9 02:57:52 DATAReady kernel: eth1: -- ERROR --
Feb 9 02:57:52 DATAReady kernel: Class: Hardware failure
Feb 9 02:57:52 DATAReady kernel: Nr: 0x272
Feb 9 02:57:52 DATAReady kernel: Msg: Uncorrectable PCI Express error
Feb 9 02:58:14 DATAReady kernel: eth1: Port A failed.
For the first interface, I cannot find any error but it just stop working. Looks like the device continues up (I can see the leds blinking, but it is unaccessible).
Boot messages:
RAIDIator version: 4.2.26:
Linux version 2.6.37.6.RNx86_64.2.4 (jmaggard@calzone) (gcc version 4.1.2 20061115 (prerelease) (Debian 4.1.1-21)) #1 SMP Tue Nov 12 18:53:39 PST 2013
e1000e: Intel(R) PRO/1000 Network Driver - 1.2.7-k2
e1000e: Copyright (c) 1999 - 2010 Intel Corporation.
Intel(R) Gigabit Ethernet Network Driver - version 2.1.0-k2
Copyright (c) 2007-2009 Intel Corporation.
ixgbe: Intel(R) 10 Gigabit PCI Express Network Driver - version 2.0.84-k2
ixgbe: Copyright (c) 1999-2010 Intel Corporation.
bonding: Ethernet Channel Bonding Driver: v3.7.0 (June 2, 2010)
bonding: Warning: either miimon or arp_interval and arp_ip_target module parameters must be specified, otherwise bonding will not detect link failures! see bonding.txt for details.
sky2: driver version 1.28
sky2 0000:01:00.0: Fall back to sk98lin instead.
sky2: probe of 0000:01:00.0 failed with error -1
sky2 0000:03:00.0: Fall back to sk98lin instead.
sky2: probe of 0000:03:00.0 failed with error -1
sk98lin 0000:01:00.0: PCI INT A -> GSI 16 (level, low) -> IRQ 16
sk98lin: Network Device Driver v10.70.1.3
(C)Copyright 1999-2008 Marvell(R).
sk98lin 0000:01:00.0: setting latency timer to 64
eth0: Marvell Yukon 88E8057 Gigabit Ethernet Controller
PrefPort:A RlmtMode:Check Link State
sk98lin 0000:03:00.0: PCI INT A -> GSI 18 (level, low) -> IRQ 18
sk98lin 0000:03:00.0: setting latency timer to 64
eth1: Marvell Yukon 88E8057 Gigabit Ethernet Controller
PrefPort:A RlmtMode:Check Link State
tun: Universal TUN/TAP device driver, 1.6
tun: (C) 1999-2004 Max Krasnyansky <maxk@qualcomm.com>
Fusion MPT base driver 3.04.17
Copyright (c) 1999-2008 LSI Corporation
Fusion MPT SAS Host driver 3.04.17
Fusion MPT misc device (ioctl) driver 3.04.17
mptctl: Registered with Fusion MPT base driver
mptctl: /dev/mptctl @ (major,minor=10,220)
eth0: network connection down
eth0: network connection up using port A
speed: 1000
autonegotiation: yes
duplex mode: full
flowctrl: symmetric
role: slave
irq moderation: disabled
tcp offload: enabled
scatter-gather: enabled
tx-checksum: enabled
rx-checksum: enabled
rx-polling: enabled
sk98lin 0000:01:00.0: PME# enabled
sk98lin 0000:03:00.0: PME# enabled
device eth0 entered promiscuous mode
tun0: Disabled Privacy Extensions
LeafNets: no IPv6 routers present
eth1: Port A failed.
ADDRCONF(NETDEV_UP): eth1: link is not ready
eth0: network connection down
eth0: network connection up using port A
speed: 1000
autonegotiation: yes
duplex mode: full
flowctrl: symmetric
role: slave
irq moderation: disabled
tcp offload: enabled
scatter-gather: enabled
tx-checksum: enabled
rx-checksum: enabled
rx-polling: enabled
I've tested OS6 in the READYNAS device to see whether that version solves the network issue, but also happens same issue, primary interface loose connectivity after some network activity, and second network interface doesn't detect cable connected.
eth0: Marvell Yukon 88E8057 Gigabit Ethernet Controller
PrefPort:A RlmtMode:Check Link State
sk98lin 0000:03:00.0: PCI INT A -> GSI 18 (level, low) -> IRQ 18
sk98lin 0000:03:00.0: setting latency timer to 64
eth1: Generic Marvell Yukon chipset Ethernet device
PrefPort:A RlmtMode:Check Link State
Data can be deleted in the READYnas device, as I have external backups done.
I'm using MacBook pro for connectivity. ISP provider (Telecable in Spain) through Cable.
19 Replies
- villa1TutorFor your Reference,
I've opened this #24376656 ticket in the MyNetgear support. - vandermerweMasterSo you have factory defaulted the nas both on 4.2.27 and OS6.2?
If so there may be a hardware issue so if your nas is still under warranty support should help you. - villa1TutorHi,
thank for the suggestion. I already followed it opening a ticket #24376656 :)
It was "factory defaulted" to 4.2.26, upgraded to 4.2.27, and, as a test, I upgraded into OS6 to see whether this upgrade could solve the network issue. I would like to say this is happening in 4.X RAIDIator versions, also in the new OS6, so, it points me to think it's a real HW issue (apart from the message: Msg: Uncorrectable PCI Express error showed) :wink:
I adviced about this upgrade to let clear the device can be "refactorized" at any time, data has been backup up already.
HW support ended last month (Murphy's law), I agree in buying a support extension for 3 years in case it will help to replace the faulty HW part, or if there is another way to pay for the Small PCI dual network card I would be pleasured to do it.
I could be able to replace it by my own, no need to send the whole device to support.
Thanks again for you reply. - vandermerweMasterI would just clarify with support, before paying, that the extended support contract would actually lead to a RMA if a hardware fault is diagnosed.
You also need to do some calculations to figure out whether it may be cheaper in the long run to buy a new readynas. - villa1TutorHi vandermerwe,
thanks for you suggestion. Support has already replied.. even adquiring 3 more years support it does not cover HW replacement (not sure exactly why when I'm paying three more years of support). I've asked if there is a way to buy only the faulty part (PCI card dual network), I don't like to throw a device when it has replacement parts for that. Three years of support is cheaper than buying a new one, I don't have to buy a new device and I can replace it in short time.
This is info taken from OS6 dmesg after retart the device also after loose again the network copying over the only available interface (eth0). Similar errors to those I've seen with RAIDIator 4.2.X version.
I cannot find errors in log file referred to eth0, but I guess the below errors caused the failure of eth0 too.eth0: Marvell Yukon 88E8057 Gigabit Ethernet Controller
PrefPort:A RlmtMode:Check Link State
sk98lin 0000:03:00.0: enabling device (0000 -> 0003)
sk98lin 0000:03:00.0: PCI INT A -> GSI 18 (level, low) -> IRQ 18
sk98lin 0000:03:00.0: setting latency timer to 64
eth1: Marvell Yukon 88E8057 Gigabit Ethernet Controller
PrefPort:A RlmtMode:Check Link State
eth1: -- ERROR --
Class: Hardware failure
Nr: 0x272
Msg: Uncorrectable PCI Express error
eth1: -- ERROR --
Class: Hardware failure
Nr: 0x272
Msg: Uncorrectable PCI Express error
eth1: -- ERROR --
Class: Hardware failure
Nr: 0x272
Msg: Uncorrectable PCI Express error
eth0: network connection up using port A
speed: 1000
autonegotiation: yes
duplex mode: full
flowctrl: none
irq moderation: disabled
tcp offload: enabled
scatter-gather: enabled
tx-checksum: enabled
rx-checksum: enabled
rx-polling: enabled
ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready
after 235 eth1 Errors.eth0: network connection down
ADDRCONF(NETDEV_UP): eth0: link is not ready
eth0: network connection up using port A
speed: 1000
autonegotiation: yes
duplex mode: full
flowctrl: none
irq moderation: disabled
tcp offload: enabled
scatter-gather: enabled
tx-checksum: enabled
rx-checksum: enabled
rx-polling: enabled
ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready
eth0: no IPv6 routers present
Really there isn't a way to buy the PCI express card? - vandermerweMasterDo you get the same errors when you connect directly to the nas from your pc?
You are using ip4 addresses? - villa1TutorHi vandermerwe,
yes, same errors. I connected the device over a 5e Cat cable directly to my MacBook Pro (also to a PC) and same errors and problems.
Connecting a cable in the second interface doesn't work, even manually setting an IP address, it doesn't reply to ping, sometimes detect connectivity, most of the attempts doesn't.
Plugin a cable on this eth1, casues the device to loose network connectivity on eth1 even without any network transfer. One of the test was setting manullay an IP address on 10.0.1.X network over eth0 and 172.16.8.x in eth1. From a laptop with both Wi-Fi and wired ethernet configured in the same subnets, pinging to both IP addresses. Result was 172.16.8. network didn't reply and 10.0.1. looses connectivity after some replies.
The problem can be be easily reproduced. All the time I tried to copy data through network, I loose connection after some mb copied :)
Yes, I use IPv4 at home (I know Google uses IPv6 for their internal network, but it is not widely used all over internet yet :)) - NhellieVirtuosoapparently the reason why support can't extend your hardware warranty is because you device is already on this list. :(
http://netgear.com/landing/eol.aspx
I have heard that once your product is listed there, all you can do is upgrade to the newer model. ah bummer. - villa1TutorHi Nhellie,
thanks for you information, very useful.
I don't understand from this page... the replacement for my x86 model (RND2000) is an ARM model (RN10200). In case I have to replace it, I would like it was a x86 model too.
The point is :) I just want the replacement for the Ethernet dual port, either through a new support I would be in a position to adquire or buying directly to them the replacement part. My end of warranty was last 23 Nov 2014, Is not a matter I'm trying to get it by free :lol: I want to pay :o - vandermerweMasterI think the replacement for an ultra would be the 312.
What would support do if there was a hardware fault, do they fix it?
If I were you I would get a new nas.
Related Content
NETGEAR Academy

Boost your skills with the Netgear Academy - Get trained, certified and stay ahead with the latest Netgear technology!
Join Us!