6.4.1-T35 (Beta 3) - 104 - NFS still crash the device

[jtheb]

Updated to beta because of those crash (front panel irresponsive, no ssh, no http). Still have them.

I have to power-cycle the device and go for a 4-day resync of the RAID5.

Please do something quick, my NAS is useless now that I can't use it.

Edit: MacOS 10.11 client - No way to get device logs ?

[mdgm-ntgr]

You can download them using the web admin interface of the NAS (see the Sending Logs link in my sig) or if you prefer you can download them using RAIDar 6.0 for Mac.

[fragglerok]

same issue here, nothing improved with the 3 betas so far, will we ever get this resolved ?

[coxo01]

Same issue here. In fact Beta 3 is even worse. The NAS just drops out even if not being used. Before it dropped out while copying files over to it.

I have started to look into buying a new brand of NAS and filing a class action lawsuit over this debacle.

[jtheb]

@mdgm-ntgrI'm not sure you would get anything. I've looked at the logs and I don't see anything of value there.

As when I get the issue:

• The device doesn't respond to ping
• The front panel text is frozen
• The button doesn't work
• No network traffic

I think there is a kernel panic of some sort and I think there is no way to troubleshoot those with the logs.

[JennC]

Hello jtheb,

Welcome to the community!

Logs are important. Download logs from the admin page - Logs > Download Logs. Send them to us (see the Sending Logs link in mdgm's sig), include this forum link and your name in the body of the message.

Regards,

[jtheb]

Logs sent.

The instability of 6.4 is a blocking issue. While new features are impressives and on my wishlist for a long time, please consider releasing a way to update to a 6.3.x-level version. 

[JennC]

Hello jtheb,

We'll see if we can get a beta FW for the issue you raised.

Regards, 

[jtheb]

If that's indeed kernel panics, could someone from Netgear confirm me if those are dumped on the uart port ?

[JennC]

Hello jtheb,

Can you try ReadyNAS OS 6.4.1-RC1?

Regards,

[Skywalker]

---

@jtheb wrote:

If that's indeed kernel panics, could someone from Netgear confirm me if those are dumped on the uart port ?

---

Yes, they are dumped on UART.  Also, starting with 6.4.1-RC1 there are also other options if you don't have a 3.3v TTL USB adapter.  (1) If there is a kernel panic, oops, etc, the LCD will display a portion of the stack trace; and (2) the network driver for the RN104 has been updated with functionality that enables the netconsole driver to work, so you should be able to get complete crash dumps that way.

[mdgm-ntgr]

Of course if you do get a crash dump it would be appreciated if you could email those in.

[jtheb]

RC1 is installed on my NAS. I'm out of home now, but I'll be able to get a report for wednesday.

I have a spare raspberry pi, I'll try to setup netconsole and I'll order a USB RS232 TTL cable.

[jtheb]

Past week has been more chaotic than expected.

Tried again with RC1. No crashes yet. @mdgm-ntgr I have thoses traces in console:

As soon as possible, I will shutdown the nas and upgrade to RC3

[675677.083622] mvneta d0070000.ethernet eth0: bad rx status 0f830000 (overrun error), size=840

[675792.942974] mvneta d0070000.ethernet eth0: bad rx status 0f830000 (overrun error), size=400

[ 1726.975589] mvneta d0070000.ethernet eth0: bad rx status 0f830000 (overrun error), size=768

[ 2016.995213] mvneta d0070000.ethernet eth0: bad rx status 0f830000 (overrun error), size=512

[ 2017.407975] mvneta d0070000.ethernet eth0: bad rx status 0f830000 (overrun error), size=512

[ 2020.807361] mvneta d0070000.ethernet eth0: bad rx status 0f830000 (overrun error), size=144

[ 2020.815873] mvneta d0070000.ethernet eth0: bad rx status 0f830000 (overrun error), size=128

[ 2024.118018] mvneta d0070000.ethernet eth0: bad rx status 0f830000 (overrun error), size=1024

[ 2068.763594] mvneta d0070000.ethernet eth0: bad rx status 0f830000 (overrun error), size=896

[ 2089.209987] mvneta d0070000.ethernet eth0: bad rx status 0f830000 (overrun error), size=144

[ 2135.135958] mvneta d0070000.ethernet eth0: bad rx status 0f830000 (overrun error), size=448

[ 2172.151218] mvneta d0070000.ethernet eth0: bad rx status 0f830000 (overrun error), size=1280

[ 2191.101261] mvneta d0070000.ethernet eth0: bad rx status 0f830000 (overrun error), size=272

[ 2191.599180] mvneta d0070000.ethernet eth0: bad rx status 0f830000 (overrun error), size=768

[ 2200.118808] mvneta d0070000.ethernet eth0: bad rx status 0f830000 (overrun error), size=440

[ 2214.774237] mvneta d0070000.ethernet eth0: bad rx status 0f830000 (overrun error), size=440

[ 2239.701402] mvneta d0070000.ethernet eth0: bad rx status 0f830000 (overrun error), size=640

[ 2248.115813] mvneta d0070000.ethernet eth0: bad rx status 0f830000 (overrun error), size=640

[jtheb]

RC3 installed, no more crashes.

I get a ton of those errors tho:

[20079.397504] mvneta d0070000.ethernet eth0: bad rx status 0f830000 (overrun error), size=640
[20079.518629] mvneta d0070000.ethernet eth0: bad rx status 0f830000 (overrun error), size=272
[20079.578381] mvneta d0070000.ethernet eth0: bad rx status 0f830000 (overrun error), size=512
[20079.724346] mvneta d0070000.ethernet eth0: bad rx status 0f830000 (overrun error), size=640
[20079.782633] mvneta d0070000.ethernet eth0: bad rx status 0f830000 (overrun error), size=640
[20079.905009] mvneta d0070000.ethernet eth0: bad rx status 0f830000 (overrun error), size=1408
[20086.202276] mvneta d0070000.ethernet eth0: bad rx status 0f830000 (overrun error), size=432
[20086.818760] mvneta d0070000.ethernet eth0: bad rx status 0f830000 (overrun error), size=504
[20086.903486] mvneta d0070000.ethernet eth0: bad rx status 0f830000 (overrun error), size=272