What's new

RT-AC86U Errors after latest firmware update (386.14)

  • SNBForums Code of Conduct

    SNBForums is a community for everyone, no matter what their level of experience.

    Please be tolerant and patient of others, especially newcomers. We are all here to share and learn!

    The rules are simple: Be patient, be nice, be helpful or be gone!

mozzarella

New Around Here
Hi All,
during last update I did mistake and hit update button instead of upload file mannualy. It tooks long time to update and in meantime i stop it and tried
to upload new firmware in a standard way. It was not possible even GUI gives me "success" message.
Finaly I did NAVRAM erase using amtm. It not helped but finally I was able to update firmware using asus restoration tool.
After that router is working, navigation is slightly slower and I feel that not all function are working as it should. I see below errors in the system log.
I know that this is EoL product but maybe someone has idea what was broken during Navram erase process.
Thanks!

Code:
Jul 26 16:51:58 kernel: UBIFS error (ubi1:0 pid 27738): do_readpage: cannot read page 2 of inode 65, error -22
Jul 26 16:51:58 kernel: UBIFS (ubi1:0): un-mount UBI device 1
Jul 26 16:51:58 kernel: ubi1: detaching mtd10
Jul 26 16:51:58 kernel: ubi1: mtd10 is detached
Jul 26 16:51:58 kernel: ubi1: attaching mtd10
Jul 26 16:51:58 kernel: ubi1: scanning is finished
Jul 26 16:51:58 kernel: ubi1: attached mtd10 (name "misc1", size 8 MiB)
Jul 26 16:51:58 kernel: ubi1: PEB size: 131072 bytes (128 KiB), LEB size: 126976 bytes
Jul 26 16:51:58 kernel: ubi1: min./max. I/O unit sizes: 2048/2048, sub-page size 2048
Jul 26 16:51:58 kernel: ubi1: VID header offset: 2048 (aligned 2048), data offset: 4096
Jul 26 16:51:58 kernel: ubi1: good PEBs: 64, bad PEBs: 0, corrupted PEBs: 0
Jul 26 16:51:58 kernel: ubi1: user volume: 1, internal volumes: 1, max. volumes count: 128
Jul 26 16:51:58 kernel: ubi1: max/mean erase counter: 70/28, WL threshold: 4096, image sequence number: 1982616507
Jul 26 16:51:58 kernel: ubi1: available PEBs: 0, total reserved PEBs: 64, PEBs reserved for bad PEB handling: 4
Jul 26 16:51:58 kernel: ubi1: background thread "ubi_bgt1d" started, PID 27818
Jul 26 16:51:59 kernel: UBIFS (ubi1:0): UBIFS: mounted UBI device 1, volume 0, name "nvram", R/O mode
Jul 26 16:51:59 kernel: UBIFS (ubi1:0): LEB size: 126976 bytes (124 KiB), min./max. I/O unit sizes: 2048 bytes/2048 bytes
Jul 26 16:51:59 kernel: UBIFS (ubi1:0): FS size: 5840896 bytes (5 MiB, 46 LEBs), journal size 1396736 bytes (1 MiB, 11 LEBs)
Jul 26 16:51:59 kernel: UBIFS (ubi1:0): reserved for root: 0 bytes (0 KiB)
Jul 26 16:51:59 kernel: UBIFS (ubi1:0): media format: w4/r0 (latest is w4/r0), UUID 70AF44BE-3B19-4ECF-B11E-616114B3F8BB, small LPT model
Jul 26 16:51:59 kernel: bcm63xx_nand ff801800.nand: uncorrectable error at 0xc1d4c00
Jul 26 16:51:59 kernel: ubi1 warning: ubi_io_read: error -74 (ECC error) while reading 160 bytes from PEB 22:84184, read only 160 bytes, retry
Jul 26 16:51:59 kernel: bcm63xx_nand ff801800.nand: uncorrectable error at 0xc1d4c00
Jul 26 16:51:59 kernel: ubi1 warning: ubi_io_read: error -74 (ECC error) while reading 160 bytes from PEB 22:84184, read only 160 bytes, retry
Jul 26 16:51:59 kernel: bcm63xx_nand ff801800.nand: uncorrectable error at 0xc1d4c00
Jul 26 16:51:59 kernel: ubi1 warning: ubi_io_read: error -74 (ECC error) while reading 160 bytes from PEB 22:84184, read only 160 bytes, retry
Jul 26 16:51:59 kernel: bcm63xx_nand ff801800.nand: uncorrectable error at 0xc1d4c00
Jul 26 16:51:59 kernel: ubi1 error: ubi_io_read: error -74 (ECC error) while reading 160 bytes from PEB 22:84184, read 160 bytes
Jul 26 16:51:59 kernel: CPU: 1 PID: 27805 Comm: envrams Tainted: P           O    4.1.27 #2
Jul 26 16:51:59 kernel: Hardware name: Broadcom-v8A (DT)
Jul 26 16:51:59 kernel: Call trace:
Jul 26 16:51:59 kernel: [<ffffffc0000876d8>] dump_backtrace+0x0/0x150
Jul 26 16:51:59 kernel: [<ffffffc00008783c>] show_stack+0x14/0x20
Jul 26 16:51:59 kernel: [<ffffffc0004f99c8>] dump_stack+0x90/0xb0
Jul 26 16:51:59 kernel: [<ffffffc0003447bc>] ubi_io_read+0x16c/0x388
Jul 26 16:51:59 kernel: [<ffffffc000341e28>] ubi_eba_read_leb+0x138/0x440
Jul 26 16:51:59 kernel: [<ffffffc000341134>] ubi_leb_read+0x7c/0xe0
Jul 26 16:51:59 kernel: [<ffffffc000215a50>] ubifs_leb_read+0x38/0xb0
Jul 26 16:51:59 kernel: [<ffffffc0002176ac>] ubifs_read_node+0x9c/0x330
Jul 26 16:51:59 kernel: [<ffffffc0002179fc>] ubifs_read_node_wbuf+0xbc/0x358
Jul 26 16:51:59 kernel: [<ffffffc0002346fc>] ubifs_tnc_read_node+0x44/0x130
Jul 26 16:51:59 kernel: [<ffffffc00021b040>] ubifs_tnc_locate+0x1c8/0x1e0
Jul 26 16:51:59 kernel: [<ffffffc0002128fc>] ubifs_iget+0x8c/0x668
Jul 26 16:51:59 kernel: [<ffffffc00020fd80>] ubifs_lookup+0x108/0x1d8
Jul 26 16:51:59 kernel: [<ffffffc000146ddc>] lookup_real+0x24/0x68
Jul 26 16:51:59 kernel: [<ffffffc00014bc8c>] do_last.isra.13+0x78c/0xc20
Jul 26 16:51:59 kernel: [<ffffffc00014c1a4>] path_openat+0x84/0x5c0
Jul 26 16:51:59 kernel: [<ffffffc00014d7d8>] do_filp_open+0x30/0x98
Jul 26 16:51:59 kernel: [<ffffffc00013d158>] do_sys_open+0x140/0x228
Jul 26 16:51:59 kernel: [<ffffffc0001859ec>] compat_SyS_open+0x1c/0x28
Jul 26 16:51:59 kernel: bcm63xx_nand ff801800.nand: uncorrectable error at 0xc287c00
Jul 26 16:51:59 kernel: ubi1 warning: ubi_io_read: error -74 (ECC error) while reading 870 bytes from PEB 28:30072, read only 870 bytes, retry
Jul 26 16:52:00 kernel: bcm63xx_nand ff801800.nand: uncorrectable error at 0xc287c00
Jul 26 16:52:00 kernel: ubi1 warning: ubi_io_read: error -74 (ECC error) while reading 870 bytes from PEB 28:30072, read only 870 bytes, retry
Jul 26 16:52:00 kernel: bcm63xx_nand ff801800.nand: uncorrectable error at 0xc287c00
Jul 26 16:52:00 kernel: ubi1 warning: ubi_io_read: error -74 (ECC error) while reading 870 bytes from PEB 28:30072, read only 870 bytes, retry
Jul 26 16:52:00 kernel: bcm63xx_nand ff801800.nand: uncorrectable error at 0xc287c00
Jul 26 16:52:00 kernel: ubi1 error: ubi_io_read: error -74 (ECC error) while reading 870 bytes from PEB 28:30072, read 870 bytes
Jul 26 16:52:00 kernel: CPU: 1 PID: 27805 Comm: envrams Tainted: P           O    4.1.27 #2
Jul 26 16:52:00 kernel: Hardware name: Broadcom-v8A (DT)
...
Jul 26 16:52:00 kernel: UBIFS error (ubi1:0 pid 27805): read_block: bad data node (block 2, inode 65)
Jul 26 16:52:00 kernel:     magic          0x6101831
Jul 26 16:52:00 kernel:     crc            0xfa8eafea
Jul 26 16:52:00 kernel:     node_type      1 (data node)
Jul 26 16:52:00 kernel:     group_type     0 (no node group)
Jul 26 16:52:00 kernel:     sqnum          21061
Jul 26 16:52:00 kernel:     len            1232
Jul 26 16:52:00 kernel:     key            (65, data, 2)
Jul 26 16:52:00 kernel:     size           4006
Jul 26 16:52:00 kernel:     compr_typ      2
Jul 26 16:52:00 kernel:     data size      1184
Jul 26 16:52:00 kernel:     data:
Jul 26 16:52:00 kernel:     00000000: dd 55 c9 6e 22 49 10 e5 53 e6 03 b0 27 33 72 2d a4 3a 18 83 6f a3 91 2c b7 a6 6f 28 57 84 6c 0c
 
Hi All,
during last update I did mistake and hit update button instead of upload file mannualy. It tooks long time to update and in meantime i stop it and tried
to upload new firmware in a standard way. It was not possible even GUI gives me "success" message.
Finaly I did NAVRAM erase using amtm. It not helped but finally I was able to update firmware using asus restoration tool.
After that router is working, navigation is slightly slower and I feel that not all function are working as it should. I see below errors in the system log.
I know that this is EoL product but maybe someone has idea what was broken during Navram erase process.
Thanks!

Code:
Jul 26 16:51:58 kernel: UBIFS error (ubi1:0 pid 27738): do_readpage: cannot read page 2 of inode 65, error -22
Jul 26 16:51:58 kernel: UBIFS (ubi1:0): un-mount UBI device 1
Jul 26 16:51:58 kernel: ubi1: detaching mtd10
Jul 26 16:51:58 kernel: ubi1: mtd10 is detached
Jul 26 16:51:58 kernel: ubi1: attaching mtd10
Jul 26 16:51:58 kernel: ubi1: scanning is finished
Jul 26 16:51:58 kernel: ubi1: attached mtd10 (name "misc1", size 8 MiB)
Jul 26 16:51:58 kernel: ubi1: PEB size: 131072 bytes (128 KiB), LEB size: 126976 bytes
Jul 26 16:51:58 kernel: ubi1: min./max. I/O unit sizes: 2048/2048, sub-page size 2048
Jul 26 16:51:58 kernel: ubi1: VID header offset: 2048 (aligned 2048), data offset: 4096
Jul 26 16:51:58 kernel: ubi1: good PEBs: 64, bad PEBs: 0, corrupted PEBs: 0
Jul 26 16:51:58 kernel: ubi1: user volume: 1, internal volumes: 1, max. volumes count: 128
Jul 26 16:51:58 kernel: ubi1: max/mean erase counter: 70/28, WL threshold: 4096, image sequence number: 1982616507
Jul 26 16:51:58 kernel: ubi1: available PEBs: 0, total reserved PEBs: 64, PEBs reserved for bad PEB handling: 4
Jul 26 16:51:58 kernel: ubi1: background thread "ubi_bgt1d" started, PID 27818
Jul 26 16:51:59 kernel: UBIFS (ubi1:0): UBIFS: mounted UBI device 1, volume 0, name "nvram", R/O mode
Jul 26 16:51:59 kernel: UBIFS (ubi1:0): LEB size: 126976 bytes (124 KiB), min./max. I/O unit sizes: 2048 bytes/2048 bytes
Jul 26 16:51:59 kernel: UBIFS (ubi1:0): FS size: 5840896 bytes (5 MiB, 46 LEBs), journal size 1396736 bytes (1 MiB, 11 LEBs)
Jul 26 16:51:59 kernel: UBIFS (ubi1:0): reserved for root: 0 bytes (0 KiB)
Jul 26 16:51:59 kernel: UBIFS (ubi1:0): media format: w4/r0 (latest is w4/r0), UUID 70AF44BE-3B19-4ECF-B11E-616114B3F8BB, small LPT model
Jul 26 16:51:59 kernel: bcm63xx_nand ff801800.nand: uncorrectable error at 0xc1d4c00
Jul 26 16:51:59 kernel: ubi1 warning: ubi_io_read: error -74 (ECC error) while reading 160 bytes from PEB 22:84184, read only 160 bytes, retry
Jul 26 16:51:59 kernel: bcm63xx_nand ff801800.nand: uncorrectable error at 0xc1d4c00
Jul 26 16:51:59 kernel: ubi1 warning: ubi_io_read: error -74 (ECC error) while reading 160 bytes from PEB 22:84184, read only 160 bytes, retry
Jul 26 16:51:59 kernel: bcm63xx_nand ff801800.nand: uncorrectable error at 0xc1d4c00
Jul 26 16:51:59 kernel: ubi1 warning: ubi_io_read: error -74 (ECC error) while reading 160 bytes from PEB 22:84184, read only 160 bytes, retry
Jul 26 16:51:59 kernel: bcm63xx_nand ff801800.nand: uncorrectable error at 0xc1d4c00
Jul 26 16:51:59 kernel: ubi1 error: ubi_io_read: error -74 (ECC error) while reading 160 bytes from PEB 22:84184, read 160 bytes
Jul 26 16:51:59 kernel: CPU: 1 PID: 27805 Comm: envrams Tainted: P           O    4.1.27 #2
Jul 26 16:51:59 kernel: Hardware name: Broadcom-v8A (DT)
Jul 26 16:51:59 kernel: Call trace:
Jul 26 16:51:59 kernel: [<ffffffc0000876d8>] dump_backtrace+0x0/0x150
Jul 26 16:51:59 kernel: [<ffffffc00008783c>] show_stack+0x14/0x20
Jul 26 16:51:59 kernel: [<ffffffc0004f99c8>] dump_stack+0x90/0xb0
Jul 26 16:51:59 kernel: [<ffffffc0003447bc>] ubi_io_read+0x16c/0x388
Jul 26 16:51:59 kernel: [<ffffffc000341e28>] ubi_eba_read_leb+0x138/0x440
Jul 26 16:51:59 kernel: [<ffffffc000341134>] ubi_leb_read+0x7c/0xe0
Jul 26 16:51:59 kernel: [<ffffffc000215a50>] ubifs_leb_read+0x38/0xb0
Jul 26 16:51:59 kernel: [<ffffffc0002176ac>] ubifs_read_node+0x9c/0x330
Jul 26 16:51:59 kernel: [<ffffffc0002179fc>] ubifs_read_node_wbuf+0xbc/0x358
Jul 26 16:51:59 kernel: [<ffffffc0002346fc>] ubifs_tnc_read_node+0x44/0x130
Jul 26 16:51:59 kernel: [<ffffffc00021b040>] ubifs_tnc_locate+0x1c8/0x1e0
Jul 26 16:51:59 kernel: [<ffffffc0002128fc>] ubifs_iget+0x8c/0x668
Jul 26 16:51:59 kernel: [<ffffffc00020fd80>] ubifs_lookup+0x108/0x1d8
Jul 26 16:51:59 kernel: [<ffffffc000146ddc>] lookup_real+0x24/0x68
Jul 26 16:51:59 kernel: [<ffffffc00014bc8c>] do_last.isra.13+0x78c/0xc20
Jul 26 16:51:59 kernel: [<ffffffc00014c1a4>] path_openat+0x84/0x5c0
Jul 26 16:51:59 kernel: [<ffffffc00014d7d8>] do_filp_open+0x30/0x98
Jul 26 16:51:59 kernel: [<ffffffc00013d158>] do_sys_open+0x140/0x228
Jul 26 16:51:59 kernel: [<ffffffc0001859ec>] compat_SyS_open+0x1c/0x28
Jul 26 16:51:59 kernel: bcm63xx_nand ff801800.nand: uncorrectable error at 0xc287c00
Jul 26 16:51:59 kernel: ubi1 warning: ubi_io_read: error -74 (ECC error) while reading 870 bytes from PEB 28:30072, read only 870 bytes, retry
Jul 26 16:52:00 kernel: bcm63xx_nand ff801800.nand: uncorrectable error at 0xc287c00
Jul 26 16:52:00 kernel: ubi1 warning: ubi_io_read: error -74 (ECC error) while reading 870 bytes from PEB 28:30072, read only 870 bytes, retry
Jul 26 16:52:00 kernel: bcm63xx_nand ff801800.nand: uncorrectable error at 0xc287c00
Jul 26 16:52:00 kernel: ubi1 warning: ubi_io_read: error -74 (ECC error) while reading 870 bytes from PEB 28:30072, read only 870 bytes, retry
Jul 26 16:52:00 kernel: bcm63xx_nand ff801800.nand: uncorrectable error at 0xc287c00
Jul 26 16:52:00 kernel: ubi1 error: ubi_io_read: error -74 (ECC error) while reading 870 bytes from PEB 28:30072, read 870 bytes
Jul 26 16:52:00 kernel: CPU: 1 PID: 27805 Comm: envrams Tainted: P           O    4.1.27 #2
Jul 26 16:52:00 kernel: Hardware name: Broadcom-v8A (DT)
...
Jul 26 16:52:00 kernel: UBIFS error (ubi1:0 pid 27805): read_block: bad data node (block 2, inode 65)
Jul 26 16:52:00 kernel:     magic          0x6101831
Jul 26 16:52:00 kernel:     crc            0xfa8eafea
Jul 26 16:52:00 kernel:     node_type      1 (data node)
Jul 26 16:52:00 kernel:     group_type     0 (no node group)
Jul 26 16:52:00 kernel:     sqnum          21061
Jul 26 16:52:00 kernel:     len            1232
Jul 26 16:52:00 kernel:     key            (65, data, 2)
Jul 26 16:52:00 kernel:     size           4006
Jul 26 16:52:00 kernel:     compr_typ      2
Jul 26 16:52:00 kernel:     data size      1184
Jul 26 16:52:00 kernel:     data:
Jul 26 16:52:00 kernel:     00000000: dd 55 c9 6e 22 49 10 e5 53 e6 03 b0 27 33 72 2d a4 3a 18 83 6f a3 91 2c b7 a6 6f 28 57 84 6c 0c
ECC errrors in your flash. This typically indicate a failing flash chip, so it`s a hardware issue.
 
Or maybe you've just corrupted it by your errant procedures. I've seen brand new flash drives irretrievably corrupted when mishandled too. And nothing I try will typically save it. I just throw it away and chalk it up to a lesson learned.
 
Thanks for quick reply. I suspected that a replacement would be necessary. Was hoping to wait a while longer and switch to a device with wifi7. Thanks.
 

Similar threads

Latest threads

Support SNBForums w/ Amazon

If you'd like to support SNBForums, just use this link and buy anything on Amazon. Thanks!

Sign Up For SNBForums Daily Digest

Get an update of what's new every day delivered to your mailbox. Sign up here!
Top