NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
ReadyNAS 2100 4.2.22 Freeze
Hi,
My 2100 box tend to freeze/hang once a week. No ISCSI response, no HTTPS response, no ping response.
I currently have 2 ISCSI LUN's (500GB each) on it, 2 servers connected (one for each LUN) no CHAP auth.
I need to Power cycle the box to get it up and running again.
I also have 2 to other 2100 boxes with same firmware version, but only one LUN each on those, and much higher load on ISCSI traffic and data on those
but they work prefect and no problems.
All other services besides ISCSI and HTTP/HTTPS are deaktivated on the boxes.
Any hints?
My 2100 box tend to freeze/hang once a week. No ISCSI response, no HTTPS response, no ping response.
I currently have 2 ISCSI LUN's (500GB each) on it, 2 servers connected (one for each LUN) no CHAP auth.
I need to Power cycle the box to get it up and running again.
I also have 2 to other 2100 boxes with same firmware version, but only one LUN each on those, and much higher load on ISCSI traffic and data on those
but they work prefect and no problems.
All other services besides ISCSI and HTTP/HTTPS are deaktivated on the boxes.
Any hints?
5 Replies
- This is what the kernel log day Before it hangs (i think):
May 12 08:38:03 TTNAS1 kernel: general protection fault: 0000 [#1] SMP
May 12 08:38:03 TTNAS1 kernel: last sysfs file: /sys/devices/system/rn_lcd/rn_lcd0/lcd_line2
May 12 08:38:03 TTNAS1 kernel: CPU 0
May 12 08:38:03 TTNAS1 kernel: Modules linked in: target_core_file iscsi_target_mod target_core_mod pvgpio nv6vpd(P)
May 12 08:38:03 TTNAS1 kernel:
May 12 08:38:03 TTNAS1 kernel: Pid: 18335, comm: exim Tainted: P 2.6.37.6.RNx86_64.2.4 #1 NETGEAR ReadyNAS/ReadyNAS
May 12 08:38:03 TTNAS1 kernel: RIP: 0010:[<ffffffff880adcd0>] [<ffffffff880adcd0>] vfs_llseek+0x0/0x30
May 12 08:38:03 TTNAS1 kernel: RSP: 0000:ffff88002df37f30 EFLAGS: 00010286
May 12 08:38:03 TTNAS1 kernel: RAX: fffffffffffffff7 RBX: 00000000ffffffea RCX: 00000000ff843008
May 12 08:38:03 TTNAS1 kernel: RDX: 0000000000000001 RSI: ffffffffffffffe4 RDI: 067f00403a453400
May 12 08:38:03 TTNAS1 kernel: RBP: ffff88002df37f78 R08: 0000000000000001 R09: 00000000ff843020
May 12 08:38:03 TTNAS1 kernel: R10: ffff88002df36000 R11: 0000000000000000 R12: ffffffffffffffe4
May 12 08:38:03 TTNAS1 kernel: R13: 0000000000000001 R14: 067f00403a453400 R15: 00000000ffffffe4
May 12 08:38:03 TTNAS1 kernel: FS: 0000000000000000(0000) GS:ffff88003f200000(0063) knlGS:00000000f73c26b0
May 12 08:38:03 TTNAS1 kernel: CS: 0010 DS: 002b ES: 002b CR0: 000000008005003b
May 12 08:38:03 TTNAS1 kernel: CR2: 00000000080cb234 CR3: 00000000391e8000 CR4: 00000000000006f0
May 12 08:38:03 TTNAS1 kernel: DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
May 12 08:38:03 TTNAS1 kernel: DR3: 0000000000000000 DR6: 00000000ffff0ff0 DR7: 0000000000000400
May 12 08:38:03 TTNAS1 kernel: Process exim (pid: 18335, threadinfo ffff88002df36000, task ffff88003da7ec10)
May 12 08:38:03 TTNAS1 kernel: Stack:
May 12 08:38:03 TTNAS1 kernel: ffffffff880aee55 00000000ff843008 0000000000000000 00000000ff843134
May 12 08:38:03 TTNAS1 kernel: 0000000000000003 0000000000000000 0000000000000000 0000000000000000
May 12 08:38:03 TTNAS1 kernel: 0000000000000000 00000000ff843020 ffffffff88024c53 0000000000000000
May 12 08:38:03 TTNAS1 kernel: Call Trace:
May 12 08:38:03 TTNAS1 kernel: [<ffffffff880aee55>] ? sys_llseek+0x85/0xc0
May 12 08:38:03 TTNAS1 kernel: [<ffffffff88024c53>] ia32_sysret+0x0/0x5
May 12 08:38:03 TTNAS1 kernel: Code: 8a 48 8b 5f 40 eb ae 66 66 66 90 55 48 8b 47 40 48 89 e5 c9 c3 66 66 90 66 66 90 55 48 c7 c0 e3 ff ff ff 48 89 e5 c9 c3 66 66 90 <f6> 47 3c 04 55 48 c7 c1 c0 dc 0a 88 48 89 e5 74 1b 48 8b 47 20
May 12 08:38:03 TTNAS1 kernel: RIP [<ffffffff880adcd0>] vfs_llseek+0x0/0x30
May 12 08:38:03 TTNAS1 kernel: RSP <ffff88002df37f30>
May 12 08:38:03 TTNAS1 kernel: ---[ end trace fe465f10adfe258b ]---
May 12 08:38:05 TTNAS1 kernel: general protection fault: 0000 [#2] SMP
May 12 08:38:05 TTNAS1 kernel: last sysfs file: /sys/devices/system/rn_lcd/rn_lcd0/lcd_line2
May 12 08:38:05 TTNAS1 kernel: CPU 0
May 12 08:38:05 TTNAS1 kernel: Modules linked in: target_core_file iscsi_target_mod target_core_mod pvgpio nv6vpd(P)
May 12 08:38:05 TTNAS1 kernel:
May 12 08:38:05 TTNAS1 kernel: Pid: 18335, comm: exim Tainted: P D 2.6.37.6.RNx86_64.2.4 #1 NETGEAR ReadyNAS/ReadyNAS
May 12 08:38:05 TTNAS1 kernel: RIP: 0010:[<ffffffff880ac8c7>] [<ffffffff880ac8c7>] filp_close+0x17/0x90
May 12 08:38:05 TTNAS1 kernel: RSP: 0000:ffff88002df37ce8 EFLAGS: 00010286
May 12 08:38:05 TTNAS1 kernel: RAX: ffff88000143b008 RBX: d3e4460a25de604c RCX: 0000000000000000
May 12 08:38:05 TTNAS1 kernel: RDX: 0000000000000000 RSI: ffff880039109e40 RDI: d3e4460a25de604c
May 12 08:38:05 TTNAS1 kernel: RBP: ffff88002df37d08 R08: ffff88002df36000 R09: 0000000000000000
May 12 08:38:05 TTNAS1 kernel: R10: ffff88003f211530 R11: 0000000000000000 R12: ffff880039109e40
May 12 08:38:05 TTNAS1 kernel: R13: 0000000000000000 R14: ffff880038e5cdc0 R15: 0000000000000008
May 12 08:38:05 TTNAS1 kernel: FS: 0000000000000000(0000) GS:ffff88003f200000(0000) knlGS:0000000000000000
May 12 08:38:05 TTNAS1 kernel: CS: 0010 DS: 002b ES: 002b CR0: 000000008005003b
May 12 08:38:05 TTNAS1 kernel: CR2: 00000000080cb234 CR3: 000000000880f000 CR4: 00000000000006f0
May 12 08:38:05 TTNAS1 kernel: DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
May 12 08:38:05 TTNAS1 kernel: DR3: 0000000000000000 DR6: 00000000ffff0ff0 DR7: 0000000000000400
May 12 08:38:05 TTNAS1 kernel: Process exim (pid: 18335, threadinfo ffff88002df36000, task ffff88003da7ec10)
May 12 08:38:05 TTNAS1 kernel: Stack:
May 12 08:38:05 TTNAS1 kernel: ffff88003335b800 0000000000000007 ffff880039109e40 0000000000000000
May 12 08:38:05 TTNAS1 kernel: ffff88002df37d48 ffffffff88036843 0000000000000000 ffff88003da7ec10
May 12 08:38:05 TTNAS1 kernel: ffff880039109e40 ffff88003da7ec10 0000000000000135 ffff880038dc4780
May 12 08:38:05 TTNAS1 kernel: Call Trace:
May 12 08:38:05 TTNAS1 kernel: [<ffffffff88036843>] put_files_struct+0xc3/0xd0
May 12 08:38:05 TTNAS1 kernel: [<ffffffff88036895>] exit_files+0x45/0x50
May 12 08:38:05 TTNAS1 kernel: [<ffffffff88037a20>] do_exit+0x190/0x770
May 12 08:38:05 TTNAS1 kernel: [<ffffffff88002bce>] ? apic_timer_interrupt+0xe/0x20
May 12 08:38:05 TTNAS1 kernel: [<ffffffff88035fd0>] ? kmsg_dump+0x110/0x160
May 12 08:38:05 TTNAS1 kernel: [<ffffffff88006506>] oops_end+0xa6/0xb0
May 12 08:38:05 TTNAS1 kernel: [<ffffffff88006606>] die+0x56/0x90
May 12 08:38:05 TTNAS1 kernel: [<ffffffff880040f2>] do_general_protection+0x152/0x160
May 12 08:38:05 TTNAS1 kernel: [<ffffffff885b48ef>] general_protection+0x1f/0x30
May 12 08:38:05 TTNAS1 kernel: [<ffffffff880adcd0>] ? vfs_llseek+0x0/0x30
May 12 08:38:05 TTNAS1 kernel: [<ffffffff880aee55>] ? sys_llseek+0x85/0xc0
May 12 08:38:05 TTNAS1 kernel: [<ffffffff88024c53>] ia32_sysret+0x0/0x5
May 12 08:38:05 TTNAS1 kernel: Code: 83 80 00 00 00 48 8b 1c 24 4c 8b 64 24 08 c9 c3 66 66 66 90 55 48 89 e5 48 83 ec 20 48 89 5d e8 4c 89 65 f0 48 89 fb 4c 89 6d f8 <48> 8b 47 30 49 89 f4 48 85 c0 74 52 48 8b 47 20 48 85 c0 74 44
May 12 08:38:05 TTNAS1 kernel: RIP [<ffffffff880ac8c7>] filp_close+0x17/0x90
May 12 08:38:05 TTNAS1 kernel: RSP <ffff88002df37ce8>
May 12 08:38:05 TTNAS1 kernel: ---[ end trace fe465f10adfe258c ]---
May 12 08:38:05 TTNAS1 kernel: Fixing recursive fault but reboot is needed! - Is this NAS connected to the same switch as the other NAS units? Does this NAS have a gigabit ethernet connection?
- No, it's connected directly to a 100Mbps CISCO Firewall.
I have set the speed/duplex manually on the interfaces.
(there are no performance issues when it's operating normally) - Put a gigabit switch between the NAS and the firewall.
- Did that now, i have to wait a week for the result now ...
NETGEAR Academy
Boost your skills with the Netgear Academy - Get trained, certified and stay ahead with the latest Netgear technology!
Join Us!
