NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
ReadyNAS Pro6 (OS 6.10.0) crashed
Greetings all,
I think for the first time in years my ReadyNas has crashed. It was not accessible anymore even though it was displaying an IP on the front panel. Changing Ethernet port would change the IP (one is fixed, the other one is DHCP) but I wouldn't be able to access the unit, or ping it anyway.
I had to force a shutdown but after 15 minutes of "powering off, goodbye" I pulled the plug. The unit came back ok, no issues.
I do not see anything wrong from the standard logs, is there anything else I can check to try to ascertain the root cause of this issue?
Thanks!
24 Replies
Replies have been turned off for this discussion
Right, I didn't realise that the system would save all the system logs when downloaded.
So far I think I found this but I am not sure what to make out of it. Any help?
--------------------
Oct 27 07:41:30 Enterprise-NAS kernel: general protection fault: 0000 [#2] SMP
Oct 27 07:41:30 Enterprise-NAS kernel: Modules linked in: nv6lcd(O) vpd(PO)
Oct 27 07:41:30 Enterprise-NAS kernel: CPU: 1 PID: 24426 Comm: bash Tainted: P D O 4.4.178.x86_64.1 #1
Oct 27 07:41:30 Enterprise-NAS kernel: Hardware name: To Be Filled By O.E.M. To Be Filled By O.E.M./To be filled by O.E.M., BIOS 080014 07/26/2010
Oct 27 07:41:30 Enterprise-NAS kernel: task: ffff88007c75aa00 ti: ffff880026760000 task.ti: ffff880026760000
Oct 27 07:41:30 Enterprise-NAS kernel: RIP: 0010:[<ffffffff8813368b>] [<ffffffff8813368b>] dup_fd+0x176/0x1e4
Oct 27 07:41:30 Enterprise-NAS kernel: RSP: 0018:ffff880026763dc0 EFLAGS: 00010206
Oct 27 07:41:30 Enterprise-NAS kernel: RAX: 0000000000000001 RBX: ffff88006ef31b80 RCX: ffff88007cdbd128
Oct 27 07:41:30 Enterprise-NAS kernel: RDX: 28e0ffffffffffff RSI: ffff88005738e828 RDI: ffff88007cdbd120
Oct 27 07:41:30 Enterprise-NAS kernel: RBP: ffff880026763e00 R08: ffff88007cdbd0a8 R09: ffff88007cdbd0a8
Oct 27 07:41:30 Enterprise-NAS kernel: R10: 0000000000000000 R11: 0000000000000000 R12: 0000000000000040
Oct 27 07:41:30 Enterprise-NAS kernel: R13: ffff88007bd9a000 R14: 0000000000000040 R15: ffff88007cdbd080
Oct 27 07:41:30 Enterprise-NAS kernel: FS: 00007fa0bfe4e700(0000) GS:ffff88007f880000(0000) knlGS:0000000000000000
Oct 27 07:41:30 Enterprise-NAS kernel: CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
Oct 27 07:41:30 Enterprise-NAS kernel: CR2: 00000000015201c0 CR3: 0000000029a76000 CR4: 0000000000000670
Oct 27 07:41:30 Enterprise-NAS kernel: Stack:
Oct 27 07:41:30 Enterprise-NAS kernel: ffff88007c210a80 ffff88007cdbd0a8 ffff88007cdbd0a8 0000000001200011
Oct 27 07:41:30 Enterprise-NAS kernel: 0000000000000000 ffff88007c75aa00 00007fa0bfe4e9d0 ffff88007c210a80
Oct 27 07:41:30 Enterprise-NAS kernel: ffff880026763ec8 ffffffff88061585 ffff880026763ed8 00000000880fdff8
Oct 27 07:41:30 Enterprise-NAS kernel: Call Trace:
Oct 27 07:41:30 Enterprise-NAS kernel: [<ffffffff88061585>] copy_process+0x5b1/0x1611
Oct 27 07:41:30 Enterprise-NAS kernel: [<ffffffff8809cb39>] ? rcu_is_watching+0x9/0xb
Oct 27 07:41:30 Enterprise-NAS kernel: [<ffffffff88062727>] _do_fork+0x78/0x243
Oct 27 07:41:30 Enterprise-NAS kernel: [<ffffffff8806d8f0>] ? __set_current_blocked+0x3d/0x51
Oct 27 07:41:30 Enterprise-NAS kernel: [<ffffffff8806da50>] ? sigprocmask+0x5b/0x5f
Oct 27 07:41:30 Enterprise-NAS kernel: [<ffffffff88062964>] SyS_clone+0x14/0x16
Oct 27 07:41:30 Enterprise-NAS kernel: [<ffffffff888e43ca>] entry_SYSCALL_64_fastpath+0x1e/0x8e
Oct 27 07:41:30 Enterprise-NAS kernel: Code: 4d d0 e8 f5 fa ff ff 4c 8b 4d d0 4d 8b 6c 24 08 31 c0 45 89 f4 49 8b 79 08 48 89 f9 4c 39 e0 74 32 49 8b 54 c5 00 48 85 d2 74 07 <f0> 48 ff 42 38 eb 15 49 8b 71 18 48 0f b3 06 89 c6 4d 8b 59 20
Oct 27 07:41:30 Enterprise-NAS kernel: RIP [<ffffffff8813368b>] dup_fd+0x176/0x1e4
Oct 27 07:41:30 Enterprise-NAS kernel: RSP <ffff880026763dc0>
Oct 27 07:41:30 Enterprise-NAS kernel: ---[ end trace d6f71a1ca94fb120 ]---
Oct 27 07:41:30 Enterprise-NAS kernel: general protection fault: 0000 [#3] SMP
Oct 27 07:41:30 Enterprise-NAS kernel: Modules linked in: nv6lcd(O) vpd(PO)
Oct 27 07:41:30 Enterprise-NAS kernel: CPU: 1 PID: 24426 Comm: bash Tainted: P D O 4.4.178.x86_64.1 #1
Oct 27 07:41:30 Enterprise-NAS kernel: Hardware name: To Be Filled By O.E.M. To Be Filled By O.E.M./To be filled by O.E.M., BIOS 080014 07/26/2010
Oct 27 07:41:30 Enterprise-NAS kernel: task: ffff88007c75aa00 ti: ffff880026760000 task.ti: ffff880026760000
Oct 27 07:41:30 Enterprise-NAS kernel: RIP: 0010:[<ffffffff8811b42d>] [<ffffffff8811b42d>] filp_close+0x9/0x6f
Oct 27 07:41:30 Enterprise-NAS kernel: RSP: 0018:ffff880026763ba0 EFLAGS: 00010206
Oct 27 07:41:30 Enterprise-NAS kernel: RAX: 0000000000000001 RBX: ffff88006ef31b80 RCX: ffff88007bd9a000
Oct 27 07:41:30 Enterprise-NAS kernel: RDX: 0000000080000000 RSI: ffff88006ef31b80 RDI: 28e0ffffffffffff
Oct 27 07:41:30 Enterprise-NAS kernel: RBP: ffff880026763bb8 R08: 0000000000000001 R09: ffffffff880ff700
Oct 27 07:41:30 Enterprise-NAS kernel: R10: ffff880026763b30 R11: fffffffffffffffc R12: 0000000000000001
Oct 27 07:41:30 Enterprise-NAS kernel: R13: ffff880056ac1000 R14: 0000000000000000 R15: 0000000000000003
Oct 27 07:41:30 Enterprise-NAS kernel: FS: 0000000000000000(0000) GS:ffff88007f880000(0000) knlGS:0000000000000000
Oct 27 07:41:30 Enterprise-NAS kernel: CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
Oct 27 07:41:30 Enterprise-NAS kernel: CR2: 00000000015201c0 CR3: 0000000008cce000 CR4: 0000000000000670
Oct 27 07:41:30 Enterprise-NAS kernel: Stack:
Oct 27 07:41:30 Enterprise-NAS kernel: ffff88006ef31b80 0000000000000001 ffff880056ac1000 ffff880026763bf8
Oct 27 07:41:30 Enterprise-NAS kernel: ffffffff8813378b 0000000100000001 ffff88007c75aa00 ffff88006ef31b80
Oct 27 07:41:30 Enterprise-NAS kernel: ffff880026763c50 0000000000000001 ffff8800636a34e8 ffff880026763c18
Oct 27 07:41:30 Enterprise-NAS kernel: Call Trace:
Oct 27 07:41:30 Enterprise-NAS kernel: [<ffffffff8813378b>] put_files_struct+0x65/0xad
Oct 27 07:41:30 Enterprise-NAS kernel: [<ffffffff88133854>] exit_files+0x3c/0x41
Oct 27 07:41:30 Enterprise-NAS kernel: [<ffffffff8806500b>] do_exit+0x3d7/0x8fc
Oct 27 07:41:30 Enterprise-NAS kernel: [<ffffffff880055c9>] oops_end+0x9d/0xa4
Oct 27 07:41:30 Enterprise-NAS kernel: [<ffffffff88005625>] die+0x55/0x5e
Oct 27 07:41:30 Enterprise-NAS kernel: [<ffffffff88003a18>] do_general_protection+0x8f/0x135
Oct 27 07:41:30 Enterprise-NAS kernel: [<ffffffff888e5b22>] general_protection+0x22/0x30
Oct 27 07:41:30 Enterprise-NAS kernel: [<ffffffff8813368b>] ? dup_fd+0x176/0x1e4
Oct 27 07:41:30 Enterprise-NAS kernel: [<ffffffff88061585>] copy_process+0x5b1/0x1611
Oct 27 07:41:30 Enterprise-NAS kernel: [<ffffffff8809cb39>] ? rcu_is_watching+0x9/0xb
Oct 27 07:41:30 Enterprise-NAS kernel: [<ffffffff88062727>] _do_fork+0x78/0x243
Oct 27 07:41:30 Enterprise-NAS kernel: [<ffffffff8806d8f0>] ? __set_current_blocked+0x3d/0x51
Oct 27 07:41:30 Enterprise-NAS kernel: [<ffffffff8806da50>] ? sigprocmask+0x5b/0x5f
Oct 27 07:41:30 Enterprise-NAS kernel: [<ffffffff88062964>] SyS_clone+0x14/0x16
Oct 27 07:41:30 Enterprise-NAS kernel: [<ffffffff888e43ca>] entry_SYSCALL_64_fastpath+0x1e/0x8e
Oct 27 07:41:30 Enterprise-NAS kernel: Code: 00 01 00 74 05 b8 02 00 00 00 41 0f ba e0 11 72 03 83 c8 01 48 8d 4d ec 89 45 fc e8 5c e6 00 00 c9 c3 55 48 89 e5 41 55 41 54 53 <48> 8b 47 38 48 85 c0 75 11 48 c7 c7 14 dd b5 88 45 31 e4 e8 f7
Oct 27 07:41:30 Enterprise-NAS kernel: RIP [<ffffffff8811b42d>] filp_close+0x9/0x6f
Oct 27 07:41:30 Enterprise-NAS kernel: RSP <ffff880026763ba0>
Oct 27 07:41:30 Enterprise-NAS kernel: ---[ end trace d6f71a1ca94fb121 ]---
Oct 27 07:41:30 Enterprise-NAS kernel: Fixing recursive fault but reboot is needed!Assuming nothing has changed with the OS recently, I'd run the memory test.
Another cause I've seen posted elsewhere is an aging/dying PSU. Though that would be harder to confirm.
It would be prudent to run a disk test on each volume followed by a scrub. Though that is more about confirming file system integrity.
Hi Stephen,
Thanks for your usual help.
No, nothing has changed. I have moved to iDrive from Crashplan but that was more than a month ago.
I've also found another thread showing the same issues and you were recommending running smartctl - which I have just done: only one drive shows some errors but that was abour 20.000 hours ago so I don't think that's relevant! :)
Disk tests and scrubs are run automatically every month I think. Last was run 28 days ago - maybe I should run another one now.
I think the memory test is run from the boot menu - I'll find out and I'll run it overnight.
I suppose that if the RAM test checks out and drives don't show issues, my next step would be to look at the PSU.
I shall keep you posted.
Thanks!
A silly question for the community, just to sanity check my finding.
To access the BOOT menu I shall power off the NAS, keep holding on the RESET button at the back and power up until the BOOT menu shows up?
I'm sure you understand my caution of pressing a RESET button on a live 12TB NAS ;) I've done this in the past but I cannot remember anymore.
Thanks!
NETGEAR Academy
Boost your skills with the Netgear Academy - Get trained, certified and stay ahead with the latest Netgear technology!
Join Us!
