RT-N66U Garbage collection problem

[giorov92]

Hi, getting these over and over again. I'm on latest firmware.

Dec 20 09:57:30 kernel: Argh. No free space left for GC. nr_erasing_blocks is 0. nr_free_blocks is 0. (erasableempty: yes, erasingempty: yes, erasependingempty: yes)
Dec 20 09:57:30 kernel: jffs2_reserve_space_gc of 48 bytes for garbage_collect_dirent failed: -28

Any suggestions? Can I clear something or should I just reset?

Thanks

 

[L&LD]

Welcome to the forums @giorov92.

Faster to just reset.

 

[giorov92]

Alright. Will give it a go!

Thanks for the welcome.

 

[giorov92]

Would you suggest installing Merlin if the router is no longer supported by Merlin devs?

 

[Crimliar]

It's an 11yo design. The last Merlin release is 4 1/2 years old and the last Asus release is just over 18 months old. Personally in that situation, if I had to keep using it then much as I cherish Merlin's work, I'd go with the Asus release.

*Just a personal opinion - based on possibly unjustified fears!

 

[giorov92]

I get the point about the old Merlin firmware, I agree! Thanks

Still got the problem though.

Logs sample (Everything from today siunce the reset I think.Pprevious ones say Jan 13 or other dates before that):

Dec 21 11:29:12 syslogd started: BusyBox v1.17.4
Dec 21 11:29:12 kernel: klogd started: BusyBox v1.17.4 (2020-06-09 09:41:02 CST)
Dec 21 11:29:12 kernel: Argh. No free space left for GC. nr_erasing_blocks is 0. nr_free_blocks is 0. (erasableempty: yes, erasingempty: yes, erasependingempty: yes)
Dec 21 11:29:12 kernel: jffs2_reserve_space_gc of 48 bytes for garbage_collect_dirent failed: -28
Dec 21 11:29:12 kernel: Argh. No free space left for GC. nr_erasing_blocks is 0. nr_free_blocks is 0. (erasableempty: yes, erasingempty: yes, erasependingempty: yes)
Dec 21 11:29:12 kernel: jffs2_reserve_space_gc of 48 bytes for garbage_collect_dirent failed: -28
Dec 21 11:29:12 nat: apply nat rules (/tmp/nat_rules_eth0_eth0)
Dec 21 11:29:13 hour monitor: daemon is starting
Dec 21 11:29:13 hour monitor: daemon terminates
Dec 21 11:29:13 miniupnpd[888]: version 1.9 started
Dec 21 11:29:13 miniupnpd[888]: HTTP listening on port 50644
Dec 21 11:29:13 miniupnpd[888]: Listening for NAT-PMP/PCP traffic on port 5351
Dec 21 11:29:13 RT-N66U: start https:1111
Dec 21 11:29:13 RT-N66U: start httpd:80
Dec 21 11:29:13 httpd: Succeed to init SSL certificate...1111
Dec 21 11:29:13 httpd: Succeed to init SSL certificate...80
Dec 21 11:29:38 kernel: Argh. No free space left for GC. nr_erasing_blocks is 0. nr_free_blocks is 0. (erasableempty: yes, erasingempty: yes, erasependingempty: yes)
Dec 21 11:29:38 kernel: jffs2_reserve_space_gc of 48 bytes for garbage_collect_dirent failed: -28
Dec 21 11:29:38 kernel: Argh. No free space left for GC. nr_erasing_blocks is 0. nr_free_blocks is 0. (erasableempty: yes, erasingempty: yes, erasependingempty: yes)
Dec 21 11:29:38 kernel: jffs2_reserve_space_gc of 48 bytes for garbage_collect_dirent failed: -28
Dec 21 11:30:38 kernel: Argh. No free space left for GC. nr_erasing_blocks is 0. nr_free_blocks is 0. (erasableempty: yes, erasingempty: yes, erasependingempty: yes)
Dec 21 11:30:38 kernel: jffs2_reserve_space_gc of 48 bytes for garbage_collect_dirent failed: -28
Dec 21 11:30:38 kernel: Argh. No free space left for GC. nr_erasing_blocks is 0. nr_free_blocks is 0. (erasableempty: yes, erasingempty: yes, erasependingempty: yes)
Dec 21 11:30:38 kernel: jffs2_reserve_space_gc of 48 bytes for garbage_collect_dirent failed: -28
Dec 21 11:31:38 rc_service: httpd 890:notify_rc restart_net
Dec 21 11:31:38 kernel: Argh. No free space left for GC. nr_erasing_blocks is 0. nr_free_blocks is 0. (erasableempty: yes, erasingempty: yes, erasependingempty: yes)
Dec 21 11:31:38 kernel: jffs2_reserve_space_gc of 48 bytes for garbage_collect_dirent failed: -28
Dec 21 11:31:38 kernel: Argh. No free space left for GC. nr_erasing_blocks is 0. nr_free_blocks is 0. (erasableempty: yes, erasingempty: yes, erasependingempty: yes)
Dec 21 11:31:38 kernel: jffs2_reserve_space_gc of 48 bytes for garbage_collect_dirent failed: -28
Dec 21 11:31:40 miniupnpd[888]: shutting down MiniUPnPd
Dec 21 11:31:46 nat: apply nat rules (/tmp/nat_rules_eth0_eth0)
Dec 21 11:31:46 kernel: wl_module_init: passivemode set to 0x0
Dec 21 11:31:47 kernel: eth1: Broadcom BCM4331 802.11 Wireless Controller 6.30.163.2002 (r382208)
Dec 21 11:31:47 kernel: eth2: Broadcom BCM4331 802.11 Wireless Controller 6.30.163.2002 (r382208)
Dec 21 11:31:47 nat: apply redirect rules
Dec 21 11:31:47 rc_service: udhcpc 1048:notify_rc start_dhcp6c
Dec 21 11:31:47 rc_service: waitting "restart_net" via ...
Dec 21 11:31:50 acsd: selected channel spec: 0x100a (10)
Dec 21 11:31:50 acsd: acs_set_chspec: 0x100a (10) for reason APCS_INIT
Dec 21 11:31:52 acsd: selected channel spec: 0xd99f (161u)
Dec 21 11:31:52 acsd: acs_set_chspec: 0xd99f (161u) for reason APCS_INIT
Dec 21 11:31:52 RT-N66U: start https:1111
Dec 21 11:31:52 RT-N66U: start httpd:80
Dec 21 11:31:52 miniupnpd[1067]: version 1.9 started
Dec 21 11:31:52 miniupnpd[1067]: HTTP listening on port 55247
Dec 21 11:31:52 miniupnpd[1067]: Listening for NAT-PMP/PCP traffic on port 5351
Dec 21 11:31:52 httpd: Succeed to init SSL certificate...1111
Dec 21 11:31:52 httpd: Succeed to init SSL certificate...80
Dec 21 11:31:52 kernel: Argh. No free space left for GC. nr_erasing_blocks is 0. nr_free_blocks is 0. (erasableempty: yes, erasingempty: yes, erasependingempty: yes)
Dec 21 11:31:52 kernel: jffs2_reserve_space_gc of 48 bytes for garbage_collect_dirent failed: -28
Dec 21 11:31:53 rc_service: udhcpc 1048:notify_rc start_firewall
Dec 21 11:31:53 rc_service: waitting "start_dhcp6c" via udhcpc ...
Dec 21 11:31:55 miniupnpd[1067]: shutting down MiniUPnPd
Dec 21 11:31:55 wan: finish adding multi routes
Dec 21 11:31:55 nat: apply nat rules (/tmp/nat_rules_eth0_eth0)
Dec 21 11:31:55 rc_service: udhcpc 1048:notify_rc stop_upnp
Dec 21 11:31:55 rc_service: waitting "start_firewall" via udhcpc ...
Dec 21 11:31:55 miniupnpd[1143]: version 1.9 started
Dec 21 11:31:55 miniupnpd[1143]: HTTP listening on port 46434
Dec 21 11:31:55 miniupnpd[1143]: Listening for NAT-PMP/PCP traffic on port 5351
Dec 21 11:31:56 rc_service: udhcpc 1048:notify_rc start_upnp
Dec 21 11:31:56 rc_service: waitting "stop_upnp" via udhcpc ...
Dec 21 11:31:56 miniupnpd[1143]: shutting down MiniUPnPd
Dec 21 11:31:57 WAN Connection: WAN was restored.
Dec 21 11:31:57 miniupnpd[1149]: version 1.9 started
Dec 21 11:31:57 miniupnpd[1149]: HTTP listening on port 57679
Dec 21 11:31:57 kernel: HTB: quantum of class 10002 is big. Consider r2q change.
Dec 21 11:31:57 kernel: HTB: quantum of class 10060 is big. Consider r2q change.
Dec 21 11:31:57 miniupnpd[1149]: Listening for NAT-PMP/PCP traffic on port 5351
Dec 21 11:31:57 kernel: HTB: quantum of class 20010 is big. Consider r2q change.
Dec 21 11:31:57 kernel: HTB: quantum of class 20040 is big. Consider r2q change.
Dec 21 11:31:57 dhcp client: bound 76.121.121.245/255.255.252.0 via 76.121.120.1 for 202390 seconds.
Dec 21 11:32:01 kernel: Argh. No free space left for GC. nr_erasing_blocks is 0. nr_free_blocks is 0. (erasableempty: yes, erasingempty: yes, erasependingempty: yes)
Dec 21 11:32:01 kernel: jffs2_reserve_space_gc of 48 bytes for garbage_collect_dirent failed: -28
Dec 21 11:32:01 kernel: Argh. No free space left for GC. nr_erasing_blocks is 0. nr_free_blocks is 0. (erasableempty: yes, erasingempty: yes, erasependingempty: yes)
Dec 21 11:32:01 kernel: jffs2_reserve_space_gc of 48 bytes for garbage_collect_dirent failed: -28
Dec 21 11:32:09 kernel: Argh. No free space left for GC. nr_erasing_blocks is 0. nr_free_blocks is 0. (erasableempty: yes, erasingempty: yes, erasependingempty: yes)
Dec 21 11:32:09 kernel: jffs2_reserve_space_gc of 48 bytes for garbage_collect_dirent failed: -28
Dec 21 11:32:09 kernel: Argh. No free space left for GC. nr_erasing_blocks is 0. nr_free_blocks is 0. (erasableempty: yes, erasingempty: yes, erasependingempty: yes)
Dec 21 11:32:09 kernel: jffs2_reserve_space_gc of 48 bytes for garbage_collect_dirent failed: -28
Dec 21 11:32:12 dhcp6 client: bound address 2001:558:600a:c4:64c9:abe:a9b7:d48f/128, prefix 2601:602:87f:a152::/64
Dec 21 11:32:39 kernel: Argh. No free space left for GC. nr_erasing_blocks is 0. nr_free_blocks is 0. (erasableempty: yes, erasingempty: yes, erasependingempty: yes)
Dec 21 11:32:39 kernel: jffs2_reserve_space_gc of 48 bytes for garbage_collect_dirent failed: -28
Dec 21 11:32:39 kernel: Argh. No free space left for GC. nr_erasing_blocks is 0. nr_free_blocks is 0. (erasableempty: yes, erasingempty: yes, erasependingempty: yes)
Dec 21 11:32:39 kernel: jffs2_reserve_space_gc of 48 bytes for garbage_collect_dirent failed: -28
Dec 21 11:33:39 kernel: Argh. No free space left for GC. nr_erasing_blocks is 0. nr_free_blocks is 0. (erasableempty: yes, erasingempty: yes, erasependingempty: yes)
Dec 21 11:33:39 kernel: jffs2_reserve_space_gc of 48 bytes for garbage_collect_dirent failed: -28
Dec 21 11:33:39 kernel: Argh. No free space left for GC. nr_erasing_blocks is 0. nr_free_blocks is 0. (erasableempty: yes, erasingempty: yes, erasependingempty: yes)
Dec 21 11:33:39 kernel: jffs2_reserve_space_gc of 48 bytes for garbage_collect_dirent failed: -28

 

[giorov92]

Wondering if it means hardware failure to some degree and what kind of an impact this would have on operations.

 

[ColinTaylor]

Do a hard reset (Method 1) using the WPS button. If you still get errors it's a hardware fault.

[Wireless Router] ASUS router Hard Factory Reset - Method 1 | Official Support | ASUS Global

 

[giorov92]

Yeah, I did that before these logs. Do you think it's a dying memory storage module of some sort? what happens when garbage collection fails to a device performance usually?

Anyway, ordered an ASUS ROG STRIX GS-AX5400 from eBay. :3

 

[ColinTaylor]

Yeah, I did that before these logs. Do you think it's a dying memory storage module of some sort? what happens when garbage collection fails to a device performance usually?

It usually means that the jffs partition is full up. This space on N66U is particularly small. I suggest you do another factory reset and do not setup anything other than the bare minimum, i.e. do not enable IPv6, HTTPS access or any other optional settings. Does the problem still exist.