- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Printer Friendly Page
Re: RNDU4000 loses network
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
RNDU4000 loses network
Hello,
I've been using RNDU4000 on 6.x os for a long time and it was mostly fine. However, lately, such things started happen: all of sudden, every few weeks or so, I can no longer access the NAS. It does not respond to ping. However, it's LCD displays correct IP address. When I unplug network cable, it says network changed. When I replug cable, it again says network changed, but says No IP address, as if it would not get one.
I do not rule out my router acting up, but how do I figure out what's going on?
here are some excerpts from the log around the time where I expect this happens:
Sep 01 21:04:03 nas systemd[1]: radar.service: main process exited, code=exited, status=1 Sep 01 21:04:03 nas systemd[1]: Unit radar.service entered failed state. Sep 01 21:11:14 nas avdu[611]: avdu.c:174(0) CURL failed. Timeout was reached Sep 01 21:11:14 nas systemd[1]: avdu.service: main process exited, code=exited, status=2 Sep 01 21:11:14 nas readynasd[1888]: Antivirus scanner definition file update failed due to downloading fail. Please check internet connection. Sep 01 21:11:14 nas kernel: Disk [0] spinning up... Sep 01 21:11:14 nas systemd[1]: Unit avdu.service entered failed state. Sep 01 21:11:20 nas noflushd[1741]: Spinning up disk 2 (/dev/sdb) after 6:07:18. Sep 01 21:11:24 nas kernel: general protection fault: 0000 [#1] SMP Sep 01 21:11:24 nas kernel: CPU 0 Sep 01 21:11:24 nas kernel: Modules linked in: pvgpio vpd(P) Sep 01 21:11:24 nas kernel: Sep 01 21:11:24 nas kernel: Pid: 634, comm: ping Tainted: P 3.0.101.RNx86_64.3 #1 NETGEAR ReadyNAS/ReadyNAS Sep 01 21:11:24 nas kernel: RIP: 0010:[<ffffffff880d79f9>] [<ffffffff880d79f9>] fget_light+0x99/0xd0 Sep 01 21:11:24 nas kernel: RSP: 0018:ffff880101679b28 EFLAGS: 00010202 Sep 01 21:11:24 nas kernel: RAX: 0000000000000000 RBX: 0000000000000000 RCX: ffff880101679b98 Sep 01 21:11:24 nas kernel: RDX: 48b0020004060008 RSI: ffff880101679b8c RDI: 0000000000000003 Sep 01 21:11:24 nas kernel: RBP: ffff880101679b28 R08: ffff880101678000 R09: 0000000000000001 Sep 01 21:11:24 nas kernel: R10: 0000000000000001 R11: 0000000000000001 R12: ffff880101679ba4 Sep 01 21:11:24 nas kernel: R13: 0000000000000000 R14: ffff880101679bac R15: 0000000000000000 Sep 01 21:11:24 nas kernel: FS: 00007f1aa7e31700(0000) GS:ffff88013fc00000(0000) knlGS:0000000000000000 Sep 01 21:11:24 nas kernel: CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 Sep 01 21:11:24 nas kernel: CR2: 00007f2ca0001f68 CR3: 000000010317b000 CR4: 00000000000007f0 Sep 01 21:11:24 nas kernel: DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000 Sep 01 21:11:24 nas kernel: DR3: 0000000000000000 DR6: 00000000ffff0ff0 DR7: 0000000000000400 Sep 01 21:11:24 nas kernel: Process ping (pid: 634, threadinfo ffff880101678000, task ffff880136ae5550) Sep 01 21:11:24 nas kernel: Stack: Sep 01 21:11:24 nas kernel: ffff880101679f38 ffffffff880e967c ffff880101679be8 ffff8801380d0500 Sep 01 21:11:24 nas kernel: ffff880136ae5550 00000000004c4b3e ffff880101679c98 ffff880101679f48 Sep 01 21:11:24 nas kernel: 0000000101679e78 ffff880101679b90 00007fff3698af30 ffff880101679b98 Sep 01 21:11:24 nas kernel: Call Trace: Sep 01 21:11:24 nas kernel: [<ffffffff880e967c>] do_sys_poll+0x20c/0x510 Sep 01 21:11:24 nas kernel: [<ffffffff880d2445>] ? kmem_cache_free+0x15/0xa0 Sep 01 21:11:24 nas kernel: [<ffffffff8838f77e>] ? radix_tree_lookup_slot+0xe/0x10 Sep 01 21:11:24 nas kernel: [<ffffffff8809e919>] ? find_get_page+0x19/0x70 Sep 01 21:11:24 nas kernel: [<ffffffff88775c82>] ? verify_iovec+0x52/0xd0 Sep 01 21:11:24 nas kernel: [<ffffffff880e8360>] ? poll_schedule_timeout+0x70/0x70 Sep 01 21:11:24 nas kernel: [<ffffffff880e8460>] ? __pollwait+0x100/0x100 Sep 01 21:11:24 nas kernel: [<ffffffff880bb628>] ? handle_pte_fault+0x88/0x7f0 Sep 01 21:11:24 nas kernel: [<ffffffff887cf3a5>] ? udp_lib_get_port+0x205/0x330 Sep 01 21:11:24 nas kernel: [<ffffffff880bd0df>] ? handle_mm_fault+0x12f/0x1f0 Sep 01 21:11:24 nas kernel: [<ffffffff880bf641>] ? find_vma+0x21/0xa0 Sep 01 21:11:24 nas kernel: [<ffffffff8876b750>] ? __sys_sendmmsg+0xa0/0x160 Sep 01 21:11:24 nas kernel: [<ffffffff8806cc8f>] ? ktime_get_ts+0xaf/0xf0 Sep 01 21:11:24 nas kernel: [<ffffffff880e8703>] ? poll_select_set_timeout+0x73/0x90 Sep 01 21:11:24 nas kernel: [<ffffffff880e9a48>] sys_poll+0x68/0xf0 Sep 01 21:11:24 nas kernel: [<ffffffff8888bf7b>] system_call_fastpath+0x16/0x1b Sep 01 21:11:24 nas kernel: Code: c3 90 31 d2 eb f6 0f 1f 40 00 48 8b 40 08 31 d2 3b 38 73 e8 89 ff 48 8b 40 08 48 8d 04 f8 48 8b 10 48 85 d2 74 d6 b8 00 00 00 00 <f6> 42 3d 40 48 0f 45 d0 48 89 d0 5d c3 48 85 ff 74 c5 48 8d 4f Sep 01 21:11:24 nas kernel: RIP [<ffffffff880d79f9>] fget_light+0x99/0xd0 Sep 01 21:11:24 nas kernel: RSP <ffff880101679b28> Sep 01 21:11:24 nas kernel: ---[ end trace bca49a215710ffe3 ]--- Sep 01 21:11:24 nas kernel: general protection fault: 0000 [#2] SMP Sep 01 21:11:25 nas kernel: CPU 0 Sep 01 21:11:25 nas kernel: Modules linked in: pvgpio vpd(P) Sep 01 21:11:25 nas kernel: Sep 01 21:11:25 nas kernel: Pid: 634, comm: ping Tainted: P D 3.0.101.RNx86_64.3 #1 NETGEAR ReadyNAS/ReadyNAS Sep 01 21:11:25 nas kernel: RIP: 0010:[<ffffffff880d3de6>] [<ffffffff880d3de6>] filp_close+0x16/0xa0 Sep 01 21:11:25 nas kernel: RSP: 0018:ffff8801016798b8 EFLAGS: 00010206 Sep 01 21:11:25 nas kernel: RAX: ffff880113917008 RBX: 0000000000000000 RCX: 0000000000000001 Sep 01 21:11:25 nas kernel: RDX: 0000000000000001 RSI: ffff88013f076680 RDI: 48b09a3a275e1b84 Sep 01 21:11:25 nas kernel: RBP: ffff8801016798d8 R08: 0000000000000000 R09: ffffffff880bf4bb Sep 01 21:11:25 nas kernel: R10: ffff880137958310 R11: 0000000000000001 R12: 0000000000000001 Sep 01 21:11:25 nas kernel: R13: 0000000000000007 R14: ffff880139025080 R15: ffff88013f076680 Sep 01 21:11:25 nas kernel: FS: 00007f1aa7e31700(0000) GS:ffff88013fc00000(0000) knlGS:0000000000000000 Sep 01 21:11:25 nas kernel: CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 Sep 01 21:11:25 nas kernel: CR2: 00007f2ca0001f68 CR3: 0000000008bc1000 CR4: 00000000000007f0 Sep 01 21:11:25 nas kernel: DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000 Sep 01 21:11:25 nas kernel: DR3: 0000000000000000 DR6: 00000000ffff0ff0 DR7: 0000000000000400 Sep 01 21:11:25 nas kernel: Process ping (pid: 634, threadinfo ffff880101678000, task ffff880136ae5550) Sep 01 21:11:25 nas kernel: Stack: Sep 01 21:11:25 nas kernel: ffffffff88958200 0000000000000000 0000000000000001 0000000000000007 Sep 01 21:11:25 nas kernel: ffff880101679928 ffffffff8804bd71 0000000000000000 ffff880100000001 Sep 01 21:11:25 nas kernel: ffff880101679948 ffff880136ae5550 ffff88013f076680 00000000000000df Sep 01 21:11:25 nas kernel: Call Trace: Sep 01 21:11:25 nas kernel: [<ffffffff8804bd71>] put_files_struct+0x91/0xf0 Sep 01 21:11:25 nas kernel: [<ffffffff8804be77>] exit_files+0x47/0x60 Sep 01 21:11:25 nas kernel: [<ffffffff8804c4f1>] do_exit+0x661/0x810 Sep 01 21:11:25 nas kernel: [<ffffffff8804a30b>] ? kmsg_dump+0x5b/0x100 Sep 01 21:11:25 nas kernel: [<ffffffff88006291>] oops_end+0x91/0xe0 Sep 01 21:11:25 nas kernel: [<ffffffff88006427>] die+0x57/0x90 Sep 01 21:11:25 nas kernel: [<ffffffff88003387>] do_general_protection+0x157/0x160 Sep 01 21:11:25 nas kernel: [<ffffffff8888ba1f>] general_protection+0x1f/0x30 Sep 01 21:11:25 nas kernel: [<ffffffff880d79f9>] ? fget_light+0x99/0xd0 Sep 01 21:11:25 nas kernel: [<ffffffff880e967c>] do_sys_poll+0x20c/0x510 Sep 01 21:11:25 nas kernel: [<ffffffff880d2445>] ? kmem_cache_free+0x15/0xa0 Sep 01 21:11:25 nas kernel: [<ffffffff8838f77e>] ? radix_tree_lookup_slot+0xe/0x10 Sep 01 21:11:25 nas kernel: [<ffffffff8809e919>] ? find_get_page+0x19/0x70 Sep 01 21:11:25 nas kernel: [<ffffffff88775c82>] ? verify_iovec+0x52/0xd0 Sep 01 21:11:25 nas kernel: [<ffffffff880e8360>] ? poll_schedule_timeout+0x70/0x70 Sep 01 21:11:25 nas kernel: [<ffffffff880e8460>] ? __pollwait+0x100/0x100 Sep 01 21:11:25 nas kernel: [<ffffffff880bb628>] ? handle_pte_fault+0x88/0x7f0 Sep 01 21:11:25 nas kernel: [<ffffffff887cf3a5>] ? udp_lib_get_port+0x205/0x330 Sep 01 21:11:25 nas kernel: [<ffffffff880bd0df>] ? handle_mm_fault+0x12f/0x1f0 Sep 01 21:11:25 nas kernel: [<ffffffff880bf641>] ? find_vma+0x21/0xa0 Sep 01 21:11:25 nas kernel: [<ffffffff8876b750>] ? __sys_sendmmsg+0xa0/0x160 Sep 01 21:11:25 nas kernel: [<ffffffff8806cc8f>] ? ktime_get_ts+0xaf/0xf0 Sep 01 21:11:25 nas kernel: [<ffffffff880e8703>] ? poll_select_set_timeout+0x73/0x90 Sep 01 21:11:25 nas kernel: [<ffffffff880e9a48>] sys_poll+0x68/0xf0 Sep 01 21:11:25 nas kernel: [<ffffffff8888bf7b>] system_call_fastpath+0x16/0x1b Sep 01 21:11:25 nas kernel: Code: f0 4c 8b 65 f8 48 89 ec 5d c3 66 66 2e 0f 1f 84 00 00 00 00 00 55 48 8d 2c 24 48 8d 64 24 e0 48 89 5d e8 4c 89 65 f0 4c 89 6d f8 Sep 01 21:11:25 nas : 8b 47 30 48 85 c0 48 8d 1f 74 63 48 8b 47 20 4c 8d 26 48 85 Sep 01 21:11:25 nas kernel: RIP [<ffffffff880d3de6>] filp_close+0x16/0xa0 Sep 01 21:11:25 nas kernel: RSP <ffff8801016798b8> Sep 01 21:11:25 nas kernel: ---[ end trace bca49a215710ffe4 ]--- Sep 01 21:11:25 nas kernel: Fixing recursive fault but reboot is needed!
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Re: RNDU4000 loses network
Which version of OS6 are you running?
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Re: RNDU4000 loses network
Hello,
sorry for very late reply, but I was on vacation, then on business trip..
anyway, now it happened again, and RAIDar is not able to locate it either. Looking at it physically it still shows correct IP address, so it thinks it's fine, but it's not.
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Re: RNDU4000 loses network
What firmware are you running? Does your router have IPv6 turned on?
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Re: RNDU4000 loses network
Correct one, the one it's supposed to have.