NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.

Forum Discussion

rantech's avatar
rantech
Aspirant
Sep 22, 2017
Solved

"walk_down_proc+2D4" error on ReadyNAS 524

A ReadyNAS 524 that I set up for a friend in June has just crashed with the error message "walk_down_proc+2D4".  The unit was working fine til August 28 and then was shutdown properly because of the ...
Installation & Upgrade
  • mdgm-ntgr's avatar
    mdgm-ntgr
    Sep 27, 2017

    Tech support mode is a boot menu option that boots the system into a low-level diagnostic mode. The RAID isn't even started automatically in this mode. It's designed to enable remote troubleshooting in situations like the one you're facing. This is a very different thing to enabling Secure Diagnostic Mode whilst the system is booted normally.

    See How do I access the boot menu on my ReadyNAS 422, 424, or 524X?

     

    I would suggest you boot into this mode and PM the requested details to Skywalker.

rantech's avatar
rantech
Aspirant
Sep 27, 2017

Logs submitted.

evan2's avatar
evan2
NETGEAR Expert
Sep 27, 2017

rantech

Did you send logs to NSBU_Logs@netgear.com,

I don't see the log.

  • rantech's avatar
    rantech
    Aspirant
    Sep 27, 2017

    pm'd a link to the logs to Marty_M as he requested, but I'll submit to this email address as well.

    • evan2's avatar
      evan2
      NETGEAR Expert
      Sep 27, 2017

      rantech

      There is btrfs errors on your NAS, could do you please create a support case?

      We need to remote access your NAS to fix it.

      ep 26 20:17:06 ReadyNAS-524 kernel: IPv6: ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready
Sep 26 20:17:19 ReadyNAS-524 kernel: ------------[ cut here ]------------
Sep 26 20:17:19 ReadyNAS-524 kernel: WARNING: CPU: 1 PID: 4199 at fs/btrfs/extent-tree.c:921 btrfs_lookup_extent_info+0x433/0x460()
Sep 26 20:17:19 ReadyNAS-524 kernel: Modules linked in: vpd(PO)
Sep 26 20:17:19 ReadyNAS-524 kernel: CPU: 1 PID: 4199 Comm: btrfs-cleaner Tainted: P           O    4.4.79.x86_64.1 #1
Sep 26 20:17:19 ReadyNAS-524 kernel: Hardware name: NETGEAR ReadyNAS 524X/ReadyNAS 524X, BIOS RN524v22 11/29/2016
Sep 26 20:17:19 ReadyNAS-524 kernel:  0000000000000000 ffff88007417fc48 ffffffff883d9498 0000000000000000
Sep 26 20:17:19 ReadyNAS-524 kernel:  ffffffff88cfb334 ffff88007417fc80 ffffffff8806e41c ffff88017ada9320
Sep 26 20:17:19 ReadyNAS-524 kernel:  ffff880074a9a600 ffff88016f310bd0 ffff8801797141b8 0000000000000000
Sep 26 20:17:19 ReadyNAS-524 kernel: Call Trace:
Sep 26 20:17:19 ReadyNAS-524 kernel:  [<ffffffff883d9498>] dump_stack+0x4d/0x65
Sep 26 20:17:19 ReadyNAS-524 kernel:  [<ffffffff8806e41c>] warn_slowpath_common+0x7c/0xb0
Sep 26 20:17:19 ReadyNAS-524 kernel:  [<ffffffff8806e505>] warn_slowpath_null+0x15/0x20
Sep 26 20:17:19 ReadyNAS-524 kernel:  [<ffffffff882d7983>] btrfs_lookup_extent_info+0x433/0x460
Sep 26 20:17:19 ReadyNAS-524 kernel:  [<ffffffff882d83d3>] walk_down_proc+0x1c3/0x2f0
Sep 26 20:17:19 ReadyNAS-524 kernel:  [<ffffffff882d97d8>] walk_down_tree+0x58/0xe0
Sep 26 20:17:19 ReadyNAS-524 kernel:  [<ffffffff882dbe3b>] btrfs_drop_snapshot+0x3bb/0x860
Sep 26 20:17:19 ReadyNAS-524 kernel:  [<ffffffff882f2970>] btrfs_clean_one_deleted_snapshot+0xb0/0x100
Sep 26 20:17:19 ReadyNAS-524 kernel:  [<ffffffff882e9d72>] cleaner_kthread+0x192/0x210
Sep 26 20:17:19 ReadyNAS-524 kernel:  [<ffffffff882e9be0>] ? btrfs_destroy_pinned_extent+0xc0/0xc0
Sep 26 20:17:19 ReadyNAS-524 kernel:  [<ffffffff88088296>] kthread+0xe6/0x100
Sep 26 20:17:19 ReadyNAS-524 kernel:  [<ffffffff880881b0>] ? kthread_create_on_node+0x170/0x170
Sep 26 20:17:19 ReadyNAS-524 kernel:  [<ffffffff88a58a1f>] ret_from_fork+0x3f/0x70
Sep 26 20:17:19 ReadyNAS-524 kernel:  [<ffffffff880881b0>] ? kthread_create_on_node+0x170/0x170
Sep 26 20:17:19 ReadyNAS-524 kernel: ---[ end trace 4b2afed994aef250 ]---
Sep 26 20:17:19 ReadyNAS-524 kernel: ------------[ cut here ]------------
Sep 26 20:17:19 ReadyNAS-524 kernel: kernel BUG at fs/btrfs/extent-tree.c:8573!
Sep 26 20:17:19 ReadyNAS-524 kernel: invalid opcode: 0000 [#1] SMP 
Sep 26 20:17:19 ReadyNAS-524 kernel: Modules linked in: vpd(PO)
Sep 26 20:17:19 ReadyNAS-524 kernel: CPU: 1 PID: 4199 Comm: btrfs-cleaner Tainted: P        W  O    4.4.79.x86_64.1 #1
Sep 26 20:17:19 ReadyNAS-524 kernel: Hardware name: NETGEAR ReadyNAS 524X/ReadyNAS 524X, BIOS RN524v22 11/29/2016
Sep 26 20:17:19 ReadyNAS-524 kernel: task: ffff880074bd4680 ti: ffff88007417c000 task.ti: ffff88007417c000
Sep 26 20:17:19 ReadyNAS-524 kernel: RIP: 0010:[<ffffffff882d84e4>]  [<ffffffff882d84e4>] walk_down_proc+0x2d4/0x2f0
Sep 26 20:17:19 ReadyNAS-524 kernel: RSP: 0018:ffff88007417fd38  EFLAGS: 00010246
Sep 26 20:17:19 ReadyNAS-524 kernel: RAX: 0000000000000000 RBX: 0000000000000002 RCX: 000000000000768b
Sep 26 20:17:19 ReadyNAS-524 kernel: RDX: 000000000000768a RSI: ffff88016f310bd0 RDI: ffff880075010900
Sep 26 20:17:19 ReadyNAS-524 kernel: RBP: ffff88007417fd78 R08: 00000000000196a0 R09: ffffffff882c9101
Sep 26 20:17:19 ReadyNAS-524 kernel: R10: ffff880175e08800 R11: ffff88017ada9320 R12: ffff880074a9a600
Sep 26 20:17:19 ReadyNAS-524 kernel: R13: ffff88016f310e00 R14: ffff880175d616f8 R15: 0000000000000002
Sep 26 20:17:19 ReadyNAS-524 kernel: FS:  0000000000000000(0000) GS:ffff88017fc80000(0000) knlGS:0000000000000000
Sep 26 20:17:19 ReadyNAS-524 kernel: CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
Sep 26 20:17:19 ReadyNAS-524 kernel: CR2: 00007f9ce046d2b0 CR3: 0000000008e65000 CR4: 00000000003406e0
Sep 26 20:17:19 ReadyNAS-524 kernel: DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
Sep 26 20:17:19 ReadyNAS-524 kernel: DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
Sep 26 20:17:19 ReadyNAS-524 kernel: Stack:
Sep 26 20:17:19 ReadyNAS-524 kernel:  ffff880074a9a650 ffff880175e08800 ffff88017ada9320 ffff88016f310e00
Sep 26 20:17:19 ReadyNAS-524 kernel:  0000000000000002 ffff880074a9a600 ffff880175e089df ffff880175e08800
Sep 26 20:17:19 ReadyNAS-524 kernel:  ffff88007417fdc0 ffffffff882d97d8 ffff88017ada9320 0000000100000002
Sep 26 20:17:19 ReadyNAS-524 kernel: Call Trace:
Sep 26 20:17:19 ReadyNAS-524 kernel:  [<ffffffff882d97d8>] walk_down_tree+0x58/0xe0
Sep 26 20:17:19 ReadyNAS-524 kernel:  [<ffffffff882dbe3b>] btrfs_drop_snapshot+0x3bb/0x860
Sep 26 20:17:19 ReadyNAS-524 kernel:  [<ffffffff882f2970>] btrfs_clean_one_deleted_snapshot+0xb0/0x100
Sep 26 20:17:19 ReadyNAS-524 kernel:  [<ffffffff882e9d72>] cleaner_kthread+0x192/0x210
Sep 26 20:17:19 ReadyNAS-524 kernel:  [<ffffffff882e9be0>] ? btrfs_destroy_pinned_extent+0xc0/0xc0
Sep 26 20:17:19 ReadyNAS-524 kernel:  [<ffffffff88088296>] kthread+0xe6/0x100
Sep 26 20:17:19 ReadyNAS-524 kernel:  [<ffffffff880881b0>] ? kthread_create_on_node+0x170/0x170
Sep 26 20:17:19 ReadyNAS-524 kernel:  [<ffffffff88a58a1f>] ret_from_fork+0x3f/0x70
Sep 26 20:17:19 ReadyNAS-524 kernel:  [<ffffffff880881b0>] ? kthread_create_on_node+0x170/0x170
Sep 26 20:17:19 ReadyNAS-524 kernel: Code: e9 b4 fe ff ff 0f 0b 0f 0b 0f 0b 4c 89 f7 e8 64 81 05 00 e9 99 fe ff ff 0f 0b 0f 0b 0f 0b 4c 89 f7 e8 b1 83 05 00 8b 45 d0 eb cf <0f> 0b 4c 89 f7 e8 42 81 05 00 8b 45 d0 eb c0 0f 0b 66 66 2e 0f 
Sep 26 20:17:19 ReadyNAS-524 kernel: RIP  [<ffffffff882d84e4>] walk_down_proc+0x2d4/0x2f0
Sep 26 20:17:19 ReadyNAS-524 kernel:  RSP <ffff88007417fd38>
Sep 26 20:17:19 ReadyNAS-524 kernel: ---[ end trace 4b2afed994aef251 ]---
    • Skywalker's avatar
      Skywalker
      NETGEAR Expert
      Sep 27, 2017

      It looks like you may have been hit by an issue in older firmware when using a combination of quotas plus ReadyDR.  From the 6.8.0 release notes:

       

      Potential file system metadata corruption on ReadyDR destination systems with multiple jobs and quotas enabled.

      Sometimes that sort of metadata corruption can be cleaned up easily in Tech Support mode.  I can check it if you boot into Tech Support mode and PM me the 5-digit number for your box.

      • rantech's avatar
        rantech
        Aspirant
        Sep 27, 2017

        Unfortunately, it is not possible to give you remote access since the box crashes pretty much anytime you try to use the web interface - I was very surprised we could even get the logs out of it.  We tried multiple times to activate the secure diagnostics mode and every time the box crashed.  It is not even possible to power down the box from either the web interface or the power button - the only way to reboot the box is to unplug it and even then it is only functional for a couple of minutes until you try to do anything and then it crashes again.

         

        This is basically the same feedback that initially came through when my own 524 crashed in July and at that time, while we could activate secure diagnostic mode on my box, I was told by the fellow that logged onto it that it couldn't be easily fixed and the best thing to do was to do a full factory restore. Note that I did not have quotas in place on my 524 and to the best of my knowledge no quotas were enabled on this 524 either.

NETGEAR Academy

Boost your skills with the Netgear Academy - Get trained, certified and stay ahead with the latest Netgear technology! 

Join Us!

ProSupport for Business

Comprehensive support plans for maximum network uptime and business peace of mind.

 

Learn More