NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
pcha
Apr 09, 2019Aspirant
RND-4D Error: add_dirent_to_buf+11c
Dear all,
We have a NAS RN10400 and it is shows on the screen Error: add_dirent_to_buf+11c . We have tried to reset it, reinstall OS, USB recovery and everything has failed. Is someone ...
StephenB
Apr 09, 2019Guru - Experienced User
I'm wondering if this is the issue:
Bad block table found at page 65472, version 0x01 Bad block table found at page 65408, version 0x01 nand_read_bbt: Bad block at 0x000000080000 nand_read_bbt: Bad block at 0x000007d60000
JohnCM_S
Apr 10, 2019NETGEAR Employee Retired
Hi pcha,
The add_dirent_to_buf means that the device is trying to add a new directory to the OS.
Please provide the logs from the unit after you tried putting in a scratch disk as they were not attached on the logs provided.
Regards,
- pchaApr 10, 2019Aspirant
Dear all,
Thank you for the responses, I am attaching the log of the factory default option using a scratch disk. The following log is after attaching the array HDDs back to the device.
** LOADER **
U-Boot 2011.12-gec25d27-dirty (Oct 26 2015 - 16:56:14) Marvell version: v2011.12 2014_T2.0p1
06/23/2015 ReadyNAS-104 V2.0Board: DB-88F6710-BP
SoC: MV6710 A1
CPU: Marvell PJ4B v7 UP (Rev 1) LE
CPU @ 1200 [MHz]
L2 @ 600 [MHz]
TClock @ 200 [MHz]
DDR @ 600 [MHz]
DDR 16Bit Width, FastPath Memory Access
DRAM: 512 MiBMap: Code: 0x1feef000:0x1ff9f514
BSS: 0x1ffef8a0
Stack: 0x1f9eeef8
Heap: 0x1f9ef000:0x1feef000NAND: (ID 0xf1ad) 128 MiB
MMC: MRVL_MMC: 0
Bad block table found at page 65472, version 0x01
Bad block table found at page 65408, version 0x01
nand_read_bbt: Bad block at 0x000000080000
nand_read_bbt: Bad block at 0x000007d60000Initialize and scan all PCI interfaces
PEX unit.port(active IF[-first bus]):
------------------------------------------
PEX 0: Root Complex Interface, Detected Link X1, GEN 2.0
PEX 1: Root Complex Interface, Detected Link X1, GEN 2.0
FPU not initialized
USB 0: Host Mode
USB 1: Host Mode
Shutting down unused interfaces:
SDIO
AUDIO
TDM
Modules/Interfaces Detected:
RGMII0 Phy
RGMII1 Phy
PEX0 (Lane 0)
PEX1 (Lane 1)
SATA0 (Lane 2)
SATA1 (Lane 3)
Net: egiga0
Warning: egiga0 MAC addresses don't match:
Address in SROM is 28:c6:08:35:a1:62
Address in environment is 28:c6:08:00:35:a1
, egiga1 [PRIME]
Power On!FDT loaded successfully
Saving Environment to NAND...
Erasing Nand...
Writing to Nand... done
Hit any key to stop autoboot: 0NAND read: device 0 offset 0x200000, size 0x400000
4194304 bytes read: OKNAND read: device 0 offset 0x800000, size 0x400000
4194304 bytes read: OK
## Booting kernel from Legacy Image at 02000000 ...
Image Name: Linux-4.4.140.armada.1
Created: 2018-07-17 15:56:09 UTC
Image Type: ARM Linux Kernel Image (uncompressed)
Data Size: 3478912 Bytes = 3.3 MiB
Load Address: 00008000
Entry Point: 00008000
Verifying Checksum ... OK
## Loading init Ramdisk from Legacy Image at 03000000 ...
Image Name: initramfs
Created: 2018-09-02 7:12:34 UTC
Image Type: ARM Linux RAMDisk Image (lzma compressed)
Data Size: 3390695 Bytes = 3.2 MiB
Load Address: 00000000
Entry Point: 00000000
Verifying Checksum ... OK
## Flattened Device Tree blob at 01000000
Booting using the fdt blob at 0x01000000
Loading Kernel Image ... OK
Loading Ramdisk to 1f6b2000, end 1f9edce7 ... OK
Using Device Tree in place at 01000000, end 010068e5
Updating device tree successfulStarting kernel ...
Starting the boot process...
Detected system type: RN104
Loading kernel modules...done
Boot mode: Normal
UBI device number 0, total 919 LEBs (116690944 bytes, 111.3 MiB), available 9 LEBs (1142784 bytes, 1.1 MiB), LEB size 126976 bytes (124.0 KiB)
Segmentation fault
Segmentation fault
Segmentation fault
Segmentation fault
Bringing up network...done
Bringing up RAID arrays...done
e2fsck 1.42.13 (17-May-2015)
080035a1_root: recovering journal
080035a1_root: clean, 11/1048576 files, 86094/1047552 blocks
*** Need to update root image! ***
Extracting root image...[ 24.513055] Internal error: Oops: 17 [#1] SMP ARM
[ 24.620645] Modules linked in: vpd(PO)
[ 24.624443] CPU: 0 PID: 957 Comm: tar Tainted: P O 4.4.140.armada.1 #1
[ 24.632135] Hardware name: Marvell Armada 370/XP (Device Tree)
[ 24.637995] task: df2b1f80 ti: db23c000 task.ti: db23c000
[ 24.643421] PC is at add_dirent_to_buf+0x11c/0x1e4
[ 24.648235] LR is at 0x76726573
[ 24.651394] pc : [<c01504b4>] lr : [<76726573>] psr: 60000013
[ 24.651394] sp : db23de20 ip : 00000065 fp : def7a360
[ 24.662924] r10: db23dec4 r9 : 00001000 r8 : def7a438
[ 24.668173] r7 : def3d020 r6 : def555c0 r5 : 00000000 r4 : 00000000
[ 24.674729] r3 : 00000069 r2 : 80000000 r1 : def5829b r0 : 00000000
[ 24.681288] Flags: nZCv IRQs on FIQs on Mode SVC_32 ISA ARM Segment user
[ 24.688456] Control: 10c5387d Table: 1b1fc019 DAC: 00000055
[ 24.694229] Process tar (pid: 957, stack limit = 0xdb23c218)
[ 24.699915] Stack: (0xdb23de20 to 0xdb23e000)
[ 24.704298] de20: db23dec4 db23dec4 db23de60 4b5cc3cb 5cadcab1 2cb4177d def573e0 def555c0
[ 24.712517] de40: def74e58 def58260 00000001 c068f3e5 00000001 def3d020 def7a360 c0150c98
[ 24.720736] de60: d4db9328 def555c0 00000018 db23df50 00000000 def7a438 def58260 c00db714
[ 24.728955] de80: db23dea8 00001000 00000000 00000000 dad58000 c00de8bc df01d000 00000000
[ 24.737174] dea0: 00000000 def57390 def58268 def57390 db23df50 c0685634 def58268 c00e834c
[ 24.745393] dec0: 00000000 def58278 def5828c 0000000f 00000004 0000002a c0912300 def57390
[ 24.753612] dee0: db23df50 def7a438 def3d020 def58260 def3d020 def74e58 def58260 df019010
[ 24.761831] df00: def7a360 c01510f8 def7a438 def3d020 00000000 00000012 def74e58 c01530b0
[ 24.770050] df20: 00000000 00000000 00000004 00000c34 00000023 00000000 def74e58 def74e58
[ 24.778268] df40: 00000000 def58260 df019010 00262230 ffffff9c 00000000 00000000 c00e00b0
[ 24.786486] df60: def74e58 def58260 df019010 00262060 df019000 def58260 00000000 c00e1290
[ 24.794705] df80: dad9e510 def57390 00262230 00262060 00262008 00262259 00000053 c000ece4
[ 24.802924] dfa0: db23c000 c000eb20 00262060 00262008 00262218 00262230 0000a1ff 0000a000
[ 24.811143] dfc0: 00262060 00262008 00262259 00000053 00002c42 00000000 b6f88f70 00000000
[ 24.819362] dfe0: 000867a4 bef31a38 0003f9cc b6f09d9c 60000010 00262218 00000000 00000000
[ 24.827591] [<c01504b4>] (add_dirent_to_buf) from [<c0150c98>] (ext4_add_entry+0x71c/0xb68)
[ 24.835985] [<c0150c98>] (ext4_add_entry) from [<c01510f8>] (ext4_add_nondir+0x14/0x58)
[ 24.844030] [<c01510f8>] (ext4_add_nondir) from [<c01530b0>] (ext4_symlink+0x230/0x2fc)
[ 24.852081] [<c01530b0>] (ext4_symlink) from [<c00e00b0>] (vfs_symlink+0xb8/0x128)
[ 24.859693] [<c00e00b0>] (vfs_symlink) from [<c00e1290>] (SyS_symlinkat+0x60/0xac)
[ 24.867310] [<c00e1290>] (SyS_symlinkat) from [<c000eb20>] (ret_fast_syscall+0x0/0x40)
[ 24.875268] Code: e1a00004 ebffff89 e3500000 bafffff5 (e594101c)
[ 24.881459] ---[ end trace 495f6cf48a44a5ca ]---
[ 24.886101] Kernel panic - not syncing: Fatal exception
[ 24.891356] ---[ end Kernel panic - not syncing: Fatal exception- JohnCM_SApr 16, 2019NETGEAR Employee Retired
Hi pcha,
I am just checking if you still need assistance on this. We would like to know what is happening on the NAS during the USB recovery. This should also output to the console. You may just get the logs then provide it to us so we can further diagnose the issue.
Regards,
Related Content
NETGEAR Academy

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