×

Introducing the Orbi 970 Series Mesh System with WiFi 7(BE) technology. For more information visit the NETGEAR Press Room.

Orbi WiFi 7 RBE973
Reply

EXT4 Filesystem Errors - Orbi Dying?

RonB223
Aspirant

EXT4 Filesystem Errors - Orbi Dying?

Hi All,

I’ve been having some problems with my router where it will stop working through the Circle application, and BitDefender stops warning of blocked websites or dangerous URLs. Also, in Circle, I don’t have history of websites visited.

I turned on telnet in debug after the last reset to see what’s going on. I’m seeing errors in dmesg when the issue occurs which makes me think the storage in the router used to store logs and info for Circle and BitDefender are bad.

Here’s some of the output of the command “dmesg | grep -i ext4”:

root@RBR40:/# dmesg |grep -i ext4
EXT4-fs: 40 callbacks suppressed
EXT4-fs (mmcblk0p28): Delayed block allocation failed for inode 176 at logical offset 265 with m
ax blocks 1 with error 28
EXT4-fs (mmcblk0p28): This should not happen!! Data will be lost
EXT4-fs (mmcblk0p28): Total free blocks count 0
EXT4-fs (mmcblk0p28): Free/Dirty block details
EXT4-fs (mmcblk0p28): free_blocks=16832
EXT4-fs (mmcblk0p28): dirty_blocks=6978
EXT4-fs (mmcblk0p28): Block reservation details
EXT4-fs (mmcblk0p28): i_reserved_data_blocks=400
EXT4-fs (mmcblk0p28): i_reserved_meta_blocks=135
EXT4-fs (mmcblk0p28): i_allocated_meta_blocks=0
EXT4-fs: 40 callbacks suppressed
EXT4-fs (mmcblk0p28): Delayed block allocation failed for inode 176 at logical offset 265 with m
ax blocks 1 with error 28
EXT4-fs (mmcblk0p28): This should not happen!! Data will be lost
EXT4-fs (mmcblk0p28): Total free blocks count 0
EXT4-fs (mmcblk0p28): Free/Dirty block details
EXT4-fs (mmcblk0p28): free_blocks=16832
EXT4-fs (mmcblk0p28): dirty_blocks=6982
EXT4-fs (mmcblk0p28): Block reservation details
EXT4-fs (mmcblk0p28): i_reserved_data_blocks=400
EXT4-fs (mmcblk0p28): i_reserved_meta_blocks=135
EXT4-fs (mmcblk0p28): i_allocated_meta_blocks=0
EXT4-fs: 40 callbacks suppressed
EXT4-fs (mmcblk0p28): Delayed block allocation failed for inode 176 at logical offset 265 with m
ax blocks 2 with error 28
EXT4-fs (mmcblk0p28): This should not happen!! Data will be lost
EXT4-fs (mmcblk0p28): Total free blocks count 0
EXT4-fs (mmcblk0p28): Free/Dirty block details
EXT4-fs (mmcblk0p28): free_blocks=16832
EXT4-fs (mmcblk0p28): dirty_blocks=6991
EXT4-fs (mmcblk0p28): Block reservation details
EXT4-fs (mmcblk0p28): i_reserved_data_blocks=401
EXT4-fs (mmcblk0p28): i_reserved_meta_blocks=135
EXT4-fs (mmcblk0p28): i_allocated_meta_blocks=0
EXT4-fs: 40 callbacks suppressed
EXT4-fs (mmcblk0p28): Delayed block allocation failed for inode 176 at logical offset 266 with m
ax blocks 1 with error 28
EXT4-fs (mmcblk0p28): This should not happen!! Data will be lost
(Reduced lines to fit post)
—-

So is there any repairing this? Wondering if a factory reset is worth trying or if I should give up hope as there may be damaged flash storage in the unit.

Ron
Model: RBR50|Orbi AC3000 Tri-band WiFi Router
Message 1 of 6
FURRYe38
Guru

Re: EXT4 Filesystem Errors - Orbi Dying?

Netgear has set up a community forum specifically for the Circle product. Most of the people who watch that forum are more likely to have experience with Circle and know how to work it better than those of us who follow this "general Orbi" forum. Might be more likely to find someone who has a solution if the question is posted there:
https://community.netgear.com/t5/Circle-Smart-Parental-Controls/bd-p/en-home-circle


Good Luck

Message 2 of 6
CrimpOn
Guru

Re: EXT4 Filesystem Errors - Orbi Dying?


@RonB223 wrote:
So is there any repairing this? Wondering if a factory reset is worth trying or if I should give up hope as there may be damaged flash storage in the unit.

I certainly would do a Factory Reset and reconfigure before I threw it out.

Message 3 of 6
FURRYe38
Guru

Re: EXT4 Filesystem Errors - Orbi Dying?

Also do you see these log entires with Circle disabled? 

Message 4 of 6
RonB223
Aspirant

Re: EXT4 Filesystem Errors - Orbi Dying?

Well, the system hung while disabling Circle, forcing me to reboot it, and restart all the satellites as they went Orange.  After getting it back online, I re-enabled telnet via the debug screen, and logged back in, and ran "dmesg" to see if there was anything suspicious.  Found that the unit is having some kernel panic messages.  Below is a snippet:

 

CPU: 0 PID: 8065 Comm: devices_info Tainted: P 3.14.77 #2
task: df53de80 ti: dd2c6000 task.ti: dd2c6000
PC is at 0xb6e9557c
LR is at 0x11488
pc : [<b6e9557c>] lr : [<00011488>] psr: 20000010
sp : be888d9c ip : 00000020 fp : be8dd7cc
r10: 01f22008 r9 : 00000001 r8 : 000051fc
r7 : 0000521c r6 : 00000000 r5 : 0000001f r4 : 000051dc
r3 : be88dfa7 r2 : 00000020 r1 : 00000000 r0 : be88dfa8
Flags: nzCv IRQs on FIQs on Mode USER_32 ISA ARM Segment user
Control: 10c5387d Table: 9194806a DAC: 00000015
CPU: 0 PID: 8065 Comm: devices_info Tainted: P 3.14.77 #2
[<c021ea68>] (unwind_backtrace) from [<c021bb60>] (show_stack+0x10/0x14)
[<c021bb60>] (show_stack) from [<c03b5738>] (dump_stack+0x78/0x98)
[<c03b5738>] (dump_stack) from [<c02234b0>] (__do_user_fault+0x74/0xbc)
[<c02234b0>] (__do_user_fault) from [<c022385c>] (do_page_fault+0x2f0/0x370)
[<c022385c>] (do_page_fault) from [<c02083dc>] (do_DataAbort+0x34/0x98)
[<c02083dc>] (do_DataAbort) from [<c02096f4>] (__dabt_usr+0x34/0x40)
Exception stack(0xdd2c7fb0 to 0xdd2c7ff8)
7fa0: be88dfa8 00000000 00000020 be88dfa7
7fc0: 000051dc 0000001f 00000000 0000521c 000051fc 00000001 01f22008 be8dd7cc
7fe0: 00000020 be888d9c 00011488 b6e9557c 20000010 ffffffff
devices_info: unhandled page fault (11) at 0x00000000, code 0x017
pgd = d6c2c000
[00000000] *pgd=93467831, *pte=00000000, *ppte=00000000

CPU: 2 PID: 8068 Comm: devices_info Tainted: P 3.14.77 #2
task: d2a34c80 ti: d42ac000 task.ti: d42ac000
PC is at 0xb6dd457c
LR is at 0x11488
pc : [<b6dd457c>] lr : [<00011488>] psr: 20000010
sp : beda7d9c ip : 00000020 fp : bedfc7cc
r10: 00aa3008 r9 : 00000001 r8 : 000051fc
r7 : 0000521c r6 : 00000000 r5 : 0000001f r4 : 000051dc
r3 : bedacfa7 r2 : 00000020 r1 : 00000000 r0 : bedacfa8
Flags: nzCv IRQs on FIQs on Mode USER_32 ISA ARM Segment user
Control: 10c5387d Table: 96c2c06a DAC: 00000015
CPU: 0 PID: 8068 Comm: devices_info Tainted: P 3.14.77 #2
[<c021ea68>] (unwind_backtrace) from [<c021bb60>] (show_stack+0x10/0x14)
[<c021bb60>] (show_stack) from [<c03b5738>] (dump_stack+0x78/0x98)
[<c03b5738>] (dump_stack) from [<c02234b0>] (__do_user_fault+0x74/0xbc)
[<c02234b0>] (__do_user_fault) from [<c022385c>] (do_page_fault+0x2f0/0x370)
[<c022385c>] (do_page_fault) from [<c02083dc>] (do_DataAbort+0x34/0x98)
[<c02083dc>] (do_DataAbort) from [<c02096f4>] (__dabt_usr+0x34/0x40)
Exception stack(0xd42adfb0 to 0xd42adff8)
dfa0: bedacfa8 00000000 00000020 bedacfa7
dfc0: 000051dc 0000001f 00000000 0000521c 000051fc 00000001 00aa3008 bedfc7cc
dfe0: 00000020 beda7d9c 00011488 b6dd457c 20000010 ffffffff
devices_info: unhandled page fault (11) at 0x00000000, code 0x017
pgd = d7f44000
[00000000] *pgd=962c5831, *pte=00000000, *ppte=00000000

CPU: 2 PID: 8081 Comm: devices_info Tainted: P 3.14.77 #2
task: d2a32d00 ti: d1bc0000 task.ti: d1bc0000
PC is at 0xb6eaa57c
LR is at 0x11488
pc : [<b6eaa57c>] lr : [<00011488>] psr: 20000010
sp : bedd2d9c ip : 00000020 fp : bee277cc
r10: 01622008 r9 : 00000001 r8 : 000051fc
r7 : 0000521c r6 : 00000000 r5 : 0000001f r4 : 000051dc
r3 : bedd7fa7 r2 : 00000020 r1 : 00000000 r0 : bedd7fa8
Flags: nzCv IRQs on FIQs on Mode USER_32 ISA ARM Segment user
pc : [<b6e9557c>] lr : [<00011488>] psr: 20000010
sp : bef07d8c ip : 00000020 fp : bef5c7bc
r10: 0148b008 r9 : 00000001 r8 : 000051fc
r7 : 0000521c r6 : 00000000 r5 : 0000001f r4 : 000051dc
r3 : bef0cf97 r2 : 00000020 r1 : 00000000 r0 : bef0cf98
Flags: nzCv IRQs on FIQs on Mode USER_32 ISA ARM Segment user
Control: 10c5387d Table: 9358406a DAC: 00000015
CPU: 2 PID: 6192 Comm: devices_info Tainted: P 3.14.77 #2
[<c021ea68>] (unwind_backtrace) from [<c021bb60>] (show_stack+0x10/0x14)
[<c021bb60>] (show_stack) from [<c03b5738>] (dump_stack+0x78/0x98)
[<c03b5738>] (dump_stack) from [<c02234b0>] (__do_user_fault+0x74/0xbc)
[<c02234b0>] (__do_user_fault) from [<c022385c>] (do_page_fault+0x2f0/0x370)
[<c022385c>] (do_page_fault) from [<c02083dc>] (do_DataAbort+0x34/0x98)
[<c02083dc>] (do_DataAbort) from [<c02096f4>] (__dabt_usr+0x34/0x40)
Exception stack(0xd648dfb0 to 0xd648dff8)
dfa0: bef0cf98 00000000 00000020 bef0cf97
dfc0: 000051dc 0000001f 00000000 0000521c 000051fc 00000001 0148b008 bef5c7bc
dfe0: 00000020 bef07d8c 00011488 b6e9557c 20000010 ffffffff
devices_info: unhandled page fault (11) at 0x00000000, code 0x017
pgd = cfc7c000
[00000000] *pgd=8fcbd831, *pte=00000000, *ppte=00000000

CPU: 3 PID: 6366 Comm: devices_info Tainted: P 3.14.77 #2
task: d1b18900 ti: cfc22000 task.ti: cfc22000
PC is at 0xb6de457c
LR is at 0x11488
pc : [<b6de457c>] lr : [<00011488>] psr: 20000010
sp : bea7cd8c ip : 00000020 fp : bead17bc
r10: 01812008 r9 : 00000001 r8 : 000051fc
r7 : 0000521c r6 : 00000000 r5 : 0000001f r4 : 000051dc
r3 : bea81f97 r2 : 00000020 r1 : 00000000 r0 : bea81f98
Flags: nzCv IRQs on FIQs on Mode USER_32 ISA ARM Segment user
Control: 10c5387d Table: 8fc7c06a DAC: 00000015
CPU: 1 PID: 6366 Comm: devices_info Tainted: P 3.14.77 #2
[<c021ea68>] (unwind_backtrace) from [<c021bb60>] (show_stack+0x10/0x14)
[<c021bb60>] (show_stack) from [<c03b5738>] (dump_stack+0x78/0x98)
[<c03b5738>] (dump_stack) from [<c02234b0>] (__do_user_fault+0x74/0xbc)
[<c02234b0>] (__do_user_fault) from [<c022385c>] (do_page_fault+0x2f0/0x370)
[<c022385c>] (do_page_fault) from [<c02083dc>] (do_DataAbort+0x34/0x98)

 

Message 5 of 6
FURRYe38
Guru

Re: EXT4 Filesystem Errors - Orbi Dying?

I'd reset the RBR and not enable Circle after settig up the RBR and check again...

Message 6 of 6
Top Contributors
Discussion stats
  • 5 replies
  • 1049 views
  • 0 kudos
  • 3 in conversation
Announcements

Orbi WiFi 7