Network card looses IP

[ScheipS]

Hi, bought a used ReadyNAS 204 which runs fine so far with 3x4TB WD drives. When moving large amounts of data eth0 looses IP and deactivates. When shutting the drive a hex number is shown in the display. Removing power and restarting makes the drive come back. The other netowrk card eth1 works fine so far.

Any suggestions what the problem might be ? (Firmware 6.9.4 Hotfix 1)

Thx,

-Stefan

[StephenB]

My recollection is that there is a potential issue with overheating the NIC cards in the arm-based NAS.  That's supposed to be fixed in 6.9.4 though, and I think it affected both NICs.

Do you need both NICs?  The obvious work-around is to just use eth1.

[ScheipS]

Hi,

thanks for your answer. Luckywise i do not need 2 LAN-Cards, so i´m using eth1 now.

In Regards to your comment, it really happens with heavy traffic as i´m just copying data onto it due to adding a drive to the RAID. So, my version does not seem to fix it...

Do you know why my firmware 6.9.4 (Hotfix 1)

-Stefan

[StephenB]

---

@ScheipS wrote:

In Regards to your comment, it really happens with heavy traffic as i´m just copying data onto it due to adding a drive to the RAID.

---

You might try 6.9.5 beta. There are some fixes in it for arm-based NAS.

[ScheipS]

Hi Good Morning,

have been travelling for a few days, so could not follow up.

My NAS now continously has issues when shutting down displaying "do_exit+4c4". After removing power and restarting it works fine again until the next shutdown.

Where could i find version 6.9.5 beta ?

Thanks !

-Stefan

[bedlam1]

You can find it HERE

[ScheipS]

Hi, it did not solve the issue, the NAS continous to be stuck after shutdown with flashing power - buton and the message do_exit 4c4 in the display. Only removing power solves the problem, the NAS comes back up.

MTU setting is fine (1500)

Performance: Cool

WoL is enabled

Power Timer is scheduled

Any further ideas what i could possible do ?

Thx,

-Stefan

[StephenB]

What services and protocols do you have enabled?  It's possible that changing some settings would reduce the memory needed by the system.

Try downloading the logs, and look in system.log and kernel.log for crashes and out of memory entries.  

[ScheipS]

Hi ... cannot attach the LOG-files, nothing that i have seen that would go along memory issues. There nothing mentioned a memory error, just about the network card:

>>>

Nov 20 09:42:34 ScheipAir-NAS kernel: al_eth 0000:00:01.0 eth0: using MSI-X per Queue interrupt mode
Nov 20 09:42:34 ScheipAir-NAS kernel:  al_eth_0 mdio read failed on error. phy_addr 0x4 reg 0x2
Nov 20 09:42:34 ScheipAir-NAS kernel:  al_eth_0 mdio read failed on error. phy_addr 0x4 reg 0x2
Nov 20 09:42:34 ScheipAir-NAS kernel:  al_eth_0 mdio read failed on error. phy_addr 0x4 reg 0x2
Nov 20 09:42:34 ScheipAir-NAS kernel:  al_eth_0 mdio read failed on error. phy_addr 0x4 reg 0x2
Nov 20 09:42:34 ScheipAir-NAS kernel:  al_eth_0 mdio read failed on error. phy_addr 0x4 reg 0x2
Nov 20 09:42:34 ScheipAir-NAS kernel: UBIFS (ubi0:0): background thread "ubifs_bgt0_0" started, PID 885
Nov 20 09:42:34 ScheipAir-NAS kernel:  al_eth_0 mdio read failed on error. phy_addr 0x4 reg 0x2
Nov 20 09:42:34 ScheipAir-NAS kernel:  al_eth_0 mdio read failed on error. phy_addr 0x4 reg 0x2

<<<

I have

SMB

AFP

FTP

ReadyDLNA

RSync

UPNP

HTTP

HTTPS

protocols activated, using Apple, Linux and Windows Clients

Thx,

-Stefan

[StephenB]

---

@ScheipS wrote:

Hi ... cannot attach the LOG-files, 

Which is a good thing, because you shouldn't post them publicly.

---

@ScheipS wrote:

There nothing mentioned a memory error, just about the network card:

>>>

Nov 20 09:42:34 ScheipAir-NAS kernel: al_eth 0000:00:01.0 eth0: using MSI-X per Queue interrupt mode
Nov 20 09:42:34 ScheipAir-NAS kernel:  al_eth_0 mdio read failed on error. phy_addr 0x4 reg 0x2
Nov 20 09:42:34 ScheipAir-NAS kernel:  al_eth_0 mdio read failed on error. phy_addr 0x4 reg 0x2
Nov 20 09:42:34 ScheipAir-NAS kernel:  al_eth_0 mdio read failed on error. phy_addr 0x4 reg 0x2
Nov 20 09:42:34 ScheipAir-NAS kernel:  al_eth_0 mdio read failed on error. phy_addr 0x4 reg 0x2
Nov 20 09:42:34 ScheipAir-NAS kernel:  al_eth_0 mdio read failed on error. phy_addr 0x4 reg 0x2
Nov 20 09:42:34 ScheipAir-NAS kernel: UBIFS (ubi0:0): background thread "ubifs_bgt0_0" started, PID 885
Nov 20 09:42:34 ScheipAir-NAS kernel:  al_eth_0 mdio read failed on error. phy_addr 0x4 reg 0x2
Nov 20 09:42:34 ScheipAir-NAS kernel:  al_eth_0 mdio read failed on error. phy_addr 0x4 reg 0x2

That looks like a hardware issue with the NIC then.  If you are the original purchaser, then you should still be under warranty (which is three years).  I suggest contacting paid support (my.netgear.com).  Note you don't want (or need) to sign up for gearhead.  Also you don't need a support contract for warranty replacements.