NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
6.5.0 crashing on readynas 314
I have a readynas 314 with and expansion chasis, and recently (since the 6.5.0 update) it has been crashing every 1-2 weeks or so. The logs don't indicate anything. Any tips on trying to troublesho...
I've generally had such poor support from official support (ha!) channels (no experience with Netgear, but just overall) that I didn't even think about it. I'll contact them. In the meantime, logs from a little after the latest crash have been sent.
Came across your case and had a look through the logs.
Probably the cable between EDA and NAS acting up, looks like the NAS loses connection to all of the EDA disks at the same time and then tries to hard-reset the link for all of them at the same time, eventually it crashes.
Jun 16 21:09:40 MordorNAS kernel: [572371.575654] ata5.00: failed to read SCR 1 (Emask=0x40) Jun 16 21:09:40 MordorNAS kernel: [572371.575664] ata5.01: failed to read SCR 1 (Emask=0x40) Jun 16 21:09:40 MordorNAS kernel: [572371.575670] ata5.02: failed to read SCR 1 (Emask=0x40) Jun 16 21:09:40 MordorNAS kernel: [572371.575674] ata5.03: failed to read SCR 1 (Emask=0x40) Jun 16 21:09:40 MordorNAS kernel: [572371.575680] ata5.04: failed to read SCR 1 (Emask=0x40) Jun 16 21:09:40 MordorNAS kernel: [572371.575684] ata5.05: failed to read SCR 1 (Emask=0x40)
Jun 16 21:09:40 MordorNAS kernel: [572371.575693] ata5.15: exception Emask 0x4 SAct 0x0 SErr 0x0 action 0x6 frozen
Jun 16 21:09:41 MordorNAS kernel: [572371.575699] ata5.00: exception Emask 0x100 SAct 0x0 SErr 0x0 action 0x6 frozen
Jun 16 21:09:41 MordorNAS kernel: [572371.575705] ata5.01: exception Emask 0x100 SAct 0x0 SErr 0x0 action 0x6 frozen
Jun 16 21:09:41 MordorNAS kernel: [572371.575711] ata5.02: exception Emask 0x100 SAct 0x0 SErr 0x0 action 0x6 frozen
Jun 16 21:09:41 MordorNAS kernel: [572371.575717] ata5.03: exception Emask 0x100 SAct 0x0 SErr 0x0 action 0x6 frozen
Jun 16 21:09:41 MordorNAS kernel: [572371.575722] ata5.03: failed command: READ DMA EXT
Jun 16 21:09:41 MordorNAS kernel: [572371.575732] ata5.03: cmd 25/00:40:80:25:62/00:05:d1:01:00/e0 tag 5 dma 688128 in
Jun 16 21:09:41 MordorNAS kernel: [572371.575732] res 40/00:01:00:4f:c2/00:00:00:00:00/00 Emask 0x4 (timeout)
Jun 16 21:09:41 MordorNAS kernel: [572371.575738] ata5.03: status: { DRDY }
Jun 16 21:09:41 MordorNAS kernel: [572371.575743] ata5.04: exception Emask 0x100 SAct 0x0 SErr 0x0 action 0x6 frozen
Jun 16 21:09:41 MordorNAS kernel: [572371.575749] ata5.05: exception Emask 0x100 SAct 0x0 SErr 0x0 action 0x6 frozen
Either cable or expansion chassis, I'd try to replace the cable myself first.. Just a standard eSATA cable. If that doesn't help it may come down to an RMA of the EDA.
Edit: Actually first of all make sure the cable is properly seated hehe
Thanks. The support case I opened at the suggestion of mdgm has led to the same suggestion. I've ordered a new cable, so it will be a little bit of a wait to see if that fixes the problem.
- So this isn't left unresolved, here is the final answer such as it is. Swapping cables and EDA units did not fix the issue. Eventually support was able to reproduce the crash, but they could not give me an estimate as to when a fix would be issued. At the point where I gave up waiting and started migration to an alternate system, I was on 6.5.1.
NETGEAR Academy
Boost your skills with the Netgear Academy - Get trained, certified and stay ahead with the latest Netgear technology!
Join Us!
