Release Asuswrt-Merlin 386.5 is now available

[itpp20]

Traffic monitor, is this a revert to a previous bug?

 

[Keenan]

Reboot the router, unmount usb if you have one then flash 386.5_1 again.

Is the data like traffic amounts retained when using that update method?

 

[octopus]

amtm > dc to try to fix the current problem.

Make sure your custom scripts shut themselves down during a reboot. Don't power off the router without unmounting the drive first.

Thanks
I can try it. will there be a lot of external scripts installed such as entware?

EDIT: I probably every time I have updated software not first unmounting my drive.

 

[Zastoff]

Is the data like traffic amounts retained when using that update method?

Not sure i understand what you mean?
If traffic amounts normally survive a reboot it should not be a problem.

 

[L&LD]

Yes, the flash was unsuccessful.

Safely remove any and all USB attached devices and try again. You may need to safely remove the USB devices and physically remove them too.

After safely removing them (via the GUI), do not reboot the router. It will mount the devices again.

 

[FLA_NL]

Dirty update from 386.5 to 386.5_1. I'm not noticing any issues.

 

[Diamond67]

Reboot the router, unmount usb if you have one then flash 386.5_1 again.

I had safely unmounted the usb devices (Eject all USB disks) from GUI as I normally do before flashing. But somehow this time it did not work.

Now I powered off the router, physically removed the usb flash drives, powered up again and flashed again.

After that everything seems to be OK.

I can see Firmware version: 386.5_1-g8858f16344 from Merlin GUI.

And when I log in via SSH, I get this:
ASUSWRT-Merlin RT-AC68U 386.5_1-g8858f16344 Tue Mar 22 02:30:42 UTC 2022

Problem solved.

 

[ColinTaylor]

Thanks
I can try it. will there be a lot of external scripts installed such as entware?

There are no external dependencies. After installing the Disk Check reboot the router (using the GUI button) and it will check the drive when it boots up.

But the main thing is to stop the drive becoming corrupted in the first place so that it doesn't need to be repaired.

 

[Tech9]

Traffic monitor, is this a revert to a previous bug?

Asuswrt bug.

 

[Wisiwyg]

Quick update... Issues with installing the 386.5_1... Upgraded my main AX88U, Mesh Node AC86U and Mesh Node AC68U. I lost my AC86U node after everything settled, couldn't get it to rejoin no matter what. Ended up factory reset AX88U and manual setup. Still couldn't add on AC86U Node, and lost the AC68U node. Fixed the AC86U node by flashing back to the latest Asus release, added as node immediately. Will be trying that with the AC68U over the weekend.

Now running 386.5_1 on main AX88U, OE Asus on AC86U node. All coming from Merlin 386.5 release.

 

[JohnD5000]

Quick update here, too. Dirty flash GT-AC2900. 386.5 -> 386.51. Everything seemed fine, but I have 3 Aimesh nodes (all nodes on the latest stock). 1 node online (AC86U) and 2 offline (2 AC68U) that I just have as backups (from upgrades). The AC86U node (that was online) was no longer connecting after flashing to 386.51. I had to reinitialize it. So, I checked the 2 AC68U nodes that were offline, and they connected when powered on--no reinitializing needed.

 

[noobertoober]

It's a bug in the original Asus web code, which only occurs on the RT-AC68U with Flow Accelerator support set to "Normal" (not all RT-AC68U revisions support it, that's why it only happens in a few rare cases).

As a temporary workaround you could temporarily disable ctf_fa_mode, enable QoS, then re-enable ctf_fa_mode.

Disable it:

nvram set ctf_fa_mode = 0

Re-enable it:

nvram set ctf_fa_mode = 2
nvram commit

It will be fixed for 386.5_2.

Thanks, this worked well. I don't really need FA, (I'm on 25/2 DSL on a good day), but couldn't figure out a way to disable FA only through the GUI. I used the commands above though and things are working (though I did need to remove spaces before and after the '=' sign.

 

[PR3MIUM]

Anyone know whats this issue:

Mar 24 06:30:15 kernel: CFG80211-ERROR) wl_cfg80211_hostapd_sec : No WPSIE in beacon
Mar 24 06:30:15 kernel: CFG80211-ERROR) wl_cfg80211_hostapd_sec : No WPSIE in beacon

All running stable overnight this was the only error so far in my logs.

 

[Snoopotic]

I don‘t know if it‘s an issue in 386.5 or earlier but using ipSEC i cannot access my private net (and thus also nit the wrt wen gui) I only can use my remot public Ip.

 

[node]

Smooth like silk, dirty upgrade on both my RT-AC5300 & RT-AC68U.

 

[octopus]

amtm > dc to try to fix the current problem.

Make sure your custom scripts shut themselves down during a reboot. Don't power off the router without unmounting the drive first.

I have just run this and get this output:

    ---------------------------------------------------

    amtm-disk-check.log has this content:


    START FILE, --- lines are not part of file

    ---------------------------------------------------


    Thu Mar 24 23:22:20 CET 2022 Probing 'ext4' on device /dev/sda1

    Running disk check v3.0, with command 'e2fsck -p' on /dev/sda1

    rt-ax86: recovering journal

    rt-ax86: Superblock needs_recovery flag is clear, but journal has data.

    rt-ax86: Run journal anyway


    rt-ax86: UNEXPECTED INCONSISTENCY; RUN fsck MANUALLY.

         (i.e., without -a or -p options)

    Thu Mar 24 23:22:20 CET 2022 Disk check done on /dev/sda1

    ---------------------------------------------------

    END FILE

 

[ColinTaylor]

I have just run this and get this output:

    ---------------------------------------------------

    amtm-disk-check.log has this content:


    START FILE, --- lines are not part of file

    ---------------------------------------------------


    Thu Mar 24 23:22:20 CET 2022 Probing 'ext4' on device /dev/sda1

    Running disk check v3.0, with command 'e2fsck -p' on /dev/sda1

    rt-ax86: recovering journal

    rt-ax86: Superblock needs_recovery flag is clear, but journal has data.

    rt-ax86: Run journal anyway


    rt-ax86: UNEXPECTED INCONSISTENCY; RUN fsck MANUALLY.

         (i.e., without -a or -p options)

    Thu Mar 24 23:22:20 CET 2022 Disk check done on /dev/sda1

    ---------------------------------------------------

    END FILE

OK. So I would do as it says. Unmount the device using the GUI (if it has been mounted). Then SSH into the router and verify that the device is indeed unmounted (df -h). And then run the e2fsck command on the device with the error:

e2fsck /dev/sda1

Once that's repaired the filesystem reboot the router and check the log again.

service reboot

But if this keeps happening you need to identify the cause of the corruption.

 

[octopus]

OK. So I would do as it says. Unmount the device using the GUI (if it has been mounted). Then SSH into the router and verify that the device is indeed unmounted (df -h). And then run the e2fsck command on the device with the error:

e2fsck /dev/sda1

Once that's repaired the filesystem reboot the router and check the log again.

service reboot

But if this keeps happening you need to identify the cause of the corruption.

I get this output.

octopus@RT-AX86U-EA08:/tmp/home/root# df -h
Filesystem                Size      Used Available Use% Mounted on
ubi:rootfs_ubifs         77.7M     73.8M      3.9M  95% /
devtmpfs                456.0M         0    456.0M   0% /dev
tmpfs                   456.1M    792.0K    455.3M   0% /var
tmpfs                   456.1M      1.2M    454.9M   0% /tmp/mnt
ubi1:data                 4.5M     72.0K      4.1M   2% /data
tmpfs                   456.1M      1.2M    454.9M   0% /tmp/mnt
tmpfs                   456.1M      1.2M    454.9M   0% /tmp
/dev/mtdblock9           47.0M      4.4M     42.6M   9% /jffs
octopus@RT-AX86U-EA08:/tmp/home/root# e2fsck /dev/sda1
e2fsck 1.45.6 (20-Mar-2020)
rt-ax86: recovering journal
Superblock needs_recovery flag is clear, but journal has data.
Run journal anyway<y>? yes
e2fsck: unable to set superblock flags on rt-ax86

rt-ax86: ********** WARNING: Filesystem still has errors **********

 

[ColinTaylor]

e2fsck: unable to set superblock flags on rt-ax86

This message would typically indicate that your USB device is faulty and has gone into read-only mode.

If you unplug the device, wait few seconds and plug it back in, what scsi/sd/usb messages do you get in the router's System Log - General Log?

 

[octopus]

This message would typically indicate that your USB device is faulty and has gone into read-only mode.

If you unplug the device, wait few seconds and plug it back in, what scsi/sd/usb messages do you get in the router's System Log - General Log?

I get this:

https://pastebin.com/qQ4s0rXC