Is the data like traffic amounts retained when using that update method?Reboot the router, unmount usb if you have one then flash 386.5_1 again.
Thanksamtm
>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.
Not sure i understand what you mean?Is the data like traffic amounts retained when using that update method?
Reboot the router, unmount usb if you have one then flash 386.5_1 again.
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.Thanks
I can try it. will there be a lot of external scripts installed such as entware?
Traffic monitor, is this a revert to a previous bug?
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.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:
Code:nvram set ctf_fa_mode = 0
Re-enable it:
Code:nvram set ctf_fa_mode = 2 nvram commit
It will be fixed for 386.5_2.
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
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.
---------------------------------------------------
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 (I have just run this and get this output:
Code:--------------------------------------------------- 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
df -h
). And then run the e2fsck
command on the device with the error:e2fsck /dev/sda1
service reboot
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 thee2fsck
command on the device with the error:
Once that's repaired the filesystem reboot the router and check the log again.Code:e2fsck /dev/sda1
Code:service reboot
But if this keeps happening you need to identify the cause of the corruption.
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 **********
This message would typically indicate that your USB device is faulty and has gone into read-only mode.Code:e2fsck: unable to set superblock flags on rt-ax86
I get this: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?
https://pastebin.com/qQ4s0rXC
Welcome To SNBForums
SNBForums is a community for anyone who wants to learn about or discuss the latest in wireless routers, network storage and the ins and outs of building and maintaining a small network.
If you'd like to post a question, simply register and have at it!
While you're at it, please check out SmallNetBuilder for product reviews and our famous Router Charts, Ranker and plenty more!