RT-AX58U crashing on 386.2 beta 1

  • ATTENTION! As of November 1, 2020, you are not able to reply to threads 6 months after the thread is opened if there are more than 500 posts in the thread.
    Threads will not be locked, so posts may still be edited by their authors.
    Just start a new thread on the topic to post if you get an error message when trying to reply to a thread.

JWoo

Senior Member
For those not following the saga of the RT-AX58U.... I sent mine back to Asus as an RMA about 6 weeks ago, Asus declared it was not repairable (NAND) and sent me a fully tested refurb RT-AX58U. It ran fine for about 7 days. The 8th day didn't go as well as I encountered the first crash with the refurb. I have had a ton of different routers over the last couple decades running mostly AsusWRT, Tomato, OpenWRT, DD-WRT, XWRT and Asus Merlin. I have never seen a router crash as much as these RT-AX58U routers do. @RMerlin any insight you might have on this would be appreciated. Crash log attached.

I have plenty of free RAM, NVRAM and JFFS space. But it does seem like rootfs is pretty heavily used.

[email protected]:/tmp/home/root# df
Filesystem 1K-blocks Used Available Use% Mounted on
ubi:rootfs_ubifs 80164 70616 9548 88% /
devtmpfs 256028 0 256028 0% /dev
tmpfs 256132 224 255908 0% /var
tmpfs 256132 572 255560 0% /tmp/mnt
ubi1:data 4584 72 4244 2% /data
tmpfs 256132 572 255560 0% /tmp/mnt
tmpfs 256132 572 255560 0% /tmp
/dev/mtdblock9 48128 2240 45888 5% /jffs


[email protected]:/tmp/home/root# cat /proc/mtd
dev: size erasesize name
mtd0: 05f00000 00020000 "rootfs"
mtd1: 05f00000 00020000 "rootfs_update"
mtd2: 00800000 00020000 "data"
mtd3: 00100000 00020000 "nvram"
mtd4: 05f00000 00020000 "image"
mtd5: 05f00000 00020000 "image_update"
mtd6: 10000000 00020000 "dummy1"
mtd7: 10000000 00020000 "dummy2"
mtd8: 00100000 00020000 "misc3"
mtd9: 02f00000 00020000 "misc2"
mtd10: 00800000 00020000 "misc1"
mtd11: 056b4000 0001f000 "rootfs_ubifs"
mtd12: 0001f000 0001f000 "METADATA"
mtd13: 0001f000 0001f000 "METADATACOPY"
mtd14: 002aea44 0001f000 "filestruct_full.bin"
mtd15: 006c8000 0001f000 "data"
 

Attachments

  • crashlog03212021_crash.txt
    48.2 KB · Views: 63

warpc0re

New Around Here
Have you tried rolling back to 384.19? I experienced crashes like this every few days on the 386.x releases from stock asus + merlin on my RT-AX3000’s. The last stable release (for me) that doesn’t exhibit this issue is 384.19.
 

alex1236hk

Regular Contributor
Have you tried rolling back to 384.19? I experienced crashes like this every few days on the 386.x releases from stock asus + merlin on my RT-AX3000’s. The last stable release (for me) that doesn’t exhibit this issue is 384.19.
I am kinda reverse,
having AC86U, keep crashing on 384.19, but stable since 386.1.
But I do multiple hard reset after upgraded to 386.1.
 

warpc0re

New Around Here
I am kinda reverse,
having AC86U, keep crashing on 384.19, but stable since 386.1.
But I do multiple hard reset after upgraded to 386.1.

The AC86U is a different model completely.

The AX58U and AX3000 are pretty much the same. I think the difference is basically the retailer you purchased it from. The AX58U is exclusive to Best Buy, and the AX3000 is what you get at every other retailer.
 

cptnoblivious

Regular Contributor
The AC86U is a different model completely.

The AX58U and AX3000 are pretty much the same. I think the difference is basically the retailer you purchased it from. The AX58U is exclusive to Best Buy, and the AX3000 is what you get at every other retailer.
That's not correct correct where I live, the AX58U is not exclusive to Best Buy. FYI :)
 

Sign Up For SNBForums Daily Digest

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